|
|
|
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:
Length: 8
Contains the Jobname/STCname/TSO ID ('INIT' for idle initiators)
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).
Length: 8
Contains the procstepname: 'NONE' if not available; 'IEFPROC' for idle initiators
Length: 4
Contains the Address Space IDentifier (ASID) (4 hexadecimal digits with leading zeroes).
Length: 3
Contains the address space status:
Length: 3
Contains the address space type:
Length: 3
Contains the number of Step-Must-Completes.
Length: 3
Contains the performance group.
Note: When the system is running in GOAL mode this value will always be zero. Use the W subfunc for WLM information when in GOAL mode.
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.
Length: 17
Contains the CPU time (in the form SSSSSSSSS.MMMMMM, where S = Seconds and M = Microseconds); this is 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.
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.
Length: 8
Contains the JES job ID
The value is NONE if the address space associated with the record was not started under JES and has not used the subsystem interface to dynamically acquire a JES job ID, as described below.
Servers and other address spaces may request a job ID later even if 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 JES allows use of any of its services, such as 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.
Length: 17
Contains the CPU Time in the format of SSSSSSSSS.MMMMMM.
S indicates seconds and M indicates microseconds.
This is the total task time (TCB) used by all jobs in the address space (the same value returned by the z/OS DISPLAY command)
There is no direct relationship between the value of word ten and the value of word thirteen. 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 multi-step jobs that are in the second or subsequent step, the values probably differ greatly.
Note: The value is NONE if the data is unavailable for any reason.
Length: 1
Contains a value indicating whether the address space is associated with USS; O if yes and N if no.
Length: 10
Contains the total number of auxiliary storage (paging space) slots used by the address space. Each slot is 4096 bytes, or 4 KB.
Length: 10
Contains the total number of real storage frames that are in the private region used by the address space. Each frame is 4096 bytes, or 4 KB.
Length: 10
Contains the total number of expanded storage pages 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 will always contain zeros.
Length: 8
Contains the USERID associated with the address space. When no USERID is available, this field contains the value NONE.
Note: In the case of a multi-user address space, the USERID reflects the USERID that was initially associated with the address space/job.
Length: 10
Contains the number of bytes of CSA associated with the address space. Contains the value NONE if Common Storage Tracking is inactive.
Length: 10
Contains the number of bytes of ECSA associated with the address space. Contains the value NONE if Common Storage Tracking is inactive.
Length: 10
Contains the number of bytes of SQA associated with the address space. Contains the value NONE if Common Storage Tracking is inactive.
Length: 10
Contains the number of bytes of ESQA associated with the address space. Contains the value NONE if Common Storage Tracking is inactive.
Length: 10
Contains the CPU Time in the format of SSSSSSSSS.MMMMMM.
S indicates seconds and M indicates microseconds.
This is the total CPU time (TCB + SRB) used by all enclaves 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. It is managed separately from the address space it runs in. CPU and I/O resources associated with processing the transaction are managed by the transaction's performance goal and reported to the transaction.
The value is NONE if the data is unavailable for any reason.
Notice that the time format given for CPU Time and Elapsed Time deviates from that displayed in OPSVIEW option 3.1. Since OPSTATUS is intended for automation rather than for producing displayable records, the format shown here reduces the need to convert time data for use in automation. Times 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)
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |