Re: Why does SDSF ST only show current JESPLEX jobs? [EXTERNAL]
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 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" <02fc94e14c43-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.031 00 11 391935 65535 46 CM02 z/OS 02.031 00 11 391833 65535 46 PR01 z/OS 02.03 51 282650 37 626583 65535 46 PR02 z/OS 02.03 35 214000 22 4757 110 65535 46 PR03 z/OS 02.03 43 264900 37 465350 65535 46 PR05 z/OS 02.033 00 46 454441 65535 46 SP01 z/OS 02.037 150 24 331537 65535 7 SP02 z/OS 02.031 00 12 281833 65535 7 TS01 z/OS 02.03 53 1081300 44 626067 65535 48 TS02 z/OS 02.03 39 766400 24 466069 65535 48 TS03 z/OS 02.03 2822600 38 485346 65535 48 When SYSNAME is blank you only see a view from the lpar you are logged onto. SDSF SYS DISPLAY PR01 PR01LINE 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 350200 37 626582 65535 46 Thanks.. Paul Feller GTS Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List 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 CLASSESLINE 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 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 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 i
Re: Why does SDSF ST only show current JESPLEX jobs? [EXTERNAL]
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" <02fc94e14c43-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.031 00 11 391935 65535 46 CM02 z/OS 02.031 00 11 391833 65535 46 PR01 z/OS 02.03 51 282650 37 626583 65535 46 PR02 z/OS 02.03 35 214000 22 4757 110 65535 46 PR03 z/OS 02.03 43 264900 37 465350 65535 46 PR05 z/OS 02.033 00 46 454441 65535 46 SP01 z/OS 02.037 150 24 331537 65535 7 SP02 z/OS 02.031 00 12 281833 65535 7 TS01 z/OS 02.03 53 1081300 44 626067 65535 48 TS02 z/OS 02.03 39 766400 24 466069 65535 48 TS03 z/OS 02.03 2822600 38 485346 65535 48 When SYSNAME is blank you only see a view from the lpar you are logged onto. SDSF SYS DISPLAY PR01 PR01LINE 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 350200 37 626582 65535 46 Thanks.. Paul Feller GTS Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List 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 CLASSESLINE 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 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 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 attach
Re: Why does SDSF ST only show current JESPLEX jobs? [EXTERNAL]
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.031 00 11 391935 65535 46 CM02 z/OS 02.031 00 11 391833 65535 46 PR01 z/OS 02.03 51 282650 37 626583 65535 46 PR02 z/OS 02.03 35 214000 22 4757 110 65535 46 PR03 z/OS 02.03 43 264900 37 465350 65535 46 PR05 z/OS 02.033 00 46 454441 65535 46 SP01 z/OS 02.037 150 24 331537 65535 7 SP02 z/OS 02.031 00 12 281833 65535 7 TS01 z/OS 02.03 53 1081300 44 626067 65535 48 TS02 z/OS 02.03 39 766400 24 466069 65535 48 TS03 z/OS 02.03 2822600 38 485346 65535 48 When SYSNAME is blank you only see a view from the lpar you are logged onto. SDSF SYS DISPLAY PR01 PR01LINE 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 350200 37 626582 65535 46 Thanks.. Paul Feller GTS Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List 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 CLASSESLINE 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 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 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 IB
Re: Why does SDSF ST only show current JESPLEX jobs?
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 CLASSESLINE 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 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 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
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 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Why does SDSF ST only show current JESPLEX jobs?
Yes, we do. Why is lost in the mists of history. It's been that way since I came here, and the folks who set that up are long gone, so no one left to ask why. Peter -Original Message- From: IBM Mainframe Discussion List On Behalf Of R.S. Sent: Friday, November 20, 2020 2:40 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Why does SDSF ST only show current JESPLEX jobs? W dniu 20.11.2020 o 20:19, Farley, Peter x23353 pisze: > 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. So, you have multiple JESplexes within SYSPLEX? -- 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
Re: Why does SDSF ST only show current JESPLEX jobs? [EXTERNAL]
Both my colleague and I had SYSNAME * set in all of these tests. That is the default here. I don't know why SYSNAME would be "authorized" specially, but in any case in this shop ordinary programmers can all use the "SYSNAME whatever" command to restrict SDSF displays to a particular LPAR. Of course we can only browse jobs in SDSF whose job names do not begin with our TSO user id's, not issue any command that affects those jobs. We also have no OPERCMD authority at all, even for DISPLAY commands. I suspect that restriction goes back decades before I came here 20 years ago, no doubt due to some errant programmer of the day not playing by the rules or being careless. Impossible to change at this point. Peter -Original Message- From: IBM Mainframe Discussion List On Behalf Of Feller, Paul Sent: Friday, November 20, 2020 2:35 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Why does SDSF ST only show current JESPLEX jobs? [EXTERNAL] EXTERNAL EMAIL Peter, I'm assuming you are using the SYSNAME then it is not supported on the ST screen. So WAD. I think the HELP screen for SYSNAME needs to be updated. I know I've used it on the SYS panel. This is on a z/OS 2.3 system. HELP: SYSNAME Command Panel 1 of 2 COMMAND INPUT ===> Purpose: Specify the systems in the sysplex that are included on the CK, DA, ENC, INIT, LI, NC, NS, NO, PR, PS, PUN, RDR, RM and SO panels. You must be authorized to use this command. Where used: Any SDSF panel. Format: SYSNAME (system-name|?) The parameters are explained on the panels that follow. Examples: SYSNAME SYS1 - Displays only data for SYS1 on the affected SDSF panels. SYSN - Displays only data for the system you are logged on to. Thanks.. Paul Feller GTS Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List On Behalf Of Farley, Peter x23353 Sent: Friday, November 20, 2020 1:19 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Why does SDSF ST only show current JESPLEX jobs? [EXTERNAL] 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
Re: Why does SDSF ST only show current JESPLEX jobs?
W dniu 20.11.2020 o 20:19, Farley, Peter x23353 pisze: 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. So, you have multiple JESplexes within SYSPLEX? -- Radoslaw Skorupka Lodz, Poland == Jeśli nie jesteś adresatem tej wiadomości: - powiadom nas o tym w mailu zwrotnym (dziękujemy!), - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś na dysku). Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać karze. mBank S.A. z siedzibą w Warszawie, ul. Prosta 18, 00-850 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2020 r. wynosi 169.401.468 złotych. If you are not the addressee of this message: - let us know by replying to this e-mail (thank you!), - delete this message permanently (including all the copies which you have printed out or saved). This message may contain legally protected information, which may be used exclusively by the addressee.Please be reminded that anyone who disseminates (copies, distributes) this message or takes any similar action, violates the law and may be penalised. mBank S.A. with its registered office in Warsaw, ul. Prosta 18, 00-850 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital City of Warsaw, 12th Commercial Division of the National Court Register, KRS 025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 169.401.468 as at 1 January 2020. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Why does SDSF ST only show current JESPLEX jobs? [EXTERNAL]
Peter, I'm assuming you are using the SYSNAME then it is not supported on the ST screen. So WAD. I think the HELP screen for SYSNAME needs to be updated. I know I've used it on the SYS panel. This is on a z/OS 2.3 system. HELP: SYSNAME Command Panel 1 of 2 COMMAND INPUT ===> Purpose: Specify the systems in the sysplex that are included on the CK, DA, ENC, INIT, LI, NC, NS, NO, PR, PS, PUN, RDR, RM and SO panels. You must be authorized to use this command. Where used: Any SDSF panel. Format: SYSNAME (system-name|?) The parameters are explained on the panels that follow. Examples: SYSNAME SYS1 - Displays only data for SYS1 on the affected SDSF panels. SYSN - Displays only data for the system you are logged on to. Thanks.. Paul Feller GTS Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List On Behalf Of Farley, Peter x23353 Sent: Friday, November 20, 2020 1:19 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Why does SDSF ST only show current JESPLEX jobs? [EXTERNAL] 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 -- Please note: This message originated outside your organization. Please use caution when opening links or attachments. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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
