Passing parameters to EQANMDBG or EQAN0DBG using only the EQANMDBG DD statement

If the user parameter string that you are passing to your program is too long to add the necessary z/OS® Debugger parameters to the PARM string, you can leave the PARM string unchanged and pass all required parameters to z/OS Debugger by using the EQANMDBG DD statement.

When you add an EQANMDBG DD statement to your JCL, or allocate the EQANMDBG or EQAN0DBG file in your TSO session, it can point to a data set with any RECFM (F, V, or U) and any LRECL. The data set must contain one or more lines. If it contains more than one line, all trailing blanks are removed from each line. However, each line is assumed to start in column 1 with any leading blanks considered to be part of the parameter data. If a sequence number is found in a line, it is ignored.

The following table compares original JCL and modified JCL:

//STEP1 EXEC PGM=MYPROG,PARM='ABC,X(12)'
 ...
//

//STEP1 EXEC PGM=EQANMDBG,
// PARM='ABC,X(12)'
//EQANMDBG DD *
MYPROG,
TEST(ALL,INSPIN,,MFI:*),
NATLANG(ENU)
/*
 ...
//

//DLIBATCH EXEC PGM=DFSRRC00,
// PARM=(DLI,MYPROG,MYPSB)

//DLIBATCH EXEC PGM=DFSRRC00,
// PARM=(DLI,EQAN0DBG,MYPSB)
//EQANMDBG DD  *
MYPROG,TEST(ALL,INSPIN,,MFI:*)