So write a PROC that puts INPUT with SYSUT1 and OUTPUT with SYSUT2. I even took this a step further and had OUTPUT get deleted first before AMATERSE.
Sent from my iPhone — small keyboarf, fat fungrs, stupd spell manglr. Expct mistaks > On Dec 24, 2020, at 3:56 PM, Paul Gilmartin > <[email protected]> wrote: > > On Wed, 23 Dec 2020 15:40:23 +0000, Pommier, Rex wrote: >> >> Yeah there's a problem with it - a human problem. It's easy when in a hurry >> to miss the fact they're reversed and key the input dataset name in the >> SYSUT2 and the output in the SYSUT1 if you're not paying attention. Yeah I >> know it's self-inflicted but that was what I thought when I saw Tom's >> comment. BTDT, felt the pain. >> > SYSUT1 and SYSUT2 are so visually similar that they invite errors. > TRSMAIN was better, using INFILE and OUTFILE. The developers > took a step in the wrong direction when AMATERSE switched to the > more error-prone SYSUT1 and SYSUT2. Just because other utilities > had the same flaw. > > "A foolish consistency is the hobgoblin of little minds, adored by > little statesmen and philosophers and divines." -- Emerson > > -- gil > > ---------------------------------------------------------------------- > 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
