Re: SDSF JS command cross-sysplex [EXTERNAL]

2022-08-12 Thread Rob Scott
KB

Much appreciated,  I will let the team know.

You will be pleased to know i have a long backlog of enhancement ideas.

Rob

Sent from a field in Hampshire

From: IBM Mainframe Discussion List  on behalf of 
kekronbekron <02dee3fcae33-dmarc-requ...@listserv.ua.edu>
Sent: Friday, August 12, 2022 3:06:07 AM
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: SDSF JS command cross-sysplex [EXTERNAL]

EXTERNAL EMAIL




Rob,

Just want to say, I think this is a great addition to SDSF.
You folks at Rocket are really doing SDSF development right.
Seamlessly adding in new functionality, without a freakshow layer.

- KB

--- Original Message ---
On Thursday, August 11th, 2022 at 9:58 PM, Rob Scott 
 wrote:


> The SDSF "JS" action does not get sent to remote systems in the sysplex. It 
> reads data from a special JES2 dataset for the job locally.
>
> A possible reason for no data being shown is that the job on the remote 
> system is not in the same MAS.
>
> Rob Scott
> Rocket Software
>
> Sent from Samsung Mobile on O2
> Get Outlook for Androidhttps://aka.ms/AAb9ysghttps://aka.ms/AAb9ysg>
>
> 
> From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU on behalf of 
> Feller, Paul 02fc94e14c43-dmarc-requ...@listserv.ua.edu
>
> Sent: Thursday, August 11, 2022 4:12:37 PM
> To: IBM-MAIN@LISTSERV.UA.EDU IBM-MAIN@LISTSERV.UA.EDU
>
> Subject: Re: SDSF JS command cross-sysplex [EXTERNAL]
>
> EXTERNAL EMAIL
>
>
>
>
>
> Keith, I'm assuming you are talking about looking at job on a different lpar 
> in the same sysplex, also part of the same JES MAS.
>
> This is a display of a job running on a different lpars then the one I was 
> logged on to. This is a z/OS 2.4 environment.
>
> SDSF JOB STEP DISPLAY - JOB DTSTM01D (JOB24586) SMF LINE 1-19 (19)
> COMMAND INPUT ===> SCROLL ===> CSR
>
> PREFIX=* DEST=(ALL) OWNER=* SYSNAME=
> NP STEPNAME ProcStep Pgm-Name Step-CC AbendRsn StepNum Elapsed CPU-Time 
> SRB-Time
> STEP000 TMSCOPY TMSCOPY CC  1 0:00:17.79 0:00:02.73 0:00:00.46
> STEP005 STEP001 TMSDATA CC  2 0:00:12.71 0:00:00.71 0:00:00.23
> STEP005 STEP002 IDCAMS CC  3 0:00:02.08 0:00:00.41 0:00:00.01
> STEP003 SAS SAS CC  4 0:01:14.04 0:00:29.98 0:00:00.58
> STEP005 STEP004 IKJEFT01 CC  5 0:00:00.06 0:00:00.02 0:00:00.00
> STEP005 STEP04A TMSUPDTE CC  6 0:00:01.08 0:00:00.14 0:00:00.01
> STEP005 STEP005 IKJEFT01 CC  7 0:00:00.05 0:00:00.02 0:00:00.00
> STEP005 STEP05A TMSUDSNB CC  8 0:00:01.22 0:00:00.17 0:00:00.02
> STEP005 STEP006 IKJEFT01 CC 0001 9 0:00:00.05 0:00:00.02 0:00:00.00
> STEP005 STEP06A TMSUPDTE FLUSH 10
> STEP005 STEP007 IKJEFT01 CC 0001 11 0:00:00.05 0:00:00.02 0:00:00.00
> STEP005 STEP07A TMSUDSNB FLUSH 12
> STEP010 TMSEXPDT TMSEXPDT CC  13 0:12:12.33 0:02:45.00 0:00:09.36
> STEP010 EARL EARL CC  14 0:00:00.55 0:00:00.04 0:00:00.00
> STEP020 TMSCTLG TMSCTLG CC  15 0:20:46.39 0:01:27.02 0:00:03.23
> STEP020 EARL EARL CC  16 0:00:00.93 0:00:00.34 0:00:00.01
> STEP030 TMSCYCLE TMSCYCLE CC  17 0:00:06.49 0:00:00.49 0:00:00.07
> STEP030 EARL EARL CC  18 0:00:00.58 0:00:00.04 0:00:00.00
> STEP040 TMSCLEAN TMSCLEAN ACTIVE 19
>
>
> F SDSF,D JES
> ISF304I Modify DISPLAY command accepted.
> ISF351I SDSF JES Subsystems
> Sysname JES Version Status
> CM01 JES2 z/OS 2.4 ACTIVE
> PR05 JES2 z/OS 2.4 ACTIVE
> CM02 JES2 z/OS 2.4 ACTIVE
> PR03 JES2 z/OS 2.4 ACTIVE
> PR02 JES2 z/OS 2.4 ACTIVE
> PR01 JES2 z/OS 2.4 ACTIVE
>
>
> Paul Feller
> GTS Mainframe Technical Support
>
> -Original Message-
> From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On Behalf Of 
> Keith Gooding
>
> Sent: Thursday, August 11, 2022 9:34 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: SDSF JS command cross-sysplex [EXTERNAL]
>
> I found that the SDSF ‘JS’ (job steps) command issued from the SDSF panels or 
> via the REXX API produces no output if the target job is running on a 
> different system in the sysplex. This is with z/os 2.5. On a 2.3 system the 
> same happens except that the heading says ‘no job steps found’ (or similar 
> message).
>
> Is anyone able to use JS cross-system or is this working as designed?. I am 
> able to use others commands such as JT (Job Tasks) so I know that the SDSF 
> address spaces are talking to each other.
>
> Keith Gooding
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> --
> Please no

