|
|
 |
|
|
|
VM TCP/IP LPR/LPD Support for the Euro
The LPR client and LPD server applications have been enhanced
to provide users with the ability to specify
alternate translation tables.
LPR Command
The new TRANSLATE tablename option has been added to
allow the user to specify which
translation table
the application will use for EBCDIC-ASCII data translations.
If TRANSLATE tablename is not specified,
a default translation table is used.
If the LPRSET command has been used to set the TRANSLATE option,
the specified translation table will be used.
If the Nickname option of LPR is specified,
the :TRANSLATE
tag associated with the nickname is used,
if present.
Otherwise,
data translation is performed as follows:
- Asynchronous processing
- Data translation is
based on the configuration of the RSCS
server and link to which the files were directed.
- Synchronous processing
- LPR searches for and uses the LPR TCPXLBIN file first, and
then the STANDARD TCPXLBIN file. If neither is found, an
internal translation table is used.
LPRSET Command
The LPRSET command (for TCP/IP for VM
Function Level 310) has been changed to support
a new option, TRANSLATE tablename, that
allows the user to set the default translation table
used for EBCDIC to ASCII data translations.
LPD (LPSERVE)
The LPD command
has been changed to support a new LPD configuration
file statement, TRANSLATETABLE tablename;
the synonym is XLATETABLE.
When used, this statement identifies a specific translation table to be
associated with a given print service.
This statement must follow a SERVICE statement in the LPD CONFIG file.
See Base TCP/IP support for a description
of the new code pages.
|
|
|
