Rexx SDSF DA info for jname

Discussion:

(too old to reply)

Joseph Reichman

2021-07-07 18:26:25 UTC

Hi

I’m monitoring a number of jobs I use the ISFEXEC ST ( status ) command to get the initial status
When a job goes from waitting execution to executing determined by the phasename column or stem variable

I do the following
ISFFILTER = “ jname = “ || jname.i || “ “
ISFCOLS = ‘ asidx excp cpu real ‘
To get the execution statistics
I then do
ADDRESS SDSF
“ISFEXEC DA “

Sometimes there are datasets that are migrated so I do
If ( asidx.0 > 0) to insure it started executing
Then do
ASD = asidx.1 /* as I know there is only one jobname as such */
Ex = excp.1
Cpu# = cpu.1
Realstor = real.1
End

However after the first job submitted I seem to be picking up the wrong asid and assumed the other variables are erroneous as well

Anyone can point out the flaw in my logic would appreciate it

Thanks

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to ***@VM.MARIST.EDU with the message: INFO TSO-REXX

Itschak Mugzach

2021-07-07 19:12:08 UTC

Permalink

Add job number (jobid) to your selection criteria to ensure you find the
proper job.

בתאריך יום ד׳, 7 ביולי 2021 ב-21:26 מאת Joseph Reichman <

Post by Joseph Reichman
Hi
I’m monitoring a number of jobs I use the ISFEXEC ST ( status ) command to
get the initial status
When a job goes from waitting execution to executing determined by the
phasename column or stem variable
I do the following
ISFFILTER = “ jname = “ || jname.i || “ “
ISFCOLS = ‘ asidx excp cpu real ‘
To get the execution statistics
I then do
ADDRESS SDSF
“ISFEXEC DA “
Sometimes there are datasets that are migrated so I do
If ( asidx.0 > 0) to insure it started executing
Then do
ASD = asidx.1 /* as I know there is only one jobname as such */
Ex = excp.1
Cpu# = cpu.1
Realstor = real.1
End
However after the first job submitted I seem to be picking up the wrong
asid and assumed the other variables are erroneous as well
Anyone can point out the flaw in my logic would appreciate it
Thanks
----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,

ITschak Mugzach

2021-07-07 19:13:07 UTC

Permalink

Add job number (jobid) to your selection criteria to ensure you find the
proper job. בתאריך יום ד׳, 7 ביולי 2021 ב-22:11 מאת Itschak Mugzach <

Post by Itschak Mugzach
Add job number (jobid) to your selection criteria to ensure you find the
proper job.
בתאריך יום ד׳, 7 ביולי 2021 ב-21:26 מאת Joseph Reichman <

Post by Joseph Reichman
Hi
I’m monitoring a number of jobs I use the ISFEXEC ST ( status ) command
to get the initial status
When a job goes from waitting execution to executing determined by the
phasename column or stem variable
I do the following
ISFFILTER = “ jname = “ || jname.i || “ “
ISFCOLS = ‘ asidx excp cpu real ‘
To get the execution statistics
I then do
ADDRESS SDSF
“ISFEXEC DA “
Sometimes there are datasets that are migrated so I do
If ( asidx.0 > 0) to insure it started executing
Then do
ASD = asidx.1 /* as I know there is only one jobname as such */
Ex = excp.1
Cpu# = cpu.1
Realstor = real.1
End
However after the first job submitted I seem to be picking up the wrong
asid and assumed the other variables are erroneous as well
Anyone can point out the flaw in my logic would appreciate it
Thanks
----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,

ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Continuous Monitoring
for z/OS, x/Linux & IBM I **| z/VM coming soon *

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to ***@VM.MARIST.EDU with the message: INFO TSO-REXX

Joseph Reichman

2021-07-07 19:21:15 UTC

Permalink

I thought about that but you know what that would kill my stem variables for ISFEXEC ST

For instance if I stance of my tsoid is joer
And I have let’s say 10 jobs joer0001 - joer0010 if the second one phasename says executing placing jname in the ISFCOLS for ISFEXEC DA would kill the jname stem variables for ST
Only thing I guess I can do is be aware of which jname.x I am executing re-issue ISFEXEC ST and continue processing from where I left off

Post by Itschak Mugzach
Add job number (jobid) to your selection criteria to ensure you find the
proper job. בתאריך יום ד׳, 7 ביולי 2021 ב-22:11 מאת Itschak Mugzach <

