Paul, that's not true. The printer has no way of knowing whether it's a
"initial" page eject or not. Some programming languages will spit an
extra page eject, like PL/1 does, but the basic printer isn't that smart.
Paul Gilmartin wrote:
On Mon, 13 Oct 2008 16:44:27 -0500, Chris Mason wrote:
I think your in trouble - or you can roll up your sleeves and get programming -
in your favourite language.
I remembered that the difference between A and M is that one prints and then
moves the print carriage while the other moves the print carriage and then
prints. I guess you can see that this negates your "simple".
Well, I hate knowing only half the story so I jumped into the DFSMS shelf and
found the matter explained - in APPENDIX1.3 Appendix C. Control Characters
of "z/OS V1R10.0 DFSMS Macro Instructions for Data Sets".
In the table of the codes in APPENDIX1.3.1 Machine Code we find
"Print--Then Act "
and in the table of codes in APPENDIX1.3.2 ISO/ANSI we find
"Action before Printing a Line"
So now I'm happy - but I suspect you will not be!
And one more thing. IBM printers ignore an initial page
eject (the rule is more complicated, but this is the
effect). Many UNIX and PC printers honor the initial
formfeed. At best, this wastes a leaf when printing
single-sided. The effect when printing two-sided is
more irritating -- the even numbered pages appear in
front; the odd numbered in back.
-- 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
----------------------------------------------------------------------
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