Re: SDSF JS command cross-sysplex [EXTERNAL]

2022-08-11 Thread kekronbekron
Rob,

Just want to say, I think this is a great addition to SDSF.
You folks at Rocket are really doing SDSF development right.
Seamlessly adding in new functionality, without a freakshow layer.

- KB

--- Original Message ---
On Thursday, August 11th, 2022 at 9:58 PM, Rob Scott 
 wrote:


> The SDSF "JS" action does not get sent to remote systems in the sysplex. It 
> reads data from a special JES2 dataset for the job locally.
>
> A possible reason for no data being shown is that the job on the remote 
> system is not in the same MAS.
>
> Rob Scott
> Rocket Software
>
> Sent from Samsung Mobile on O2
> Get Outlook for Androidhttps://aka.ms/AAb9ysg
>
> 
> From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU on behalf of 
> Feller, Paul 02fc94e14c43-dmarc-requ...@listserv.ua.edu
>
> Sent: Thursday, August 11, 2022 4:12:37 PM
> To: IBM-MAIN@LISTSERV.UA.EDU IBM-MAIN@LISTSERV.UA.EDU
>
> Subject: Re: SDSF JS command cross-sysplex [EXTERNAL]
>
> EXTERNAL EMAIL
>
>
>
>
>
> Keith, I'm assuming you are talking about looking at job on a different lpar 
> in the same sysplex, also part of the same JES MAS.
>
> This is a display of a job running on a different lpars then the one I was 
> logged on to. This is a z/OS 2.4 environment.
>
> SDSF JOB STEP DISPLAY - JOB DTSTM01D (JOB24586) SMF LINE 1-19 (19)
> COMMAND INPUT ===> SCROLL ===> CSR
>
> PREFIX=* DEST=(ALL) OWNER=* SYSNAME=
> NP STEPNAME ProcStep Pgm-Name Step-CC AbendRsn StepNum Elapsed CPU-Time 
> SRB-Time
> STEP000 TMSCOPY TMSCOPY CC  1 0:00:17.79 0:00:02.73 0:00:00.46
> STEP005 STEP001 TMSDATA CC  2 0:00:12.71 0:00:00.71 0:00:00.23
> STEP005 STEP002 IDCAMS CC  3 0:00:02.08 0:00:00.41 0:00:00.01
> STEP003 SAS SAS CC  4 0:01:14.04 0:00:29.98 0:00:00.58
> STEP005 STEP004 IKJEFT01 CC  5 0:00:00.06 0:00:00.02 0:00:00.00
> STEP005 STEP04A TMSUPDTE CC  6 0:00:01.08 0:00:00.14 0:00:00.01
> STEP005 STEP005 IKJEFT01 CC  7 0:00:00.05 0:00:00.02 0:00:00.00
> STEP005 STEP05A TMSUDSNB CC  8 0:00:01.22 0:00:00.17 0:00:00.02
> STEP005 STEP006 IKJEFT01 CC 0001 9 0:00:00.05 0:00:00.02 0:00:00.00
> STEP005 STEP06A TMSUPDTE FLUSH 10
> STEP005 STEP007 IKJEFT01 CC 0001 11 0:00:00.05 0:00:00.02 0:00:00.00
> STEP005 STEP07A TMSUDSNB FLUSH 12
> STEP010 TMSEXPDT TMSEXPDT CC  13 0:12:12.33 0:02:45.00 0:00:09.36
> STEP010 EARL EARL CC  14 0:00:00.55 0:00:00.04 0:00:00.00
> STEP020 TMSCTLG TMSCTLG CC  15 0:20:46.39 0:01:27.02 0:00:03.23
> STEP020 EARL EARL CC  16 0:00:00.93 0:00:00.34 0:00:00.01
> STEP030 TMSCYCLE TMSCYCLE CC  17 0:00:06.49 0:00:00.49 0:00:00.07
> STEP030 EARL EARL CC  18 0:00:00.58 0:00:00.04 0:00:00.00
> STEP040 TMSCLEAN TMSCLEAN ACTIVE 19
>
>
> F SDSF,D JES
> ISF304I Modify DISPLAY command accepted.
> ISF351I SDSF JES Subsystems
> Sysname JES Version Status
> CM01 JES2 z/OS 2.4 ACTIVE
> PR05 JES2 z/OS 2.4 ACTIVE
> CM02 JES2 z/OS 2.4 ACTIVE
> PR03 JES2 z/OS 2.4 ACTIVE
> PR02 JES2 z/OS 2.4 ACTIVE
> PR01 JES2 z/OS 2.4 ACTIVE
>
>
> Paul Feller
> GTS Mainframe Technical Support
>
> -Original Message-
> From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On Behalf Of 
> Keith Gooding
>
> Sent: Thursday, August 11, 2022 9:34 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: SDSF JS command cross-sysplex [EXTERNAL]
>
> I found that the SDSF ‘JS’ (job steps) command issued from the SDSF panels or 
> via the REXX API produces no output if the target job is running on a 
> different system in the sysplex. This is with z/os 2.5. On a 2.3 system the 
> same happens except that the heading says ‘no job steps found’ (or similar 
> message).
>
> Is anyone able to use JS cross-system or is this working as designed?. I am 
> able to use others commands such as JT (Job Tasks) so I know that the SDSF 
> address spaces are talking to each other.
>
> Keith Gooding
> --
> 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
>
> 
> Rocket Software, Inc. and subsidiaries ¦ 77 Fourth Avenue, Waltham MA 02451 ¦ 
> Main Office 

