Re: REXX and SDSF question (expanded API question)

2017-09-23 Thread Wayne Bickerdike
Example of RGEN from the ST panel:

/* REXX */
Arg debug

/**
*
*  SDSF RGEN Generated EXEC
*
*  This exec was generated by the SDSF RGEN command on
*  Sunday 2017/09/24 at 06:01:00.17.
*
*  5650-ZOS
*  SDSF level = z/OS 02.02.00 (HQX77A0)
*
*  Operation =
*
*- Access primary panel ST
*
**/

rc=isfcalls('ON')

trace o

if debug<>"" then   /* If debug mode */
  verbose="VERBOSE"  /* .. use SDSF verbose mode */
else
  verbose=""

/*--*/
/* Configure environment with special variables */
/*--*/
isfprefix='*'/* Corresponds to PREFIX command */
isfowner='*'  /* Corresponds to OWNER command */
isfsysname=''   /* Corresponds to SYSNAME command */

isfdest=' ' || ,/* Dest name 1 */
' ' || ,/* Dest name 2 */
' ' || ,/* Dest name 3 */
' ' /* Dest name 4 */


/* Access the ST panel */
Address SDSF "ISFEXEC 'ST' (" verbose ")"
lrc=rc

call msgrtn  "ISFEXEC 'ST'"   /* List messages */
if lrc<>0 then   /* If command failed */
  do
Say "** ISFEXEC failed with rc="lrc"."
exit 20
  end

call colsrtn isfrows "." sdsfocols  /* List all rows and columns */


rc=isfcalls('OFF')

Exit 0


/**
*
* NAME =
*   msgrtn
*
* FUNCTION =
*   List all messages in the isfmsg and isfmsg2. variables
*
* INPUT =
*   req - Request being processed
*
* EXPOSED VARIABLES =
*   isfmsg   - Short message
*   isfmsg2. - Numbered messages
*
* OUTPUT =
*   Messages written to terminal
*
**/
msgrtn: Procedure expose isfmsg isfmsg2.
Arg req

/*---*/
/* Process numbered messages */
/*---*/
Say "** Numbered messages associated with" req "follow ..."
do ix=1 to isfmsg2.0
  Say isfmsg2.ix
end

if isfmsg<>"" then/* If short message present */
  do
Say "** Short message associated with the request is:" isfmsg
  end

return


/**
*
* NAME =
*   colsrtn
*
* FUNCTION =
*   List all rows and their column values
*
* INPUT =
*   numrows - number of rows to process
*   pfx - column variable prefix or "." if none
*   ocols   - word delimited column names to process
*
* EXPOSED VARIABLES =
*   None
*
* OUTPUT =
*   Responses written to terminal
*
**/
colsrtn:
Arg numrows pfx ocols
Say "Number of rows to process: " numrows

do rowix=1 to numrows  /* Loop for all rows */
  Say "Now processing row" rowix "..."

  do colix=1 to words(ocols)  /* Loop for all columns */

if pfx="." then   /* If no prefix */
  pfx=""

varname=pfx||word(ocols,colix)||'.'||rowix

Say "  Column" varname '=' value(varname)
  end /* For all columns */
end   /* For all rows */

return


On Fri, Sep 22, 2017 at 6:02 AM, Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:

> On Fri, 22 Sep 2017 05:38:11 +1000, Wayne Bickerdike wrote:
>
> >Not sure how useful this command is. It generates what looks like a common
> >template and the output from the SDSF command is directed to a stem
> >variable.
> >
> Is that direction to a stem intrinsic or does it use EXECIO DISKR?  I know
> example(s) in the Ref. use EXECIO.  I modified them considerably to use
> IEBGENER to write to a UNIX file.  IEBGENER propagates the attributes
> of a DD allocated by SDSF.
>
> >Since ISPF edit has the MODEL command, why not put a series of models for
> >SDSF API calls in the same place as the model templates?
> >
> >The command also directs the user to save the contents of the tempfile for
> >future use. Personally I always use the "CUT ALL" command and "PASTE ALL"
> >into my EXEC PDS.
> >
> My compliments on your ingenious alternative.  The manual I read says only:
>
>  You might use RGEN as follows:
>  ...
> Copy the exec to a data set using the CREATE command.
>  ...
>
> -- gil
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>



-- 
Wayne V. Bickerdike

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


Re: REXX and SDSF question (expanded API question)

2017-09-21 Thread Paul Gilmartin
On Fri, 22 Sep 2017 05:38:11 +1000, Wayne Bickerdike wrote:

