Re: SDSF RCF (was: MVS modify command capture)
On Thu, 27 Aug 2020 18:18:52 +, Rob Scott wrote: >ISFCALLS is an external REXX function - all that is required is that the load >module (it is an alias to ISFYHOST in SISFLOAD) is available via the normal >search sequence. > I have never had to be concerned with this when I call ISFCALLS under UNIX. Perhaps it's in LPA or link list: https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.4.0/com.ibm.zos.v2r4.bpxb600/bpx1rx22.htm >ISFCALLS returns rc=0 by design when the host envirmnment already exists. > So there's no way the coder can restore the caller's status quo ante. Perhaps it matters little. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SDSF RCF (was: MVS modify command capture)
ISFCALLS is an external REXX function - all that is required is that the load
module (it is an alias to ISFYHOST in SISFLOAD) is available via the normal
search sequence.
ISFCALLS returns rc=0 by design when the host environment already exists.
There are no integrity issues introduced by omitting the ISFCALLS('OFF').
Rob Scott
Rocket Software
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Paul Gilmartin
Sent: Thursday, August 27, 2020 5:35 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SDSF RCF (was: MVS modify command capture)
EXTERNAL EMAIL
On Thu, 27 Aug 2020 16:10:01 +, Rob Scott wrote:
>From what I can see, the original script was a REXX exec and from Chapter 5 in
>the SDSF User Guide :
>
>"Adding the SDSF host command environment with ISFCALLS
>
>Using SDSF with REXX requires that you add a host command environment prior to
>any other SDSF host environment commands.
>
But that in turn depends on ISFCALLS's availability in the function package
with which Rexx is started. That's true for TMP, UNIX, and IRXJCL. It may be
untrue for minor products, perhaps from ISVs.
What is the adverse consequence of omitting ISFCALLS( 'OFF' )? Integrity?
I'm inclined to omit it, especially near the end of an EXEC. I suspect the case
worst for performance is multiple ISFCALLS ON ... OFF pairs bracketing short
sections of code.
ISFCALLS appears not to have a Result code defined for "ISFCALLS already
active" to enable the coder of a Rexx subroutine to restore the status on entry.
-- gil
--
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.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy
This communication and any attachments may contain confidential information of
Rocket Software, Inc. All unauthorized use, disclosure or distribution is
prohibited. If you are not the intended recipient, please notify Rocket
Software immediately and destroy all copies of this communication. Thank you.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SDSF RCF (was: MVS modify command capture)
I replied too soon; I agree that the manual should mention in what contexts the
external function ISFCALLS is available.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of Rob
Scott
Sent: Thursday, August 27, 2020 12:10 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SDSF RCF (was: MVS modify command capture)
>From what I can see, the original script was a REXX exec and from Chapter 5 in
>the SDSF User Guide :
"Adding the SDSF host command environment with ISFCALLS
Using SDSF with REXX requires that you add a host command environment prior to
any other SDSF host environment commands.
The host command environment is what allows you to use Address SDSF on the
ISFEXEC and ISFACT commands.
You add the host command environment with the ISFCALLS() function.
You should delete the host command environment, again using ISFCALLS, prior to
the termination of the exec.
The syntax of the ISFCALLS() function is: rc = ISFCALLS ( 'ON' 'OFF'
,'SSTYPE=JES2' )
ON adds the SDSF host command environment
OFF deletes the SDSF host command environment
SSTYPE=JES2 requests that SDSF process JES2 rather than determining whether to
process JES2 or JES3"
I think the above documentation is placed in the correct chapter (as long the
"Invoking SDSF" section is updated to point to Chapter 5 for REXX).
SDSF is not implicitly activated in REXX, you have to explicitly activate it
using the ISFCALLS() function (which the original REXX script does).
Rob Scott
Rocket Software
From: IBM Mainframe Discussion List On Behalf Of
Seymour J Metz
Sent: Thursday, August 27, 2020 3:46 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SDSF RCF (was: MVS modify command capture)
EXTERNAL EMAIL
> Any product can dynamically add itself
In the case under discussion, the script has not invoked SDSF. At a minimum,
the SDSF documentation should mention that SDSF can be implicitly activated;
ideally it should mention the relevant contexts.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3<http://mason.gmu.edu/~smetz3>
From: IBM Mainframe Discussion List
mailto:IBM-MAIN@LISTSERV.UA.EDU>> on behalf of Rob
Scott mailto:rsc...@rocketsoftware.com>>
Sent: Thursday, August 27, 2020 6:22 AM
To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>
Subject: Re: SDSF RCF (was: MVS modify command capture)
Any product can dynamically add itself to the REXX host environment table to
provide "ADDRESS foobar" style support, so I think that it is the requirement
of the underlying product to document that fact (rather than TSO or z/OS Unix).
On re-reading the SDSF User Guide, the section on "Invoking SDSF" only mentions
TSO and ISPF as I believe it is referring to the interactive interface and the
things you can do on the panels (or screens).
I agree that this is misleading as there other ways of invoking SDSF to get
data.
I will see if I can get the "Invoking SDSF" section in the user guide to be
more explicit and point to the later chapters that describe REXX (and batch).
Rob Scott
Rocket Software
From: IBM Mainframe Discussion List
mailto:IBM-MAIN@LISTSERV.UA.EDU>> On Behalf Of Paul
Gilmartin
Sent: Thursday, August 27, 2020 12:58 AM
To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>
Subject: SDSF RCF (was: MVS modify command capture)
EXTERNAL EMAIL
On Wed, 26 Aug 2020 20:27:10 +, Seymour J Metz wrote:
>Well, here there's nothing to escalate; I've generally gotten good responses
>from RCFs.
>
Submitted as below. Has anyone suggestions for additions?
Hello, MHVRCFs,
Neither z/OS Version 2 Release 4 TSO/E REXX Reference
IBM SA32-0972-40
nor z/OS Version 2 Release 4 Using REXX and z/OS UNIX System Services
IBM SA23-2283-40
mentions that the SDSF command environment ("ADDRESS SDSF")
is available under IRXJCL and Unix System Services. I have
used ADDRESS SDSF in both contexts. I suspect this function
is provided intentionally by IBM with intent to support it.
z/OS Version 2 Release 4 SDSF User's Guide IBM
SC27-9028-40
mentions only that it's available under TSO, not IRXJCL nor
UNIX System Services.
I find UNIX and IRXJCL mentioned somewhat obliquely in
http://www.redbooks.ibm.com/redbooks/pdfs/sg247419.pdf<http://www.redbooks.ibm.com/redbooks/pdfs/sg247419.pdf><http://www.redbooks.ibm.com/redbooks/pdfs/sg247419.pdf<http://www.redbooks.ibm.com/redbooks/pdfs/sg247419.pdf>>
... but a Redbook is not where most programmers would
seek such documentation.
The availability of "ADDRESS SDSF" under UNIX and IRXJCL
should be mentioned in a Reference manual.
More generally, should the availability of a command
environment be documented in a Rexx manual such as
SA32-0972-40 or SA23-2283-40, or in the manual describin
Re: SDSF RCF (was: MVS modify command capture)
Thanks; I missed that. Yes, pointing to Chapter 5 should be enough.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of Rob
Scott
Sent: Thursday, August 27, 2020 12:10 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SDSF RCF (was: MVS modify command capture)
>From what I can see, the original script was a REXX exec and from Chapter 5 in
>the SDSF User Guide :
"Adding the SDSF host command environment with ISFCALLS
Using SDSF with REXX requires that you add a host command environment prior to
any other SDSF host environment commands.
The host command environment is what allows you to use Address SDSF on the
ISFEXEC and ISFACT commands.
You add the host command environment with the ISFCALLS() function.
You should delete the host command environment, again using ISFCALLS, prior to
the termination of the exec.
The syntax of the ISFCALLS() function is: rc = ISFCALLS ( 'ON' 'OFF'
,'SSTYPE=JES2' )
ON adds the SDSF host command environment
OFF deletes the SDSF host command environment
SSTYPE=JES2 requests that SDSF process JES2 rather than determining whether to
process JES2 or JES3"
I think the above documentation is placed in the correct chapter (as long the
"Invoking SDSF" section is updated to point to Chapter 5 for REXX).
SDSF is not implicitly activated in REXX, you have to explicitly activate it
using the ISFCALLS() function (which the original REXX script does).
Rob Scott
Rocket Software
From: IBM Mainframe Discussion List On Behalf Of
Seymour J Metz
Sent: Thursday, August 27, 2020 3:46 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SDSF RCF (was: MVS modify command capture)
EXTERNAL EMAIL
> Any product can dynamically add itself
In the case under discussion, the script has not invoked SDSF. At a minimum,
the SDSF documentation should mention that SDSF can be implicitly activated;
ideally it should mention the relevant contexts.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3<http://mason.gmu.edu/~smetz3>
From: IBM Mainframe Discussion List
mailto:IBM-MAIN@LISTSERV.UA.EDU>> on behalf of Rob
Scott mailto:rsc...@rocketsoftware.com>>
Sent: Thursday, August 27, 2020 6:22 AM
To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>
Subject: Re: SDSF RCF (was: MVS modify command capture)
Any product can dynamically add itself to the REXX host environment table to
provide "ADDRESS foobar" style support, so I think that it is the requirement
of the underlying product to document that fact (rather than TSO or z/OS Unix).
On re-reading the SDSF User Guide, the section on "Invoking SDSF" only mentions
TSO and ISPF as I believe it is referring to the interactive interface and the
things you can do on the panels (or screens).
I agree that this is misleading as there other ways of invoking SDSF to get
data.
I will see if I can get the "Invoking SDSF" section in the user guide to be
more explicit and point to the later chapters that describe REXX (and batch).
Rob Scott
Rocket Software
From: IBM Mainframe Discussion List
mailto:IBM-MAIN@LISTSERV.UA.EDU>> On Behalf Of Paul
Gilmartin
Sent: Thursday, August 27, 2020 12:58 AM
To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>
Subject: SDSF RCF (was: MVS modify command capture)
EXTERNAL EMAIL
On Wed, 26 Aug 2020 20:27:10 +, Seymour J Metz wrote:
>Well, here there's nothing to escalate; I've generally gotten good responses
>from RCFs.
>
Submitted as below. Has anyone suggestions for additions?
Hello, MHVRCFs,
Neither z/OS Version 2 Release 4 TSO/E REXX Reference
IBM SA32-0972-40
nor z/OS Version 2 Release 4 Using REXX and z/OS UNIX System Services
IBM SA23-2283-40
mentions that the SDSF command environment ("ADDRESS SDSF")
is available under IRXJCL and Unix System Services. I have
used ADDRESS SDSF in both contexts. I suspect this function
is provided intentionally by IBM with intent to support it.
z/OS Version 2 Release 4 SDSF User's Guide IBM
SC27-9028-40
mentions only that it's available under TSO, not IRXJCL nor
UNIX System Services.
I find UNIX and IRXJCL mentioned somewhat obliquely in
http://www.redbooks.ibm.com/redbooks/pdfs/sg247419.pdf<http://www.redbooks.ibm.com/redbooks/pdfs/sg247419.pdf><http://www.redbooks.ibm.com/redbooks/pdfs/sg247419.pdf<http://www.redbooks.ibm.com/redbooks/pdfs/sg247419.pdf>>
... but a Redbook is not where most programmers would
seek such documentation.
The availability of "ADDRESS SDSF" under UNIX and IRXJCL
should be mentioned in a Reference manual.
More generally, should the availability of a command
environment be documented in a Rexx manual such as
SA32-0972-40 or SA23-2283-40, or in the manual describin
Re: SDSF RCF (was: MVS modify command capture)
On Thu, 27 Aug 2020 16:10:01 +, Rob Scott wrote: >From what I can see, the original script was a REXX exec and from Chapter 5 in >the SDSF User Guide : > >"Adding the SDSF host command environment with ISFCALLS > >Using SDSF with REXX requires that you add a host command environment prior to >any other SDSF host environment commands. > But that in turn depends on ISFCALLS's availability in the function package with which Rexx is started. That's true for TMP, UNIX, and IRXJCL. It may be untrue for minor products, perhaps from ISVs. What is the adverse consequence of omitting ISFCALLS( 'OFF' )? Integrity? I'm inclined to omit it, especially near the end of an EXEC. I suspect the case worst for performance is multiple ISFCALLS ON ... OFF pairs bracketing short sections of code. ISFCALLS appears not to have a Result code defined for "ISFCALLS already active" to enable the coder of a Rexx subroutine to restore the status on entry. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SDSF RCF (was: MVS modify command capture)
>From what I can see, the original script was a REXX exec and from Chapter 5 in
>the SDSF User Guide :
"Adding the SDSF host command environment with ISFCALLS
Using SDSF with REXX requires that you add a host command environment prior to
any other SDSF host environment commands.
The host command environment is what allows you to use Address SDSF on the
ISFEXEC and ISFACT commands.
You add the host command environment with the ISFCALLS() function.
You should delete the host command environment, again using ISFCALLS, prior to
the termination of the exec.
The syntax of the ISFCALLS() function is: rc = ISFCALLS ( 'ON' 'OFF'
,'SSTYPE=JES2' )
ON adds the SDSF host command environment
OFF deletes the SDSF host command environment
SSTYPE=JES2 requests that SDSF process JES2 rather than determining whether to
process JES2 or JES3"
I think the above documentation is placed in the correct chapter (as long the
"Invoking SDSF" section is updated to point to Chapter 5 for REXX).
SDSF is not implicitly activated in REXX, you have to explicitly activate it
using the ISFCALLS() function (which the original REXX script does).
Rob Scott
Rocket Software
From: IBM Mainframe Discussion List On Behalf Of
Seymour J Metz
Sent: Thursday, August 27, 2020 3:46 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SDSF RCF (was: MVS modify command capture)
EXTERNAL EMAIL
> Any product can dynamically add itself
In the case under discussion, the script has not invoked SDSF. At a minimum,
the SDSF documentation should mention that SDSF can be implicitly activated;
ideally it should mention the relevant contexts.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3<http://mason.gmu.edu/~smetz3>
From: IBM Mainframe Discussion List
mailto:IBM-MAIN@LISTSERV.UA.EDU>> on behalf of Rob
Scott mailto:rsc...@rocketsoftware.com>>
Sent: Thursday, August 27, 2020 6:22 AM
To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>
Subject: Re: SDSF RCF (was: MVS modify command capture)
Any product can dynamically add itself to the REXX host environment table to
provide "ADDRESS foobar" style support, so I think that it is the requirement
of the underlying product to document that fact (rather than TSO or z/OS Unix).
On re-reading the SDSF User Guide, the section on "Invoking SDSF" only mentions
TSO and ISPF as I believe it is referring to the interactive interface and the
things you can do on the panels (or screens).
I agree that this is misleading as there other ways of invoking SDSF to get
data.
I will see if I can get the "Invoking SDSF" section in the user guide to be
more explicit and point to the later chapters that describe REXX (and batch).
Rob Scott
Rocket Software
From: IBM Mainframe Discussion List
mailto:IBM-MAIN@LISTSERV.UA.EDU>> On Behalf Of Paul
Gilmartin
Sent: Thursday, August 27, 2020 12:58 AM
To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>
Subject: SDSF RCF (was: MVS modify command capture)
EXTERNAL EMAIL
On Wed, 26 Aug 2020 20:27:10 +, Seymour J Metz wrote:
>Well, here there's nothing to escalate; I've generally gotten good responses
>from RCFs.
>
Submitted as below. Has anyone suggestions for additions?
Hello, MHVRCFs,
Neither z/OS Version 2 Release 4 TSO/E REXX Reference
IBM SA32-0972-40
nor z/OS Version 2 Release 4 Using REXX and z/OS UNIX System Services
IBM SA23-2283-40
mentions that the SDSF command environment ("ADDRESS SDSF")
is available under IRXJCL and Unix System Services. I have
used ADDRESS SDSF in both contexts. I suspect this function
is provided intentionally by IBM with intent to support it.
z/OS Version 2 Release 4 SDSF User's Guide IBM
SC27-9028-40
mentions only that it's available under TSO, not IRXJCL nor
UNIX System Services.
I find UNIX and IRXJCL mentioned somewhat obliquely in
http://www.redbooks.ibm.com/redbooks/pdfs/sg247419.pdf<http://www.redbooks.ibm.com/redbooks/pdfs/sg247419.pdf><http://www.redbooks.ibm.com/redbooks/pdfs/sg247419.pdf<http://www.redbooks.ibm.com/redbooks/pdfs/sg247419.pdf>>
... but a Redbook is not where most programmers would
seek such documentation.
The availability of "ADDRESS SDSF" under UNIX and IRXJCL
should be mentioned in a Reference manual.
More generally, should the availability of a command
environment be documented in a Rexx manual such as
SA32-0972-40 or SA23-2283-40, or in the manual describing
the commands such as SC27-9028-40? An incomplete list
such as in SA32-0972-40 or SC27-9028-40 is likely to
mislead programmers.
Thanks,
gil
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
lists...@listserv.ua.edu<mailto:lists...@listserv.ua.edu<mailto:lists...@listserv.ua.edu%3cmailto:lists...@listserv.ua.edu>&
Re: SDSF RCF (was: MVS modify command capture)
> Any product can dynamically add itself
In the case under discussion, the script has not invoked SDSF. At a minimum,
the SDSF documentation should mention that SDSF can be implicitly activated;
ideally it should mention the relevant contexts.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of Rob
Scott
Sent: Thursday, August 27, 2020 6:22 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SDSF RCF (was: MVS modify command capture)
Any product can dynamically add itself to the REXX host environment table to
provide “ADDRESS foobar” style support, so I think that it is the requirement
of the underlying product to document that fact (rather than TSO or z/OS Unix).
On re-reading the SDSF User Guide, the section on “Invoking SDSF” only mentions
TSO and ISPF as I believe it is referring to the interactive interface and the
things you can do on the panels (or screens).
I agree that this is misleading as there other ways of invoking SDSF to get
data.
I will see if I can get the “Invoking SDSF” section in the user guide to be
more explicit and point to the later chapters that describe REXX (and batch).
Rob Scott
Rocket Software
From: IBM Mainframe Discussion List On Behalf Of
Paul Gilmartin
Sent: Thursday, August 27, 2020 12:58 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: SDSF RCF (was: MVS modify command capture)
EXTERNAL EMAIL
On Wed, 26 Aug 2020 20:27:10 +, Seymour J Metz wrote:
>Well, here there's nothing to escalate; I've generally gotten good responses
>from RCFs.
>
Submitted as below. Has anyone suggestions for additions?
Hello, MHVRCFs,
Neither z/OS Version 2 Release 4 TSO/E REXX Reference
IBM SA32-0972-40
nor z/OS Version 2 Release 4 Using REXX and z/OS UNIX System Services
IBM SA23-2283-40
mentions that the SDSF command environment ("ADDRESS SDSF")
is available under IRXJCL and Unix System Services. I have
used ADDRESS SDSF in both contexts. I suspect this function
is provided intentionally by IBM with intent to support it.
z/OS Version 2 Release 4 SDSF User's Guide IBM
SC27-9028-40
mentions only that it's available under TSO, not IRXJCL nor
UNIX System Services.
I find UNIX and IRXJCL mentioned somewhat obliquely in
http://www.redbooks.ibm.com/redbooks/pdfs/sg247419.pdf<http://www.redbooks.ibm.com/redbooks/pdfs/sg247419.pdf>
... but a Redbook is not where most programmers would
seek such documentation.
The availability of "ADDRESS SDSF" under UNIX and IRXJCL
should be mentioned in a Reference manual.
More generally, should the availability of a command
environment be documented in a Rexx manual such as
SA32-0972-40 or SA23-2283-40, or in the manual describing
the commands such as SC27-9028-40? An incomplete list
such as in SA32-0972-40 or SC27-9028-40 is likely to
mislead programmers.
Thanks,
gil
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu<mailto: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://secure-web.cisco.com/152_YT5WeUW8V-MUvUJRW1vu8UNhOvka-dOvVIaT6_06_0oWEqt0qAEwTTbxa_OXtDmGU9skNwm-L_ulvUJr4ErTfG1Yi4oXHHBZ06KNGvv2ulLx5zg_MWRThH45tgXJU9J3sbsPDmIQ7Qx6JH90HrxOjO1yGsIzhkrRfUDvZ5bKnuBiKCwKil1hz4zWViEau8v1puxyMRoGixoizzD0JkXIQRtAttG4tiblXXUFjVOTmyeH8e-VUmViZcQ1szNR16xyAPrJVPlAi1iXrRdR2G0yplJxb9e0n4nz_ohZcUQeUH-Za30Jzy23F5DPBNPrszNAkazt9hNjnstK-zcKHH-PE2u-fpJlXQtIGkyzImFFh5TpH8yi3KobJ6Z5SbgwXckSIp8kh2MBzMAPlNKW9OPBs14y8V32jzrZI3TsJiAKH68K8f4GoYm4PSI2EKLAz/https%3A%2F%2Fmy.rocketsoftware.com%2FRocketCommunity%2FRCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences -
http://secure-web.cisco.com/1gzTzcKx0ODDaqFYEUzPOp83WJGyGEvIqa5uhsKuQLDpPN7QzqzkXpKjjMqsqc33WfB2Au4fRiUxsLB-59ul61kP9FVINZS6bOC45gMiCGsYnUbnNHJ7B_sLX4SLepXmzScy9XheIU3j20LUkrB-EpTAthkZpZhlYVkJnYw0Pgw_AWxzAYh_RSB2-2TWmKlmXoTWJSmV565S09hixE9l_2BPLPSd_VPRj0bRIQ-gh6VR0P4sh4k-1C8CwmsMfvOVLBGlbGVZHl1S1hnhkiJeJgi6f3A7fpDeeFfQoKU8abVF5lk-Q-CPxffGEODjCtthaJ4LF5uIgmuiLqBRRyZSO2msTKECzo_NTc65HXL8E9LL2bB44Y7icQnZfzEmn8f1pQMek8N-EI9EKaHsxvG30I8q434hs15Cj090mQNFyv1JfTU_5v3xAY5lmA-AImuHIPTXF7FAivV3GvCHTtOspLw/http%3A%2F%2Fwww.rocketsoftware.com%2Fmanage-your-email-preferences
Privacy Policy -
http://secure-web.cisco.com/1vDEUeh84uuwcpye5F6-NIDEsx5G9CtNPb8Hyjodk8cfi4rG--4IkLJbV8EHCPMaA7Fo0JiJrPxYj1SxntTTxHjgSpIXNB9KmFmo8i7IFXQ8VJIBDZxvgsTc3WhNf1A0-hHNOEvR5KmgqT9dm7V2VqwlDpFaWjb7ZoMmu-v8n6s8pIS-TyyotsOmii7BTfs-nZncQ7zpK6w3rrfL2Uf0UPU6AedJTGp-wQxlOIMvWlTeIt25ScVHQa8yXwcbIiwpBNjUqzHODvKnuvj8NKrNCYr_yV4Hm7RNO-HdNFq0e4W3NMfN1ud25zs0D2oAv9KXFdrXr
Re: SDSF RCF (was: MVS modify command capture)
Any product can dynamically add itself to the REXX host environment table to
provide “ADDRESS foobar” style support, so I think that it is the requirement
of the underlying product to document that fact (rather than TSO or z/OS Unix).
On re-reading the SDSF User Guide, the section on “Invoking SDSF” only mentions
TSO and ISPF as I believe it is referring to the interactive interface and the
things you can do on the panels (or screens).
I agree that this is misleading as there other ways of invoking SDSF to get
data.
I will see if I can get the “Invoking SDSF” section in the user guide to be
more explicit and point to the later chapters that describe REXX (and batch).
Rob Scott
Rocket Software
From: IBM Mainframe Discussion List On Behalf Of
Paul Gilmartin
Sent: Thursday, August 27, 2020 12:58 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: SDSF RCF (was: MVS modify command capture)
EXTERNAL EMAIL
On Wed, 26 Aug 2020 20:27:10 +, Seymour J Metz wrote:
>Well, here there's nothing to escalate; I've generally gotten good responses
>from RCFs.
>
Submitted as below. Has anyone suggestions for additions?
Hello, MHVRCFs,
Neither z/OS Version 2 Release 4 TSO/E REXX Reference
IBM SA32-0972-40
nor z/OS Version 2 Release 4 Using REXX and z/OS UNIX System Services
IBM SA23-2283-40
mentions that the SDSF command environment ("ADDRESS SDSF")
is available under IRXJCL and Unix System Services. I have
used ADDRESS SDSF in both contexts. I suspect this function
is provided intentionally by IBM with intent to support it.
z/OS Version 2 Release 4 SDSF User's Guide IBM
SC27-9028-40
mentions only that it's available under TSO, not IRXJCL nor
UNIX System Services.
I find UNIX and IRXJCL mentioned somewhat obliquely in
http://www.redbooks.ibm.com/redbooks/pdfs/sg247419.pdf<http://www.redbooks.ibm.com/redbooks/pdfs/sg247419.pdf>
... but a Redbook is not where most programmers would
seek such documentation.
The availability of "ADDRESS SDSF" under UNIX and IRXJCL
should be mentioned in a Reference manual.
More generally, should the availability of a command
environment be documented in a Rexx manual such as
SA32-0972-40 or SA23-2283-40, or in the manual describing
the commands such as SC27-9028-40? An incomplete list
such as in SA32-0972-40 or SC27-9028-40 is likely to
mislead programmers.
Thanks,
gil
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu<mailto: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.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy
This communication and any attachments may contain confidential information of
Rocket Software, Inc. All unauthorized use, disclosure or distribution is
prohibited. If you are not the intended recipient, please notify Rocket
Software immediately and destroy all copies of this communication. Thank you.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SDSF RCF (was: MVS modify command capture)
What about System REXX?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu>
Sent: Wednesday, August 26, 2020 7:58 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: SDSF RCF (was: MVS modify command capture)
On Wed, 26 Aug 2020 20:27:10 +, Seymour J Metz wrote:
>Well, here there's nothing to escalate; I've generally gotten good responses
>from RCFs.
>
Submitted as below. Has anyone suggestions for additions?
Hello, MHVRCFs,
Neither z/OS Version 2 Release 4 TSO/E REXX Reference
IBM SA32-0972-40
nor z/OS Version 2 Release 4 Using REXX and z/OS UNIX System Services
IBM SA23-2283-40
mentions that the SDSF command environment ("ADDRESS SDSF")
is available under IRXJCL and Unix System Services. I have
used ADDRESS SDSF in both contexts. I suspect this function
is provided intentionally by IBM with intent to support it.
z/OS Version 2 Release 4 SDSF User's Guide IBM
SC27-9028-40
mentions only that it's available under TSO, not IRXJCL nor
UNIX System Services.
I find UNIX and IRXJCL mentioned somewhat obliquely in
http://www.redbooks.ibm.com/redbooks/pdfs/sg247419.pdf
... but a Redbook is not where most programmers would
seek such documentation.
The availability of "ADDRESS SDSF" under UNIX and IRXJCL
should be mentioned in a Reference manual.
More generally, should the availability of a command
environment be documented in a Rexx manual such as
SA32-0972-40 or SA23-2283-40, or in the manual describing
the commands such as SC27-9028-40? An incomplete list
such as in SA32-0972-40 or SC27-9028-40 is likely to
mislead programmers.
Thanks,
gil
--
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
SDSF RCF (was: MVS modify command capture)
On Wed, 26 Aug 2020 20:27:10 +, Seymour J Metz wrote:
>Well, here there's nothing to escalate; I've generally gotten good responses
>from RCFs.
>
Submitted as below. Has anyone suggestions for additions?
Hello, MHVRCFs,
Neither z/OS Version 2 Release 4 TSO/E REXX Reference
IBM SA32-0972-40
nor z/OS Version 2 Release 4 Using REXX and z/OS UNIX System Services
IBM SA23-2283-40
mentions that the SDSF command environment ("ADDRESS SDSF")
is available under IRXJCL and Unix System Services. I have
used ADDRESS SDSF in both contexts. I suspect this function
is provided intentionally by IBM with intent to support it.
z/OS Version 2 Release 4 SDSF User's Guide IBM
SC27-9028-40
mentions only that it's available under TSO, not IRXJCL nor
UNIX System Services.
I find UNIX and IRXJCL mentioned somewhat obliquely in
http://www.redbooks.ibm.com/redbooks/pdfs/sg247419.pdf
... but a Redbook is not where most programmers would
seek such documentation.
The availability of "ADDRESS SDSF" under UNIX and IRXJCL
should be mentioned in a Reference manual.
More generally, should the availability of a command
environment be documented in a Rexx manual such as
SA32-0972-40 or SA23-2283-40, or in the manual describing
the commands such as SC27-9028-40? An incomplete list
such as in SA32-0972-40 or SC27-9028-40 is likely to
mislead programmers.
Thanks,
gil
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
