JCL requirements

Edit online

Because IDF runs from JCL, you need to specify any files that your program needs in that JCL. You need to allocate optional IDF files, such as REXX customization macros and IDF Language extract files. Even though IDF is started as a batch job, it needs a terminal (defined by its VTAM® logical unit (LU) name) to run. This terminal is specified through the LUTERM option in the PARM value of the // EXEC ASMIDF statement. The LUTERM is the name used by VTAM to define the LU to the network, and is used by IDF to address the terminal.

JCL example:

// SETPFIX LIMIT=24K
// LIBDEF PHASE,SEARCH=(my.library,HLASM.LIBRARY)
// LIBDEF PROC,SEARCH=(MY.PROCLIB,HLASM.LIBRARY)
// EXEC ASMIDF,PARM='MYPROG (LU MYterm /phase-parameters'
/*

The following JCL statements are required:

SETPFIX LIMIT: Sets the page fix limit. IDF needs this set to 24K to allow the product exit to function correctly.
LIBDEF PHASE: Defines the library which contains the phase map created by ASMLKEDT and the target phase.
LIBDEF PROC: Defines the procedure library which contains any REXX procedures that might be used.
EXEC ASMIDF: Executes the program ASMIDF (IDF) using the parameters specified with the PARM option.