Thanks Rob. That is the answer I suspected was the case.
I'll let my colleague know it is WAD.
Peter
-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Rob
Scott
Sent: Sunday, November 22, 2020 6:27 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Why does SDSF ST only show current JESPLEX jobs? [EXTERNAL]
EXTERNAL EMAIL
There are displays in SDSF that are from a system/sysplex viewpoint (eg DA,
LPA,SYS) and others that are from JES/MAS view (eg H, O and ST).
The data for ST is gotten from a SSI call to the JES that the user is running
under ( or has specified at SDSF session start).
There are options in SDSF to restrict sysplex views to only include systems
that are within the current MAS, and that is called "jesplex scoping".
There is not an option to perform the same thing in reverse, and it is highly
unlikely that there ever will be.
Rob Scott
Rocket Software
On 21 Nov 2020 13:32, "Feller, Paul"
<000002fc94e14c43-dmarc-requ...@listserv.ua.edu> wrote:
EXTERNAL EMAIL
Peter the famous bottom line is the SYSNAME=* gives you a view of the world
that SDSF/SDSFAUX knows about. If SYSNAME is blank then you only see the stuff
the lpar you are logged on to. The other thing is SYSNAME is not support on
every screen in SDSF. The "ST" screen is one of these screens that does not
support SYSNAME.
The following displays are from a z/OS 2.3 system.
This is with SYSNAME of "*". The display shows all the lpars that the
SDSF/SDSFAUX task know about.
SDSF SYS DISPLAY PR01 (ALL) LINE 1-11 (11)
COMMAND INPUT ===> SCROLL ===> CSR
PREFIX=* DEST=(ALL) OWNER=* SYSNAME=*
NP SYSNAME SysLevel CPU% SIO Aux% CSA% SQA% ECSA% ESQA% UIC Spool%
CM01 z/OS 02.03 1 0 0 11 39 19 35 65535 46
CM02 z/OS 02.03 1 0 0 11 39 18 33 65535 46
PR01 z/OS 02.03 51 28265 0 37 62 65 83 65535 46
PR02 z/OS 02.03 35 21400 0 22 47 57 110 65535 46
PR03 z/OS 02.03 43 26490 0 37 46 53 50 65535 46
PR05 z/OS 02.03 3 0 0 46 45 44 41 65535 46
SP01 z/OS 02.03 7 15 0 24 33 15 37 65535 7
SP02 z/OS 02.03 1 0 0 12 28 18 33 65535 7
TS01 z/OS 02.03 53 108130 0 44 62 60 67 65535 48
TS02 z/OS 02.03 39 76640 0 24 46 60 69 65535 48
TS03 z/OS 02.03 28 2260 0 38 48 53 46 65535 48
When SYSNAME is blank you only see a view from the lpar you are logged onto.
SDSF SYS DISPLAY PR01 PR01 LINE 1-1 (1)
COMMAND INPUT ===> SCROLL ===> CSR
PREFIX=* DEST=(ALL) OWNER=* SYSNAME=
NP SYSNAME SysLevel CPU% SIO Aux% CSA% SQA% ECSA% ESQA% UIC Spool%
PR01 z/OS 02.03 48 35020 0 37 62 65 82 65535 46
Thanks..
Paul Feller
GTS Mainframe Technical Support
-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of
Farley, Peter x23353
Sent: Friday, November 20, 2020 3:16 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Why does SDSF ST only show current JESPLEX jobs? [EXTERNAL]
Thanks Lizette, but I always have DISPLAY turned on so I know what I told SDSF
to do. Here are my usual settings (user id PREFIX faked):
SDSF STATUS DISPLAY ALL CLASSES LINE 1-19 (19)
COMMAND INPUT ===> SCROLL ===> CSR
PREFIX=MYUSER* DEST=(ALL) OWNER=* SYSNAME=*
Our system PARMS libraries are restricted access (reasons for that are lost in
the mists of history; anyway I get a 913 abend trying to browse them) so I
cannot tell you what our ISFPRMxx settings may be.
Peter
-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of
Lizette Koehler
Sent: Friday, November 20, 2020 3:36 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Why does SDSF ST only show current JESPLEX jobs?
So this could be due to ISFPRMxx member restricting your ability to list
You could have a PREFIX or DEST or SYSNAME turned on - I recommend doing a SET
DISPLAY ON and see what your have for filtering.
Lizette
-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of
Farley, Peter x23353
Sent: Friday, November 20, 2020 12:19 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Why does SDSF ST only show current JESPLEX jobs?
A colleague asked me today if there was an error in SDSF because from his ISPF
/ SDSF DA screen he can see all active jobs with selected names (e.g., using
PREFIX or a SELECT command) across the entire SYSPLEX.
However, using his ISPF / SDSF ST screen he can only see those selected job
names which are running in the JESPLEX to which he is logged on. We have two
JESPLEX instances with different LPAR's in each one.
I confirmed the behavior he reported. My ISPF / SDSF ST screen behaves the
same as his, and my ISPF / SDSF DA screen does too.
At this point I am just curious, is this WAD or an SDSF bug?
TIA for any info or RTFM you can provide.
Peter
--
This message and any attachments are intended only for the use of the addressee
and may contain information that is privileged and confidential. If the reader
of the message is not the intended recipient or an authorized representative of
the intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication
in error, please notify us immediately by e-mail and delete the message and any
attachments from your system.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