Re: SDSF JS command cross-sysplex

2022-08-11 Thread Keith Gooding
Mark. 
Sorry for the confusing terminology. I meant cross-system within the same 
sysplex. As I have already posted, the problem seems to be the lack of a 
journal dataset for STCs - it is working OK for journaled job classes. 

A conversion to SDSF RACF security was involved in the migration but I am 
fairly sure that security is not related to the problem. 

Keith

> On 11 Aug 2022, at 19:37, Mark Zelden  wrote:
> 
> On Thu, 11 Aug 2022 13:32:46 -0500, Mark Zelden  wrote:
> 
>>> On Thu, 11 Aug 2022 15:34:20 +0100, Keith Gooding  wrote:
>>> 
>>> I found that the SDSF ‘JS’ (job steps) command issued from the SDSF panels 
>>> or via the REXX API  produces no output if the target job is running on a 
>>> different system in the sysplex. This is with z/os 2.5. On a 2.3 system the 
>>> same happens except that the heading says ‘no job steps found’ (or similar 
>>> message).
>>> 
>>> Is anyone able to use JS cross-system or is this working as designed?.  I 
>>> am able to use others commands such as JT (Job Tasks) so I know that the 
>>> SDSF address spaces are talking to each other.
>>> 
>>> Keith Gooding
>> 
>> Unfortunately I am getting a really late start on 2.5 and can't test this 
>> yet.  Not only that, this 
>> migration will be a pain because I have 9 sysplexes using ISFPARMs still.  
>> Which brings me to 
>> my point...   Was a migration from ISFPARMs involved with upgrading to 2.5 
>> and could
>> this just be a security related problem? I assume both LPARs are in the 
>> same JESplex.
>> Works fine under z/OS 2.4.  
>> 
>> 
>> Best Regards,
>> 
>> Mark
>> --
>> Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
>> ITIL v3 Foundation Certified
>> mailto:m...@mzelden.com
>> Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
>> 
> 
> I just noticed (and caught up with messages) - your subject says 
> "cross-sysplex".   But
> your descriptions says "different system in the sysplex".   Which is it?  I 
> don't know how
> this could ever work cross-sysplex which implies JES2 is not shared.  As I 
> wrote, it
> works fine under z/OS 2.4.   
> 
> Best Regards,
> 
> Mark
> --
> Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
> ITIL v3 Foundation Certified
> mailto:m...@mzelden.com
> Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
> 
> --
> 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: SDSF JS command cross-sysplex

2022-08-11 Thread Mark Zelden
On Thu, 11 Aug 2022 13:32:46 -0500, Mark Zelden  wrote:

