Selective dump processing requires additional information to generate a formatted dump, but it allows for complete or selective dump processing.
The name of the standard main dump file is
application-group-name*DUMPn(cycle)
where n is a number from 0 to 9 and cycle is the file cycle number.
Whenever a dump is initiated, it creates a new F-cycle for the dump file. Therefore, you can have more than one dump file on the system. Whenever you perform dump processing, therefore, be sure to note and specify correctly the F-cycle and dump name increment (n) of the dump file.
If more than one file is required for a dump, the additional files are named
application-group-name*DUMPnPmm(cycle)
where mm is a two-digit number of the dump file part, starting with 01. Note that the cycle number of these additional dump files may be different from the main dump file. See 4.1 for a runstream that finds the cycle numbers of the additional dump files.
Example
The following sample dump shows the standard application group. Line numbers in parentheses refer to the explanation that follows the example.
(1) @use udsdump,udssrc*dump0(25). (2) @use udsfunc,uds$$src*util$. (3) @use udsprint,userprint. (4) @cat,p udsprint.,f///10000 (5) @asg,a udsprint. (6) @add udsfunc.uds$diag (7) DAP 12R2 (8) INPUT
(9) WAIT FOR DAP TO RETURN CONTROL . . . .
. .
(Dump label displayed) .
. .
(10) ENTER YOUR DAP COMMANDS (11) !UDS$DCSD
.
. (any other routines to process) .
(12) END DAP
Processing UDS Dumps
Explanation
(1), (2), (3) Attaches required @USE names of UDSDUMP, UDSFUNC, and UDSPRINT to the dump file, the utility file, and an alternate print file. If there are multiple files associated with the dump, there are two cases:
• If the dump files have their original qualifiers, names and cycles, you only need an @USE command for the main dump file, as in (1).
• If the qualifiers, names, or cycles are different, you must do an @USE command for each file in the dump. The @USE command for the main dump file is like (1). Each additional dump file must also have an @USE command like the following:
@use udsdumppmm,dumpfilepartmm
where dumpfilepartmm is the name of the dump file that was originally named application-group-name*DUMPnPmm(cycle), and
mm is 01, 02, 03, and so on.
(4), (5) Catalogs and assigns your print file.
(6) Adds a runstream that executes DAP, loads the dump functions for DAP, and sets up an alternate file for the print formatted in DAP (UDSPRINT).
(8) After this line, a dump header appears on your screen. This dump header shows the dump file name, the run-id initiating the dump, the time the dump was produced, and the level of UDS Control producing the dump.
(9), (10) Message lines that appear before and after the dump label.
(11) Produces the formatted dump by entering various dump functions. The exclamation point (!) indicates that the formatted dump is produced in an alternate print file (UDSPRINT). To generate a formatted dump and display it on your screen, enter the dump functions without the exclamation points.
(13) Sends a paper copy of the formatted dump. This line is not required to generate a formatted dump and display it.
Processing UDS Dumps
4.3.
DAP Functions
UDS Control supplies a set of DAP functions adapted specifically for UDS, which you can use to print and analyze all or part of the dump file in various formats. Table 4–1 describes these DAP functions.
Table 4–1. DAP Functions Supplied by UDS
DAP Function Result
UDS$ALL Produces a formatted octal dump of all banks in the dump file. UDS$DCSD Produces a formatted octal dump of the UDS Control D-banks. UDS$DPBDI(bdi) Produces a formatted octal dump of the bank with the specified
bank descriptor index (BDI). Specify the BDI in octal (prefixed with a zero) or decimal.
UDS$LBL Produces a tabular display that identifies the dump, when it was produced, and so on. UDS$LBL executes automatically whenever you add UDSFUNC.UDS$DIAG. The element contains the
addstream that copies the dump file to a temporary file and executes DAP.
dumpfiles Produces runstreams for use with multifile dumps. It has one optional parameter, which has the following values:
0 List names of all raw dump files for the dump 1 Generate a runstream to delete all the raw dump files 2 Generate a runstream to copy the raw dump files to the tape
file with the name UDS$TAPE
For example, the following runstream saves the names of the raw dump files in the temporary SDF file OUT:
@asg,a appsvn*dump0(5) @use diag$.,appsvn*dump0(5) @asg,t out @dap *restore uds$$svn*util$. *alt /out !dumpfiles(0) @eof
Processing UDS Dumps
4.4.
Dump File Format
The dump file is formatted with a header similar to the format of a generic
postmortem dump (PMD) DIAG$ file. The rest of the dump file consists of copies of UDS Control structures that define the content of the rest of the file and the actual UDS bank contents. The following figure illustrates the format of the UDS Control postmortem dump file header. The line numbers are explained following the illustration.
Main Dump File Header Format
00 PMD$$$
01
Program file name 02
03 Mass storage address of absolute element
04 Type Level Version ASA
address 05 TDATE 06 Condition word 07 . . . . . . . nnn
UDS Control structures that define the content of the rest of the file
. . .
Content of UDS banks
. . .
Line Numbers
Word 0 A Fieldata sentinel verifying that the table is present. UDS-Control sets this word to Fieldata PMD$$$.
Words 1, 2 Internal file name of the program file that contains the absolute element. UDS-Control sets this word to Fieldata CSINTNAME$.
Word 3 Relative sector address of the program header table. UDS-Control sets uses this word to locate the structures in the file that define the format of the rest of the file.
Processing UDS Dumps
Word 4 Information relating to the last activity to terminate. UDS-Control stores the information about the activity that took the dump.
S1 Program type S2 Switching level
S3 Version of the PDM header. Version 1 supports multiple dump files.
H2 PCT relative address of the last activity to terminate (PCT is the program control table, which contains control information about each active run in the system and any program being executed within the run.)
Word 5 Time and date in TDATE format.
Word 6 Information about the condition of the program when the last activity terminated. UDS-Control actually stores the information about the condition of the program when the dump was executed.
T1 If zero, program terminated normally. S2 If set to E, last activity terminated in error. S2 If set to X, last activity aborted.
A dump can include the bank types in the following list. Cache banks (dedicated, small, and general page banks) are not in the dump if the application group specifies
NO-PAGE-BANKS in a dump. Refer to the Repository for ClearPath OS 2200
Programming Reference Manual for more information about the UREP DUMP-TYPE
attribute.
Non-application-level D-banks that are not associated with the dumping activity are never dumped. For example, activity-level RDMS scratch banks allocated to a thread that is not dumping are not dumped, because the dumping activity cannot access the non-application-level banks of other activities.
In the following list, an asterisk (*) indicates a bank associated with the activity that is dumping:
• PCT bank*
• UDS Control D-banks (DCSD and XDCSD)
• TCS D-banks
• FPTE banks
• Thread D-banks
• Page banks
• Dedicated page banks
• Schema D-banks
• Lock D-banks
Processing UDS Dumps
• Small page D-banks
• Encryption D-bank
• UDS Monitor (UMON) caller D-bank*
• Activity local stack (ALS) bank*
• RDMS physical file D-banks*
• RDMS logical file D-banks*
• RDMS scratch D-banks
Note: Some dump types do not dump all bank types.
4.5.
Dumping the ADT Bank
Whenever an error situation occurs that affects more than one application group, it is probably a problem with the ADT code. It is important to dump the contents of the ADT bank when this occurs. If you are running in an XTC environment, you must capture the ADT bank on all hosts.
Use the following commands to dump the ADT bank:
@use util$.,qualifier*UTIL$. @add,l util$.dump-adt/bank