On Mon, 16 Jun 2008 09:56:33 -0300, Shmuel Metz (Seymour J.) wrote: >In <[EMAIL PROTECTED]>, on >06/15/2008 > at 09:07 PM, John McKown <[EMAIL PROTECTED]> said: > >>The above inserts the comma between (e.g) TOM and DICK. Suppose that I >>need a PARM of 80 characters which contains no commas anywhere in it? > >Then you run it out to column 71[1], put a continuation character in >column 72[1] and continue it in the next record, per existing rules. > As I stated, if columns 71-72 fall within a JCL symbol, the converter fails to substitute the symbol value. IBM has told me this is "working as intended". I'm highly skeptical. This strikes me as less likely the effect of what the designer "intended" and more likely the effect of an implementor's lack of pride in craftsmanship, with ex_post_facto specification.
>In <[EMAIL PROTECTED]>, on >06/15/2008 > at 09:08 PM, John McKown said: > >>I know that BSAM itself doesn't do the folding. > >Then it doesn't get folded, because there is no TSO code between you and >the READ or CHECK macro. > >>What I think happens is that the TSO service > >What TSO service? The behavior is the same when you do the READ from your >own code. Is IEBGENER a TSO service? > Ummm. I was able to circumvent the behavior with a TGET. What acess method, then, does TGET use? Or is TGET itself an access method? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