Post by Itschak Mugzach
Add job number (jobid) to your selection criteria to ensure you find the
proper job.
בתאריך יום ד׳, 7 ביולי 2021 ב-21:26 מאת Joseph Reichman <

Post by Joseph Reichman
Hi
I’m monitoring a number of jobs I use the ISFEXEC ST ( status ) command
to get the initial status
When a job goes from waitting execution to executing determined by the
phasename column or stem variable
I do the following
ISFFILTER = “ jname = “ || jname.i || “ “
ISFCOLS = ‘ asidx excp cpu real ‘
To get the execution statistics
I then do
ADDRESS SDSF
“ISFEXEC DA “
Sometimes there are datasets that are migrated so I do
If ( asidx.0 > 0) to insure it started executing
Then do
ASD = asidx.1 /* as I know there is only one jobname as such */
Ex = excp.1
Cpu# = cpu.1
Realstor = real.1
End
However after the first job submitted I seem to be picking up the wrong
asid and assumed the other variables are erroneous as well
Anyone can point out the flaw in my logic would appreciate it
Thanks
----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,

ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Continuous Monitoring
for z/OS, x/Linux & IBM I **| z/VM coming soon *
----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to ***@VM.MARIST.EDU with the message: INFO TSO-REXX

ITschak Mugzach

2021-07-07 19:30:09 UTC

Permalink

Why not monitoring all jobs from the status screen? Are you looking for
performance data at run time? If not, keep monitoring the job from the
status screen sorted by queue.

בתאריך יום ד׳, 7 ביולי 2021 ב-22:21 מאת Joseph Reichman <

Post by Joseph Reichman
I thought about that but you know what that would kill my stem variables for ISFEXEC ST
For instance if I stance of my tsoid is joer
And I have let’s say 10 jobs joer0001 - joer0010 if the second one
phasename says executing placing jname in the ISFCOLS for ISFEXEC DA would
kill the jname stem variables for ST
Only thing I guess I can do is be aware of which jname.x I am executing
re-issue ISFEXEC ST and continue processing from where I left off

Post by Itschak Mugzach
Add job number (jobid) to your selection criteria to ensure you find the
proper job. בתאריך יום ד׳, 7 ביולי 2021 ב-22:11 מאת Itschak Mugzach <

Post by Itschak Mugzach
Add job number (jobid) to your selection criteria to ensure you find the
proper job.
בתאריך יום ד׳, 7 ביולי 2021 ב-21:26 מאת Joseph Reichman <

Post by Joseph Reichman
Hi
I’m monitoring a number of jobs I use the ISFEXEC ST ( status ) command
to get the initial status
When a job goes from waitting execution to executing determined by the
phasename column or stem variable
I do the following
ISFFILTER = “ jname = “ || jname.i || “ “
ISFCOLS = ‘ asidx excp cpu real ‘
To get the execution statistics
I then do
ADDRESS SDSF
“ISFEXEC DA “
Sometimes there are datasets that are migrated so I do
If ( asidx.0 > 0) to insure it started executing
Then do
ASD = asidx.1 /* as I know there is only one jobname as such */
Ex = excp.1
Cpu# = cpu.1
Realstor = real.1
End
However after the first job submitted I seem to be picking up the wrong
asid and assumed the other variables are erroneous as well
Anyone can point out the flaw in my logic would appreciate it
Thanks
----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,

**|*

Post by Itschak Mugzach

Post by Itschak Mugzach
*Skype**: ItschakMugzach **|* *Web**: www.Securiteam.co.il **|*
--

ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Continuous Monitoring
for z/OS, x/Linux & IBM I **| z/VM coming soon *
----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,

--
ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Continuous Monitoring
for z/OS, x/Linux & IBM I **| z/VM coming soon *

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to ***@VM.MARIST.EDU with the message: INFO TSO-REXX

Joseph Reichman

2021-07-07 19:35:14 UTC

Permalink

The only thing I’m really looking for is excp’s

Anytime I see a job actually executing I have to reissue ISFEXEC DA

Thanks

Post by ITschak Mugzach
Why not monitoring all jobs from the status screen? Are you looking for
performance data at run time? If not, keep monitoring the job from the
status screen sorted by queue.
בתאריך יום ד׳, 7 ביולי 2021 ב-22:21 מאת Joseph Reichman <

