Dump
v
Switch auxiliary trace user spaces using the EXEC CICS SET TRACEDEST command. The EXEC CICS SET TRACEDEST command is also used to set auxiliary trace on and off.
Trace entry points
There are two types of trace entry produced during CICS operations: system trace entry points and user trace entry points.
System trace entry points
These are points within CICS at which trace control requests are made. The most important system trace entry points for application programmers are for the EXEC interface program. These produce entries in the trace table whenever a CICS command is processed.
Two trace entries are made: the first when the command is issued, and the second when CICS has performed the required function and is about to return control to your application program. Between them, these two trace entries allow you to trace the flow of control through an application, and to check which exception conditions, if any, occurred during its execution.
User trace entry points
These are additional points within your application program that you can include in the trace table to allow complete program debugging. For example, you could specify an entry for a program loop containing a counter value showing the number of times that the loop had been entered.
A trace entry is produced wherever the EXEC CICS ENTER TRACENUM command is run. Each trace entry request, which can be given a unique identifier, causes data to be placed in the trace table.
CICS/400 provides a diagnostic dump facility that takes advantage of dump facilities provided within OS/400. Dump output is directed to a DPFHDMP spool file. CICS/400 sets the user data (USRDTA) attribute of the spool file to indicate the CICS abend code that caused the dump.
Dump support is provided for: v
EXEC CICS DUMP command v
EXEC CICS ABEND command v
CEMT PERFORM SNAP command v
Internal dump requests; for example, an unhandled transaction abend
Transaction abends result in dump information only if the
Dump on abend
field of the PCT entry for the active transaction is set to *YES. When the dump is run for a program that has a PPT
Calling convention (PGMLNG)
parameter value of
*COBOL, CICS/400 provides a COBOL/400 formatted dump. In other circumstances, CICS/400 uses the DMPJOB CL command to dump the appropriate level of information.
Note:
Use of the DMPJOB CL command may be restricted at your installation.
112
CICS for iSeries Application Programming Guide V5
Part 3. Files and databases
Chapter 10. File control
. . . . . . . . . 115
Direct reading (using EXEC CICS READ) . . . 118
Direct reading by way of a path . . . . . 119
Deleting groups of records (generic delete) . . 123
Review of file control command options . . . . 124
KEYLENGTH option for remote files . . . . . 127
Relative byte address (RBA) and relative record
CICS locking of emulated VSAM records in
© Copyright IBM Corp. 1998, 2004
113
114
CICS for iSeries Application Programming Guide V5
