JDUMP (Job Dump Request) Macro

The dump can contain one of the following:

• The contents of either the entire supervisor area and the used part of the system GETVIS area, or of some supervisor control blocks only. The dump includes the contents of some supervisor control blocks only if either:
  • The STDOPT job control command specifies DUMP=PART or DUMP=NO, or
  • the job is submitted with PARTDUMP or NODUMP specified in a job control OPTION statement.
• The contents of the partition that issued the macro.
• The contents of the registers.

In addition, the macro causes the job to be terminated if JDUMP was issued by the main (or only) task of the program. If JDUMP was issued by a subtask, the macro causes that subtask to be detached without terminating the program in the partition.

If the job control option SYSDUMP is active, the output of the dump is directed to the dump sublibrary of the partition. If the option NOSYSDUMP is active, the output is directed to SYSLST, which can be assigned to a printer, disk or tape unit.

If SYSLST is assigned to tape, this tape must be positioned as wanted.

If SYSLST is assigned to an IBM® 3211 and indexing was used before you issue the JDUMP macro, a certain number of characters on every line of the printed dump might be lost. To avoid this, reload the printer's FCB (forms control buffer) by issuing an LFCB macro before you issue the JDUMP macro. The FCB image you load must not have an indexing byte.

If JDUMP is issued by a job running in real mode, the storage contents of the partition are dumped only up to the limit as determined by the SIZE operand of the EXEC job control statement, plus the storage obtained dynamically through the GETVIS macro. If SIZE was not specified, the entire partition is dumped.

If JDUMP is issued by a program running in virtual mode, the entire partition is dumped.