>On Thu, 11 Aug 2022 15:34:20 +0100, Keith Gooding  wrote:
>
>>I found that the SDSF ‘JS’ (job steps) command issued from the SDSF panels or 
>>via the REXX API  produces no output if the target job is running on a 
>>different system in the sysplex. This is with z/os 2.5. On a 2.3 system the 
>>same happens except that the heading says ‘no job steps found’ (or similar 
>>message).
>>
>>Is anyone able to use JS cross-system or is this working as designed?.  I am 
>>able to use others commands such as JT (Job Tasks) so I know that the SDSF 
>>address spaces are talking to each other.
>>
>>Keith Gooding
>
>Unfortunately I am getting a really late start on 2.5 and can't test this yet. 
> Not only that, this 
>migration will be a pain because I have 9 sysplexes using ISFPARMs still.  
>Which brings me to 
>my point...   Was a migration from ISFPARMs involved with upgrading to 2.5 and 
>could
>this just be a security related problem? I assume both LPARs are in the 
>same JESplex.
>Works fine under z/OS 2.4.  
>
>
>Best Regards,
>
>Mark
>--
>Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
>ITIL v3 Foundation Certified
>mailto:m...@mzelden.com
>Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
>

I just noticed (and caught up with messages) - your subject says 
"cross-sysplex".   But
your descriptions says "different system in the sysplex".   Which is it?  I 
don't know how
this could ever work cross-sysplex which implies JES2 is not shared.  As I 
wrote, it
works fine under z/OS 2.4.   

Best Regards,

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
ITIL v3 Foundation Certified
mailto:m...@mzelden.com
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: SDSF JS command cross-sysplex [EXTERNAL]

2022-08-11 Thread Keith Gooding
Got it. The ‘special dataset’ is presumably $JOURNAL. I found that I had only 
tested with STCs. It works ok for JOBs where the jobclass has JOURNAL=Yes. It 
does not seem possible to set JOURNSL=YES for STCs. Back to the drawing board.

Keith

> On 11 Aug 2022, at 19:06, Keith Gooding  wrote:
> 
> Thank you Rob and Paul. At least I know that it should work. In fact I think 
> it *did* once work in the same sysplex at z/os 2.4 but I cannot be 100% sure.
> 
> The systems are in the same MAS (2 systems sharing a JES2 spool and 
> checkpoint). Are there any instructions in the SDSF configuration that I may 
> have missed ? . Should I open a case with IBM ?
> 
> Keith
> 
>> On 11 Aug 2022, at 17:28, Rob Scott  wrote:
>> 
>> The SDSF "JS" action does not get sent to remote systems in the sysplex. It 
>> reads data from a special JES2 dataset for the job locally.
>> 
>> A possible reason for no data being shown is that the job on the remote 
>> system is not in the same MAS.
>> 
>> Rob Scott
>> Rocket Software
>> 
>> Sent from Samsung Mobile on O2
>> Get Outlook for Android<https://aka.ms/AAb9ysg>
>> 
>> From: IBM Mainframe Discussion List  on behalf of 
>> Feller, Paul <000002fc94e14c43-dmarc-requ...@listserv.ua.edu>
>> Sent: Thursday, August 11, 2022 4:12:37 PM
>> To: IBM-MAIN@LISTSERV.UA.EDU 
>> Subject: Re: SDSF JS command cross-sysplex [EXTERNAL]
>> 
>> EXTERNAL EMAIL
>> 
>> 
>> 
>> 
>> 
>> Keith, I'm assuming you are talking about looking at job on a different lpar 
>> in the same sysplex, also part of the same JES MAS.
>> 
>> This is a display of a job running on a different lpars then the one I was 
>> logged on to.  This is a z/OS 2.4 environment.
>> 
>> SDSF JOB STEP DISPLAY - JOB DTSTM01D (JOB24586) SMFLINE 1-19 (19)
>> COMMAND INPUT ===>SCROLL ===> CSR
>> PREFIX=*  DEST=(ALL)  OWNER=*  SYSNAME=
>> NP   STEPNAME ProcStep Pgm-Name Step-CCAbendRsn StepNum Elapsed 
>> CPU-TimeSRB-Time
>>STEP000  TMSCOPY  TMSCOPY  CC    1  0:00:17.79  
>> 0:00:02.73  0:00:00.46
>>STEP005  STEP001  TMSDATA  CC    2  0:00:12.71  
>> 0:00:00.71  0:00:00.23
>>STEP005  STEP002  IDCAMS   CC    3  0:00:02.08  
>> 0:00:00.41  0:00:00.01
>>STEP003  SAS  SAS  CC    4  0:01:14.04  
>> 0:00:29.98  0:00:00.58
>>STEP005  STEP004  IKJEFT01 CC    5  0:00:00.06  
>> 0:00:00.02  0:00:00.00
>>STEP005  STEP04A  TMSUPDTE CC    6  0:00:01.08  
>> 0:00:00.14  0:00:00.01
>>STEP005  STEP005  IKJEFT01 CC    7  0:00:00.05  
>> 0:00:00.02  0:00:00.00
>>STEP005  STEP05A  TMSUDSNB CC    8  0:00:01.22  
>> 0:00:00.17  0:00:00.02
>>STEP005  STEP006  IKJEFT01 CC 0001   9  0:00:00.05  
>> 0:00:00.02  0:00:00.00
>>STEP005  STEP06A  TMSUPDTE FLUSH10
>>STEP005  STEP007  IKJEFT01 CC 0001  11  0:00:00.05  
>> 0:00:00.02  0:00:00.00
>>STEP005  STEP07A  TMSUDSNB FLUSH12
>>STEP010  TMSEXPDT TMSEXPDT CC   13  0:12:12.33  
>> 0:02:45.00  0:00:09.36
>>STEP010  EARL EARL CC   14  0:00:00.55  
>> 0:00:00.04  0:00:00.00
>>STEP020  TMSCTLG  TMSCTLG  CC   15  0:20:46.39  
>> 0:01:27.02  0:00:03.23
>>STEP020  EARL EARL CC   16  0:00:00.93  
>> 0:00:00.34  0:00:00.01
>>STEP030  TMSCYCLE TMSCYCLE CC   17  0:00:06.49  
>> 0:00:00.49  0:00:00.07
>>STEP030  EARL EARL CC   18  0:00:00.58  
>> 0:00:00.04  0:00:00.00
>>STEP040  TMSCLEAN TMSCLEAN ACTIVE   19
>> 
>> 
>> F SDSF,D JES
>> ISF304I Modify DISPLAY command accepted.
>> ISF351I SDSF JES Subsystems
>> Sysname  JES  Version  Status
>> CM01 JES2 z/OS 2.4 ACTIVE
>> PR05 JES2 z/OS 2.4 ACTIVE
>> CM02 JES2 z/OS 2.4 ACTIVE
>> PR03 JES2 z/OS 2.4 ACTIVE
>> PR02 JES2 z/OS 2.4 ACTIVE
>> PR01 JES2 z/OS 2.4 ACTIVE
>> 
>> 
>> Paul Feller
>> GTS Mainframe Technical Support
>> 
>> -Original Message-
>> From: IBM Mainframe Discussion List  On Behalf Of 
>> Keith Gooding
>> Sent: Thursday, August 11, 2022 9:34 AM

