DTC/3000 Terminal I/O Enhancements [ COMMUNICATOR 3000/XL XL RELEASE 3.0 ] MPE/iX Communicators
COMMUNICATOR 3000/XL XL RELEASE 3.0
DTC/3000 Terminal I/O Enhancements
by Stephen Lin/Mary Ann Little
Information Networks Division
This XL release includes enhancements to the Datacommunications and
Terminal Controller (DTC/3000). DTC/3000 is a LAN-based controller for
asynchronous access to HP 3000 and non-HP systems, and for X.25 access to
public and private X.25 packet-switching networks. For asynchronous
access, DTC/3000 provides connections to terminals, PCs in terminal
emulation mode, and serial printers.
DTC/3000 now supports duplex printing for the LaserJet 2000 and LaserJet
IID. It increases the maximum number of supported asynchronous devices
from 600 to 850. Also implemented in this release, is programmatic
control of Typeahead Echo Mode through the FDEVICECONTROL intrinsic,
which was introduced in XL Release 2.2.
DUPLEX PRINTING
Duplex printing is the ability to print on both the front and back sides
of the printer paper. The Laserjet 2000 and the Laserjet IID are the two
PCL (Printer Control Language) laser printers that support duplex
printing. These two printers also support simplex (one sided) printing.
Configuring the Termtype File
To utilize duplex printing on supported printers, the user must configure
AND enable duplex printing. Configuration consists of modifying an
existing printer file so that Duplex Printer Mode is enabled. This is
done using the TTUTIL.PUB.SYS utility. This printer file is then
assigned to the printer LDEVs in NMMGR. This enables the Terminal I/O
driver to send the Front-Of-Page (FOP) escape sequence to the printer
when appropriate.
The Duplex Printer Mode option is included in the Printer Control screen
in TTUTIL as illustrated below:
[ ] Does the printer support duplex printing (Y,N)
To indicate that a printer may be used as a duplex printer, enter Y
in the field. To save the modification, press ENTER and then the SAVE
DATA function key.
In addition to assigning the appropriate printer profiles to the duplex
printer LDEVs, the printers must be set for duplex printing according to
the appropriate printer reference manuals.
Enabling Duplex Printing
Once configuration is complete, the printer is capable of duplex printing
but not yet enabled for it. Duplex printing is enabled and disabled by
sending escape sequences to the printer. This can be done in three ways.
Escape sequences can be embedded in the data file being printed, the
printer file can be modified to include the escape sequence as part of
the initialization string, or the printer file can be modified to include
the escape sequence as a Vertical Forms Control (VFC) string. If the
escape sequences are to be included in the printer file, this must be
done at configuration time. There are three escape sequences for duplex
printing:
ESC&l1S - Enable vertical binding duplex mode
ESC&l2S - Enable horizontal binding duplex mode
ESC&l0S - Disable duplex mode (enable simplex mode)
The two duplex modes provide for the binding of the final document.
Vertical Binding allows for binding a document along the physical length
of the page and Horizontal Binding allows for binding a document along
the physical width of the page. This is pictured below where the +
represents binding.
Figure 3-1. Vertical and Horizontal Binding with Duplex Printing.
In addition to the escape sequences mentioned above, the RESET escape
sequence (ESCe) will also disable duplex mode and return the printer to
simplex mode. Therefore, the duplex mode escape sequences should be
entered after the RESET escape sequence in an initialization string.
For detailed information on TTUTIL, refer to Customizing Terminal-Type
Files and Printer-Type Files with Workstation Configurator (P/N
5959-2870). This version of the manual does not include information
specific to duplex printing.
For detailed information on the use of the escape sequences refer to the
technical reference manual provided with the printer.
850 ASYNCHRONOUS DEVICES
All Datacomm product configurations are done with the configuration
utility NMMGR. In release 3.0, the configuration limit of 600
asynchronous devices has been increased to 850 asynchronous devices.
Configuration errors caused by exceeding the limit are reported through
DTS/LINK Validation within NMMGR. The error, Too many LDEVs are being
used (must be <= 850). DTSERR = 13, is displayed on the console.
For NMMGR screen information and configuration steps, refer to
Configurating Systems for Terminals, Printers, and Other Serial Devices
(P/N 32022-90001). This version of the manual does not contain
information specific to the increase in the supported number of
configured asynchronous devices.
For additional information on system limitations, refer to HP
Configuration Guide (P/N 5954-9354).
PROGRAMMATIC CONTROL OF TYPEAHEAD ECHO MODE
The Typeahead Echo Mode option was implemented in Release 2.2 to specify
the echo behavior, which permits either echoing typed-ahead input
characters only once, or echoing the characters twice. This option is
offered on the Control Screen in TTUTIL.PUB.SYS.
In this XL release, FDEVICECONTROL 192, with subcode 63, is introduced to
allow programmatic control of the typeahead echo mode. The syntax and
parameters are shown below.
FDEVICECONTROL(filenum,buffer,length,controlcode,parm1,
parm2,fserrorcode);
filenum The file number of the device file.
buffer Device control setting
Value 1 = Enable single echo
0 = Disable single echo
(allow double echo)
length The length of buffer. Value= -2
controlcode The number of the operation. Value=192
parm1 Subcode. Value= 63
parm2 Access; Read = 1, Write = 2,
Read/Write = 3
fserrorcode File system error code number.
HOST UPGRADE
If the XL system is updating from a release prior to MPE XL 2.2, it is
necessary to use the conversion utility NMMGRVER to convert the
configuration file NMCONFIG.PUB.SYS to the MPE XL 3.0 format. As part of
all updates, run the TTUTIL utility to make any terminal/printer file
changes and run NMMGR to make any Datacomm configuration changes. Be
sure to perform the DTS validation before exiting NMMGR, and the SYSGEN
cross validation before rebooting the system. Reboot the system and
reset the DTC(s) to make the changes effective.
HP OPENVIEW DTC MANAGER VERSIONS
In a PC-based network management environment, using version A.06.06 of
the HP OpenView DTC Manager along with this release of MPE XL, will
provide full 3.0 TIO functionality.
It is possible to run XL Release 3.0 with some earlier versions of the
DTC Manager. In this case, you will not get the full 3.0 functionality.
Instead, you will get the TIO functionality associated with the earlier
version of the DTC Manager. Conversely, it is also possible to run the
DTC Manager A.06.06 with some earlier versions of FOS. The resulting
functionality will be that of the particular MPE XL FOS version.
MPE/iX Communicators