How about TSO output command to list all waiting files?

ITschak

ITschak Mugzach
Z/OS, ISV Products and Application Security & Risk Assessments Professional

On Thu, Nov 19, 2015 at 8:33 PM, Paul Gilmartin <
0000000433f07816-dmarc-requ...@listserv.ua.edu> wrote:

> On Thu, 19 Nov 2015 12:18:23 -0600, Elardus Engelbrecht wrote:
> >
> >>RECEIVE is extraordinarily ill-suited to automation:
> >>o The user has no a priori control over which spool file will be
> RECEIVEd.
> >>o The user must be present to reply to a prompt.
> >
> >That is very true. JES2 simply gives to you what it seemed to be the
> first. I could not find the reason/algorithm for how RECEIVE and JES2
> decide what to present to the receiver.
> >
> Deep within the Rexx SDSF API, a program can cause SDSF to ALLOCATE
> a DSID to a SYS00nnn DD name.  The programmer could use that in
> RECEIVE INDD(SYS00nnn) (I think; I haven't tried it.), gaining control of
> what to RECEIVE.
>
> >I recommend using FTP instead of XMIT/RECEIVE for another reason - Speed
> and no filling up of JES2 spool.
> >
> I like a combination of sftp and pax.
>
> -- 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

Reply via email to