Transporting Applications in Object Form › Object Transport Utility (IDUTOTRN) › Sample JCL and EXEC Statements

Sample JCL and EXEC Statements

This section shows sample execution JCL and EXEC statements needed for each run of IDUTOTRN.

Since IDUTOTRN uses the Datadictionary, the Datadictionary must be up. STEPLIB/LIBDEF must contain the necessary load libraries for the Datadictionary and CA Datacom/DB interface modules and the DD URT, DBURT002.

The JCL must also specify the VLS file for each program object, panel library, and plan source library. You might need to specify multiple libraries if programs or panels are on more than one system. The DD/DLBL names must be the same as those specified in their respective system definition fill‑ins in CA Ideal.

z/OS

The following sample JCL for z/OS requires control statements described previously. All object and panel libraries must be in the IDSYSFT.

// JOB
// EXEC IDLOTRN
//SYSPRINT DD SYSOUT=A
//PGMOBJ DD DSN=... system pgm object library
//PNLLIB DD DSN=... system panel library
//XPRT DD DSN=XPRT,UNIT=TAPE,...
//SYSIN DD *
control statements

VSE

The following sample JCL for VSE requires control statements described previously. All object and panel libraries must be defined in the IDLPROC JCL procedure and in the IDSYSFT.

* $$ JOB JNM=name
* $$ LST DISP=D,CLASS=L
// JOB
// LIBDEF PHASE,SEARCH=(CAI.IDEAL22)
// OPTION LOG,NODUMP
// EXEC PROC=IDLPROC
*
// PAUSE PLEASE MOUNT TAPE volser ON 180
// TLBL xprt,'IDEAL.XPRT.TAPE',,volser
// ASSGN SYS107,180
*
// EXEC IDUTOTRN,SIZE=AUTO
control statements
/*
// EXEC LISTLOG
/*
/&
* $$ EOJ

'xprt' is the label assembled in your batch file table for the tape file used for importing/exporting programs and SYS107 is the DEVADDR parameter specified for same.