Post by Itschak Mugzach
Add job number (jobid) to your selection criteria to ensure you find the
proper job. בתאריך יום ד׳, 7 ביולי 2021 ב-22:11 מאת Itschak Mugzach <

Post by Itschak Mugzach
Add job number (jobid) to your selection criteria to ensure you find the
proper job.
בתאריך יום ד׳, 7 ביולי 2021 ב-21:26 מאת Joseph Reichman <

Post by Joseph Reichman
Hi
I’m monitoring a number of jobs I use the ISFEXEC ST ( status ) command
to get the initial status
When a job goes from waitting execution to executing determined by the
phasename column or stem variable
I do the following
ISFFILTER = “ jname = “ || jname.i || “ “
ISFCOLS = ‘ asidx excp cpu real ‘
To get the execution statistics
I then do
ADDRESS SDSF
“ISFEXEC DA “
Sometimes there are datasets that are migrated so I do
If ( asidx.0 > 0) to insure it started executing
Then do
ASD = asidx.1 /* as I know there is only one jobname as such */
Ex = excp.1
Cpu# = cpu.1
Realstor = real.1
End
However after the first job submitted I seem to be picking up the wrong
asid and assumed the other variables are erroneous as well
Anyone can point out the flaw in my logic would appreciate it
Thanks
----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,

**|*

Post by Itschak Mugzach

Post by Itschak Mugzach
*Skype**: ItschakMugzach **|* *Web**: www.Securiteam.co.il **|*
--

ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Continuous Monitoring
for z/OS, x/Linux & IBM I **| z/VM coming soon *
----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,

--
ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Continuous Monitoring
for z/OS, x/Linux & IBM I **| z/VM coming soon *
----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to ***@VM.MARIST.EDU with the message: INFO TSO-REXX

Lizette Koehler

2021-07-07 19:39:30 UTC

Permalink

Did you look at John McKown's JES2DISK to see how he did things?

https://gist.github.com/JohnArchieMckown/b27747d0c4750a258997

-----Original Message-----
From: TSO REXX Discussion List <TSO-***@VM.MARIST.EDU> On Behalf Of Joseph Reichman
Sent: Wednesday, July 7, 2021 12:21 PM
To: TSO-***@VM.MARIST.EDU
Subject: Re: [TSO-REXX] Rexx SDSF DA info for jname

I thought about that but you know what that would kill my stem variables for ISFEXEC ST

For instance if I stance of my tsoid is joer And I have let’s say 10 jobs joer0001 - joer0010 if the second one phasename says executing placing jname in the ISFCOLS for ISFEXEC DA would kill the jname stem variables for ST Only thing I guess I can do is be aware of which jname.x I am executing re-issue ISFEXEC ST and continue processing from where I left off

Post by Itschak Mugzach
Add job number (jobid) to your selection criteria to ensure you find
the proper job. בתאריך יום ד׳, 7 ביולי 2021 ב-22:11 מאת Itschak
Mugzach <

Post by Itschak Mugzach
Add job number (jobid) to your selection criteria to ensure you find
the proper job.
בתאריך יום ד׳, 7 ביולי 2021 ב-21:26 מאת Joseph Reichman <

0) to insure it started executing Then do ASD = asidx.1 /* as I

know there is only one jobname as such */ Ex = excp.1 Cpu# = cpu.1
Realstor = real.1 End
However after the first job submitted I seem to be picking up the
wrong asid and assumed the other variables are erroneous as well
Anyone can point out the flaw in my logic would appreciate it
Thanks
--------------------------------------------------------------------
-- For TSO-REXX subscribe / signoff / archive access instructions,

ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Continuous
Monitoring for z/OS, x/Linux & IBM I **| z/VM coming soon *
----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions, send

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions, send email to ***@VM.MARIST.EDU with the message: INFO TSO-REXX

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to ***@VM.MARIST.EDU with the message: INFO TSO-REXX

Joseph Reichman

2021-07-07 19:42:55 UTC

Permalink

Thanks

Post by Lizette Koehler
Did you look at John McKown's JES2DISK to see how he did things?
https://gist.github.com/JohnArchieMckown/b27747d0c4750a258997
-----Original Message-----
Sent: Wednesday, July 7, 2021 12:21 PM
Subject: Re: [TSO-REXX] Rexx SDSF DA info for jname
I thought about that but you know what that would kill my stem variables for ISFEXEC ST
For instance if I stance of my tsoid is joer And I have let’s say 10 jobs joer0001 - joer0010 if the second one phasename says executing placing jname in the ISFCOLS for ISFEXEC DA would kill the jname stem variables for ST Only thing I guess I can do is be aware of which jname.x I am executing re-issue ISFEXEC ST and continue processing from where I left off