Re: SDSF JS command cross-sysplex

2022-08-11 Thread Mark Zelden
On Thu, 11 Aug 2022 15:34:20 +0100, Keith Gooding  wrote:

>I found that the SDSF ‘JS’ (job steps) command issued from the SDSF panels or 
>via the REXX API  produces no output if the target job is running on a 
>different system in the sysplex. This is with z/os 2.5. On a 2.3 system the 
>same happens except that the heading says ‘no job steps found’ (or similar 
>message).
>
>Is anyone able to use JS cross-system or is this working as designed?.  I am 
>able to use others commands such as JT (Job Tasks) so I know that the SDSF 
>address spaces are talking to each other.
>
>Keith Gooding

Unfortunately I am getting a really late start on 2.5 and can't test this yet.  
Not only that, this 
migration will be a pain because I have 9 sysplexes using ISFPARMs still.  
Which brings me to 
my point...   Was a migration from ISFPARMs involved with upgrading to 2.5 and 
could
this just be a security related problem? I assume both LPARs are in the 
same JESplex.
Works fine under z/OS 2.4.  


Best Regards,

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
ITIL v3 Foundation Certified
mailto:m...@mzelden.com
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: SDSF JS command cross-sysplex [EXTERNAL]

2022-08-11 Thread Keith Gooding
Thank you Rob and Paul. At least I know that it should work. In fact I think it 
*did* once work in the same sysplex at z/os 2.4 but I cannot be 100% sure.

The systems are in the same MAS (2 systems sharing a JES2 spool and 
checkpoint). Are there any instructions in the SDSF configuration that I may 
have missed ? . Should I open a case with IBM ?

Keith

