MERGE and MERGEEND subcommands — merge multiple traces
Use the MERGE subcommand to merge multiple component traces and generalized trace facility (GTF) traces chronologically. MERGE combines formatted trace entries produced by CTRACE subcommands, GTFTRACE subcommands, or both, into chronological order in a single report. Use the MERGEEND subcommand to stop merging traces.
Start the merging by entering MERGE in IPCS line mode. Next, format the traces to be merged by entering, one at a time, CTRACE and GTFTRACE subcommands. You can enter up to 16 subcommands. To mark the end of the merging, enter MERGEEND.
MERGE can process any of the dump or trace data sets that CTRACE and GTFTRACE can process; however, MERGE has one restriction. Only one of the trace sources may be on tape. The rest must be on direct access storage device (DASD).
Do not specify different output locations on the CTRACE and GTFTRACE subcommands. Each subcommand must contain the same output specifications. For example, do not specify PRINT on one subcommand and TERMINAL on another.
- Syntax
MERGE ⋮ 1 to 16 CTRACE and GTFTRACE subcommands ⋮ MERGEEND
- Return Codes
See Standard subcommand return codes for a description of the return codes produced by the MERGE subcommand.
- Example: Merge a component trace and GTF trace.
- Action
MERGE CTRACE COMP(SYSRSM) FULL LIMIT(1) DSN('MYDUMP1') GTFTRACE DSN('COPY.TRACE1') MERGEEND
- Result
MERGE produces a report similar to the following.
********** MERGED TRACES *********** 01. GTF dsn(copy.trace1) 02. CTRACE dsn(rsm.ctrace) limit(5) comp(sysrsm) summary **** GTFTRACE DISPLAY OPTIONS IN EFFECT **** SSCH=ALL IO=ALL CCW=SI SVC=ALL PI=ALL EXT RNIO SRM RR DSP SLIP **** GTF DATA COLLECTION OPTIONS IN EFFECT: **** System resource manager events traced **** GTF TRACING ENVIRONMENT **** Release: SP4.2.0 FMID: HBB4420 System name: SYSTEM42 CPU Model: 3090 Version: FF Serial no. 170067 COMPONENT TRACE SUMMARY FORMAT SYSNAME(SYSTEM41) COMP(SYSRSM)
**** 07/23/90 MNEMONIC ENTRY ID TIME STAMP DESCRIPTION -------- -------- --------------- ----------- 02. XEPEXIT 00000002 14:18:40.000001 External Entry Point Exit FUNC1... FLTAEPAG Enabled Addr Space Page Faults JOBN1... EDWTR1 ASID1... 0014 PLOCKS.. 00000000 CPU.... 0001 JOBN2... EDWTR1 ASID2... 0014 RLOCKS.. 00000000 SRM ASCB.... 00FD2E00 CPU..... 0001 JOBN.... *MASTER* R15..... 00000000 R0...... 00010005 R1...... 00000000 01. GMT-07/23/90 14:18:40.120000 LOC-07/23/90 14:18:40.120000 02. XEPENTRY 00000001 14:18:40.130594 External Entry Point Entry FUNC1... GENIOCMP General I/O Completion JOBN1... JES2 ASID1... 0012 PLOCKS.. 08000081 CPU.... 0001 JOBN2... *ALL* ASID2... FFFE RLOCKS.. 08000000 SRM ASCB.... 00FD2E00 CPU..... 0001 JOBN.... *MASTER* R15..... 00000000 R0...... 00010005 R1...... 00000000 01. GMT-07/23/90 14:18:40.142505 LOC-07/23/90 14:18:40.142505 SRM ASCB.... 00FD2E00 CPU..... 0001 JOBN.... *MASTER* R15..... 00000000 R0...... 00010005 R1...... 00000000 01. GMT-07/23/90 14:18:40.814690 LOC-07/23/90 14:18:40.814690
02. PAGEA2R 0000001D 14:18:40.891890 Page Request Auxiliary to Real FUNC1... GENIOCMP General I/O Completion FUNC2... FLTAEPAG Enabled Addr Space Page Faults JOBN1... JES2 ASID1... 0012 PLOCKS.. 08004081 CPU.... 0001 JOBN2... EDWTR1 ASID2... 0014 RLOCKS.. 08004000 SRM ASCB.... 00FD2E00 CPU..... 0001 JOBN.... *MASTER* R15..... 00000000 R0...... 00010005 R1...... 00000000 01. GMT-07/23/90 14:18:40.901011 LOC-07/23/90 14:18:40.901011
02. XEPEXIT 00000002 14:18:40.952534 External Entry Point Exit FUNC1... GENIOCMP General I/O Completion JOBN1... JES2 ASID1... 0012 PLOCKS.. 08004081 CPU.... 0001 JOBN2... *ALL* ASID2... FFFE RLOCKS.. 08004000 02. XEPENTRY 00000001 14:18:40.964644 External Entry Point Entry FUNC1... PGFIX Page Fix JOBN1... EDWTR1 ASID1... 0014 PLOCKS.. 80000001 CPU.... 0001 JOBN2... EDWTR1 ASID2... 0014 RLOCKS.. 80000000 . . .
- Explanation The output from the MERGE subcommand begins with a numbered list of CTRACE and GTFTRACE subcommands that were input to MERGE. In the trace output, these numbers appear in the first two columns to identify each formatted trace entry with the trace subcommand that produced it. In the example:
- 01. identifies a GTF trace entry
- 02. identifies an RSM component trace entry
The number for a component trace entry is on the first line of the entry. The number for a GTF entry is on the time-stamp line at the end of the entry.
- Action