Post by Itschak Mugzach
Add job number (jobid) to your selection criteria to ensure you find
the proper job. בתאריך יום ד׳, 7 ביולי 2021 ב-22:11 מאת Itschak
Mugzach <

Post by Itschak Mugzach
Add job number (jobid) to your selection criteria to ensure you find
the proper job.
בתאריך יום ד׳, 7 ביולי 2021 ב-21:26 מאת Joseph Reichman <

0) to insure it started executing Then do ASD = asidx.1 /* as I

ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Continuous
Monitoring for z/OS, x/Linux & IBM I **| z/VM coming soon *
----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions, send

----------------------------------------------------------------------
----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to ***@VM.MARIST.EDU with the message: INFO TSO-REXX

Lizette Koehler

2021-07-07 21:27:20 UTC

Permalink

If you are at the correct level of z/OS

And have SDSF

SDSF Has a tutorial and I think Wizard on how to build SDSF Rexx.

Lizette

-----Original Message-----
From: TSO REXX Discussion List <TSO-***@VM.MARIST.EDU> On Behalf Of Joseph Reichman
Sent: Wednesday, July 7, 2021 12:43 PM
To: TSO-***@VM.MARIST.EDU
Subject: Re: [TSO-REXX] Rexx SDSF DA info for jname

Thanks

Post by Lizette Koehler
Did you look at John McKown's JES2DISK to see how he did things?
https://gist.github.com/JohnArchieMckown/b27747d0c4750a258997
-----Original Message-----
Sent: Wednesday, July 7, 2021 12:21 PM
Subject: Re: [TSO-REXX] Rexx SDSF DA info for jname
I thought about that but you know what that would kill my stem
variables for ISFEXEC ST
For instance if I stance of my tsoid is joer And I have let’s say 10
jobs joer0001 - joer0010 if the second one phasename says executing
placing jname in the ISFCOLS for ISFEXEC DA would kill the jname stem
variables for ST Only thing I guess I can do is be aware of which
jname.x I am executing re-issue ISFEXEC ST and continue processing
from where I left off

Post by Itschak Mugzach
Add job number (jobid) to your selection criteria to ensure you find
the proper job. בתאריך יום ד׳, 7 ביולי 2021 ב-22:11 מאת Itschak
Mugzach <

Post by Itschak Mugzach
Add job number (jobid) to your selection criteria to ensure you find
the proper job.
בתאריך יום ד׳, 7 ביולי 2021 ב-21:26 מאת Joseph Reichman <

0) to insure it started executing Then do ASD = asidx.1 /* as I

know there is only one jobname as such */ Ex = excp.1 Cpu# = cpu.1
Realstor = real.1 End
However after the first job submitted I seem to be picking up the
wrong asid and assumed the other variables are erroneous as well
Anyone can point out the flaw in my logic would appreciate it
Thanks
-------------------------------------------------------------------
-
-- For TSO-REXX subscribe / signoff / archive access instructions,
TSO-REXX

ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Continuous
Monitoring for z/OS, x/Linux & IBM I **| z/VM coming soon *
---------------------------------------------------------------------
- For TSO-REXX subscribe / signoff / archive access instructions,

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions, send
----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions, send

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions, send email to ***@VM.MARIST.EDU with the message: INFO TSO-REXX

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to ***@VM.MARIST.EDU with the message: INFO TSO-REXX

Joseph Reichman

2021-07-07 22:14:17 UTC

Permalink

It 2.4

This is work I’m doing not zdpt

Post by Lizette Koehler
If you are at the correct level of z/OS
And have SDSF
SDSF Has a tutorial and I think Wizard on how to build SDSF Rexx.
Lizette
-----Original Message-----
Sent: Wednesday, July 7, 2021 12:43 PM
Subject: Re: [TSO-REXX] Rexx SDSF DA info for jname
Thanks

