Job variables can be set for an XATMI application. They are linked to the application using the following link names:
XTPATH | Link to job variable containing the prefix for the names of the trace files. |
XTLCF | Link to job variable containing the file name of the Local Configuration File (LCF). |
XTPALCF | Link to job variable containing the search path for additional descriptions of typecast buffers. The system continues to search for all the important XATMI configurations (e.g. SVCU ...) in the Local Configuration File specified by XTLCF. The system searches for Local Configuration Files under all the IDs specified in the search path and the descriptions of the typecast buffers are collected internally from these files (in the event of two identical names, only the first buffer description takes effect). The search path is specified in the form userid1:userid2:.... |
XTCLTTR | Link to job variable containing the trace mode for the XATMI client application. |
E (Error): Activates the error trace | |
I (Interface): Activates the interface trace for the XATMI calls | |
F (Full): Activates the full XATMI trace and that UPIC trace |
Table 13: Job variables on BS2000 systems
If the software product JV is loaded as a subsystem, the job variables can be set as follows on BS2000 systems, for instance:
Create job variable:
CREATE-JV JV-NAME=FULLTR
Pass value to job variable:
MODIFY-JV JV[-CONTENTS]=FULLTR, SET-VALUE=‘F‘
Set task-specific job variable link:
SET-JV-LINK LINK-NAME=XTCLTTR, JV-NAME=FULLTR
Show task-specific job variable link:
SHOW-JV-LINK JV[-NAME]=FULLTR
Delete task-specific job variable link:
REMOVE-JV-LINK LINK-NAME=XTCLTTR
The job variables are task-specific on BS2000 systems. Different job variables can be assigned to a second application running under the same ID.