> On 11 Aug 2022, at 17:28, Rob Scott  wrote:
> 
> The SDSF "JS" action does not get sent to remote systems in the sysplex. It 
> reads data from a special JES2 dataset for the job locally.
> 
> A possible reason for no data being shown is that the job on the remote 
> system is not in the same MAS.
> 
> Rob Scott
> Rocket Software
> 
> Sent from Samsung Mobile on O2
> Get Outlook for Android<https://aka.ms/AAb9ysg>
> 
> From: IBM Mainframe Discussion List  on behalf of 
> Feller, Paul <02fc94e14c43-dmarc-requ...@listserv.ua.edu>
> Sent: Thursday, August 11, 2022 4:12:37 PM
> To: IBM-MAIN@LISTSERV.UA.EDU 
> Subject: Re: SDSF JS command cross-sysplex [EXTERNAL]
> 
> EXTERNAL EMAIL
> 
> 
> 
> 
> 
> Keith, I'm assuming you are talking about looking at job on a different lpar 
> in the same sysplex, also part of the same JES MAS.
> 
> This is a display of a job running on a different lpars then the one I was 
> logged on to.  This is a z/OS 2.4 environment.
> 
> SDSF JOB STEP DISPLAY - JOB DTSTM01D (JOB24586) SMFLINE 1-19 (19)
> COMMAND INPUT ===>SCROLL ===> CSR
> PREFIX=*  DEST=(ALL)  OWNER=*  SYSNAME=
> NP   STEPNAME ProcStep Pgm-Name Step-CCAbendRsn StepNum Elapsed 
> CPU-TimeSRB-Time
> STEP000  TMSCOPY  TMSCOPY  CC    1  0:00:17.79  
> 0:00:02.73  0:00:00.46
> STEP005  STEP001  TMSDATA  CC    2  0:00:12.71  
> 0:00:00.71  0:00:00.23
> STEP005  STEP002  IDCAMS   CC    3  0:00:02.08  
> 0:00:00.41  0:00:00.01
> STEP003  SAS  SAS  CC    4  0:01:14.04  
> 0:00:29.98  0:00:00.58
> STEP005  STEP004  IKJEFT01 CC    5  0:00:00.06  
> 0:00:00.02  0:00:00.00
> STEP005  STEP04A  TMSUPDTE CC    6  0:00:01.08  
> 0:00:00.14  0:00:00.01
> STEP005  STEP005  IKJEFT01 CC    7  0:00:00.05  
> 0:00:00.02  0:00:00.00
> STEP005  STEP05A  TMSUDSNB CC    8  0:00:01.22  
> 0:00:00.17  0:00:00.02
> STEP005  STEP006  IKJEFT01 CC 0001   9  0:00:00.05  
> 0:00:00.02  0:00:00.00
> STEP005  STEP06A  TMSUPDTE FLUSH10
> STEP005  STEP007  IKJEFT01 CC 0001  11  0:00:00.05  
> 0:00:00.02  0:00:00.00
> STEP005  STEP07A  TMSUDSNB FLUSH12
> STEP010  TMSEXPDT TMSEXPDT CC   13  0:12:12.33  
> 0:02:45.00  0:00:09.36
> STEP010  EARL EARL CC   14  0:00:00.55  
> 0:00:00.04  0:00:00.00
> STEP020  TMSCTLG  TMSCTLG  CC   15  0:20:46.39  
> 0:01:27.02  0:00:03.23
> STEP020  EARL EARL CC   16  0:00:00.93  
> 0:00:00.34  0:00:00.01
> STEP030  TMSCYCLE TMSCYCLE CC   17  0:00:06.49  
> 0:00:00.49  0:00:00.07
> STEP030  EARL EARL CC   18  0:00:00.58  
> 0:00:00.04  0:00:00.00
> STEP040  TMSCLEAN TMSCLEAN ACTIVE   19
> 
> 
> F SDSF,D JES
> ISF304I Modify DISPLAY command accepted.
> ISF351I SDSF JES Subsystems
> Sysname  JES  Version  Status
> CM01 JES2 z/OS 2.4 ACTIVE
> PR05 JES2 z/OS 2.4 ACTIVE
> CM02 JES2 z/OS 2.4 ACTIVE
> PR03 JES2 z/OS 2.4 ACTIVE
> PR02 JES2 z/OS 2.4 ACTIVE
> PR01 JES2     z/OS 2.4 ACTIVE
> 
> 
> Paul Feller
> GTS Mainframe Technical Support
> 
> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf Of 
> Keith Gooding
> Sent: Thursday, August 11, 2022 9:34 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: SDSF JS command cross-sysplex [EXTERNAL]
> 
> I found that the SDSF ‘JS’ (job steps) command issued from the SDSF panels or 
> via the REXX API  produces no output if the target job is running on a 
> different system in the sysplex. This is with z/os 2.5. On a 2.3 system the 
> same happens except that the heading says ‘no job steps found’ (or similar 
> message).
> 
> Is anyone able to use JS cross-system or is this working as designed?.  I am 
> able to use others commands such as JT (Job Tasks) so I know that the SDSF 
> address spaces are talking to each other.
> 
> Keith Gooding
> ---

Re: SDSF JS command cross-sysplex [EXTERNAL]

2022-08-11 Thread Rob Scott
The SDSF "JS" action does not get sent to remote systems in the sysplex. It 
reads data from a special JES2 dataset for the job locally.

