Tracing options include the sizes of the system and adjunct trace tables, and whether trace information is saved or not. You can specify these options using SYSGEN syntax, DCMT commands, and SYSIDMS parameters.
Note: Options specified through SYSIDMS parameters generally override those specified on the SYSGEN statement. Options specified through DCMT commands dynamically change the attributes currently in effect for a CV.
To support trace options, the SYSGEN SYSTEM statement has been enhanced in the following ways:
The following diagram shows the syntax updates to the SYSGEN SYSTEM statement:
►►─┬──────────┬─── SYStem dc/ucf-version-number ─────── … ──────────────────────► ├─ ADD ────┤ ├─ MODify ─┤ └─ DELete ─┘ ►─┬────────────────────────┬───────────────────────────────────────────────────► └─ SNAp TASk is ─┬─ ON ◄─┤ └─ OFF ─┘ ►─┬───────────────────────────────────────────────────────────────────┬────────► └─ SNAp TASk TRAce is ─┬─ ON ◄──┬─ LIMit is ─┬─ 1000 ◄──────────────┤ ├─ OFF ──┤ ├─ <snap-trace-limit> ─┤ └─ TASk ─┘ └─ OFF ────────────────┘ ►─┬──────────────────────┬──────────────────────────────────────────────► └─ SYSTrace ──┬─ ON ───┤ └─ OFF ◄─┘ ►─┬───────────────────────────────────────────────────────────────────┬─► │ ┌───────────────────────────────────────────────────────┐ │ └─ TRAce ─▼─┬─ TABle SIZe is table-size ─┬─ KB ─┬─────────────┬───┴─┘ │ └─ MB ─┘ │ ├─ ADJunct table SIZe is adjunct-size ─┬─ KB ─┬───┤ │ └─ MB ─┘ │ └─ SAVe ─┬─ ON ────┬──────────────────────────────┘ └─ OFF ◄──┘
This section describes the new parameters for the SYSGEN SYSTEM statement:
Specifies whether to write a task snap dump to the DC/UCF log file. A task snap dump writes a formatted display of the resources allocated to the task being snapped.
Enables the writing of a task snap dump
Disables the writing of a task snap dump.
Controls the inclusion of trace information in task snaps.
Includes formatted trace information for all tasks in a task snap.
Includes no trace information in a task snap.
Includes only trace information for the task for which the snap is being issued.
Default: ON
Limits the number of trace entries reported in a task snap.
Specifies the maximum number of trace entries that are reported in a task snap.
Limit: 0–32767
Default: 1000
Note: A value of 0 is the same as specifying OFF.
Indicates that there is no limit to the number of trace entries included in a task snap.
Enables or disables basic system tracing.
Enables basic system tracing.
Disables basic system tracing.
Default: OFF
Specifies system trace options.
Specifies the size of the system trace table in kilobytes (KB) or megabytes (MB).
Limit: 0–9999
Default: 4 MB
Note: Two copies of the system trace table are allocated on all z/OS systems.
Specifies the size of the adjunct trace table in kilobytes (KB) or megabytes (MB).
Limit: 0–9999
Default: 0
Controls whether trace information is saved for future reporting.
Enables saving of trace information.
Disables saving of trace information.
Default: OFF
To support trace options, some of the DCMT commands have been enhanced in the following ways:
Note: The DCMT DISPLAY DBTRACE and DCMT VARY DBTRACE commands are no longer supported. Those commands have been replaced by the DCMT DISPLAY TRACE and DCMT VARY TRACE commands, respectively.
The DCMT VARY TRACE command alters the tracing options currently in effect for your system.
The following diagram shows the syntax for the DCMT VARY TRACE command:
►►─ DCMT ─┬───────────────────┬───────────────────────────────────────►
└─ broadcast-parms ─┘
►── Vary TRACe ─┬─ TABle SIZe table-size ─┬─ KB ─┬────────────────┬──►◄
│ └─ MB ─┘ │
├─ ADJunct table SIZe is adjunct-size ─┬─ KB ─┬───┤
│ └─ MB ─┘ │
└─ SAVe ─┬─ ON ─┬───────┬─────┬───────────────────┘
│ └─ ALL ─┘ │
└─ OFF ──────────────┘
This section describes the parameters for the DCMT VARY TRACE command:
Specifies the size of the system trace table in kilobytes (KB) or megabytes (MB).
Limits: 0–9999.
Specifies the size of the adjunct trace table in kilobytes (KB) or megabytes (MB).
Limits: 0–9999.
Controls whether trace information is saved for future reporting.
Saves trace information.
Note: If an adjunct trace table has been allocated, only its contents are saved; otherwise, the contents of the system trace table are saved.
Trace information is written to the trace area if one is defined in the runtime DMCL; otherwise, it is written to the log area if one is defined. If the DMCL contains neither area, no trace information is saved.
Saves both the current and future contents of the trace table. If ALL is not specified, only future entries are saved.
Specifies that trace information is not saved for future reporting.
The following example changes the size of the system trace table to 1 MB:
DCMT V TRACE TABLE SIZE 1 MB System tracing (SYSTRACE): ON Trace table size: 1 MB Address: 36605000 Adjunct table size: 0 KB Address: 00000000 Save: OFF Driver: INACTIVE Area: DDLDCTRC
The DCMT DISPLAY TRACE command displays the tracing options currently in effect for your system.
The following diagram shows the syntax for the DCMT DISPLAY TRACE command:
►►─ DCMT ─┬───────────────────┬─ Display TRACe ───────────────────────►◄ └─ broadcast-parms ─┘
This section describes the parameters for the DCMT DISPLAY TRACE statement:
Executes the DCMT command on all or a list of data sharing group members.
For more information about broadcasting and broadcast-parms syntax, see "How to Broadcast System Tasks" in the System Tasks and Operator Commands Guide.
The following example illustrates the output from a DCMT DISPLAY TRACE command when trace information is not being saved.
DCMT DISPLAY TRACE System tracing (SYSTRACE): ON Trace table size: 20 MB Address: 39A40000 Adjunct table size: 10 MB Address: 36603000 Save: OFF Driver: INACTIVE Area: DDLDCLOG
The following example illustrates the output from a DCMT DISPLAY TRACE command when trace information is being saved to a DDLDCTRC area.
DCMT DISPLAY TRACE System tracing (SYSTRACE): ON Trace table size: 4 KB Address: 39B65000 Adjunct table size: 8 MB (S) Address: 36603000 Save: ON Driver: ACTIVE Area: DDLDCTRC 0% FULL ------------Trace service driver statistics-------------- Driver started.................2009-12-08-12.23.21.151167 Number of save requests................................44 Number of times entries missed..........................2 Bytes/hour........................................1067733 Pages/hour............................................300 Number of reads........................................14 Number of writes........................................9 Number of read waits....................................1 Number of write waits...................................0 Number of page range resets.............................1 Number of area full waits...............................0 Number of errors........................................0 % of waits to I/Os......................................0 Number of RUs...........................................8 Number of look aheads...................................5 % of look aheads to RUs................................63
Potential values are as follows:
The size of the system trace table in kilobytes (KB) or megabytes (MB).
If the characters “(S)” follow table size, it indicates that the contents of the system trace table are being saved.
The address of the system trace table.
The size of the adjunct trace table in kilobytes (KB) or megabytes (MB).
If the characters “(S)” follow table size, it indicates that the contents of the adjunct trace table are being saved.
The address of the adjunct trace table.
Potential values are as follows:
Potential values are as follows:
Potential values are as follows:
The percentage of space used in the area.
A header for statistics that are displayed only if trace saving is enabled.
The date and time at which the trace service driver was started.
The date and time when the driver statistics were reset due to overflow.
The number of requests made to save trace information.
The number of times one or more trace entries were not saved because they had been overlaid before they could be written.
The rate at which trace information is being written, specified as bytes per hour.
The rate at which pages are written to the log or trace area, specified as pages per hour.
The number of pages read from the log or trace area.
The number of pages written to the log or trace area.
The number of times the driver had to wait for a read to complete.
The number of times the driver had to wait for a write to complete.
The number of times the driver had to recalculate the range of pages into which it can write information.
The number of times the driver had to wait for the contents of the log or trace area to be archived.
The number of I/O errors encountered.
The percent of waits to I/O requests.
The number of run units currently in use.
The number of look ahead reads in effect.
The percent of run units being used for look ahead reads.
Eliminating missed trace entries can be difficult; however, there are steps you can take to reduce the number of missed entries. In the trace information output, if the value for number of times entries missed is large compared to the value for number of save requests, consider taking one or more of the following actions:
The new TRACE and TRACE LIMIT parameters on the DCMT VARY SNAP command control the inclusion of trace information in task snaps.
The following syntax shows the enhancements to the DCMT VARY SNAP command:
►►─ DCMT ─┬───────────────────┬───────────────────────────────────────►
└─ broadcast-parms ─┘
►── Vary SNAP ─┬─ SYStem ─┬─ ON ──────┬──────────────────────────┬───►◄
│ ├─ OFF ─────┤ │
│ ├─ PHOto ───┤ │
│ └─ NOPHOto ─┘ │
│ │
└─ TASK ───┬─ ON ────────────────────────────────┬┘
├─ OFF ───────────────────────────────┤
├─ PHOto ─────────────────────────────┤
├─ NOPHOto ───────────────────────────┤
├─ TRAce ─┬─ ON ─────┬────────────────┤
│ ├─ OFF ────┤ │
│ └─ TASk ───┘ │
└─ TRAce LIMit ─┬─ snap-trace-limit ─┬┘
└─ OFF ──────────────┘
This section describes the new parameters for the DCMT VARY SNAP command:
Executes the DCMT command on all or a list of data sharing group members.
Note: For more information about broadcasting and broadcast-parms syntax, see How to Broadcast System Tasks in the System Tasks and Operator Commands Guide.
Applies the VARY SNAP command to system snaps.
Enables the writing of system snap dumps to the DC/UCF log file.
Disables the writing of system snap dumps to the DC/UCF log file.
Enables the writing of system snap photos to the DC/UCF log file.
Disables the writing of system snap photos to the DC/UCF log file.
Applies the VARY SNAP command to task snaps.
Enables the writing of task snap dumps to the DC/UCF log file.
Disables the writing of task snap dumps to the DC/UCF log file.
Enables the writing of task snap photos to the DC/UCF log file.
Disables the writing of task snap photos to the DC/UCF log file.
Controls the inclusion of system trace information in task snaps.
Includes system trace information for all tasks in a task snap.
Includes no system trace information in a task snap.
Includes only system trace information for the task for which the snap is being issued.
Limits the number of trace entries reported in a task snap.
Specifies the maximum number of trace entries that are reported in a task snap.
Limit: 0–32767
Note: A value of 0 (zero) is the same as specifying OFF.
Includes an unlimited number of trace entries in a task snap.
Note:
For more information about setting snaps at the system level, see documentation of the SYSTEM statement in the CA IDMS System Generation Guide.
The following example shows how to change the trace limit for task snaps to 500.
DCMT V SNAP TASK TRACE LIMIT 500 IDMS DC278011 V73 USER:*** TASK SNAP TRACE LIMIT SET
In Version 18.0, the DCMT VARY SYSTRACE command no longer supports an ENTRIES parameter. Use the DCMT VARY SNAP TASK TRACE LIMITS parameter to limit the number of trace entries in a task snap and use the DCMT VARY TRACE TABLE SIZE parameter to specify the size of the system trace table.
Note: A warning is issued if you specify the ENTRIES parameter.
The following diagram shows the syntax change to the DCMT VARY SYSTRACE command:
►►─ DCMT ─┬───────────────────┬──────────────────────────────────────► └─ broadcast-parms ─┘ ►── Vary SYSTrace ──┬─ ON ───┬──────────────────────────────────────►◄ └─ OFF ──┘
This section describes the new parameters for the DCMT VARY SYSTRACE command:
Executes the DCMT command on all or a list of data sharing group members.
For more information on broadcasting and broadcast-parms syntax, see the section "How to Broadcast System Tasks" in the System Tasks and Operator Commands Guide.
Enables standard system tracing.
Disables standard system tracing.
More Information
For more information about defining the system trace table, see the System Generation Guide.
The output of the DCMT DISPLAY LOG command has been enhanced to indicate when log statistics were last reset if they needed to be reset to avoid an overflow of the read count.
New SYSIDMS parameters have been added to support tracing enhancements:
New SYSIDMS parameters have been added to support tracing enhancements:
Specifies the size of the system trace table in kilobytes (KB) or megabytes (MB).
Limit: 0–9999
Default: 0
Note: If basic system tracing is enabled by the SYSIDMS SYSTRACE parameter and the table size is 0, the table size is changed to 4 MB.
Any non-zero table size established by a SYSIDMS parameter overrides the trace table size specified in the system definition.
Controls whether basic system tracing is enabled.
Enables basic system tracing.
Note: If basic system tracing is enabled by the SYSIDMS SYSTRACE parameter, it remains enabled for a system even if its system definition indicates that SYSTRACE is OFF.
Does not enable basic system tracing.
Specifies the size of the adjunct trace table in kilobytes (KB) or megabytes (MB).
Limit: 0–9999
Default: 0
Note: Any non-zero adjunct table size established by a SYSIDMS parameter overrides the adjunct trace table size specified in the system definition.
Starting with Version 18.0, the following enhancements facilitate the printing and archiving of trace information:
The format of trace entries in snap dumps has been enhanced to show additional information for system trace entries and to display extended trace entries, if they exist in the system trace table.
Entries now appear in newest to oldest order rather than oldest to newest as in prior releases. Each entry now includes the UTC time and date it was generated, the address of the primary LTE associated with the task, and the TOD clock value at the time it was generated.
012610 10.09.37 TRACE ENTRIES, ORDERED NEWEST TO OLDEST. TASKID/ TOD TIME/DATE SCA A(LTE) MOD MAC CALL R11/R2 R12/R3 R13/R4 R14/R5 R15/R6 R0/R7 R1/R8 TOD CLOCK 15.10.01.809756 00 12 9 240 1 000000C8 3836B0B8 36FAF750 B836B0CC 3836B0B8 371675B8 36FAF678 C5722F6CF3F5C00B 2010/01/26 00267D30 SNAP #GETSTK 00085009 00000000 383A6FF2 00085019 383C86B8 383A6EAC 383A68B8 15.10.01.809755 00 12 11 29 13 36FAF678 383A58B8 36FAF724 B83A6C8C 3836B0B8 371675B8 36FAF678 C5722F6CF3F5BC8B 2010/01/26 00267D30 WTL SNAPEP1 00085009 00000000 383A6FF2 00085019 383C86B8 383A6EAC 383A68B8 15.10.01.809754 00 12 10 27 32 36FAF764 38368404 36FAF798 B8368690 38375CB8 002674C8 36FAF764 C5722F6CF3F5A80B 2010/01/26 00267D30 MISC RMGREP1 36FAF764 37166988 B8376B28 37318CDC 00000000 37176780 B83685F4 15.10.01.809754 00 12 10 12 34 36FAF764 38368404 36FAF798 B8368708 38376888 383684A6 36FAF764 C5722F6CF3F5A58B 2010/01/26 00267D30 MISC RMGREP2 37167108 37318F3C 00000001 37318CDC 00027734 37176780 B83685F0 15.10.01.809754 00 12 10 240 29 00000000 38368404 36FAF768 B8368414 38368404 00000002 38366F3C C5722F6CF3F5A38B 2010/01/26 00267D30 MISC #GETSTK 37318B18 37318F3C 00000001 37318CDC 00000000 B836611A 37B49708 15.10.01.809754 00 12 10 62 5 00000000 B83660A6 36FAF754 B836613E 38368404 00000002 38366F3C C5722F6CF3F5A08B 2010/01/26 00267D30 MISC SNGLEP1 37318B18 37318F3C 00000001 37318CDC 00000000 B836611A 37B49708 15.10.01.809752 00 12 14 240 1 0000003C 383A3CB8 36FAF780 B83A3CCC 383A3CB8 00000008 00000040 C5722F6CF3F5808B 2010/01/26 00267D30 TIMP #GETSTK 37318B18 37318F3C 00000001 37318CDC 00000000 00000006 37B49708 15.10.01.809751 00 12 10 9 6 00000000 B83660A6 36FAF754 B8366620 383A3CB8 00000008 00000040 C5722F6CF3F57C8B 2010/01/26 00267D30 MISC TIMPGET 37318B18 37318F3C 00000001 37318CDC 00000000 00000006 37B49708 15.10.01.809748 00 12 10 27 31 36FAF77C 38368404 36FAF7B0 B8368650 38375CB8 002674C8 36FAF77C C5722F6CF3F5488B 2010/01/26 00267D30 MISC RMGREP1 37167108 FFFFC00F 00000001 00085019 00027734 37176780 B83684D2 . . .
The following new utilities manipulate saved trace information:
Note: The ARCHIVE LOG utility archives trace information written to the DDLDCLOG area, but will not print it. You must use the PRINT TRACE utility for that purpose.
The PRINT TRACE utility prints all or selected trace entries that reside in a DDLDCTRC area, a DDLDCLOG area, or one or more archive files created by the ARCHIVE TRACE or ARCHIVE LOG utilities.
You can select entries for printing based on the following:
Note: To print trace information you need the DBAREAD privilege on the SYSTEM.DDLDCTRC or SYSTEM.DDLDCLOG area.
The following diagram shows the syntax for the PRINT TRACE utility statement:
►►── PRINT TRACE ────────────────────────────────────────────────────────►
►─┬──────────────────────────────────────────────────────┬──────────────►
└─ FROM ─┬─ DATABASE ────────────────────────────────┬─┘
└─ ARCHIVE ──┬────────────────────────────┬─┘
└─DDNAME─┬──SYS001 ◄──────┬──┘
│ ┌────,─────┐ │
└──▼─ ddname ─┴──┘
►─┬──────────────────────┬──────────────────────────────────────────────►
│ ┌─────────────────┐ │
└──▼─┬─ SYSTRACE ──┬─┴─┘
└─ EXTENDED ──┘
►─┬───────────────────────┬─────────────────────────────────────────────►
│ ┌────,─────┐ │
└─ TASKID ─▼ taskid ─┴─┘
►─┬─────────┬───────────────────────────────────────────────────────────►
└─ UTC────┘
►─┬───────────────────────────────────┬─────────────────────────────────►
└── START AT ' ┬── date ──────── ' ─┤
├── date-time ┬──────┘
└── time ─────┘
►─┬──────────────────────────────────┬──────────────────────────────────►◄
└── STOP AT ' ┬── date ──────── ' ─┤
├── date-time ┬──────┘
└── time ─────┘
This section describes the PRINT TRACE command parameters:
Indicates the location from which to print trace information: a database area or an archive file.
Prints trace information from either the DDLDCTRC or the DDLDCLOG area. If the DMCL contains a DDLDCTRC area, only trace information in that area is printed; otherwise, only trace information in the DDLDCLOG area is printed.
Prints trace information from one or more archive files.
Identifies the ddname of one or more archive files whose contents are to be printed. If more than one ddname is specified, trace information is merged and displayed in chronological sequence.
Specifies the ddname of an archive file.
Default: SYS001
Limit: 32 ddnames
Note: Printing trace information from multiple archive files is only available to z/OS users. z/VSE users need to consolidate multiple archive files into a single file (in the order in which they were created) and use this file with the PRINT TRACE utility.
Includes basic system trace information in the output.
Includes extended trace information in the output.
Note: If you specify SYSTRACE or EXTENDED, only the specified type of information is printed. If you do not specify either option, both types of information are printed.
Prints trace information for selected tasks.
Specifies the taskid of a task whose trace information is to be printed.
Default: Trace information associated with all tasks is printed.
Limit: 32 task identifiers.
Prints only trace information recorded at or after the specified time.
Default: Prints information from the beginning of the database area or archive file.
Prints only trace information recorded at or before the specified date and time.
Default: Prints information recorded in the database area or archive file (starting at the time specified in the START AT parameter, if any).
Specifies a date, in one of the following formats:
The date components are:
Limit: 0001–9999 (leading zeros are optional)
Limit: 01–12 (leading zeros are optional)
Limit: 01–31 (leading zeros are optional)
Note: The combined values of yyyy, mm, and dd must represent a valid date. For example, 1988-02-29 is a valid date but 1989-02-29 is not.
Specifies a date and time in one of the following formats:
The date components are the same as those that can be specified for date.
The time components are:
Limit: 00-23 (leading zeros are optional)
Limit: 00-59 (leading zeros are optional)
Limit: 00-59 (leading zeros are optional)
Limit: 000000-999999 (trailing zeros are optional)
Default: 000000
Specifies a time in the following format:
The time components are the same as those that can be specified for date-time.
Note: The date is assumed to be the current date.
Specifies that Start and Stop times are interpreted as UTC times instead of local times.
The following items are included in the PRINT TRACE output for system trace entries.
The UTC time and date the trace entry was generated.
The relative SCA number of the subtask that generated the trace entry.
Taskid of the task that generated the trace entry.
The address of the generating task’s LTE.
The internal module number and four-character identifier of the module generating the trace entry.
The issuing macro number or entry point.
The relative macro expansion within the issuing program.
The contents of registers 11 through 1 and 2 through 8 at the time the entry was generated.
The contents of the TOD clock at the time the entry was generated.
Node or data sharing member name of issuing system.
The following PRINT TRACE statement requests printing of all SYSTRACE and EXTENDED trace entries from the archive file starting from March 02,2011 at 4:12 p.m. until just before 4:30 p.m. on March 02,2011 using the archive file with DDNAME SYS001.
PRINT TRACE FROM ARCHIVE DDNAME SYS001 START AT '2011-03-02-21.12.00' STOP AT '2011-03-02-21.30.00';
The ARCHIVE TRACE utility offloads the contents of the DC/UCF trace area to an archive file.
Note: To archive trace information you need DBAWRITE privilege on the SYSTEM.DDLDCTRC area.
The following diagram shows the syntax for the ARCHIVE TRACE utility statement:
►►─ ARCHIVE TRACE ─┬─────────┬────────────────────────────────────►◄ └─ PRINT ─┘
This section describes the parameters for the ARCHIVE TRACE utility:
Prints a copy of the contents of the archived trace information. If you do not specify PRINT, a copy of the archived trace information is not printed.
Note: For a description of the output produced by the PRINT option of the ARCHIVE TRACE utility, see the PRINT TRACE Utility.
The following example writes the contents of a system trace area (DDLDCTRC) to an archive file and empties the area.
ARCHIVE TRACE
The sample WTO exit distributed with CA IDMS has been updated to automate the offloading of trace information from the DDLDCTRC area. It now performs the following activities:
To use this sample exit, you must add a PTRCJOB DD statement to your DC/UCF system startup JCL. The contents of the associated file should include a command facility job stream that executes the ARCHIVE TRACE utility.
|
Copyright © 2010 CA.
All rights reserved.
|
|