>Not sure how useful this command is. It generates what looks like a common
>template and the output from the SDSF command is directed to a stem
>variable.
> 
Is that direction to a stem intrinsic or does it use EXECIO DISKR?  I know
example(s) in the Ref. use EXECIO.  I modified them considerably to use
IEBGENER to write to a UNIX file.  IEBGENER propagates the attributes
of a DD allocated by SDSF.

>Since ISPF edit has the MODEL command, why not put a series of models for
>SDSF API calls in the same place as the model templates?
>
>The command also directs the user to save the contents of the tempfile for
>future use. Personally I always use the "CUT ALL" command and "PASTE ALL"
>into my EXEC PDS.
> 
My compliments on your ingenious alternative.  The manual I read says only:

 You might use RGEN as follows:
 ...
Copy the exec to a data set using the CREATE command.
 ...

-- gil

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


Re: REXX and SDSF question (expanded API question)

2017-09-21 Thread Wayne Bickerdike
Not sure how useful this command is. It generates what looks like a common
template and the output from the SDSF command is directed to a stem
variable.

Since ISPF edit has the MODEL command, why not put a series of models for
SDSF API calls in the same place as the model templates?

The command also directs the user to save the contents of the tempfile for
future use. Personally I always use the "CUT ALL" command and "PASTE ALL"
into my EXEC PDS.


On Fri, Sep 22, 2017 at 1:58 AM, Farley, Peter x23353 <
peter.far...@broadridge.com> wrote:

> Yes, RGEN is "invalid command" on our V2.1 system.
>
> Peter
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Beesley, Paul
> Sent: Thursday, September 21, 2017 5:19 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: REXX and SDSF question (expanded API question)
>
> ... assuming you have z/OS 2.2 and up ...
>
> Paul
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Rob Scott
> Sent: Thursday, September 21, 2017 9:57 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: REXX and SDSF question (expanded API question)
>
> On any SDSF panel (for example "DA"), just type "RGEN"
>
> SDSF will generate sample code for you.
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Peter Ten Eyck
> Sent: Wednesday, September 20, 2017 6:25 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: REXX and SDSF question (expanded API question)
>
> Can someone point me to some documentation (coding examples) on how to use
> the SDSF API in REXX? I have my REXX/SDSF exec working, but it runs slow
> issuing those commands. I would like to try a different approach.
>
> --
>
>
> 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
>



-- 
Wayne V. Bickerdike

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


Re: REXX and SDSF question (expanded API question)

2017-09-21 Thread Farley, Peter x23353
Yes, RGEN is "invalid command" on our V2.1 system.

Peter

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Beesley, Paul
Sent: Thursday, September 21, 2017 5:19 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX and SDSF question (expanded API question)

... assuming you have z/OS 2.2 and up ...

Paul

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Rob Scott
Sent: Thursday, September 21, 2017 9:57 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX and SDSF question (expanded API question)

On any SDSF panel (for example "DA"), just type "RGEN"

SDSF will generate sample code for you.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Peter Ten Eyck
Sent: Wednesday, September 20, 2017 6:25 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX and SDSF question (expanded API question)

Can someone point me to some documentation (coding examples) on how to use the 
SDSF API in REXX? I have my REXX/SDSF exec working, but it runs slow issuing 
those commands. I would like to try a different approach.

--


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: REXX and SDSF question (expanded API question)

2017-09-21 Thread Beesley, Paul
... assuming you have z/OS 2.2 and up ...

Paul

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Rob Scott
Sent: Thursday, September 21, 2017 9:57 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX and SDSF question (expanded API question)

On any SDSF panel (for example "DA"), just type "RGEN"

SDSF will generate sample code for you.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Peter Ten Eyck
Sent: Wednesday, September 20, 2017 6:25 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX and SDSF question (expanded API question)

Can someone point me to some documentation (coding examples) on how to use the 
SDSF API in REXX? I have my REXX/SDSF exec working, but it runs slow issuing 
those commands. I would like to try a different approach.

--
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 877.328.2932 
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
Atos, Atos Consulting, Worldline and Canopy The Open Cloud Company are trading 
names used by the Atos group. The following trading entities are registered in 
England and Wales: Atos IT Services UK Limited (registered number 01245534), 
Atos Consulting Limited (registered number 04312380), Atos Worldline UK Limited 
(registered number 08514184) and Canopy The Open Cloud Company Limited 
(registration number 08011902). The registered office for each is at 4 Triton 
Square, Regent’s Place, London, NW1 3HG.The VAT No. for each is: GB232327983.