A possible reason for no data being shown is that the job on the remote system 
is not in the same MAS.

Rob Scott
Rocket Software

Sent from Samsung Mobile on O2
Get Outlook for Android<https://aka.ms/AAb9ysg>

From: IBM Mainframe Discussion List  on behalf of 
Feller, Paul <02fc94e14c43-dmarc-requ...@listserv.ua.edu>
Sent: Thursday, August 11, 2022 4:12:37 PM
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: SDSF JS command cross-sysplex [EXTERNAL]

EXTERNAL EMAIL





Keith, I'm assuming you are talking about looking at job on a different lpar in 
the same sysplex, also part of the same JES MAS.

This is a display of a job running on a different lpars then the one I was 
logged on to.  This is a z/OS 2.4 environment.

SDSF JOB STEP DISPLAY - JOB DTSTM01D (JOB24586) SMFLINE 1-19 (19)
COMMAND INPUT ===>SCROLL ===> CSR
PREFIX=*  DEST=(ALL)  OWNER=*  SYSNAME=
NP   STEPNAME ProcStep Pgm-Name Step-CCAbendRsn StepNum Elapsed 
CPU-TimeSRB-Time
 STEP000  TMSCOPY  TMSCOPY  CC    1  0:00:17.79  
0:00:02.73  0:00:00.46
 STEP005  STEP001  TMSDATA  CC    2  0:00:12.71  
0:00:00.71  0:00:00.23
 STEP005  STEP002  IDCAMS   CC    3  0:00:02.08  
0:00:00.41  0:00:00.01
 STEP003  SAS  SAS  CC    4  0:01:14.04  
0:00:29.98  0:00:00.58
 STEP005  STEP004  IKJEFT01 CC    5  0:00:00.06  
0:00:00.02  0:00:00.00
 STEP005  STEP04A  TMSUPDTE CC    6  0:00:01.08  
0:00:00.14  0:00:00.01
 STEP005  STEP005  IKJEFT01 CC    7  0:00:00.05  
0:00:00.02  0:00:00.00
 STEP005  STEP05A  TMSUDSNB CC    8  0:00:01.22  
0:00:00.17  0:00:00.02
 STEP005  STEP006  IKJEFT01 CC 0001   9  0:00:00.05  
0:00:00.02  0:00:00.00
 STEP005  STEP06A  TMSUPDTE FLUSH10
 STEP005  STEP007  IKJEFT01 CC 0001  11  0:00:00.05  
0:00:00.02  0:00:00.00
 STEP005  STEP07A  TMSUDSNB FLUSH12
 STEP010  TMSEXPDT TMSEXPDT CC   13  0:12:12.33  
0:02:45.00  0:00:09.36
 STEP010  EARL EARL CC   14  0:00:00.55  
0:00:00.04  0:00:00.00
 STEP020  TMSCTLG  TMSCTLG  CC   15  0:20:46.39  
0:01:27.02  0:00:03.23
 STEP020  EARL EARL CC   16  0:00:00.93  
0:00:00.34  0:00:00.01
 STEP030  TMSCYCLE TMSCYCLE CC   17  0:00:06.49  
0:00:00.49  0:00:00.07
 STEP030  EARL EARL CC   18  0:00:00.58  
0:00:00.04  0:00:00.00
 STEP040  TMSCLEAN TMSCLEAN ACTIVE   19


F SDSF,D JES
ISF304I Modify DISPLAY command accepted.
ISF351I SDSF JES Subsystems
Sysname  JES  Version  Status
CM01 JES2 z/OS 2.4 ACTIVE
PR05 JES2 z/OS 2.4 ACTIVE
CM02 JES2 z/OS 2.4 ACTIVE
PR03 JES2 z/OS 2.4 ACTIVE
PR02 JES2 z/OS 2.4 ACTIVE
PR01 JES2 z/OS 2.4 ACTIVE


Paul Feller
GTS Mainframe Technical Support

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Keith Gooding
Sent: Thursday, August 11, 2022 9:34 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: SDSF JS command cross-sysplex [EXTERNAL]

I found that the SDSF ‘JS’ (job steps) command issued from the SDSF panels or 
via the REXX API  produces no output if the target job is running on a 
different system in the sysplex. This is with z/os 2.5. On a 2.3 system the 
same happens except that the heading says ‘no job steps found’ (or similar 
message).

Is anyone able to use JS cross-system or is this working as designed?.  I am 
able to use others commands such as JT (Job Tasks) so I know that the SDSF 
address spaces are talking to each other.

Keith Gooding
--
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


Rocket Software, Inc. and subsidiaries ¦ 77 Fourth Avenue, Waltham MA 02451 ¦ 
Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support: 
https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - 
http://www.rocketso

