Loading programs (TSO)

How IDF loads your target program is dependent on whether the LIBE option is used or not.

If the LIBE option is NOT specified, then IDF uses the standard z/OS® load module search order. However after the load completes, IDF will attempt to read the module to determine the module map. This read will fail unless the module was loaded from a STEPLIB, TASKLIB or ISPLLIB (when in ISPF) data set.

If the LIBE option is specified, the next option token specifies the DD name of a pre-allocated DD concatenation to be used in loading the target. If the target is not in the specified concatenation of libraries the target is not loaded using the standard z/OS search order.

TASKLIBs and the SVC97 option

If the NOSVC97 option is specified, the TSO TEST SVC 97 support is not used for breakpoints.

In this case, IDF does not set up a TASKLIB, contrary to what is normally done when TSO/E CALL or TEST commands are used.

Programs that dynamically load other modules and programs that are link-edited as overlay programs may get z/OS System 106 ABENDs under IDF, unless the library in which the target program resides is in the STEPLIB, ISPLLIB, or other TASKLIB DD concatenation.

If MYPROG is a program that is normally invoked directly from the TSO/E READY prompt, you could debug it with the following IDF command:

     ASMIDF myprog /Parms for MYPROG

if myprog is loaded from a TASKLIB or STEPLIB.