

Subprograms › Guidelines for Batch and Online Non-Ideal Subprograms › Batch Non-Ideal Subprograms
Batch Non-Ideal Subprograms
COBOL, PL/I, and Assembler subprograms that a CA Ideal application running in batch calls must follow these guidelines.
- z/OS-The load library where the subprogram is located must appear in one of the STEPLIB statements.
- COBOL-Specify the NOENDJOB compiler option.
- VSE-The name of the core image library where the subprogram is located must appear in one of the LIBDEF PHASE,SEARCH= statements.
The following are prohibited:
- Terminal I/O.
- Freeing, releasing, or modifying any resource that CA Ideal allocated.
- If the subprogram is called in the scope of an updated FOR construct, the non-Ideal subprogram cannot access the same set of CA Datacom/DB CBS, DB2, or VSAM records with update intent.
- Enqueuing or dequeuing on a CA Ideal internal system name. For more information about CA Ideal internal names, see the Problem Determination Guide.
- Any return other than a normal return. COBOL programs must use GOBACK. Assembler programs must branch to the address contained in R14 at entry. In VSE, you cannot use the EOJ macro.
- In z/OS-Any SPIE or (E) STAE macro
- In VSE-Any STXIT macro.
- Any scheduled abend
- Attempting to read the primary input file:
In z/OS, SYSIN
In VSE, SYSIPT
Copyright © 2015 CA Technologies.
All rights reserved.
 
|
|