SSRV trace entries

An SSRV trace entry represents entry to a system service. The service can be entered by a PC instruction or a branch.

 PR ASID TCB-ADDR  IDENT CD/D PSW----- ADDRESS- UNIQUE-1 UNIQUE-2 UNIQUE-3  PSACLHS- PSALOCAL PASD SASD TIMESTAMP-RECORD CP
                                                UNIQUE-4 UNIQUE-5 UNIQUE-6

 pr home tcb-addr  SSRV ssid          return--  data---- data---- data----  psaclhs- psalocal pasd sasd timestamp------- 06
PR
pr: Identifier of the processor that produced the TTE.
ASID
home: Home address space identifier (ASID) associated with the TTE.
TCB-ADDR
tcb-addr: Address of the task control block (TCB) for the current task or the work element block (WEB).
IDENT
The TTE identifier, as follows:
SSRV
Request for a system service
CD/D
ssid: One of the following SSRV entry identifiers:
ssid (hexadecimal) Macro for SSRV Request Component
0001 WAIT Task management
0002 POST Task management
0004 GETMAIN Virtual storage management
0005 FREEMAIN Virtual storage management
000A GETMAIN, FREEMAIN Virtual storage management
005F SYSEVENT System resource manager
0078 GETMAIN, FREEMAIN Virtual storage management
007A SPI, SPIINT Service processor interface
0100 ETCON PC/AUTH
0101 ETCRE PC/AUTH
0102 ATSET PC/AUTH
0103 AXSET PC/AUTH
0104 AXEXT PC/AUTH
0105 AXFRE PC/AUTH
0106 AXRES PC/AUTH
0107 ETDES PC/AUTH
0108 ETDIS PC/AUTH
0109 LXFRE PC/AUTH
010A LXRES PC/AUTH
010E SUSPEND Supervisor control
010F RESUME Supervisor control
0110 SCHEDULE Supervisor control
0111 SCHEDULE Supervisor control
0112 SCHEDULE Supervisor control
0113 DSGNL Supervisor control
0114 RISGNL Supervisor control
0115 RPSGNL Supervisor control
0116 SCHEDULE Supervisor Control
0117 SCHEDULE Supervisor Control
0118 SUSPEND Supervisor Control
0119 RESUME Supervisor Control
011A RESUME Supervisor Control
011B RESUME Supervisor Control
011C SCHEDULE Supervisor Control
011D IEAMSCHD Supervisor Control
011E Start of changePause (IEAVPSE / IEAVPSE2 / IEA4PSE / IEA4PSE2)End of change Supervisor Control
011F Start of changeRelease (IEAVRLS / IEAVRLS2 / IEA4RLS / IEA4RLS2) End of change Supervisor Control
Start of change0120End of change Start of changeTimer DIEEnd of change Start of changeSupervisor ControlEnd of change
0128 WAIT Task management
0129 POST Task management
012A POST Task management
012B POST Task management
012C ASCBCHAP Task management
012D STATUS Task management
012E STATUS Task management
0132 STORAGE OBTAIN Virtual storage management
0133 STORAGE RELEASE Virtual storage management
0146 SPI, SPIINT Service processor interface
014B IARV64 Real storage management
014C ISGENQ Global resource serialization
014D ENQ/RESERVE Global resource serialization
014E DEQ Global resource serialization
014F SYSCALL UNIX System Services
1050 CF CPU command or internal request Reconfiguration
PSW----- ADDRESS-
return--:
  • For PC/AUTH, supervisor control, and task management: Caller's return address if the service was entered by a branch; 0 if the service was entered by a PC instruction
  • For virtual storage management: For SSRV 132 (Storage Obtain) and SSRV 133 (Storage Release), it is the ALET. For other VSM SSRVs (004, 005, 00A, 078), it is the caller's return address.
  • For z/OS® UNIX System Services: the syscall code.
  • For real storage management: Bytes as follows:
    0 Request type identifier:
        01 GETSTOR
        02 GETSHARED
        03 DETACH
        04 PAGEFIX
        05 PAGEUNFIX
        06 PAGEOUT
        07 DISCARDDATA
        08 PAGEIN
    Start of change End of change Start of change End of change Start of change09End of change Start of changePROTECTEnd of change
        0A SHAREMEMOBJ
        0B CHANGEACCESS
    Start of change End of change Start of change End of change Start of change0CEnd of change Start of changeUNPROTECTEnd of change
    Start of change End of change Start of change End of change Start of change0DEnd of change Start of changeCHANGEGUARDEnd of change
    Start of change End of change Start of change End of change Start of change0FEnd of change Start of changeGETCOMMONEnd of change
    Start of change End of change Start of change End of change Start of change11End of change Start of changePCIEFIXEnd of change
    Start of change End of change Start of change End of change Start of change12End of change Start of changePCIEUNFIXEnd of change
    1 GETSTOR GETSHARED Request flags:
      1... .... COND=YES request
      .1.. .... FPROT=NO request
      ..1. .... CONTROL=AUTH request (only applies to GETSTOR)
      ...1 .... SVCDUMPRGN=NO request (only applies to GETSTOR)
      .... 1... CHANGEACCESS = GLOBAL request (only applies to GETSHARED)
      .... .1.. GUARDLOC=HIGH request (only applies to GETSTOR)
    1 DETACH Request flags:
      1... .... COND=YES request
      .1.. .... MATCH=USERTOKEN request
      ..1. .... AFFINITY=SYSTEM request
      ...1 .... OWNER=NO request
    1 SHAREMEMOBJ Request flags:
      1... .... COND=YES request
      .1.. .... SVCDUMPRGN=NO request
    1 CHANGEGUARD Request flags:
      1... .... COND=YES request
      .1.. .... TOGUARD request
      ..1. .... FROMGUARD request
    1 PAGEFIX Request flags:
      1... .... LONG=NO request
    1 DISCARDDATA Request flags
      1... .... CLEAR=NO request
      .1.. .... KEEPREAL=NO request
    1 CHANGEACCESS Request flags
      1... .... READONLY request
      .1.. .... SHAREDWRITE request
      ..1. .... HIDDEN request
    Start of change1End of change Start of changeGETCOMMON Request flags End of change
    Start of change End of change Start of change1...End of change Start of change....End of change Start of changeCOND=YES request End of change
    Start of change End of change Start of change.1.. End of change Start of change....End of change Start of changeFPROT=NO request End of change
    Start of change1End of change Start of changePCIEFIX Request flags: End of change
      1... .... LONG=NO request
    2 Keys Used flag
      1... .... KEY specified
      .1.. .... USERTOKEN specified
      ..1. .... TTOKEN specified
      ...1 .... CONVERTSTART specified
      .... 1... GUARDSIZE64 request
      .... .1.. CONVERTSIZE64 request
    Start of change End of change Start of change....End of change Start of change..1. End of change Start of changeMOTKN specified End of change
    3 Miscellaneous Byte
    • Start of changeStorage Key for GETSTOR, GETSHARED, and GETCOMMON requestsEnd of change
    • Number of ranges in range list for range list requests
    • 0 for all other requests
  • For CONFIGURE CPU: Bytes as follows:
    Bytes 0 and 1 Target CPU ID
    Byte 2 Internal flags
    Byte 3 Bits 0-3 Reserved
      Bits 4-7 Direction and source
       
    Value
    Meaning
    0
    Online or Offline at MSI time
    1
    Online Operator request
    2
    Offline Operator request
    3
    Online WLM request
    4
    Offline WLM request
