Is the FTP destination another JES environment? If so, maybe SPOOL offload could be leveraged. It looks like offload transmitters can be defined to limit jobs by different criteria (jobname, creator, class, etc.)
I had envisioned a short term SPOOL backup/restore scheme using transmitters for backup and receivers for restore if/when someone accidently purged a job and wanted it back. I never got around to ever make it happen. If I recall, RETPD played a part on the OFFLOAD(n) definition to keep it "short term", and DISP=KEEP as part of the OFF(n).JT definition. I was inspired by the process during offsite Disaster Recovery exercises where offloaders were used to bring job output back home from the DR site. On Wed, Jan 14, 2026 at 2:45 PM Phil Smith III <[email protected]> wrote: > I'm tinkering with a Rexx program to take job output from SPOOL and put it > in a deterministic disk data set so it can be FTPed later. > > First, if there's a better way than using ISFEXEC, please point me! > > I have it all working except I can't find the JES DDnames in any of the > variables created by ISFACT ST. I mean JESMSGLG, JESJCL, JESYSMSG, > SYSPRINT, et al. Are those available anywhere? What I want them for is so > the output could be: > > --JESMSGLG------------- > <lines from JESMSGLG> > --JESJCL--------------- > <lines from JESJCL> > etc. > > That's not a hard requirement, just seems like it would be useful. > > Any ideas? TIA > > ---------------------------------------------------------------------- > 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
