There should be no performance difference; the access needs to look a line ahead for RECFM=*A in order to determine the appropriate CCW opcode, but that takes a negligible amount of CPU time compared to everything else it does.
> Doesn't seem right to me. If we're takling ANSI carriage control. > 0 - move double Change previous 09 (Write and Space 1 Line) CCW opcode to 11 (Write and Space 2 Lines) > blank - move single No change to previous CCW + - no LF Change previous 09 (Write and Space 1 Line) CCW opcode to 01 (Write Without Spacing) 1 - Skip to next page (Channel 1) Change previous 09 (Write and Space 1 Line) CCW opcode to 89 (Write and Skip to Channel 1) In the days of the 1401 there was no RECFM=*M; the W instruction always spaced one line after printing and the F instruction did an immediate skip, immediate space, skip after next print or space after next print depending on the value of the d character. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Wayne Bickerdike [wayn...@gmail.com] Sent: Monday, April 27, 2020 9:47 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: C Doesn't seem right to me. If we're takling ANSI carriage control. 0 - move double blank - move single + - no LF 1 - Skip to next page (Channel 1) We always used machine code characters because they didn't have to be immediate whereas ANSI were immediate. The reasoning was that it was faster to perform the print action and then do the carriage move to the next line or channel. In the days of the 1403 line printer. On Tue, Apr 28, 2020 at 7:21 AM Seymour J Metz <sme...@gmu.edu> wrote: > That's OS/360, not just MVT, and it applies to COBOL E and F, which do not > claim to be standards compliant. > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > ________________________________________ > From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf > of Joe Monk [joemon...@gmail.com] > Sent: Monday, April 27, 2020 3:31 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: C > > Not according to the MVT Cobol compiler manual... > > "The AFTER ADVANCING option is used for output destined to be printed or > punched. When this option is used, the first character in each logical > record for the file must be reserved for the control character. When the > AFTER > ADVANCING option is used, integer must be unsigned and have the value 0, 1, > 2, or 3. The value 0 designates a carriage-control eject (i.e., skip to > next > page). The value 1 designates single spacing; the value 2, double spacing; > and the value 3, triple spacing." > > > http://secure-web.cisco.com/13JssaKkgEv6PvHbWqBb4_nGJr_KEk7X_p5dUxZ430B0TL067KAC3GmG62amVkyrK0wFJ6uAEiyuAI7pb90pBKUQu0efiy_EcUfFMps04VF_q3JCv2_EZfIyvaUoSxqVPc2j53HP4bEbd1UFUAFCLEfVb44yWkXMNs6D-ajkuaFWpwmOQ7DLdelU_kFoBfwK5MZ_99qKk1CuLZlVgozWOZL-_bSq_TGDGSJTg-n_WyQMcvJyYY36pAe8ZuT04bcBv85pG4_ec93Kta1h-fnUfm1av5W4Rrbx5p7qylU04uJOEM0P6WFyLKZsVsN9fcwPlF6x_1LZidv6aycTEAYyrPSpAWy7wZpPldHH-cnTUKc-qPz9772YMzNFNq0kfjiUmqVlSSL_YelM-_hg_l4oKtelOcnJWpjuuVTQ6Ppnp-zMhgROTwHMtUNj4JWJLEXBR/http%3A%2F%2Fwww.bitsavers.org%2Fpdf%2Fibm%2F360%2Fos%2Fcobol%2FC28-6516-2_IBM_OS360_COBOL_Language_Dec64.pdf > > Joe > > On Mon, Apr 27, 2020 at 11:52 AM Seymour J Metz <sme...@gmu.edu> wrote: > > > That's a bug; the carriage control character is supposed to be > transparent > > to the COBOL programmer. > > > > > > -- > > Shmuel (Seymour J.) Metz > > http://mason.gmu.edu/~smetz3 > > > > ________________________________________ > > From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf > > of Paul Gilmartin [0000000433f07816-dmarc-requ...@listserv.ua.edu] > > Sent: Monday, April 27, 2020 11:04 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: C > > > > On Mon, 27 Apr 2020 15:06:03 +1000, Wayne Bickerdike wrote: > > > > > >I had neither mainframe COBOL nor SPPS skills but I'd written a whole > > bunch > > >of Microfocus COBOL on CP/M micros. > > > > > >I convinced them that I could do mainframe COBOL, which wasn't that > > >difficult. When I looked at the SPPS code, it was macro Assembler, so > that > > >was the start of a short time with same. > > > > > My one foray into COBOL occurred when I worked for a small consulting > > firm. Warm body with no COBOL skill. I developed a small COBOL > > program timesharing to DECSystem-10. > > > > My co-worker carried it to client's IBM 360. > > > > Failed. > > > > Using AFTER ADVANCING construct in IBM COBOL clobbers the first > > character of my data record. Who woulda thunk it? > > > > DEC COBOL, more wisely IMO, prefixes the intact record with LF, FF, > > whatever carriage motion command(s). Better design; standard be > > damned! > > > > -- gil > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
