Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Executing a DSP or Installation Exit Routine in a C/I FSS Address Space z/OS JES3 Customization SA32-1006-00 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
If your installation uses C/I functional subsystem (FSS) address spaces, any installation exit routine that executes during the converter, interpreter, and prescan phases of C/I processing must be able to execute in a C/I FSS address space environment. Any DSP you write that executes in a C/I FSS address space must also be compatible with the C/I FSS address space environment. The C/I FSS address space contains only a subset of the nucleus modules and services that are available in the JES3 address space. When writing an installation exit routine or DSP to execute in a C/I FSS address space, apply the same rules and procedures as those explained in section Programming Conventions for Writing DSPs and Installation Exits. However, be sure that the routine or DSP uses only those services that are available in a C/I FSS address space. The following installation exit routines can execute in a C/I FSS
address space:
&tab;IATUX03&tab;IATUX09 Table 1 shows which macros are available in a C/I address space.
The following other services are available in a C/I FSS address
space:
Each C/I FSS address space has its own trace table and storage queue (not shared by the JES3 address space) in private area virtual storage. For a complete list of all modules contained in the C/I FSS address space nucleus (IATNUCF), see z/OS JES3 Diagnosis Reference. Installation exits and DSPs executing in C/I FSS address spaces may update a job's spool files using JSAM or USAM. JSAM should be used when running under an FCT. USAM should be used when running under a subtask. To serialize access to the spool files, most of the job's control blocks are “locked” in the JES3 global address space before the job is sent to the C/I FSS address space. (Control blocks are locked by turning off the FDBCLOSE bit in the appropriate FDB in the job's RQ.) Routines in the C/I FSS address space can then update the job's spool files while routines in the JES3 global address space cannot. The only control block that is not “locked” is the job track allocation table (TAT). Job TAT updating for a DSP or installation exit routine executing in a C/I FSS address space must be done only from the JES3 global address space. To ensure proper spool space allocation, use the ATRACK macro, which sends the allocation request to the JES3 global address space. Failure to do so could cause duplicate track allocation and may force a cold start. |
Copyright IBM Corporation 1990, 2013
|