X'D9' trace entry

The X'D9' trace entry is shown.

The X'D9' trace entry - words 0 through 2

Most X'D9' trace entries have the following information in the first three words, except for OLR command processing. The following figure shows words 0 through 2 of the X'D9' trace entry.

  TRACE ID   = X'D9'

       word 0 — byte 1 - x'D9' - Online Reorganization (OLR) trace
                         entry.
                byte 2 - PST number. 
                bytes 3-4 - Trace sequence number.               
       word 1 — byte 1 - Module ID.
                byte 2 - Module subcode.
                bytes 3-4 - Local DMB number.
       word 2 - bytes 1-2 - Global DMB number.
                bytes 3-4 - Partition ID.

X'D9' trace entry: OLR output data set validation or creation and inactive data set deletion

The following figure shows words that are specific to the OLR output data set validation or creation and inactive data set deletion.

  TRACE ID   = X'D9'

       word 3 - bytes 1-2 - Error message number as four packed
                            decimal digits or as binary 0 if there
                            is no error.
                byte 3 - Reserved, 0.
                byte 4 - DCB number for the data set involved.  
                         The x'80' bit is on if the data set is 
                         one of the M through V and Y data sets
                         (see notes 1 and 2 below).
       word 4 - bytes 1-4 - DDIR address.
Notes:
  1. When no error has occurred, the error message number in word 3 has a value of binary zero, and there is no further information in the trace entry beyond word 4.
  2. For the following error message numbers, there is information that is specific to the particular error:
    Unexpected error from system macro instruction:
           words 5-6 - Macro name.  
           word 7 - bytes 1-2 - Return code. 
                    bytes 3-4 - Reason Code.
    2991 - Output data set validation error:
           word 5 - Reason code from DFS2991I message text.
           
    2992 - Unexpected error from CSI or catalog management, form 1:
           word 5 - Reason area from CSI or catalog management
           word 6 - byte 1 - Reason area type:
                      'C'   catalog  error                                        
                      'D'   data set error                                        
                      'I'   CSI call
    2992 - Unexpected return code from CSI, form 2:
           word 5 - Return code from CSI call.
           word 6 - byte 1 - X'00'
                    bytes 2-4 - Reason code from CSI call.
    2993 - Unexpected device class:
           word 5 - byte 1 - UCB device class.
    2994 - Unexpected IDCAMS return code creating a data set:
           word 5 - Return code from IDCAMS.
    2995 - Unexpected IDCAMS return code deleting a data set:
           word 5 - Return code from IDCAMS.
    2996 - Insufficient DASD space to create a data set:
           word 5 - bytes 1-2 - SVC 99 error reason
                                code.
                    bytes 3-4 - Reserved.
           word 6 - SMS error reason code.
           word 7 - Number of blocks wanted.
    2998 - Miscellaneous SVC 99 errors creating a data set:
           word 5 - SVC 99 error reason
                                   code.
                    bytes 3-4 - Reserved.
           word 6 - SMS error reason code.
           word 7 - Number of blocks wanted.
