Since you have a "shared I/O module", it's possible that it may have to accept a mixture of both RECFM=A and RECFM=M records. If this is the case, it would have to normalize the records before output. For final printing, the control characters would need to be in the form of channel commands and so RECFM=M would be the obvious choice of norm. After all, someone has to do the conversion whether it be the access method, JES, or this shared I/O module. It wouldn't make sense for this module arbitrarily to choose RECFM=A knowing that, at some point, some other module would have to convert to RECFM=M.
A quick glance at the tables provided by Chris Mason reveals that the codes are unique with the exception of x'C1' so, unless someone is "skipping to channel 10 before printing" or "skipping to channel 8 after printing", the shared module would not have to concern itself with ambiguity. ;-) I note that recent versions of the (green/white/yellow) Reference Summary do not list any channel skipping other than for line 1. > Date: Fri, 15 Jan 2010 18:19:45 -0700 > From: [email protected] > Subject: sysout using machine control instead of ANSI control > To: [email protected] > > Is there any reason that an Enterprise Cobol 4.2 program running under > z/OS 1.10 might use 'machine control' characters instead of ANSI characters? > > We have a vendor program that uses a rather complex shared I/O module, > and it appears to be the only one that's doing it. > _________________________________________________________________ Your E-mail and More On-the-Go. Get Windows Live Hotmail Free. http://clk.atdmt.com/GBL/go/196390709/direct/01/ ---------------------------------------------------------------------- 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
