You can direct a program dump to a printer backup file for printing, to a disk file for later analysis and printing, or both. You can control the program dump destination through two dump options: TOPRINTER and TODISK. These options are available in ALGOL, FORTRAN77, and Pascal through program dump statements. Languages that provide access to task attributes can also assign these options by way of the OPTION task attribute. Additionally, these options can be assigned in a DS (Discontinue) or DUMP (Dump Memory) system command.
The TOPRINTER option directs program dumps to a printer backup file called the task file. For details about the task file, refer to Using the Task File later in this section.
The TODISK option directs program dumps to disk files and causes a brief summary of each dump to be written to the task file, unless the PDUMPONLY option is also set, in which case the brief summary option is suppressed. The contents of the program dump are determined by the other dump options, except for the BASE option. Whenever TODISK is set, the BASE option is treated as if it is also set.
The following are advantages to using the TODISK option instead of the TOPRINTER option:
-
The dump is performed more rapidly, and less printer output is produced at the time of the dump. This factor makes it convenient for you to set the dump options to dump all possible information. By setting all the dump options, you reduce the likelihood of having to try to reproduce the problem later to obtain more information.
-
The disk file stores dump information in a format that can be analyzed by the DUMPANALYZER utility. DUMPANALYZER also enables you to decide at analysis time what information to include in the report. You can even run DUMPANALYZER repeatedly to produce reports on different information from the same dump. Another benefit is that DUMPANALYZER provides a detailed analysis of the process information block (PIB).
You can also use DUMPANALYZER to produce a report similar to one created by the TOPRINTER option. Like TOPRINTER reports, DUMPANALYZER reports include the names of all the identifiers used by the process. (However, identifiers are included in the report only if all object code files used by the process are present when DUMPANALYZER is run.) For information about running the DUMPANALYZER utility, refer to the System Software Utilities Operations Reference Manual.
When the TODISK option is used, the default title for the resulting disk file has the following format:
(<usercode>)PDUMP/<process name>/<date>/<time>/<mix number>/<counter> ON <family>
The values of the various elements of this title are as follows:
|
Title Element |
Value |
|---|---|
|
<usercode> |
The value of the USERCODE task attribute of the process. |
|
<process name> |
The value of the NAME task attribute of the process, except that any usercode or family name is omitted. If the resulting process name is more than eight nodes long, then only the first eight nodes are included. |
|
<date> |
The current date, in the form YYMMDD. |
|
<time> |
The current time, in the form HHMMSS. |
|
<mix number> |
The value of the MIXNUMBER task attribute of the process. |
|
<counter> |
A number from 1 to 999 to generate a unique file title. If the title is unique without this node, the node is omitted. |
|
<family> |
|
The following is an example title:
(UC)PDUMP/OBJECT/TEST/PDUMP/961009/154444/09581 ON APACK
If you are running the process from CANDE, it will display the name of the final program, dump to disk. Only the final dump name is displayed even though the program may perform more than one.
Program Dump: (UC)PDUMP/OBJECT/TEST/PDUMP/961009/154444/09581 ON APACK
You can use file equations to specify a different file name or family name for a dump to disk. You can file-equate the FILENAME, FAMILYNAME, and TITLE file attributes. The file equations must specify PDUMP as the internal name of the file.
If you specify file equation for the PDUMP file, the name and location may change as follows:
-
If file equation changes the title of the PDUMP file, the specified title is used along with a numeric suffix that changes incrementally for each program dump taken by a task.
-
If file equation only alters the usercode prefix, family name, or both, then the standard naming rule applies. The file will be created under the specified usercode directory, and on the specified family.
For example, a WFL job can use the following statement to initiate a program and specify the title of any program dumps generated by the program. Note that the file equation has effect only if the TODISK option is specified, either in the OPTION task attribute or in the statement that invokes the program dump.
RUN OBJECT/JADCON;
FILE PDUMP(TITLE = JADCON/DUMP ON PACK);
OPTION = (FAULT, TODISK);If a program dump occurs, the system adds a suffix to the file-equated title. The suffix is an integer ranging from 000 to 1048575. The suffix is incremented by one for each program dump generated by the process. Thus, in the previous example, if OBJECT/JADCON runs under usercode BLAKE and generates three program dumps in a single run, the program dumps receive the following titles:
(BLAKE)JADCON/DUMP/000 ON PACK; (BLAKE)JADCON/DUMP/001 ON PACK; (BLAKE)JADCON/DUMP/002 ON PACK;
You can include a usercode in the PDUMP file equation, but only a privileged process can assign the program dump a usercode different from that of the process. If the process is nonprivileged, and PDUMP is equated to a different usercode, then a security violation results when a program dump occurs. The system deletes the program dump file rather than saving it under the requested usercode.
If neither the TODISK nor the TOPRINTER option is set, the operating system option PDTODISK determines whether the program dump is directed to a disk file or to the task file. If the PDTODISK option is set, program dumps are written by default to a disk file; otherwise, program dumps are directed by default to the task file. An operator can use the OP (Options) system command to set or reset the PDTODISK option.
If either the TODISK or TOPRINTER option is set for a process, the program dump is directed only to the destination specified by the option: a disk file for TODISK, or the task file for TOPRINTER. If both of these options are set, then two program dumps occur: the first is directed to disk and the second is directed to the task file.
If the TODISK and TOPRINTER options are both used, the two resulting dumps may differ slightly, because the act of directing a program dump to disk can cause some arrays used by the process to be made present or overlaid. The contents of the arrays are not affected, and both present and overlaid arrays are included in the dump. However, if you compare both of the dumps that were produced, you might see the same array indicated as present in one dump, and overlaid in the other dump.
