To me, the simplest way would be to ftp the desired data to an appropriately allocated dataset, and then change to filetype=jes to put jcl to copy the newly created dataset to sysout, and perform housekeeping if/when the copy was complete. I do not believe filetype=jes was meant to be exclusive.
On Fri, Sep 22, 2023 at 3:26 PM Schmitt, Michael <[email protected]> wrote: > Is there a way to transfer sysout type data from a remote, non-mainframe > system, into a JES3 spool? From which already existing tasks will grab the > output according to destination, class, writer, etc. > > Such as, use some product or capability to connect and transfer to a > TCP/IP port. > > Most of what I see is going the other direction, answering the question of > "how do I get this report from the JES spool to my printer/pc/file > server/etc?" But I need to get it into JES3, because the existing report > distribution software wants to grab it from there. > > I thought I remembered being able to inject jobs into the IEFRDER via FTP, > and thought perhaps could also transfer to sysout, but don't see it in the > Communications Server manual. > > Bonus points for a solution that will also work with JES2, after the > inevitable end-of-support for JES3. > > ______________________________________________ > Michael Schmitt | DXC Apps Development | MassMutual > (737) 910-8248 | [email protected] > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
