On Wed, 7 May 2025 19:42:30 +0000, Seymour J Metz wrote: >The only utility I can see is that it protects jo from a malformed JOB card >following your job.
On Wed, 7 May 2025 19:46:57 +0000, Seymour J Metz wrote: >DD DATA,DLM='xx'' suppresses recognition of a null statement, but I suspect >that a /*EOF on the internal reader will terminate the job prematurely. BAD. > Are we discussing INTRDR or a physical (possibly virtual) reader? In the former case, it might be due caution, even as I prefer explicit "//SYSIN DD *" to the implied form, and wish the explicit were mandatory. I don't recall that I've ever submitted multiple jobs to INtRDR in a single file. For a physical reader, a careless or mischievous programmer might disable the terminator with "DLM=xx" and read succeeding jobs, possibly violating security. The only defense is to require the operator to load single jobs and press the EOF button after each. I once used a (non-IBM) site where the operator inserted a terminator card after each job. The terminator had a distinctive color and corner cut, but IIRC its recognition could be disabled. Alas, no reader can detect the cut corner. Distantly related, I once received a punched output deck with one card backward. I repaired it by inverting the card and reproducing it. I surmise that the operator had loaded the card inverted in the hopper, noticed the wrong corner only in the stacker and attempted a repair by inverting the card ex post facto. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
