INCLUDE statement

Specifies default values for substitution variables.

Syntax


Pseudo-JCL VARS syntax

Parameters

label
Is ignored, but must be present.
MEMBER
The external SCRIPT file to be included. Specify a valid member name from the PDS specified in the DD statement labled CCUPROC, or in the BUILD_SCRIPT_LIBRARY if specified by the client.

Example

The following example shows a pseudo-JCL file that uses the INCLUDE statement: 
//* Configuration variables
//INC INCLUDE MEMBER=CONFIG
//* *** rest of script
//

This expects a member named CONFIG in the build script library, to replace the INCLUDE statement. Following is an example of the contents of the CONFIG member.

//DEFAULTS VARS CGHLQ=USER,                      
//              ELA=ELA.V601,                    
//              COBCICS=CEE.SCEECICS,            
//              COBCOMP=COBOL.V3R3M0.SIGYCOMP,   
//              COBLIB=CEE.SCEELKED,             
//              DFHLOAD=CICS.TS53.CICS.SDFHLOAD, 
//              DFHLOAD1=CICS.TS53.CICS.SDFHEXCI,
//              DSNEXIT=DB2.V8R1M0.DSNEXIT,      
//              DSNLOAD=DB2.V8R1M0.DSNLOAD

Notes

  1. If a PDS for the scripts is specified using the BUILD_SCRIPT_LIBRARY by the client, then that PDS is first searched before the CCUPROC DD statement.
  2. The member name can be specified using variable substitution; for example, MEMBER=&MEM
  3. The included member is statically copied, replacing the INCLUDE statement, and then normal parsing is performed.
  4. An included member can contain other INCLUDE statements. However, the nesting level cannot exceed 5.
  5. An INCLUDE statement must follow a complete pseudo-JCL statement, and the included member must contain complete pseudo-JCL statements. That means a statement cannot be split across scripts.