On Tue, 16 Aug 2016 08:31:19 -0700, Ed Jaffe wrote:
>On 8/16/2016 7:37 AM, Jon Bathmaker wrote:
>> Hi,
>> We are running NVAS and the SYSPRINT file gets directed to SYSOUT=* which is
>> fine as we can browse it if we need to.
>>
>> For some reason (Audit request?) I am being asked to vacuum up the SYSOUT
>> file and put it into a GDG when the task is recycled, while still leaving it
>> as SYSOUT when the STC is active. . Based on a message I received, a disp
>> of PASS and SYSOUT are incompatible. I am now considering using SDSF in
>> batch so solve this problem (thanks to Lorne Heffer).
>>
The SDSF Ops and Customization manual admits that Rexx is a better
alternative to SDSF in batch. That's easily true.
>> Anyone have any ideas? Using a commercial Program Product is a non-starter
>> as, like everyone else the client is only interested in lower cost. Thanks.
>
>Note: SDSF _is_ a commercial Program Product with an associated price tag.
>
Yes, but is it nonetheless available to Jon's client?
>You might consider a second step ... SDSF
>should have a similar capability, but I'm not sure how you get the
>"current" job name and/or number into variables you can use for
>selection purposes. You might have to do it through REXX instead.
>
I can get job number with:
address ISPEXEC 'vget (ZSEQ) shared'
... I just need to claw my way upward from a batch job step,
through TSO, then through ISPF, then adapt the sample in
the SDSF manual.
I wonder whether it works while the job is executing?
Yes, at least in PoC. If it logs what it's doing, the output
ends in the middle of SYSTSPRT, right after the line that
says it's unloading SYSTSPRT. Very nice!
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