The following table shows the module ID and module subcode values for the X'D9' trace entries that represent the OLR output data set validation or creation process and the inactive data set deletion process.
Table 1. Module and subcode ID for X'D9'
Module ID Module Subcode Meaning
A DFSORA00 X'10' Data set creation successful
A DFSORA00 X'11' Data set creation successful
A DFSORA00 X'12' Data set creation successful
A DFSORA00 X'13' Data set creation successful
A DFSORA00 X'14' Data set validation successful
A DFSORA00 X'15' Data set validation successful
A DFSORA00 X'16' Data set validation successful
A DFSORA00 X'20' Primary index was not a VSAM KSDS
A DFSORA00 X'21' VSAM data set did not have REUSE attribute
A DFSORA00 X'22' VSAM record length did not match input
A DFSORA00 X'23' VSAM control interval size did not match input
A DFSORA00 X'24' KSDS key offset or length size did not match input
A DFSORA00 X'25' Miscellaneous errors; another trace entry precedes this one
A DFSORA00 X'C1' Internal error: invalid DFSORA00 call
A DFSORA00 X'C2' Internal error: No data set in X'2930' log record
A DFSORA00 X'C3' Invalid input data set
A DFSORA00 X'C4' Multi-volume input, but no output data set
A DFSORA00 X'C5' Non-DASD data set
A DFSORA00 X'C6' Multi-volume data set to be recovered
A DFSORA00 X'C7' Non-DASD data set
A DFSORA00 X'C8' Data set not usable for OSAM
A DFSORA00 X'C9' Data set is a PDS or PDSE
A DFSORA00 X'D1' Data set is not VSAM
A DFSORA00 X'D2' Data set is not a VSAM KSDS
A DFSORA00 X'D3' VSAM data set did not have REUSE attribute
A DFSORA00 X'D4' VSAM record length did not match input
A DFSORA00 X'D5' VSAM control interval size did not match input
A DFSORA00 X'D6' KSDS key offset or length size did not match input
A DFSORA00 X'D7' Data set not usable for OSAM
A DFSORA00 X'D8' Data set is a PDS or PDSE
A DFSORA00 X'D9' Data set is not VSAM
A DFSORA00 X'E2' Data set is not a VSAM KSDS
A DFSORA00 X'E3' VSAM data set did not have REUSE attribute
A DFSORA00 X'E4' VSAM record length did not match input
A DFSORA00 X'E5' VSAM control interval size did not match input
A DFSORA00 X'E6' KSDS key offset or length size did not match input
A DFSORA00 X'E7' Data set not usable for OSAM
A DFSORA00 X'E8' Data set is a PDS or PDSE
A DFSORA00 X'E9' Data set is not VSAM
B DFSORA10 X'C1' Data set error reported by CSI
B DFSORA10 X'C2' No error information available from CSI
B DFSORA10 X'C3' Catalog error reported by CSI
B DFSORA10 X'C4' Unexpected return code 4 from CSI
B DFSORA10 X'C5' Unexpected return code 4 from CSI
B DFSORA10 X'C6' Unexpected return code from CSI
B DFSORA10 X'C7' Unexpected return code from DEVTYPE
B DFSORA10 X'C8' Data set not on volume
B DFSORA10 X'C9' Unexpected return code from OBTAIN
B DFSORA10 X'D1' Unexpected return code from OBTAIN
B DFSORA10 X'D2' Unexpected return code from TRKCALC
B DFSORA10 X'D3' Unexpected return code 12 from GETDSAB
B DFSORA10 X'D4' Unexpected return code from GETDSAB
B DFSORA10 X'D5' Unexpected return code from SWAREQ
B DFSORA10 X'D6' Invalid data set name
D DFSORA20 X'C1' SVC 99 information reason returned
D DFSORA20 X'C2' Insufficient space on volume
D DFSORA20 X'C3' Data set in use
D DFSORA20 X'C4' Insufficient space, SMS
D DFSORA20 X'C5' SVC 99 error and SMS reason returned
D DFSORA20 X'C6' SVC 99 error code returned
D DFSORA20 X'C7' SVC 99 error code returned
D DFSORA20 X'C8' Unexpected return code from SVC 99
D DFSORA20 X'C9' SVC 99 information reason returned
D DFSORA20 X'D1' SVC 99 error code
D DFSORA20 X'D2' Unexpected return code from SVC 99
D DFSORA20 X'D3' Unexpected return code from IDCAMS
E DFSORA30 X'C1' Unexpected return code from IDCAMS
G DFSORA40 X'C1' GETMAIN failure

X'D9' trace entry: fence value before an OLR IPOST/IWAIT

The following figure shows the remaining words of the X'D9' trace entries that are specific to the fence value before an OLR IPOST/IWAIT:

 TRACE ID   = X'D9'

        word 3 - Can contain the address of the PST
                 to be posted.   
        words 4-5 - Contains DMBORFEN.     
        words 6-7 - Contains DMBAMFEN.

