This Reference section provides information about initialization parameters, operator commands, utilities and control statements, and many other reference topics.
Referencesection provides information about initialization parameters, operator commands, utilities and control statements, and other reference topics.
Also see the information about the following topics on this page:
SMF Record Layouts
The Type 6 External Writer SMF record is optional and is created if the startup parameter SMF= is set to YES.
Note:The z/OS Type 6 record format definition can be found in the assembler language macro SYS1.MACLIB(IFASMFR).
The Type 30 Common Address Space Work (generally used for accounting) is optional and can be created by the operating system and can be processed by CA Deliver to determine job termination.
- CA-Deliver uses these records if the startup parameter SMF30= is set to YES.
- If you specify NO, type 5 SMF records must be produced by your operating system for CA Deliver to determine job termination.
In a Cross Memory Services (XMS) session, SMF records can also be created. The creation and record type number is controlled by the XMS startup parameter SMFSESS=. The record format definition can be found in the assembler language macro CAI.CVDEMAC(EBCSMFU1).
Obtaining Print Attributes
When the OUTPUT=YES initialization parameter is used, CA Deliver extracts print attributes from //OUTPUT statements and dynamically creates //OUTPUT statements as necessary to produce reports. The same rules used by the operating system for overrides are followed.
CA Deliver obtains print attributes for a report from the internal representation of the DD and OUTPUT JCL statements (from the JFCB, SIOT, and SWB control blocks).
If a SYSOUT DD statement references more than one //OUTPUT statement, CA Deliver uses only the first statement to obtain print attributes. Other statements are ignored.
Print attributes for the following //OUTPUT parameters are obtained:
FORMAT JES3 Control Statement
The //*FORMAT JES3 control statement is not directly supported by CA Deliver because the parameters on the statement are kept on the JES3 spool volume and are not available to CA Deliver.
- Although CA Deliver does not use the //*FORMAT control statement, JES3 can still apply the statement to a report DD statement that is dynamically allocated.
- Any //*FORMAT statement (that is, the //*FORMAT statement contains DDNAME=) is applied; however, only those parameters not specified by CA Deliver to allocate the DD statement dynamically are used.It is unlikely, however, that any specific //*FORMAT statement (that is, the //*FORMAT statement contains DDNAME=ddname) is applied since the DDNAME of the dynamically allocated DD statement is generated by the operating system.