Loss of access to a job variable

The following table indicates how the system responds if it is not possible to access a job variable that is in use.

S i t u a t i o n
The job variable is in the catalog of a different processor, the connection to which has been interrupted. The catalog was entered in the MRSCAT of the home computer by means of: ADD-MASTER-CATALOG-ENTRY or via MODIFY-MASTER-CATALOG-ENTRY and the following operands:	The job variable is in a catalog which was exported by means of EXPORT-PUBSET. The following operands were specified:
DIALOG-WAIT= value BATCH-WAIT= value	TERMINATE-JOBS= NO	TERMINATE-JOBS = YES or additionally a FORCE-PUBSET-EXPORT
R e s p o n s e
The command (or also the macro) which wants to access the catalog waits the specified time, then execution is aborted with an error (spin-off).  A wait time with the value zero results in immediate abortion. Without error handling, this results in termination of the procedure or batch job. If error handling take place, the next catalog entry once again leads to the defined wait time.	A current job or the program can terminate the access	A current job is terminated immediately
Default: value=30 seconds                value=28800 seconds	The catalog is not available for jobs still being initiated (termination)

Table 11: System response to failure to access a job variable

Further information on the use of job variables in a multiprocessor network, along with possible situations precipitating a loss of access, can be found in the manual “HIPLEX MSCF” [8].