The following table shows the module ID and module subcode values for the X'D9' trace entries that represent the fence value before an OLR IPOST/IWAIT.

Table 2. Module and subcode ID for X'D9': fence value before an OLR IPOST/WAIT
Module ID Module Subcode Meaning
J DFSORP70 X'01' IPOST for the OLR I/O fence
J DFSORP70 X'02' IWAIT for the OLR action module fence
J DFSORP70 X'03' IPOST for the OLR I/O fence
J DFSORP70 X'04' IWAIT for the OLR action module fence
L DFSORP40 X'01' IWAIT for the OLR action module fence
L DFSORP40 X'02' IPOST for the OLR action module fence
M DFSPCSH0 X'01' IWAIT for the OLR action module fence
M DFSPCSH0 X'02' IPOST for the OLR action module fence
M DFSPCSH0 X'03' IWAIT for the OLR action module fence
M DFSPCSH0 X'04' IPOST for the OLR action module fence
O DFSDLOC0 X'01' IPOST for the OLR I/O fence
O DFSDLOC0 X'02' IWAIT for the OLR I/O fence
R DFSDLR00 X'01' IPOST for the OLR action module fence
R DFSDLR00 X'02' IPOST for the OLR action module fence
R DFSDLR00 X'03' IWAIT for the OLR action module fence
R DFSDLR00 X'04' IPOST for the OLR action module fence
R DFSDLR00 X'05' IPOST for the OLR action module fence
R DFSDLR00 X'06' IWAIT for the OLR action module fence
R DFSDLR00 X'07' IWAIT for the OLR action module fence
R DFSDLR00 X'08' IWAIT for the OLR action module fence
S DFSDVBH0 X'01' IWAIT for the OLR I/O fence
S DFSDVBH0 X'02' IPOST for the OLR I/O fence
V DFSDVSM0 X'01' IPOST for the OLR I/O fence
V DFSDVSM0 X'02' IPOST for the OLR I/O fence

X'D9' trace entry : next UOR determination

The following figure shows the remaining words of the X'D9' trace entries that are specific to the next UOR determination.

 TRACE ID   = X'D9'

        word 3 - The total number of UORs performed.
        word 4 - The execution span for this UOR.
        word 5 - The proposed size for the next UOR.
        word 6 - The total bytes moved during this UOR.
        word 7 - The total locks held during this UOR.

X'D9' trace entry: OLR command processing