This e-mail and the documents attached are confidential and intended solely for 
the addressee, and may contain confidential or privileged information. If you 
receive this e-mail in error, you are not authorised to copy, disclose, use or 
retain it. Please notify the sender immediately and delete this email from your 
systems. As emails may be intercepted, amended or lost, they are not secure. 
Atos therefore can accept no liability for any errors or their content. 
Although Atos endeavours to maintain a virus-free network, we do not warrant 
that this transmission is virus-free and can accept no liability for any 
damages resulting from any virus transmitted. The risks are deemed to be 
accepted by everyone who communicates with Atos by email.

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


Re: REXX and SDSF question (expanded API question)

2017-09-21 Thread Rob Scott
On any SDSF panel (for example "DA"), just type "RGEN"

SDSF will generate sample code for you.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Peter Ten Eyck
Sent: Wednesday, September 20, 2017 6:25 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX and SDSF question (expanded API question)

Can someone point me to some documentation (coding examples) on how to use the 
SDSF API in REXX? I have my REXX/SDSF exec working, but it runs slow issuing 
those commands. I would like to try a different approach.

--
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 877.328.2932
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: REXX and SDSF question (expanded API question)

2017-09-20 Thread Peter Ten Eyck
Thanks, this will be a good starting point for me.

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


Re: REXX and SDSF question (expanded API question)

2017-09-20 Thread Alan Young
Take a look at 
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.isfa500/rexx.htm


Peter Ten Eyck wrote:

Can someone point me to some documentation (coding examples) on how to use the 
SDSF API in REXX? I have my REXX/SDSF exec working, but it runs slow issuing 
those commands. I would like to try a different approach.


  


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


Re: REXX and SDSF question (expanded API question)

2017-09-20 Thread Paul Gilmartin
On Wed, 20 Sep 2017 12:34:50 -0500, John McKown wrote:

>On Wed, Sep 20, 2017 at 12:25 PM, Peter Ten Eyck wrote:
>
>> Can someone point me to some documentation (coding examples) on how to use
>> the SDSF API in REXX? I have my REXX/SDSF exec working, but it runs slow
>> issuing those commands. I would like to try a different approach.
>>
>​An example of one of mine, which some others have said was useful, is
>here: https://gist.github.com/JohnArchieMckown/b27747d0c4750a258997​
>
Similar to earlier:
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.isfa600/rexxexmp.htm

There's an detailed example in:

https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.isfa600/xmpbrowse.htm
z/OS SDSF User's Guide
Using SDSF with the REXX programming language
Examples of REXX execs

... that I've modified extesively and successfully.  I'd start from there or 
its neighbors
and hammer and file to fit.

-- gil

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


Re: REXX and SDSF question (expanded API question)

2017-09-20 Thread John McKown
On Wed, Sep 20, 2017 at 12:25 PM, Peter Ten Eyck <
peter.tene...@americannational.com> wrote:

> Can someone point me to some documentation (coding examples) on how to use
> the SDSF API in REXX? I have my REXX/SDSF exec working, but it runs slow
> issuing those commands. I would like to try a different approach.
>
>
​An example of one of mine, which some others have said was useful, is
here: https://gist.github.com/JohnArchieMckown/b27747d0c4750a258997​


-- 
*L'Shanah Tovah Tikatevu*

Maranatha! <><
John McKown

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


Re: REXX and SDSF question (expanded API question)

2017-09-20 Thread Peter Ten Eyck
Can someone point me to some documentation (coding examples) on how to use the 
SDSF API in REXX? I have my REXX/SDSF exec working, but it runs slow issuing 
those commands. I would like to try a different approach.

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


Re: REXX and SDSF question

2017-09-19 Thread Peter Ten Eyck
Yes, that API does sound nice. This is the technique documented in the Redbook 
for REXX and SDSF, which was the starting point for my REXX script. Thanks for 
the tip.

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


Re: REXX and SDSF question

2017-09-18 Thread Jesse 1 Robinson
As Gil noted, this is the old pre-API method of running SDSF out of Rexx. 
There's nothing essentially wrong with the technique except that you have to 
orchestrate a complete scenario like a line of domino tiles. If anything goes 
wrong, you have no way to intervene and change direction. The API allows you 
execute SDSF functions and take action based on what actually happens rather 
than solely on what you planned for.

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Peter Ten Eyck
Sent: Monday, September 18, 2017 1:10 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: REXX and SDSF question

This is now working for me. I added the SDSF command input on to see all DDs 
via TSO SDSF and ISPF SDSF:

CHECKCICSSTATUS:
ADDRESS TSO 
 "ALLOC F(FILEOUT) UNIT(VIO) NEW REUSE",  "CYLINDERS SPACE(10 10) RECFM(F B A)" 
 
 "ALLOC FI(ISFOUT) SYSOUT(Q)"   
 "ALLOC F(ISFIN) UNIT(VIO) NEW REUSE",  
 "RECFM(F B) BLK(3120) LRECL(80)",  
 "SPACE(5 5) CYLINDERS DSORG(PS)"   
 QUEUE " DA ALL"
 QUEUE " OWNER *"   
 QUEUE " SYSNAME ESA1"  
 QUEUE " INPUT ON"  
 QUEUE " PRE " CICSREGION   
 QUEUE " FIND " CICSREGION  
 QUEUE " ++?"   
 QUEUE " FIND JESMSGLG" 
 QUEUE " ++S"   
 QUEUE " PRINT FILE FILEOUT"
 QUEUE " PRINT" 
 QUEUE " PRINT CLOSE"   
 QUEUE ""   
 "EXECIO * DISKW ISFIN (FINIS"  
ADDRESS ISPEXEC 
 "SELECT PGM(SDSF)"

Thanks for all the suggestions.


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


Re: REXX and SDSF question

2017-09-18 Thread Paul Gilmartin
On Mon, 18 Sep 2017 15:09:45 -0500, Peter Ten Eyck wrote:

>This is now working for me. I added the SDSF command input on to see all DDs 
>via TSO SDSF and ISPF SDSF:
>
>CHECKCICSSTATUS:
>ADDRESS TSO 
> "ALLOC F(FILEOUT) UNIT(VIO) NEW REUSE",
> "CYLINDERS SPACE(10 10) RECFM(F B A)"  
> "ALLOC FI(ISFOUT) SYSOUT(Q)"   
> "ALLOC F(ISFIN) UNIT(VIO) NEW REUSE",  
> "RECFM(F B) BLK(3120) LRECL(80)",  
> "SPACE(5 5) CYLINDERS DSORG(PS)"   
> QUEUE " DA ALL"
> QUEUE " OWNER *"   
> QUEUE " SYSNAME ESA1"  
> QUEUE " INPUT ON"  
> QUEUE " PRE " CICSREGION   
> QUEUE " FIND " CICSREGION  
> QUEUE " ++?"   
> QUEUE " FIND JESMSGLG" 
> QUEUE " ++S"   
> QUEUE " PRINT FILE FILEOUT"
> QUEUE " PRINT" 
> QUEUE " PRINT CLOSE"   
> QUEUE ""   
> "EXECIO * DISKW ISFIN (FINIS"  
>ADDRESS ISPEXEC 
> "SELECT PGM(SDSF)"
>
Guessing at the answer to Eileen's question:

On 2017-09-18, at 12:55, Barkow, Eileen wrote:

>Not that it would necessarily fix the problem, but you are using the old 
>SDSF/BATCH product
>and not the SDSF/REXX interface.  SDSF/REXX has parms like ISFPREFIX, 
>ISFOWNER, ISFFILTER.
>
... It appears that you're using neither, but a sort of Screen Operations 
Simulation.
That more approximates batch than an API.

I find the API very powerful, not least because I get a status that I can act 
upon
from each command -- not possible with queued commands, and because I can use
it not only from ISPF but also from JCL and even from a UNIX session -- no TSO
(much less ISPF) needed.

-- gil

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


Re: REXX and SDSF question

2017-09-18 Thread Peter Ten Eyck
This is now working for me. I added the SDSF command input on to see all DDs 
via TSO SDSF and ISPF SDSF:

CHECKCICSSTATUS:
ADDRESS TSO 
 "ALLOC F(FILEOUT) UNIT(VIO) NEW REUSE",
 "CYLINDERS SPACE(10 10) RECFM(F B A)"  
 "ALLOC FI(ISFOUT) SYSOUT(Q)"   
 "ALLOC F(ISFIN) UNIT(VIO) NEW REUSE",  
 "RECFM(F B) BLK(3120) LRECL(80)",  
 "SPACE(5 5) CYLINDERS DSORG(PS)"   
 QUEUE " DA ALL"
 QUEUE " OWNER *"   
 QUEUE " SYSNAME ESA1"  
 QUEUE " INPUT ON"  
 QUEUE " PRE " CICSREGION   
 QUEUE " FIND " CICSREGION  
 QUEUE " ++?"   
 QUEUE " FIND JESMSGLG" 
 QUEUE " ++S"   
 QUEUE " PRINT FILE FILEOUT"
 QUEUE " PRINT" 
 QUEUE " PRINT CLOSE"   
 QUEUE ""   
 "EXECIO * DISKW ISFIN (FINIS"  
