Previous Topic: OPSTATUS FunctionNext Topic: IMS Records That OPSTATUS Returns


ASID Records That OPSTATUS Returns

If the OPSTATUS function specifies a func argument of A, J, P, S, or T, and a subfunc argument of I, the function generates ASID records with the following format:

Word Number: 1

Length: 8

Contains the Jobname/STCname/TSO ID ('INIT' for idle initiators)

Word Number: 2

Length: 8

Contains the stepname ('NONE' if not available; job class name for idle initiators under JES3 control; TSO logon procedure name for TSO users).

Word Number: 3

Length: 8

Contains the procstepname: 'NONE' if not available; 'IEFPROC' for idle initiators

Word Number: 4

Length: 4

Contains the Address Space IDentifier (ASID) (four hexadecimal digits with leading zeros).

Word Number: 5

Length: 3

Contains the address space status:

Word Number: 6

Length: 3

Contains the address space type:

Word Number: 7

Length: 3

Contains the number of Step-Must-Completes.

Word Number: 8

Length: 3

Contains the performance group.

Note: When the system is running in GOAL mode, this value is always zero. Use the W subfunc for WLM information when in GOAL mode.

Word Number: 9

Length: 3

Contains the domain.

Note: When the system is running in GOAL mode, this value is always zero. Use the W subfunc for WLM information when in GOAL mode.

Word Number: 10

Length: 17

Contains the CPU time (in the form SSSSSSSSS.MMMMMM, where S = Seconds and M = Microseconds). This word represents the total CPU time (TCB + SRB) consumed by the current job step only.

Note: The value is 'NONE' if the data is unavailable for any reason.

Word Number: 11

Length: 17

Contains the elapsed Time (in the form SSSSSSSSS.MMMMMM, where S = Seconds and M = Microseconds).

Note: The value is 'NONE' if the data is unavailable for any reason.

Word Number: 12

Length: 8

Contains the JES job ID

The value is NONE if the address space associated with the record did not start under JES and it has not used the subsystem interface to dynamically acquire a JES job ID, as described in the following text.

Servers and other address spaces may request a job ID later, even when they are not started under JES. (That is, if the address space was started under the master subsystem-MSTR.) In such cases, JES builds the correct data structures, and then creates a job ID for the address space. Job IDs can also be returned. Having a JES job ID at a particular moment means that JES allows use of any of its services. These services include internal readers for job submission, writers for SYSOUT data sets and allocation, and so on. Without a JES job ID, JES services cannot be used, and errors occur as a result.

This list illustrates the format of data that is returned for each type of job:

Note: The JES job ID of an idle initiator is always in the STCnnnnn format.

Word Number: 13

Length: 17

Contains the CPU Time in the format of SSSSSSSSS.MMMMMM.

S indicates seconds and M indicates microseconds.

This word represents the total task time (TCB) used by all jobs in the address space (the same value that is returned by the z/OS DISPLAY command).

The value of word ten has no direct relationship with the value of word 13. They are two different measures of CPU time. For started tasks, TSO users, and single-step batch jobs, the two values may or may not be fairly close. For multistep jobs that are in the second or subsequent step, the values probably differ greatly.

Note: If the data is unavailable for any reason, the value is NONE.

Word Number: 14

Length: 1

Contains a value that indicates whether the address space is associated with USS: if yes, O; if no, N.

Word Number: 15

Length: 10

Contains the total number of auxiliary storage (paging space) slots that are used by the address space. Each slot is 4096 bytes, or 4 KB.

Word Number: 16

Length: 10

Contains the total number of real storage frames that are in the private region that is used by the address space. Each frame is 4096 bytes, or 4 KB.

Word Number: 17

Length: 10

Contains the total number of expanded storage pages that are used by the address space. Each page is 4096 bytes, or 4 KB.

Note: On z/OS systems running in 64-bit mode, expanded storage is not supported and this value always contains zeros.

Word Number: 18

Length: 8

Contains the USERID that is associated with the address space. When no USERID is available, this field contains the value NONE.

Note: If the address space is a multiuser address space, the USERID reflects the USERID that was initially associated with the address space/job.

Word Number: 19

Length: 10

Contains the number of bytes of CSA associated with the address space. If Common Storage Tracking is inactive, this word contains the value NONE.

Word Number: 20

Length: 10

Contains the number of bytes of ECSA associated with the address space. If Common Storage Tracking is inactive, this word contains the value NONE.

Word Number: 21

Length: 10

Contains the number of bytes of SQA associated with the address space. If Common Storage Tracking is inactive, this word contains the value NONE.

Word Number: 22

Length: 10

Contains the number of bytes of ESQA associated with the address space. If Common Storage Tracking is inactive, this word contains the value NONE.

Word Number: 23

Length: 10

Contains the CPU Time in the format of SSSSSSSSS.MMMMMM.

S indicates seconds and M indicates microseconds.

This word represents the total CPU time (TCB + SRB) used by all enclaves that are owned by the current address space with the current jobname.

An enclave is a transaction that can span multiple dispatchable units (SRBs and tasks) in one or more address spaces and is reported on and managed as a unit. An enclave is managed separately from the address space it runs in. CPU and I/O resources that are associated with processing the transaction are managed by the performance goal of the transaction and reported to the transaction.

The value is NONE if the data is unavailable for any reason.

Note: The time format that is given for CPU Time and Elapsed Time deviates from the format that is displayed in OPSVIEW option 3.1. Since OPSTATUS is intended for automation rather than for producing displayable records, the format that is shown here reduces the need to convert time data for use in automation. Times that are returned by OPSTATUS for the use of OPS/REXX still require separation into seconds and microseconds.

The following OPS/REXX statements separate seconds and microseconds:

CPUTIME = OPSTATUS('A','I','VTAM')
PULL CPUTIME
SECONDS = WORD(TRANSLATE(CPUTIME,' ','.'),10)
MICROSECS = WORD(TRANSLATE(CPUTIME,' ','.'),11)