X'31', X'32', X'34', X'B1', and X'B2' trace entries

Example of X'31', X'32', X'34', X'B1', and X'B2' trace entries

 TRACE ID   = X'31', X'32', X'34', X'B1', X'B2'
 
       word 0 — byte 1 - X'31', X'32', X'34', X'B1', or X'B2' - Function code for
                         HD space management (see note 1 below)
                byte 2 - PST number
                bytes 3-4 - Trace sequence number
       word 1 — bytes 1-2 - Length of request (see note 3 below)
                bytes 3-4 - Offset (requested or returned)
       word 2 — byte 1 - PSTTRNID (ID of module calling space management)
                byte 2 - PSTTRMSC (subcode of module calling the buffer handler - 
                         see note 4 below)
                byte 3 - Not used
                byte 4 - PSTRTCDE (return code from space management)
       word 3 — byte 1 - Flag byte (X'80' - entry already in use)
                bytes 2-4 - PSTDATA (core address - see note 5 below)
       word 4 — PSTBYTNM (RBA or RRN - see note 6 below)
       word 5 — RBA of space given to caller
       word 6 — bytes 1-2 - DMB number
                byte 3 - DCB number
                byte 4 - Reserved
       word 7 — MSG/ABEND feedback

       

Notes:

1. You need the X'32' entries to resolve this problem.
2. Numbers 3 and 4 are very important. In most cases, the segment was deleted by another task (see PST number), and this task (see PST number) tried to enqueue on the segment that waited while the other PST finished its processing. During the attempt, an FSE was found and abend U0832 resulted. An IMS internal error usually causes this problem.
3. The length of the segment that was freed.
4. The real storage address of the segment during the time of deletion.
5. The PSTBYTNM is the key field in the trace table. Look for a X'32' entry with the PSTBYTNM field equal to the PSTBYTNM field found in the buffer trace.