UNIQUE-1/UNIQUE-2/UNIQUE-3
UNIQUE-4/UNIQUE-5/UNIQUE-6
data----: Data. The unique trace data for each event is obtained from data areas. The areas for PC/AUTH, supervisor control, and task management are in the z/OS MVS™ Data Areas in z/OS Internet library.
  • For an SSRV request to the PC/AUTH component: the PCTRC data area
  • For an SSRV request to supervisor control: the SPTRC data area
  • For an SSRV request to task management: the TMTRC data area
  • For an SSRV request to virtual storage management, the data is:
    • Under UNIQUE-1: Information input to the VSM STORAGE (OBTAIN and RELEASE) service: Bytes as follows:
      0 Flags:
        X... .... RESERVED
        .1.. .... CALLRKY=YES was specified
        ..1. .... AR 15 is in use
        ..0. .... AR 15 is not in use
        ...1 .... LOC=(nnn,64) was specified. Storage can be backed above the bar
        .... 1... CHECKZERO=YES was specified
        .... 0... CHECKZERO=NO was specified explicitly, or by default
        .... .1.. TCBADDR was specified on STORAGE OBTAIN or RELEASE
        .... ..00 OWNER=HOME was specified explicitly, or by default
        .... ..01 OWNER=PRIMARY was specified
        .... ..10 OWNER=SECONDARY was specified
        .... ..11 OWNER=SYSTEM was specified
      1 Storage key (bits 0 through 3). Ignore when CALLRKY=YES is flagged in byte 0.
      2 Subpool number
      3 Request flags:
        1... .... ALET operand specified
        .1.. .... Storage can be backed anywhere
        ..00 .... Storage must have callers residency
        ..01 .... Storage must have a 24-bit address
        ..10 .... The request is for an explicit address
        ..11 .... Storage can have a 24- or 31-bit address
        .... 1... Maximum and minimum request
        .... .1.. Storage must be on a page boundary
        .... ..1. Unconditional request
        .... ...0 OBTAIN request
        .... ...1 RELEASE request
    • Under UNIQUE-2:
      • In an SSRV trace entry for a VSM STORAGE OBTAIN or GETMAIN, one of the following:
        • The length of the storage successfully obtained
        • The maximum storage requested, if the storage was not obtained
      • In an SSRV trace entry for a VSM STORAGE RELEASE or FREEMAIN:
        • the length of the storage to be released, or zero if a subpool release was requested.
    • Under UNIQUE-3:
      • In an SSRV trace entry for a VSM STORAGE OBTAIN or GETMAIN, one of the following:
        • The address of the storage successfully obtained, if you specified address; otherwise, zero.
        • The minimum storage requested, if the storage was not obtained
      • In an SSRV trace entry for a VSM STORAGE RELEASE or FREEMAIN:
        • The address of the storage to be released.
    • Under UNIQUE-4:
      • Left 2 bytes under UNIQUE-4: ASID of the target address space
      • Next byte under UNIQUE-4: Reserved
      • Right byte under UNIQUE-4:

        If the GETMAIN/FREEMAIN/STORAGE OBTAIN/STORAGE RELEASE is unconditional, an abend will be issued and the SSRV trace entry 3rd byte of UNIQUE-4 will contain X'FF'. If the GETMAIN/FREEMAIN/STORAGE OBTAIN/STORAGE RELEASE is conditional, no abend will be issued and the SSRV trace entry 3rd byte of UNIQUE4 will contain the actual return code from the storage service.

  • For an SSRV request to real storage management (SSID 14B), the IARV64 data is:
    • Under UNIQUE-1
      • Return Code/Abend Code (4 bytes)
    • Under UNIQUE-2
      • Reason Code (4 bytes)
    • Under UNIQUE-3
      • ALET specified on the IARV64 request (4 bytes)
    • Additional UNIQUE fields depending on the IARV64 service that follows:
      • GETSTOR/GETSHAREDStart of change/GETCOMMONEnd of change
        • Origin address of the memory object - 8 bytes
        • Size of the memory object - 8 bytes
        • User token - 8 bytes
      • DETACH
        • Memory object start address (for MATCH=SINGLE requests) zeroes (for MATCH=USERTOKEN requests) - 8 bytes
        • User token - 8 bytes
      • PAGEFIX, PAGEUNFIX, PAGEOUT, PAGEIN, DISCARDDATA, CHANGEACCESS, Start of changePROTECT, UNPROTECT, PCIEFIX, PCIEUNFIXEnd of change
        • Address of rangelist - 8 bytes
        • VSA from 1st range list entry - 8 bytes
        • Number of blocks from 1st range list entry - 8 bytes
      • CHANGEGUARD
        • Memory object start (if ConvertStart was not specified), or convert start address (if ConvertStart was specified) - 8 bytes
        • Number of segments to be converted - 8 bytes
      • SHAREMEMOBJ
        • Range list address - 8 bytes
        • VSA from 1st range list entry - 8 bytes
        • User token - 8 bytes
  • In an SSRV trace entry for global resource serialization with SSID (14C), the ISGENQ data is:
    • Under UNIQUE-1:
      • Return address (4 bytes)
    • Under UNIQUE-2:
      • Two bytes of flags as follows:
        1 Flags:
          01.. .... REQUEST=OBTAIN
          10.. .... REQUEST=CHANGE
          11.. .... REQUEST=RELEASE
          ..1. .... COND=YES
          ...0 0... SCOPE=STEP
          ...1 0... SCOPE=SYSTEM
          ...1 1... SCOPE=SYSTEMS
          .... .1.. CONTROL=SHARED
          .... .0.. CONTROL=EXCLUSIVE
          .... ..1. RESERVEVOLUME=YES
          .... ...1 SYNCHRES=YES
        2 Flags:
          1... .... SYNCHRES=NO
          .1.. .... An exit changed the request
          ..1. .... WAITTYPE=ECB
          ...1 .... CONTENTIONACT=Fail
          .... 1... RESLIST=YES
          .... .1.. RNLs Changed Scope
          .... ..1. TEST=YES
          .... ...1 RNL=NO
        Note: If the last bit of byte one and the first bit of byte two are both off, the system default for SYNCHRES is used.

        ISGENQ reason code (2 bytes): If a list request was provided, this field will provide the reason code for the particular list entry in error. If more than one entry is in error, it will provide the highest reason code.

    • Under UNIQUE-3:
      • Primary ASID (2 bytes)
      • The last 2 bytes may represent
        • X'FFFF' if an incomplete trace entry. An incomplete entry may be the result of a program check or an error was detected. The entry will be populated only with data we know we can trust. Therefore, some flags may only be partially filled in. To avoid confusion, having a X'FFFF' as a device number and having the reserve request bit off will inform the user the entry is incomplete. (2 bytes)
        • X'0000' if not a reserve request (2 bytes)
        • Device number if a reserve request (2 bytes)
    • Under UNIQUE-4
      • First 4 bytes of the QNAME (4 bytes). For a list request, this represents the first QNAME in the request.
    • Under UNIQUE-5
      • Last 4 bytes of the QNAME (4 bytes). For a list request, this represents the first QNAME in the request.
  • In an SSRV trace entry for global resource serialization with SSID (14D) the ENQ and SSID (14E) the DEQ, the information is:
    • Under UNIQUE-1:
      • Return address (4 bytes)
    • Under UNIQUE-2:
      • Refer to the PEL mapping for explanation of PELLAST and PELXFLG1. See z/OS MVS Data Areas in z/OS Internet library.
      • 3 bytes of flags.
      • Byte 1 is:
        1 Flags:
          0... .... Exclusive request
          .0.. .... STEP
          .1.. .... SYSTEM
          .0.. .... SYSTEM w/UCB
          .0.. 1... SYSTEMS w/UCB
          .1.. 0... SYSTEMS
          ..1. 0... An exit changed the request
          ...1 1... RNLs changed scope
          .... .000 RET=NONE
          .... .001 RET=HAVE
          .... ..010 RET=CHNG
          .... .011 RET=USE
          .... .100 RET=ECB
          .... .101 RESERVED
          .... .110 RESERVED
          .... .111 RET=TEST
        • Byte 2 represents PELLAST
          • Bit 4 is ignored.
        • Byte 3 represents PELXFLG1
          • Bit 8 is ignored.
      • ENQ return code (SSID14D) (1 byte) or DEQ return code (SSID 14E) (1 byte)
        • If a list request was provided, this field will provide the Return Code for the particular list entry in error. If more than one entry is in error, it will provide the highest Return Code.
        • If ABEND, this field is in the form X'Fn' where n signifies the first hex digit of the ABEND code. For example, a ‘X'F7' signifies a X'738' ABEND and X'F4' signifies a X'438' ABEND.
    • Under UNIQUE-3:
      • Primary ASID (2 bytes)
      • The last 2 bytes may represent
        • X'FFFF' if an incomplete trace entry. An incomplete entry may be the result of a program check or an error was detected. The entry will be populated only with data we know we can trust. Therefore, some flags may only be partially filled in. To avoid confusion, having a X'FFFF' as a device number and having the reserve request bit off will inform the user the entry is incomplete. (2 bytes)
        • X'0000' if not a reserve request (2 bytes)
        • Device number if a reserve request (2 bytes)
    • Under UNIQUE-4
      • First 4 bytes of the QNAME (4 bytes). For a list request, this represents the first QNAME in the request.
    • Under UNIQUE-5
      • Last 4 bytes of the QNAME (4 bytes). For a list request, this represents the first QNAME in the request.
  • For an SSRV request to UNIX system services, the data is:
    • Under UNIQUE-1

      The address of the PPRT control block

    • Under UNIQUE-2:

      For an 8 byte parameter of an AMODE 64 caller, the low four bytes of the first parameter, otherwise the first four bytes of the first parameter, if available. Zero, if parameter not available.

    • Under UNIQUE-3

      For an 8 byte parameter of an AMODE 64 caller, the low four bytes of the second parameter, otherwise the first four bytes of the second parameter, if available. Zero, if parameter not available.

    • Under UNIQUE-4

      For an 8 byte parameter of an AMODE 64 caller, the low four bytes of the third parameter, otherwise the first four bytes of the third parameter, if available. Zero, if parameter not available.

  • In an SSRV trace entry for CONFIGURE CPU with SSID (1050), the information is:
    • Under UNIQUE-1

      Contents of an internal return code field.

    • Under UNIQUE-2

      Shows which 8-byte block of CSD_CPU_ALIVE.

    • Under UNIQUE-4 through UNIQUE-5

      The 8-byte contents of CSD_CPU_ALIVE mask at the 8-byte block offset in UNIQUE-2 as updated by the CF CPU command.

