On Mon, 7 Dec 2015 11:15:29 -0600, Paul Gilmartin (whoever) wrote:
>
>I'll read doc for SDSF to see whether its API provides a way to capture output
>from operator commands it issues.
>
So: in:
http://www-01.ibm.com/support/knowledgecenter/api/content/nl/en-us/SSLTBW_2.1.0/com.ibm.zos.v2r1.isfa500/comline.htm
I read:
Issuing MVS or JES commands
z/OS SDSF Operation and Customization
SA23-2274-00
...
The messages issued in response are displayed on the information lines of the
panel. The complete set of responses is in the user session log (ULOG).
>
So, issue the command with ISFSLASH and scrape ULOG for the result.
Hope it's not stuck in a buffer.
>... You can set a delay interval, which is the maximum amount of time SDSF
>will wait for messages, with this command: SET DELAY seconds. The default is 1
>second. A delay of 0 specifies that messages issued in response to / commands
>should not be displayed on the message lines.
>
Terrible design! Simply should have a WAIT option so the command doesn't
return until complete.
REXX: Use ISFSLASH. See Issuing system commands with ISFSLASH.
>z/OS's lack of redirection is primitive. I've seen the technique of issuing a
>command
>and WAITing an unknowable interval for its output to become available.
>
Like I said. Equally bad is that HSM messages are not necessarily returned to
the
requesting address space.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
