OAS is counted this way:
DO J = 1 TO ASVTMAXU; /* Scan all the ASCBs. @P9A*/
ASCBADDR = ASVTENTY(J); /* Get the ASCB pointer from the
current ASVT entry. @P9A*/
IF ASVTAVAL(J) = OFF
& ASCBADDR ¬= ZERO
& ASSBOASB ¬= ZERO
THEN /* If the ASID for this entry is
assigned (i.e. valid) -and- the
ASCB pointer is not zero (¬0)
-and- this is an OpenMVS Address
Space then... @PHC*/
OASNUM = OASNUM + ONE; /* ...count the Address Space. @P9A*/
ELSE; /* Otherwise, do nothing. @P9A*/
END; /* End for ASVT scan. @P9A*/
JOBS is counted this way:
SELECT; /* Select on type of CSCB */
WHEN ((CHTRKID= CHJOBID) | /* JOB CSCB @L3C*/
(CHTRKID = CHSASID) | /* Started Task Mount or
System Address Space @L3C*/
(CHTRKID = CHATXPID)) /* ATX CSCB @L3C*/
DO; /* @L3C*/
/* Started tasks including System address space */
IF (CHVCD = STARTJOB)| /* FOR STARTED TASKS
INCLUDING SYSTEM ADDR SPACES @G381P2E*/
(CHVCD = MOUNTJOB) THEN /* OR MOUNTS @L3C*/
DO; /* DO FOR STARTS,MOUNTS,SYSTEM ADR @G381P2E*/
IF CHTRKID=CHSASID THEN /* SYSTEM ADDR SPC @G381P2E*/
SYSASNUM=SYSASNUM+ONE; /* INCREASE COUNT @G381P2E*/
ELSE
STRMTNUM=STRMTNUM+ONE; /* INCREASE COUNT @G381P2E*/
END; /* END FOR STARTS,MOUNTS,SYSTEM ADDR SPC @G381P2E*/
/* Jobs and ATXs */
ELSE
JOBNUM=JOBNUM+ONE; /* INCREASE COUNT @G381P2E*/
END; /* END FOR JOBS, STARTED TASKS,
MOUNTS, AND SYSTEM ADDRESS
SPACES @G381P2E*/
WHEN (CHTRKID=CHINITID) /* Started Initiator CSCB @L3C*/
INITNUM = INITNUM +ONE; /*YES,INCREMENT COUNTER*/
WHEN (CHTRKID=CHTSID) /* TSO CSCB @L3C*/
TSNUM = TSNUM +ONE; /* YES, INCREMENT COUNTER */
OTHERWISE; /* Other CSCBs not accountable @L3A*/
END; /* End select on type of CSCB @L3A*/
So when something is running in a BPXAS initiator, that is counted
as a JOB.
This code is called for every CSCB. While there is a job running
in an initiator or BPXAS address space, the address space has
has two CSCBs (one for the initiator, and one for the job).
D A,ALL will show you everything (more than D A,L). For
initiator/BPXAS address spaces that are running a job, D A,ALL
will show two entries for the same ASID (one for each CSCB).
For BPXAS address spaces, both will be marked O (dubbed).
But OAS will count that address space only once.
Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp.
Poughkeepsie NY
IBM Mainframe Discussion List <[email protected]> wrote on
02/23/2017 08:08:28 AM:
> From: Peter Hunkeler <[email protected]>
> To: [email protected]
> Date: 02/23/2017 02:09 PM
> Subject: IEE114I header line summary figures - what do they mean
exactly?
> Sent by: IBM Mainframe Discussion List <[email protected]>
>
> In response to a "D A,L" the system displays message IEE114I. In the
> header part, messages shows some totals as "JOBS", "M/S", "INITS",
> "OAS" (and others which I'm not interested in).
>
>
> After the heading information about active address spaces is show;
> two per line. The type is shown as "Jx", "Ax", "Sx", or "Tx", where
> "x" is "O" if the address space is dubbed, and blank if not.
>
>
> The manual is a bit fuzzy with some parts.
>
>
> I would have expected the "JOBS" total to be equal to the number of
> address spaces shown with type "Jx". However, I see "JOBS" to be much
higher.
>
> The difference between "JOBS" and "INITS" is the number of idle
> initiators (both JES and WLM managed ones). We do not use APPC. But
> what about the difference between "JOBS" and type "Jx" address spaces
shown?
>
>
>
> I would have expected the "OAS" to be equal to the number of address
> spaces shown with type "yO" (where "y" is any of "J", "A", "S",
> "T"). However, I see "OAS" to be much higher.
>
> Is the difference the number of idle BPXAS initiators?
>
>
>
> Since we do not use APPC, are type "AO" address spaces all UNIX
> process running in BPXAS initiator address spaces?
>
>
> Does anyone have some insight?
>
> --
> Peter Hunkeler
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