Post by Lizette Koehler
Did you look at John McKown's JES2DISK to see how he did things?
https://gist.github.com/JohnArchieMckown/b27747d0c4750a258997
-----Original Message-----
Sent: Wednesday, July 7, 2021 12:21 PM
Subject: Re: [TSO-REXX] Rexx SDSF DA info for jname
I thought about that but you know what that would kill my stem
variables for ISFEXEC ST
For instance if I stance of my tsoid is joer And I have let’s say 10
jobs joer0001 - joer0010 if the second one phasename says executing
placing jname in the ISFCOLS for ISFEXEC DA would kill the jname stem
variables for ST Only thing I guess I can do is be aware of which
jname.x I am executing re-issue ISFEXEC ST and continue processing
from where I left off

Post by Itschak Mugzach
Add job number (jobid) to your selection criteria to ensure you find
the proper job. בתאריך יום ד׳, 7 ביולי 2021 ב-22:11 מאת Itschak
Mugzach <

Post by Itschak Mugzach
Add job number (jobid) to your selection criteria to ensure you find
the proper job.
בתאריך יום ד׳, 7 ביולי 2021 ב-21:26 מאת Joseph Reichman <

0) to insure it started executing Then do ASD = asidx.1 /* as I

know there is only one jobname as such */ Ex = excp.1 Cpu# = cpu.1
Realstor = real.1 End
However after the first job submitted I seem to be picking up the
wrong asid and assumed the other variables are erroneous as well
Anyone can point out the flaw in my logic would appreciate it
Thanks
-------------------------------------------------------------------
-
-- For TSO-REXX subscribe / signoff / archive access instructions,

ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Continuous
Monitoring for z/OS, x/Linux & IBM I **| z/VM coming soon *
---------------------------------------------------------------------
- For TSO-REXX subscribe / signoff / archive access instructions,

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to ***@VM.MARIST.EDU with the message: INFO TSO-REXX

Styles, Andy , ITS zPlatform Services

2021-07-07 21:59:28 UTC

Permalink

Classification: Public

You can use