PSACLHS-
psaclhs-: String for the current lock held, from the PSACLHS field of the PSA. This field will contain descriptive text for some SSRV trace entries. The descriptive text will not appear in SNAP, SYSUDUMP, or SYSABEND output.
PSALOCAL
psalocal: Locally locked address space indicator, from the PSALOCAL field of the PSA. This field will contain descriptive text for some SSRV trace entries. The descriptive text will not appear in SNAP, SYSUDUMP, or SYSABEND output.
PASD
pasd: Primary ASID (PASID) at trace entry. This field will contain descriptive text for some SSRV trace entries. The descriptive text will not appear in SNAP, SYSUDUMP, or SYSABEND output.
SASD
sasd: Secondary ASID (SASID) at trace entry. This field will contain descriptive text for some SSRV trace entries. The descriptive text will not appear in SNAP, SYSUDUMP, or SYSABEND output.
TIMESTAMP-RECORD
timestamp-------: Time-of-day (TOD) clock value when system trace created the trace entry. The value is in the same format as the time stamp on the logrec data set records.
CP
The CP column contains 2 hex digits of the processor model dependent information, which is intended to identify the physical CP that made the trace entry. CP is only provided when formatting SYSTRACE under IPCS. CP is not provided for SYSUDUMP, SYSABEND, or SNAP.
Parent topic: Reading system trace output