|
Well, first some theory:
FTSIE$PP process is launching an FTSIE$OSP process under three
conditions:
o shortly after it is created (via START ASYNC)
o it gets mbx message from FTSIE$CMD when a user has entered an async
copy request
o every 5 minutes. (This mainly for restarting broken connections)
The created OSP itself looks in the Queue file FTSIE$FTRQ.DAT if ther's
any job (new or restart) to do. If not it dies silently.
An OSP also looks in the queue for new job if it's done with the old
job.
What does that mean:
Normally if a job gets entered from the user it shuld get started imme-
diatelly,
o if the FTSIE$PP is really running
o if the job gets to the front of the queue
o if ther are enough OSP allowed to run
o if the are enough VMS processes allowed to run
Jobs with broken links or remote system not reachable or crashed
OSP's or unable to create OSP are restarted same way as new jobs
(subject to above conditions).
You can immediately force the restart of those abandoned guys by
$FTSIE TERM ASY & $FTSIE START ASY.
For the future we consider to make the retry_interval and the
max_retry_count manageable for the system (=default) and the job.
regards, Andreas
|