PSF/6000: ASCII form feeds and PAGEDEF processing
ITEM: RTA000090711
Q:
ABSTRACT: PSF/6000: ASCII form feeds and PAGEDEF processing
SEARCH ARG: ebcdic ascii psf/6000
TOPIC THREAD: PRINT
AFP
PSF6000
..
My customer has an ASCII application that is currently printing
on XEROX printers. They are migrating it to an IBM 3829 being
driven by PSF/6000 1.2. In the XEROX ASCII datastream an
ESC L is used to force a new page and they would like this to
work the same way on the 3829. I suggested that they use
Conditional Processing to test for the ESC L, (it is in the same
horizontal position each time it is used).
However, in my experience it seems that PSF/6000 typically converts
ASCII to EBCDIC prior to printing so that the EBCDIC fonts can be
used. So my question is what will the ESC L be coded in when the
PAGEDEF is processed, ASCII or EBCDIC?
Thank you.
A:
In ASCII, it's very common to have a CTRL-L to force a new page; this
equates to a X'0C'. Would you by chance be referring to that instead
of ESC-L? If so, they can use the "asciinp" or "asciinpe" ACIF input
user exits that were added by PTF in late 1994 (as an alternative to
apka2e). These new exits are documented in the PSF/6000 Update Guide,
Volume 2 (G544-5264). The customer would specify them on the inpexit
parameter to acif, and would also need to specify cc=yes and cctype=z.
We also supply the source files (in /usr/lpp/psf/acif) in case the
customer wants to change the exit; it might be possible to change it
to check for the hex value of ESC-L if that's what they really need.
Note that PSF/6000 maintenance is cumulative, so they would just need
the most recent PTFs.
Closing, but reopen if you have additional questions.
| The above information also holds true for PSF/AIX V2.1 and
| InfoPrint Manager 2.1 and later.
| Revised December 1998
S e a r c h - k e y w o r d s:
AIX PSF/6000 PSF FOR AIX ASCII ASCIINPE FORM FEED psf/aix apka2e
0c page eject line2afp acif pagedef
WWQA: ITEM: RTA000090711 ITEM: RTA000090711
Dated: 12/1998 Category: XPSF6000
This HTML file was generated 99/06/24~12:43:30
Comments or suggestions?
Contact us