On Wed, 6 Jan 2016 19:01:15 -0500, Tony Harminc wrote: >And this all started with arbitrary (GOFF) files as input to SMP/E, >which has, AFAIK, no delimiter option on e.g. the ++MOD statement. JCL >isn't the only thing with this problem. A single GOFF file could >plausibly contain records starting with ++ and // and /* .
Even if that were true, I fail to see what the fuss is all about. Why would anyone want to go to the trouble of wrapping JCL around such a file such that it would be read as in-stream data? Why not code the reference to the data set? This all started when Gil complained that GIMDTS won't transform FB 80-byte data unless it contains a "++" in columns 1 and 2 What about "//", he said. I didn't understand why he needed to GIMDTS to transform data containing such a file. I still don't understand why. The example of DD * data that contains JCL seems contrived. Do you really build JCL containing in-stream data that you don't know the contents of, and that you can't select a delimiter for? Does anyone build JCL that contains in-stream data with arbitrary contents? I remain unconvinced that there is a need for GIMDTS to transform data just because it contains "//" or "/*" in columns 1 and 2. If this hs ever come up as a problem for you where you couldn't select a two byte delimiter, please show an example. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