ADDRESS ISPEXEC 
 "SELECT PGM(SDSF)"

Thanks for all the suggestions.

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


Re: REXX and SDSF question

2017-09-18 Thread Elardus Engelbrecht
Peter Ten Eyck wrote:

>I have found the issue. STC output is displayed differently (DDs displayed) on 
>this LPAR when viewing it through SDSF launched via the ISPF menu option; 
>compared to SDSF launched via TSO command line. I do not know why, researching.

Bravo, you, as a brave detective, really deserve a polished and clean golden 
star! ;-)

This is what I suspected, look at the source which provide data to you program. 
Now I will remember next time (when someone is moaning and b*tching) to look at 
the DD used. Thanks!

Good luck finding out why. if you can, please be very kind post what you found. 
I really believe someone in IBM-MAIN will benefit from what you can post.

Thanks, your thread was really interesting and educational for me.

Groete / Greetings
Elardus Engelbrecht

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


Re: REXX and SDSF question

2017-09-18 Thread Peter Ten Eyck
I have found the issue. STC output is displayed differently (DDs displayed) on 
this LPAR when viewing it through SDSF launched via the ISPF menu option; 
compared to SDSF launched via TSO command line. I do not know why, researching.

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


Re: REXX and SDSF question

2017-09-18 Thread Ed Jaffe

On 9/18/2017 11:43 AM, Paul Gilmartin wrote:


Someone will proudly tell you that (E)JES has a command that shows
everything in the spool so you don't need to jump around madly.
I don't know whether that likewise covers the Rexx API.


Haha! But, of course!
[Spoken with an French Occitan accent ;-) ]

--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/

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


Re: REXX and SDSF question

2017-09-18 Thread Barkow, Eileen
Not that it would necessarily fix the problem, but you are using the old 
SDSF/BATCH product and not the SDSF/REXX interface.
SDSF/REXX has parms like ISFPREFIX, ISFOWNER, ISFFILTER.


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Elardus Engelbrecht
Sent: Monday, September 18, 2017 2:50 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX and SDSF question

Grinsell, Don wrote:

>>Are you accommodating for the different SYSNAMEs that you are processing 
>>(LPARs) : QUEUE " SYSNAME ESA1"
>Good eye.  I'm betting you'll be getting the gold star for this one.  ☺

I originally missed that one, and of course I will not get a gold star. ;-)

Thanks for mentioning that!


Paul Gilmartin wrote:

>>"ALLOC FI(ISFOUT) SYSOUT(X)"
>Is X a bitbucket class?  (I suspect it's configurable in PARMs.)

No, at least not for us. The OP could use another class. I just copied/modified 
that line from one of my REXX/SDSF jobs.

We have an output class defined as bitbucket class. Very handy for jobs with 
One-Time-Passwords.

Groete / Greetings
Elardus Engelbrecht

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




This e-mail, including any attachments, may be confidential, privileged or 
otherwise legally protected. It is intended only for the addressee. If you 
received this e-mail in error or from someone who was not authorized to send it 
to you, do not disseminate, copy or otherwise use this e-mail or its 
attachments. Please notify the sender immediately by reply e-mail and delete 
the e-mail 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: REXX and SDSF question

2017-09-18 Thread Elardus Engelbrecht
Grinsell, Don wrote:

>>Are you accommodating for the different SYSNAMEs that you are processing 
>>(LPARs) : QUEUE " SYSNAME ESA1" 
>Good eye.  I'm betting you'll be getting the gold star for this one.  ☺ 

I originally missed that one, and of course I will not get a gold star. ;-)

Thanks for mentioning that!


Paul Gilmartin wrote:

