MODULE

Defines the origin and length of a module that was loaded while the original target program was executing.

module-name

The name of the module that is to have its origin and length defined.

Note: Unless the module is qualified by the QUALIFY command, address expressions that refer to a dynamically loaded module must prefix any symbols with the module and CSECT wrapped in parentheses (see Address expressions).

CDE

z/OS® only.

Scan the Contents Dictionary Entries (CDEs) in the Job Pack Queue (list of modules loaded for the current job, the z/OS session) for an entry corresponding to module-name. If no suitable CDE was found, the search continues with a scan of the Link Pack Dictionary Entries (LPDEs) in the Link Pack Area (the list of pre-defined and resident modules).

If a matching CDE or LPDE is found, set up a module definition for module-name with appropriate module start address and length values.

NUCEXT

CMS Only.

Scan the CMS Nucleus Extension Subcommand control block chain and locate an entry for module-name.

If an entry is found, set up a module definition for module-name with appropriate module start address and length values.

TRANS

CMS Only.

Check the module-name MODULE file to make sure that it is a transient program (has only 1 record).

If module-name MODULE is a transient program, set up a module definition for module-name with a module start address of X'0E000' and a module length of X'FFF'.

The second argument is the module search type. It is not needed for z/VSE®.

The origin and length are taken from system control blocks.

This command lets you debug many modules at once.

The new module definition is needed before symbols are loaded for modules loaded by the original target.

Examples

MODULE IDF CDE
MODULE IDFMAIN NUCEXT