The following figure shows the X'9D' trace entry definitions used by the Online Reorganization (OLR) command processing:

 TRACE ID   = X'D9'

        word 0 - byte 1 - X'D9' Online Reorganization (OLR)
                          trace entry.
                 byte 2 - Zero - not used.
                 bytes 3-4 - Trace sequence number.
        word 1 - byte 1 - Module ID.
                 byte 2 - Module subcode.
                 byte 3 - Module function.
                 byte 4 - FREESTOR error return code.
        word 2 - Last 4 bytes of the IMS ID (SCDIMSNM+4)
                 processing the command.
        words 3-4 - Command VERB (INIT, UPD, TERM, and QRY
                    if an type-2 command)
        words 5-6 - Operation Manager name ('NONOMCMD' if OLR
                    type-1 command.
        word 7 - Address of storage not freed if FREESTOR
                 failure.

For all X'D9' trace entries, the module ID, and usually the module subcode as well, indicate both the meaning of the trace entry and the format of the rest of the trace entry.

The following table shows the module ID values in X'D9' trace entries that represent OLR command processing.

Table 3. Module and subcode ID for X'D9': OLR command processing
Module ID Module Subcode Meaning
C DFSORC00 X'00' OLR type-2 command issued
C DFSORC00 X'01' FREESTOR error during INIT error processing
C DFSORC00 X'02' FREESTOR error after sending command response
P DFSORC10 X'00' OLR type-1 command issued
P DFSORC10 X'01' FREESTOR error during INIT processing cleanup

X'D9' trace entry: OLR start

The following figure shows the remaining words of the X'D9' trace entries that are specific to the OLR start.

X'9D' trace entry - words specific to OLR start

 TRACE ID   = X'D9'

       word 3 - The RBA of the cursor in the second CI
                or block.
       word 4 - Unused.
       word 5 - Unused.
       word 6 - Unused.
       word 7 - Unused.

X'D9' trace entry: start of a UOR

The following figure shows the remaining words of the X'D9' trace entries that are specific to the start of a UOR.

X'9D' trace entry - words specific to start of UOR

 TRACE ID   = X'D9'

       word 3 - The first four bytes of the last committed
                cursor.
       word 4 - The start time of this UOR.
       word 5 - The execution span for this UOR.
       word 6 - The time that was waited before this
                UOR started.
       word 7 - Unused.

X'D9' trace entry: UOR wait for timer

The following figure shows the X'D9' trace entries that are specific to the UOR wait for timer.

X'9D' trace entry - words specific to UOR wait for timer

 TRACE ID   = X'D9'

       word 3 - Unused
       word 4 - The start time of this UOR.
       word 5 - The execution span for this UOR.
       word 6 - The time that will be waited before
                the next UOR starts.
       word 7 - Unused.

X'D9' Trace Entry: OLR Full-Block Logging

TRACE ID = X'D9'

      Word 3 - Not used
      Word 4 - AMP
      Word 5 - Buffer prefix (IBFPRF for OSAM or IDABUFC for VSAM)
      Word 6 - Block number for OSAM or RBA for VSAM

The following table shows the module ID and module subcode values for the X'D9' trace entries that represent the OLR logging of a full-block of database changes in a single X'5050' log record rather than the logging of individual database changes in separate log records.

Table 4. Module and subcode ID for X'D9': OLR full-block logging
Module ID Module Subcode Meaning
F DFSDBH20 X'00' After full-block logging during OSAM buffer steal
H DFSDBH30 X'00' After full-block logging during OSAM buffer purge
S DFSDBVH0 X'03' After full-block logging by DL/I buffer handler router before purge
V DFSDVSM0 X'03' Before full-block logging during VSAM buffer purge
V DFSDVSM0 X'04' After full-block logging during VSAM buffer purge

X'D9' Trace Entry: OLRK PNDX Store

TRACE ID = X'D9'

      Word 3 - OLRK entry address
      Word 4 - Root RBA of the primary index entry.
      Word 5 byte 1 - x'80' entry for primary index entry or VSAM)
             byte 2 - x'80' queued onto chain by OLR 

X'D9' Trace entry: OLRK ILE Store

TRACE ID   = X'D9'

     Word 3    - OLRK entry address
     Words 4,5 - Key of ILDS record
     Word 6 byte 1 - segment code
            byte 2 - x'40' entry for ILDS entry
            byte 3 - x'80' queued onto chain by OLR 

X'D9' Trace entry: OLRK ILE Write

TRACE ID   = X'D9'

     Word 3 - OLRK entry address
     Word 4,5 - Key of ILDS record
     Word 6 byte 1 - segment code
            byte 2 - x'40' entry for ILDS entry
            byte 3 - x'40' written to KSDS by VSAM interface
                     x'20' deleted off chain by OLR

X'FB' Trace entry: PSTSTLOR.

INSERT LOGICAL RECORDS (KSDS) to the primary index database or INSERT LOGICAL RECORDS (KSDS) to the ILDS database for HALDB integrated online reorganization. See the previous OLRK ILE/ILDS Store/Write trace entries that are associated with this trace entry.

TRACE ID   = X'FB'

     Word 3 - Unused
     Word 4 - Unused
     Word 5 - Unused
     Word 6 - Unused
     Word 7 - Unused