JCL Statements

You can use the JCL statements to perform batch jobs and to queue file transfers.

The Script interface JCL is identical to the Batch interface JCL with the following exceptions:
  • The program executed is OSIUC000 instead of OSIUB000.
  • The SYSTRACE DD statement is added.

Required JCL Statements

The following is a sample JCL that includes the required JCL statements: 
//OSIUC000 EXEC PGM=OSIUC000,PARM='SERVER=FUSION' 
//STEPLIB  DD DISP=SHR,DSN=FUSION.LOADLIB         	
//SYSPRINT DD SYSOUT=* 
//SYSTRACE DD SYSOUT=*                        
//SYSIN  DD *                       
//INCLUDE DD DSN=YOUR.INCLUDE.LIBRARY,DISP=SHR

The following table lists the required JCL statements:

Statement Description
EXEC PGM=OSIUC000,PARM='data' Defines the program that must be executed to run the Script interface.

The PARM field defines the name of the platform server started task. You can also use the PARM parameter to override any SYSIN parameters. For more information, see Appendix G. Overriding JCL SYSIN Parameters.

Note: The program name must be defined as OSIUC000.
STEPLIB Defines the library that contains the platform server load modules.
Note: You must include this statement in the JCL to identify the platform server load library. But it is not required if the platform server LOADLIB is located inside a LNKLST.
SYSPRINT Defines the output report file that records the parameters that are used for file transfers.

If the file is successfully queued, you can read the output report file and find out the transaction number assigned to the job.

SYSTRACE Defines the output file that provides information on the script records which have been executed. It provides a log of all script records that have been executed and return code information for file transfer requests.
SYSIN The input file that contains the script records and any PROCESS statements required.

Optional JCL Statements

The following table lists the optional JCL statements:

Statement Description
SYSSAY Defines the output file that provides information on the destination where all Script SAY commands are written If this DD statement is not defined, SAY data will be written to the SYSTRACE DD statement.
INCLUDE Defines the library that should be searched when an INCLUDE statement is encountered.
Note: This DD statement is required only when the INCLUDE statement is used. It can be left out in all other cases.