>>"ALLOC FI(ISFOUT) SYSOUT(X)"  
>Is X a bitbucket class?  (I suspect it's configurable in PARMs.)

No, at least not for us. The OP could use another class. I just copied/modified 
that line from one of my REXX/SDSF jobs.

We have an output class defined as bitbucket class. Very handy for jobs with 
One-Time-Passwords.

Groete / Greetings
Elardus Engelbrecht

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


Re: REXX and SDSF question

2017-09-18 Thread Grinsell, Don
Anthony,

Good eye.  I'm betting you'll be getting the gold star for this one.  ☺

Regards.

--
 
Donald Grinsell, Systems Programmer
Enterprise Technology Services Bureau
SITSD/Montana Department of Administration
406.444.2983 (D)


"I would like to see every single soldier on every single side, just take off 
your helmet, unbuckle your kit, lay down your rifle, and set down at the side 
of some shady lane, and say, nope, I aint a gonna kill nobody.  Plenty of rich 
folks wants to fight.  Give them the guns."
~ Woody Guthrie

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Cieri, Anthony
> Sent: Monday, September 18, 2017 12:36 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: REXX and SDSF question
> 
> 
>   Are you accommodating for the different SYSNAMEs that you are
> processing (LPARs) :
> 
>   QUEUE " SYSNAME ESA1"
> 
> 
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Barkow, Eileen
> Sent: Monday, September 18, 2017 2:30 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: REXX and SDSF question
> 
> Is CICSREGION set properly?
> What happens if you hard code the region name prefix?
> Or try it in quotes and SET DISPLAY ON:
> 
> QUEUE "SET DISPLAY ON"
> QUEUE "PREFIX "CICSREGION"  "
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Peter Ten Eyck
> Sent: Monday, September 18, 2017 12:43 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: REXX and SDSF question
> 
> I have some rexx code that is working on one z/OS 2.2 LPAR and "partially" on
> another.
> 
> The code determines if a CICS region is running and if the desired messages
> are found in the DD JESMSGLG.
> 
> This code chunk is what goes out gets the SDSF output:
> 
> CHECKCICSSTATUS:
> ADDRESS TSO
>  "ALLOC F(FILEOUT) UNIT(VIO) NEW REUSE",  "CYLINDERS SPACE(10 10) RECFM(F B
> A)"
>  "ALLOC FI(ISFOUT) DUMMY"
>  "ALLOC F(ISFIN) UNIT(VIO) NEW REUSE",
>  "RECFM(F B) BLK(3120) LRECL(80)",
>  "SPACE(5 5) CYLINDERS DSORG(PS)"
>  QUEUE " DA ALL"
>  QUEUE " OWNER"
>  QUEUE " SYSNAME ESA1"
>  QUEUE " PRE " CICSREGION
>  QUEUE " FIND " CICSREGION
>  QUEUE " ++?"
>  QUEUE " FIND JESMSGLG"
>  QUEUE " ++S"
>  QUEUE " PRINT FILE FILEOUT"
>  QUEUE " PRINT"
>  QUEUE " PRINT CLOSE"
>  QUEUE ""
>  "EXECIO * DISKW ISFIN (FINIS"
> ADDRESS ISPEXEC
>  "SELECT PGM(SDSF)"
> ADDRESS TSO
>  "EXECIO * DISKR FILEOUT (STEM REC. FINIS"
>  "FREE FI(ISFIN ISFOUT FILEOUT)"
> 
> It returns all the output records in a stem variable REC.
> 
> REC.0 contains the total number of records and REC.1 - REC.?
> contains each record.
> 
> This works fine on one LPAR and works for something's (possibly just jobs) on
> another LPAR, but not STCs.
> 
> Does anyone have a suggestion why I am not able to retrieve the output for
> STCs on one of the LPARs?
> 
> Scratching my head...
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> 
> 
> 
> This e-mail, including any attachments, may be confidential, privileged or
> otherwise legally protected. It is intended only for the addressee. If you
> received this e-mail in error or from someone who was not authorized to send
> it to you, do not disseminate, copy or otherwise use this e-mail or its
> attachments. Please notify the sender immediately by reply e-mail and delete
> the e-mail 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

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


Re: REXX and SDSF question

2017-09-18 Thread Paul Gilmartin
On Mon, 18 Sep 2017 12:17:47 -0500, Elardus Engelbrecht wrote:

>Peter Ten Eyck wrote:
>
>> "ALLOC FI(ISFOUT) DUMMY"   
>
>I'm curious, why DUMMY?
>
>Try this out just for tests and see if something appears there:
>
>"ALLOC FI(ISFOUT) SYSOUT(X)"  
> 
Is X a bitbucket class?  (I suspect it's configurable in PARMs.)

-- gil

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


Re: REXX and SDSF question

2017-09-18 Thread Cieri, Anthony

Are you accommodating for the different SYSNAMEs that you are 
processing (LPARs) :

QUEUE " SYSNAME ESA1"



-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Barkow, Eileen
Sent: Monday, September 18, 2017 2:30 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX and SDSF question

Is CICSREGION set properly?
What happens if you hard code the region name prefix?
Or try it in quotes and SET DISPLAY ON:

QUEUE "SET DISPLAY ON"
QUEUE "PREFIX "CICSREGION"  "

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Peter Ten Eyck
Sent: Monday, September 18, 2017 12:43 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: REXX and SDSF question

I have some rexx code that is working on one z/OS 2.2 LPAR and "partially" on 
another.

The code determines if a CICS region is running and if the desired messages are 
found in the DD JESMSGLG.

This code chunk is what goes out gets the SDSF output:

CHECKCICSSTATUS:
ADDRESS TSO
 "ALLOC F(FILEOUT) UNIT(VIO) NEW REUSE",  "CYLINDERS SPACE(10 10) RECFM(F B A)"
 "ALLOC FI(ISFOUT) DUMMY"
 "ALLOC F(ISFIN) UNIT(VIO) NEW REUSE",
 "RECFM(F B) BLK(3120) LRECL(80)",
 "SPACE(5 5) CYLINDERS DSORG(PS)"
 QUEUE " DA ALL"
 QUEUE " OWNER"
 QUEUE " SYSNAME ESA1"
 QUEUE " PRE " CICSREGION
 QUEUE " FIND " CICSREGION
 QUEUE " ++?"
 QUEUE " FIND JESMSGLG"
 QUEUE " ++S"
 QUEUE " PRINT FILE FILEOUT"
 QUEUE " PRINT"
 QUEUE " PRINT CLOSE"
 QUEUE ""
 "EXECIO * DISKW ISFIN (FINIS"
ADDRESS ISPEXEC
 "SELECT PGM(SDSF)"
ADDRESS TSO
 "EXECIO * DISKR FILEOUT (STEM REC. FINIS"
 "FREE FI(ISFIN ISFOUT FILEOUT)"

It returns all the output records in a stem variable REC.

REC.0 contains the total number of records and REC.1 - REC.?
contains each record.

This works fine on one LPAR and works for something's (possibly just jobs) on 
another LPAR, but not STCs.

Does anyone have a suggestion why I am not able to retrieve the output for STCs 
on one of the LPARs?

Scratching my head...

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




This e-mail, including any attachments, may be confidential, privileged or 
otherwise legally protected. It is intended only for the addressee. If you 
received this e-mail in error or from someone who was not authorized to send it 
to you, do not disseminate, copy or otherwise use this e-mail or its 
attachments. Please notify the sender immediately by reply e-mail and delete 
the e-mail 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: REXX and SDSF question

2017-09-18 Thread Barkow, Eileen
Is CICSREGION set properly?
What happens if you hard code the region name prefix?
Or try it in quotes and SET DISPLAY ON:

QUEUE "SET DISPLAY ON"
QUEUE "PREFIX "CICSREGION"  "

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Peter Ten Eyck
Sent: Monday, September 18, 2017 12:43 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: REXX and SDSF question

I have some rexx code that is working on one z/OS 2.2 LPAR and "partially" on 
another.

The code determines if a CICS region is running and if the desired messages are 
found
in the DD JESMSGLG.

This code chunk is what goes out gets the SDSF output:

CHECKCICSSTATUS:
ADDRESS TSO
 "ALLOC F(FILEOUT) UNIT(VIO) NEW REUSE",
 "CYLINDERS SPACE(10 10) RECFM(F B A)"
 "ALLOC FI(ISFOUT) DUMMY"
 "ALLOC F(ISFIN) UNIT(VIO) NEW REUSE",
 "RECFM(F B) BLK(3120) LRECL(80)",
 "SPACE(5 5) CYLINDERS DSORG(PS)"
 QUEUE " DA ALL"
 QUEUE " OWNER"
 QUEUE " SYSNAME ESA1"
 QUEUE " PRE " CICSREGION
 QUEUE " FIND " CICSREGION
 QUEUE " ++?"
 QUEUE " FIND JESMSGLG"
 QUEUE " ++S"
 QUEUE " PRINT FILE FILEOUT"
 QUEUE " PRINT"
 QUEUE " PRINT CLOSE"
 QUEUE ""
 "EXECIO * DISKW ISFIN (FINIS"
ADDRESS ISPEXEC
 "SELECT PGM(SDSF)"
ADDRESS TSO
 "EXECIO * DISKR FILEOUT (STEM REC. FINIS"
 "FREE FI(ISFIN ISFOUT FILEOUT)"

It returns all the output records in a stem variable REC.

REC.0 contains the total number of records and REC.1 - REC.?
contains each record.

This works fine on one LPAR and works for something's (possibly just jobs) on 
another LPAR, but not STCs.

Does anyone have a suggestion why I am not able to retrieve the output for STCs 
on one of the LPARs?

Scratching my head...

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




This e-mail, including any attachments, may be confidential, privileged or 
otherwise legally protected. It is intended only for the addressee. If you 
received this e-mail in error or from someone who was not authorized to send it 
to you, do not disseminate, copy or otherwise use this e-mail or its 
attachments. Please notify the sender immediately by reply e-mail and delete 
the e-mail 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: REXX and SDSF question

2017-09-18 Thread Peter Ten Eyck
Yes, I have tried that, no change. Recall that this REXX exec is working on the 
LPAR for CICS regions running as jobs and the commands do work manually. I must 
be missing something...

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


Re: REXX and SDSF question

2017-09-18 Thread Barkow, Eileen
Try  QUEUE "OWNER *" not just OWNER

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Elardus Engelbrecht
Sent: Monday, September 18, 2017 1:12 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: REXX and SDSF question

Peter Ten Eyck  wrote:

> QUEUE " DA ALL"
> QUEUE " OWNER"
> QUEUE " SYSNAME ESA1"
> QUEUE " PRE " CICSREGION

... and ...

>This works fine on one LPAR and works for something's (possibly just jobs) on 
>another LPAR, but not STCs.
>Does anyone have a suggestion why I am not able to retrieve the output for 
>STCs on one of the LPARs?

Check that your are not limited by FILTER (FILTER should be OFF), DESTINATION, 
etc.

Try your SDSF by hand, one command after the other and compare the results.

Also compare the WHO command in SDSF.

Once all is the same at the SOURCE (SDSF) of your records, I believe the 
problem is then in your REXX program.

Check/compare your RACF authority in JESSPOOL and SDSF classes.


>Scratching my head...

I also get now and then some queries why I don't see X, Y, Z in SDSF, I know 
they have run because of NOTIFY for example...

Groete / Greetings
Elardus Engelbrecht

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




This e-mail, including any attachments, may be confidential, privileged or 
otherwise legally protected. It is intended only for the addressee. If you 
received this e-mail in error or from someone who was not authorized to send it 
to you, do not disseminate, copy or otherwise use this e-mail or its 
attachments. Please notify the sender immediately by reply e-mail and delete 
the e-mail 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: REXX and SDSF question

2017-09-18 Thread Peter Ten Eyck
This is how it was coded in my starting example code from the Redbook. I 
changed it to your suggestion, no change, still not getting the output.

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


Re: REXX and SDSF question

2017-09-18 Thread Peter Ten Eyck
Yes, I have manually entered the SDSF commands for the STCs not working... and 
they work (output retrieved). I think that takes care of SDSF and RACF. The 
REXX exec runs under my id.

I did see a difference with the WHO command...COMM=NOTAVAIL as opposed to 
COMM=ENABLED.

Recall that this REXX exec is working for CICS regions that are running as 
jobs, but not for CICS regions running as STCs. It works for CICS regions 
running as STCs on another LPAR.

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


Re: REXX and SDSF question

2017-09-18 Thread Elardus Engelbrecht
Peter Ten Eyck wrote:

> "ALLOC FI(ISFOUT) DUMMY"   

I'm curious, why DUMMY?

Try this out just for tests and see if something appears there:

"ALLOC FI(ISFOUT) SYSOUT(X)"  

Groete / Greetings
Elardus Engelbrecht

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


Re: REXX and SDSF question

2017-09-18 Thread Elardus Engelbrecht
Peter Ten Eyck  wrote:

> QUEUE " DA ALL"
> QUEUE " OWNER" 
> QUEUE " SYSNAME ESA1"  
> QUEUE " PRE " CICSREGION   

... and ...

>This works fine on one LPAR and works for something's (possibly just jobs) on 
>another LPAR, but not STCs.
>Does anyone have a suggestion why I am not able to retrieve the output for 
>STCs on one of the LPARs?

Check that your are not limited by FILTER (FILTER should be OFF), DESTINATION, 
etc.

Try your SDSF by hand, one command after the other and compare the results.

Also compare the WHO command in SDSF.

Once all is the same at the SOURCE (SDSF) of your records, I believe the 
problem is then in your REXX program.

Check/compare your RACF authority in JESSPOOL and SDSF classes.


>Scratching my head...

I also get now and then some queries why I don't see X, Y, Z in SDSF, I know 
they have run because of NOTIFY for example...

Groete / Greetings
Elardus Engelbrecht

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