ISFEXEC DA <stuff> (PREFIX DA_

to have the variables assigned from the DA panel to variables prefixed with 'DA_'; that should avoid the clash.

Andy Styles
z/Series System Programmer

-----Original Message-----
From: TSO REXX Discussion List <TSO-***@VM.MARIST.EDU> On Behalf Of Joseph Reichman
Sent: 07 July 2021 20:21
To: TSO-***@VM.MARIST.EDU
Subject: Re: [TSO-REXX] Rexx SDSF DA info for jname

*** This email is from an external source - be careful of attachments and links. Please report suspicious emails ***

I thought about that but you know what that would kill my stem variables for ISFEXEC ST

For instance if I stance of my tsoid is joer And I have let’s say 10 jobs joer0001 - joer0010 if the second one phasename says executing placing jname in the ISFCOLS for ISFEXEC DA would kill the jname stem variables for ST Only thing I guess I can do is be aware of which jname.x I am executing re-issue ISFEXEC ST and continue processing from where I left off

Post by Itschak Mugzach
Add job number (jobid) to your selection criteria to ensure you find
the proper job. בתאריך יום ד׳, 7 ביולי 2021 ב-22:11 מאת Itschak
Mugzach <

Post by Itschak Mugzach
Add job number (jobid) to your selection criteria to ensure you find
the proper job.
בתאריך יום ד׳, 7 ביולי 2021 ב-21:26 מאת Joseph Reichman <

0) to insure it started executing Then do ASD = asidx.1 /* as I

--
*| **Itschak Mugzach | Director | SecuriTeam Software **|**
IronSphere
Platform* *|* *Information Security Continuous Monitoring for Z/OS,
zLinux and IBM I **| *
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcli
cktime.symantec.com%2F38jareBucbAepXRhyDt9FVN6H2%3Fu%3Dwww.Securiteam
.co.il&data=04%7C01%7CAndy.Styles%40LloydsBanking.com%7C6dfa199d6
8a94c17bfad08d9417c6de8%7C3ded2960214a46ff8cf4611f125e2398%7C0%7C0%7C
637612824936831710%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIj
oiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=%2B8DiDEGX%
2Fyew2CDkMxmgX45TdEODWRasQ6r4yp4AfoQ%3D&reserved=0 **|*
--

ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Continuous
Monitoring for z/OS, x/Linux & IBM I **| z/VM coming soon *
----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions, send

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions, send email to ***@VM.MARIST.EDU with the message: INFO TSO-REXX
Lloyds Banking Group plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in Scotland no. SC95000. Telephone: 0131 225 4555.

Lloyds Bank plc. Registered Office: 25 Gresham Street, London EC2V 7HN. Registered in England and Wales no. 2065. Telephone 0207626 1500.

Bank of Scotland plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in Scotland no. SC327000. Telephone: 03457 801 801.

Lloyds Bank Corporate Markets plc. Registered office: 25 Gresham Street, London EC2V 7HN. Registered in England and Wales no. 10399850.

Scottish Widows Schroder Personal Wealth Limited. Registered Office: 25 Gresham Street, London EC2V 7HN. Registered in England and Wales no. 11722983.

Lloyds Bank plc, Bank of Scotland plc and Lloyds Bank Corporate Markets plc are authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and Prudential Regulation Authority.

Scottish Widows Schroder Personal Wealth Limited is authorised and regulated by the Financial Conduct Authority.

Lloyds Bank Corporate Markets Wertpapierhandelsbank GmbH is a wholly-owned subsidiary of Lloyds Bank Corporate Markets plc. Lloyds Bank Corporate Markets Wertpapierhandelsbank GmbH has its registered office at Thurn-und-Taxis Platz 6, 60313 Frankfurt, Germany. The company is registered with the Amtsgericht Frankfurt am Main, HRB 111650. Lloyds Bank Corporate Markets Wertpapierhandelsbank GmbH is supervised by the Bundesanstalt für Finanzdienstleistungsaufsicht.

Halifax is a division of Bank of Scotland plc.

HBOS plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in Scotland no. SC218813.

This e-mail (including any attachments) is private and confidential and may contain privileged material. If you have received this e-mail in error, please notify the sender and delete it (including any attachments) immediately. You must not copy, distribute, disclose or use any of the information in it or any attachments. Telephone calls may be monitored or recorded.

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to ***@VM.MARIST.EDU with the message: INFO TSO-REXX

Joseph Reichman

2021-07-08 12:23:03 UTC

Permalink

What I have noticed is when using stem variable jname or jobid in ISFEXEC ST and in order to get execution statistics issue ISFEXEC DA and with a filter of let’s say jobid
Where I expect to get only only 1 variable returned
When I then want to return to ISFEXEC ST processing and reissue ISFEXEC ST the jname stem variable is not necessarily in the same order
In John Mckown Rexx SDSF that lizette
Suggested I I look at I saw a (Delayed) parameter appended will look into that

Post by Joseph Reichman
It 2.4
This is work I’m doing not zdpt

Post by Lizette Koehler
Did you look at John McKown's JES2DISK to see how he did things?
https://gist.github.com/JohnArchieMckown/b27747d0c4750a258997
-----Original Message-----
Joseph Reichman
Sent: Wednesday, July 7, 2021 12:21 PM
Subject: Re: [TSO-REXX] Rexx SDSF DA info for jname
I thought about that but you know what that would kill my stem
variables for ISFEXEC ST
For instance if I stance of my tsoid is joer And I have let’s say 10
jobs joer0001 - joer0010 if the second one phasename says executing
placing jname in the ISFCOLS for ISFEXEC DA would kill the jname stem
variables for ST Only thing I guess I can do is be aware of which
jname.x I am executing re-issue ISFEXEC ST and continue processing
from where I left off

Post by Itschak Mugzach
Add job number (jobid) to your selection criteria to ensure you find
the proper job. בתאריך יום ד׳, 7 ביולי 2021 ב-22:11 מאת Itschak
Mugzach <

Post by Itschak Mugzach
Add job number (jobid) to your selection criteria to ensure you find
the proper job.
בתאריך יום ד׳, 7 ביולי 2021 ב-21:26 מאת Joseph Reichman <

0) to insure it started executing Then do ASD = asidx.1 /* as I

know there is only one jobname as such */ Ex = excp.1 Cpu# = cpu.1
Realstor = real.1 End
However after the first job submitted I seem to be picking up the
wrong asid and assumed the other variables are erroneous as well
Anyone can point out the flaw in my logic would appreciate it
Thanks
-------------------------------------------------------------------
-
-- For TSO-REXX subscribe / signoff / archive access instructions,
TSO-REXX

ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Continuous
Monitoring for z/OS, x/Linux & IBM I **| z/VM coming soon *
---------------------------------------------------------------------
- For TSO-REXX subscribe / signoff / archive access instructions,

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to ***@VM.MARIST.EDU with the message: INFO TSO-REXX