Re: SDSF JS command cross-sysplex [EXTERNAL]

2022-08-11 Thread Feller, Paul
Keith, I'm assuming you are talking about looking at job on a different lpar in 
the same sysplex, also part of the same JES MAS.

This is a display of a job running on a different lpars then the one I was 
logged on to.  This is a z/OS 2.4 environment.

SDSF JOB STEP DISPLAY - JOB DTSTM01D (JOB24586) SMFLINE 1-19 (19)   
   
COMMAND INPUT ===>SCROLL ===> CSR   
   
PREFIX=*  DEST=(ALL)  OWNER=*  SYSNAME= 
   
NP   STEPNAME ProcStep Pgm-Name Step-CCAbendRsn StepNum Elapsed 
CPU-TimeSRB-Time   
 STEP000  TMSCOPY  TMSCOPY  CC    1  0:00:17.79  
0:00:02.73  0:00:00.46
 STEP005  STEP001  TMSDATA  CC    2  0:00:12.71  
0:00:00.71  0:00:00.23
 STEP005  STEP002  IDCAMS   CC    3  0:00:02.08  
0:00:00.41  0:00:00.01
 STEP003  SAS  SAS  CC    4  0:01:14.04  
0:00:29.98  0:00:00.58
 STEP005  STEP004  IKJEFT01 CC    5  0:00:00.06  
0:00:00.02  0:00:00.00
 STEP005  STEP04A  TMSUPDTE CC    6  0:00:01.08  
0:00:00.14  0:00:00.01
 STEP005  STEP005  IKJEFT01 CC    7  0:00:00.05  
0:00:00.02  0:00:00.00
 STEP005  STEP05A  TMSUDSNB CC    8  0:00:01.22  
0:00:00.17  0:00:00.02
 STEP005  STEP006  IKJEFT01 CC 0001   9  0:00:00.05  
0:00:00.02  0:00:00.00
 STEP005  STEP06A  TMSUPDTE FLUSH10 
   
 STEP005  STEP007  IKJEFT01 CC 0001  11  0:00:00.05  
0:00:00.02  0:00:00.00
 STEP005  STEP07A  TMSUDSNB FLUSH12 
   
 STEP010  TMSEXPDT TMSEXPDT CC   13  0:12:12.33  
0:02:45.00  0:00:09.36
 STEP010  EARL EARL CC   14  0:00:00.55  
0:00:00.04  0:00:00.00
 STEP020  TMSCTLG  TMSCTLG  CC   15  0:20:46.39  
0:01:27.02  0:00:03.23
 STEP020  EARL EARL CC   16  0:00:00.93  
0:00:00.34  0:00:00.01
 STEP030  TMSCYCLE TMSCYCLE CC   17  0:00:06.49  
0:00:00.49  0:00:00.07
 STEP030  EARL EARL CC   18  0:00:00.58  
0:00:00.04  0:00:00.00
 STEP040  TMSCLEAN TMSCLEAN ACTIVE   19 
   


F SDSF,D JES
ISF304I Modify DISPLAY command accepted.
ISF351I SDSF JES Subsystems 
Sysname  JES  Version  Status   
CM01 JES2 z/OS 2.4 ACTIVE   
PR05 JES2 z/OS 2.4 ACTIVE   
CM02 JES2 z/OS 2.4 ACTIVE   
PR03 JES2 z/OS 2.4 ACTIVE   
PR02 JES2 z/OS 2.4 ACTIVE   
PR01 JES2 z/OS 2.4 ACTIVE   


Paul Feller
GTS Mainframe Technical Support

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Keith Gooding
Sent: Thursday, August 11, 2022 9:34 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: SDSF JS command cross-sysplex [EXTERNAL]

I found that the SDSF ‘JS’ (job steps) command issued from the SDSF panels or 
via the REXX API  produces no output if the target job is running on a 
different system in the sysplex. This is with z/os 2.5. On a 2.3 system the 
same happens except that the heading says ‘no job steps found’ (or similar 
message).

Is anyone able to use JS cross-system or is this working as designed?.  I am 
able to use others commands such as JT (Job Tasks) so I know that the SDSF 
address spaces are talking to each other.

Keith Gooding
--
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


SDSF JS command cross-sysplex

2022-08-11 Thread Keith Gooding
I found that the SDSF ‘JS’ (job steps) command issued from the SDSF panels or 
via the REXX API  produces no output if the target job is running on a 
different system in the sysplex. This is with z/os 2.5. On a 2.3 system the 
same happens except that the heading says ‘no job steps found’ (or similar 
message).

Is anyone able to use JS cross-system or is this working as designed?.  I am 
able to use others commands such as JT (Job Tasks) so I know that the SDSF 
address spaces are talking to each other.

Keith Gooding
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN