HP LaserJet 9000 Manual 

HP 9000 Computers DTC Device File Access Utilities and T elnet P ort Identification ABCDE HP P art No. B1030-90002 Printed in U.S.A. 01/95 Edition 2 E0195

Legal Notices The information in this do cumen t is sub ject to c hange without notice. Hew lett-Packar d makes no warr anty of any kind with r e gar d to this material, including, but not limite d to, the implie d warr anties of mer chantability and tness for a p articular purp ose. Hewlett-Pac k ard shall not b e liable for errors con tained herein or direct, indirect, sp ecial, inciden tal, or consequen tial damages in connection with the furnishing, p erformance, or use of this material. W arran ty . A cop y of the sp ecic w arrant y terms applicable to y our Hewlett-Pac k ard pro duct and replacemen t parts can b e obtained from y our lo cal Sales and Service oce. Restricted Rights Legend. Use, duplication or disclosure b y the U.S. Gov ernmen t is sub ject to restrictions as set forth in subparagraph (c) (1) (ii) of the Righ ts in T ec hnical Data and Computer Softw are clause at DF ARS 252.227.7013 for DOD agencies, and subparagraphs (c) (1) and (c) (2) of the Commercial Computer Softw are Restricted Righ ts clause at F AR 52.227-19 for other agencies. HEWLETT-P A CKARD COMP ANY 3000 Hanov er Street P alo Alto, California 94304 U.S.A. Use of this man ual and exible disk(s) or tap e cartridge(s) supplied for this pac k is restricted to this pro duct only . Additional copies of the programs may b e made for security and bac k-up purp oses only . Resale of the programs in their presen t form or with alterations, is expressly prohibited.

Cop yrigh t Notices. (c)copyright 1979, 1980, 1983, 1985-93 Regen ts of the Univ ersit y of California This soft w are is based in part on the F ourth Berk eley Softw are Distribution under license from the Regen ts of the Univ ersity of California. (c)copyrigh t 1980, 1984, 1986 No v ell, Inc. (c)copyrigh t 1986-1992 Sun Microsystems, Inc. (c)copyrigh t 1985-86, 1988 Massach usetts Institute of T ec hnology (c)copyrigh t 1989-93 The Op en Softw are F oundation, Inc. (c)copyrigh t 1986 Digital Equipmen t Corp oration (c)copyrigh t 1990 Motorola, Inc. (c)copyrigh t 1990, 1991, 1992 Cornell Univ ersit y (c)copyrigh t 1989-1991 The Univ ersit y of Maryland (c)copyrigh t 1988 Carnegie Mellon Univ ersity T rademark Notices UNIX is a registered trademark in the United States and other coun tries, licensed exclusiv ely through X/Op en Company Limited. X Window System is a trademark of the Massach usetts Institute of T ec hnology . MS-DOS and Microsoft are U.S. registered trademarks of Microsoft Corp oration. OSF/Motif is a is a trademark of the Op en Softw are F oundation, Inc. in the United States and other coun tries. c Cop yright 1995, Hewlett-Pac k ard Company .

Printing History The man ual prin ting date and part n um b er indicate its curren t edition. The prin ting date will c hange when a new edition is prin ted. Minor c hanges may b e made at reprin t without c hanging the prin ting date. The man ual part n um b er will c hange when extensiv e c hanges are made. Manual up dates may b e issued b et w een editions to correct errors or do cumen t pro duct c hanges. T o ensure that y ou receiv e the up dated or new editions, y ou should subscrib e to the appropriate pro duct supp ort service. See y our HP sales respresen tativ e for details. Edition 2 Jan uary 1995 (HP-UX Release 10.0) iv

Contents 1. In tro duction In tended Audience . . . . . . . . . . 1-2 Prerequisites . . . . . . . . . . . . . 1-2 Supported Congurations . . . . . . . 1-3 Related HP Do cumen tation . . . . . . 1-5 2. Ov erview of DDF A And T elnet P ort Iden tication Ho w DDF A Utilities W ork . . . . . . . 2-2 Ho w T elnet P ort Iden tication W orks . . 2-5 Ho w Device Files Are Handled By MUXes and DTC T erminal Serv ers . . . . . 2-5 Setting Up Outgoing and Incoming Connections . . . . . . . . . . . 2-6 DDF A File Directories and Setup . . . . 2-9 3. Conguring DDF A Connections DDF A Master Files . . . . . . . . . . 3-1 Related Conguration T asks . . . . . . 3-3 DDF A Conguration T asks . . . . . . 3-4 Conguring Outgoing Connections (Printers) . . . . . . . . . . . . 3-5 Conguring Incoming Connections (T erminals) . . . . . . . . . . . 3-8 Starting Up the o cd Daemons . . . . 3-9 Contents-1

4. Dening and Executing DDF A P arameters Using Dedicated P orts . . . . . . . . . 4-1 The Dedicated P ort File, dp . . . . . . 4-2 The P ort Conguration File, p cf . . . . 4-4 Managing Outgoing Dedicated P orts With dpp and o cd . . . . . . . . . . . 4-9 Preparing to Use dpp . . . . . . . . 4-11 Using dpp to Kill and Restart o cds . . 4-12 Using dpp to Start Up New o cds . . . 4-12 Using dpp to Remo v e Existing o cds . . 4-12 Managing Incoming Connections b y telnetd 4-13 Using dpp to Up date T elnet P ort Iden tication Info . . . . . . . . 4-13 5. Application Examples Setting Up Printers with the HP-UX Sp o oler . . . . . . . . . . . . . . 5-1 HP-UX Sp o oler Example . . . . . . 5-2 Accessing DTC or non-DTC P orts Programmatically . . . . . . . . . 5-3 Conguring Incoming Connections for CSLIP/SLIP . . . . . . . . . . . 5-5 6. Simple DDF A T roublesho oting T roublesho oting Chec klist . . . . . . . 6-2 T roublesho oting Outgoing Connections . 6-3 Chec k for Syn tax Errors . . . . . . . 6-3 Chec k for Incorrect Addresses . . . . 6-3 Chec k T elnet Op eration . . . . . . . 6-3 V erify o cd . . . . . . . . . . . . . 6-4 Chec k the pt y . . . . . . . . . . . 6-4 Chec k System Lev el Data P ath . . . . 6-4 T roublesho oting Incoming Connections . 6-5 If Y ou Ha v e to Call Hewlett-Pac k ard . 6-6 Contents-2

A. Appendix A: dpp Error Messages B. Appendix B: o cd Logging Messages Critical Messages . . . . . . . . . . . B-2 Serious Messages . . . . . . . . . . . B-7 W arning Messages . . . . . . . . . . B-19 Informational Messages . . . . . . . . B-26 Index Contents-3

Figures 2-1. HP 9000 and DTC In teraction With DDF A . . . . . . . . . . . . . 2-4 2-2. Incoming Connection Using T elnet P ort Iden tication . . . . . . . . . . 2-8 Contents-4

1 Introduction This man ual explains ho w to use the DTC Device File Access Utilities (DDF A) and the T elnet P ort Iden tication feature to communicate with HP 9000 serial devices connected to net w ork terminal serv ers suc h as the HP Datacomm unications and T erminal Con troller (DTC). DDF A facilitates the use of pseudoterminal (pty) device les to op en outgoing T elnet connections to the DTC or other terminal serv er, while T elnet P ort Iden tication uses them to establish incoming T elnet connections from kno wn devices on the serv er. T elnet is one of the HP 9000 In ternet Services (HP B1030B), formerly kno wn as the HP 9000 ARP A Services. DDF A w as originally designed for use with DTCs, but as of HP-UX 10.0, it can no w b e used with other terminal serv ers whic h use addressing sc hemes similar to the DTC. There will b e some guidelines on ho w to congure DDF A for use with non-DTC terminal serv ers, but the DTC will b e used as the primary example throughout this man ual. In addition, there is general discussion on the topic of pt y use with HP DTC terminal serv ers v ersus the HP MUX, and ho w to troublesho ot incoming and outgoing DDF A connections. Introduction 1-1

Intended Audience This man ual is in tended for at least three typ es of users: The HP 9000 system administrator or net w ork administrator who denes and congures the device les asso ciated with DTC and other terminal serv er devices on the system. The HP 9000 system op erator or net w ork op erator who may implemen t the actual tasks set up b y the system or net w ork administrator. The applications programmer who needs programmatic con trol of devices on the DTC or other terminal serv er using standard HP-UX input/output calls suc h as op en, close , io ctl , read , and write. This programmer may also ha v e applications using devices connected to MUX p orts and wishes to extend the application to use DTC devices. Prerequisites Before reading this man ual and using this softw are, y ou should b e familiar with ho w to: Handle HP-UX op erating system and system administration, esp ecially with devices and device les. Congure a DTC with either the DTC Manager/UX pro duct (HP J2120A) or the Op enView DTC Manager pro duct on the PC (HP D2355A). Congure and administer other terminal serv ers. Program devices and use device les for pseudoterminals (ptys) or MUXes. Access on-line DDF A man pages on y our system like ddfa(7), dp(4), dpp(1M), o cd(1M), o cdebug(1M), as w ell as io ctl(2), io ctl(5), p cf(4), and termio(7). 1-2 Introduction

Supported Configurations There are sev eral typ es of softw are and hardw are pro ducts and services used in conjunction with DTC Device File Access Utilities. Refer to the \Related HP Do cumen tation" section for more information. HP-UX op erating system v ersion. The DTC Device File Access Utilities are included with HP-UX v ersion 9.0 and later. The DDF A Utilities consists of executable les, default conguration les and man ual reference pages. In ternet Services. DDF A is an extension of the T elnet service. Because T elnet is one of the In ternet Services (HP B1030B), DDF A is automatically installed and requires In ternet Services and the LAN Link to b e congured and op erating prop erly . HP 9000 Series 700 and 800 systems. The DDF A Utilities are supp orted only on HP 9000 Series 700 and 800 systems. Because these systems ha v e In ternet Services as part of their HP-UX system, these systems also ha v e DDF A installed. DTC Manager/UX or Op enView DTC Manager. The HP DTCs whic h access an HP 9000 Series 800 are congured and managed b y either the host-based HP DTC Manager/UX (HP J2120A) or the PC-based Op enView DTC Manager (HP D2355A). The PC-based Op enView DTC Manager also congures and manages DTCs whic h access HP 9000 Series 700 systems and HP 3000 systems. The v ersion for DTC Manager/UX should b e A.04.00 or later. The v ersion of the Op enView DTC Manager should b e A.14.10 or later. The v ersion for DTC 16RX Manager/UX should b e A.04.00 or later. Prin ters and plotters. DDF A Utilities can b e used with the HP-UX sp o oler for prin ters and plotters for whic h a mo del script exists., and are supp orted for use with HP DTCs. Introduction 1-3

T erminals. An y terminal supp orted for use with HP DTCs is also supp orted. Mo dems. An y mo dem supp orted for use with HP DTCs is also supp orted. HP DTCs. The following DTCs are supp orted on HP 9000 systems: HP 2340A - DTC 16 with 16 p orts. HP 2360A - DTC 16TN with 16 p orts. HP 2363A - DTC 16MX with 16 p orts. HP 2364A - DTC 16RX with 16 p orts. HP 2345A - DTC 48 with 48 p orts. HP 2370A - DTC 72MX with 72 p orts. Other T erminal Serv ers. DDF A Utilities can b e used with non-HP terminal serv ers whic h use addressing sc hemes similar to the DTC. Ho w ev er, in order to w ork, the individual user m ust p erform three tasks: (a) Congure the non-DTC terminal serv er p orts for use with the DDF A pro duct. (b) Congure DDF A for use with non-DTC p orts, and (c) T est whether this particular terminal serv er conguration w orks correctly with DDF A b efore calling HP . The user m ust follow the conguration guidelines discussed in this man ual, as w ell as those given b y the sp ecic terminal serv er v endor in order for HP to supp ort the DDF A in terface. 1-4 Introduction

Related HP Documentation HP-UX System man uals: HP-UX System A dministr ation T asks (the HP part n um b er is dieren t for eac h of the HP 9000 systems) Instal ling HP-UX 10.0 (the HP part n um b er is dieren t for eac h of the HP 9000 systems) LAN and In ternet Services man uals: Instal ling and A dministering Internet Servic es (B1030-90000) Instal ling and A dministering LAN/9000 (98194-90050) Using Serial Line IP Pr oto c ols (98194-90051) DTC Manager man uals: Using HP Op enView DTC Manager (D2355-90001) for the PC-based DTC manager. Using HP Op enView DTC Manager/UX (J2120-62000) for the host-based DTC manager for HP 9000s. Using DTC 16RX Manager (J2496-90000) for the DTC 16RX manager. Introduction 1-5

2 Ov erview of DDF A And T elnet P ort Identification This c hapter gives a brief ov erview of DTC Device File Access (DDF A) Utilities and T elnet P ort Iden tication. Read this c hapter to learn ho w DDF A and T elnet P ort Iden tication w ork, and ho w device les are used to communicate with devices attac hed to DTCs and other terminal serv ers. Chapters 3, 4, and 6 provide information on conguring, executing and troublesho oting DDF A connections to DTCs and other terminal serv ers. This pro duct enhances and supplemen ts the T elnet proto col b y providing the follo wing b enets: DDF A mak es accessing devices attac hed to DTCs or other terminal serv ers like accessing MUX devices. DDF A Utilities allo w the system administrator to set up a corresp ondence b et w een these DTC p orts and HP-UX device les. With this corresp ondence dened, the system sp o oler or a user application can manipulate w ell-known device les to read and write to sp ecic serv er p orts. DDF A allows the HP-UX Sp o oler for prin ters attac hed to DTCs or other serv ers to b e congured in SAM. After the corresp ondence b et w een prin ters on a DTC and HP-UX device les has b een set-up, SAM (System Administration Management to ol) can b e used to congure the sp o oler for DTC-connected prin ters as w ell as for MUX-connected prin ters. The only dierence is that the pt y device le name of the DTC prin ter m ust b e used instead of a tty name for Ov erview of DDF A And T elnet P ort Identification 2-1

a MUX prin ter. In fact, the standard sp o oler mo del scripts can b e used with serv er prin ter(s). DDF A allows user applications to access devices attac hed to DTC and other terminal serv ers using standard HP-UX system calls. After the corresp ondence b et w een DTC devices and HP-UX device les has b een set up, user applications can use the standard HP-UX read , write, op en, close , and io ctl calls. These calls access the devices b y manipulating their corresp onding device les. T elnet P ort Iden tication lets the system administrator ensure that incoming T elnet connections from sp ecic DTC p orts will b e assigned to sp ecic, rather than random pt y device les. DDF A Utilities and T elnet P ort Iden tication c annot b e used simultaneously on the same device le, since they provide separate functionality . Ho w ev er, they may b e used on the system at the same time. How DDF A Utilities W ork The DTC Device File Access Utilities are a group of conguration les, executable les and one or more daemons. T ogether these utilities allo w the HP 9000 system administrator to set up logical pairs of pt y device les and ph ysical p orts on the DTC or other serv er. Once this is done, the serv er's pt y devices can b e accessed in the same w ay as MUX-connected tty devices can. These pt ys can b e assigned to \incoming" connections or to \outgoing" connections. Incoming connections to the system are initiated b y input devices attached to the serv er (suc h as terminals), while outgoing connections are initiated b y the system to output devices attached to the serv er (usually prin ters). When an application on 2-2 Ov erview of DDF A And T elnet P ort Identification

the system op ens one of these device les, the DDF A Utilities transparently manage the creation of a T elnet connection to the asso ciated serv er p ort and its device. Congure and execute the DDF A Utilities in tw o simple steps: 1. Edit the Dedicated P ort conguration le ( dp) to add an en try for eac h ph ysical terminal serv er p ort whic h describ es the asso ciation to a unique pt y device lename. 2. Run the Dedicated P ort P arser program ( dpp) to parse the dp le and to execute an o cd pro cess for eac h outgoing connection dened in the dp le. Eac h time the HP-UX system initiates an outgoing connection to a pre-dened terminal serv er p ort, its unique Outgoing Connection Daemon ( o cd) b ecomes active. It then establishes the T elnet connection and manages it un til the connection is closed. Figure 2-1 sho ws ho w the system, the DTC terminal serv er, and the DDF A Utilities in teract with one another. Ov erview of DDF A And T elnet P ort Identification 2-3

Figure 2-1. HP 9000 and DTC Interaction With DDF A 2-4 Ov erview of DDF A And T elnet P ort Identification

How T elnet P ort Identification W orks T elnet P ort Iden tication is made p ossible b y a set of enhancemen ts to the T elnet daemon ( telnetd), whic h is part of In ternet Services. In earlier v ersions of T elnet, incoming connections, including those coming from a DTC serv er, w ere alwa ys assigned pt y device les on a random basis. In ternet Services T elnet allows the system administrator to set up pre-dened pt y names dened in the DDF A dedicated p ort le, dp. In addition, the DTC do wnload co de w as enhanced so that it will deliver b oard and p ort information to the host (via T elnet) at connection establishment time. The host will map the incoming connection to its pre-dened pt y device le, thereb y providing a \dedicated p ort" b y whic h the iden tity of the caller can b e determined. The T elnet P ort Iden tication feature is av ailable with HP-UX and DTCs, but may not b e compatible on other serv ers. How Device Files Are Handled By MUXes and DTC T erminal Serv ers Recall that a device le is an HP-UX le that \p oints" to a system device. The system administrator often uses the name of the device le when conguring softw are to access that device. When devices are connected to an HP-UX MUX (multiplexer), they are assigned to tty device le names. When devices are connected to a DTC serv er, they are assigned to r andom pt y device le names. T o the user logging on at his terminal from either a MUX or a DTC, the terminal functions the same w ay . The user do es not see ho w the device le is assigned to the connection, and whether the MUX driver or the terminal serv er driver is used. The HP-UX System Administrator creates a device le for eac h MUX p ort, using the HP-UX insf or mkno d command. Eac h device le maps to a sp ecic ph ysical Ov erview of DDF A And T elnet P ort Identification 2-5

MUX p ort, and device les are named b y con v en tion, so that eac h iden ties a unique MUX p ort. F or example, /dev/tty2p3 means p ort 3 on MUX card 2. A device connected to a DTC or other terminal serv er communicates with the system via T elnet. Therefore, it is considered to b e a logical device, and it is serviced b y a pseudoterminal device driv er (pty). It is referenced using its pt y device le name. Usually , this pt y is assigned to the T elnet connection randomly from a p o ol of free pt ys in the /dev directory or sub directories at connection setup time. In man y cases, the randomness of pt y assignments for T elnet users is acceptable, b ecause the ph ysical lo cation of the T elnet user is unimp ortant. In fact, users of system-to-system T elnet ha v e always b een sub ject to this situation. Ho w ev er, when a sp ecic DTC device m ust alwa ys b e asso ciated with the same pt y , then the randomness of pt y assignments m ust b e remov ed through a utilit y suc h as DDF A. Starting with HP-UX 10.0, pt y device les for incoming connections should b e assigned to the directory /dev/telnet so that they can b e more easily track ed and b e correctly display ed b y commands suc h as ps -ef . Setting Up Outgoing and Incoming Connections A prin t job sen t from the system to a prin ter creates an outgoing connection. When a user logs in at a terminal on a DTC and receiv es a system prompt from the host to complete the login, an incoming connection is created. Both op erations require the use of a device le name. Whenev er an application on the host needs to access a MUX device, the application can read and write to the tty device le that b elongs to the MUX device. Ho w ev er, if an application w an ts to op en a DTC device, 2-6 Ov erview of DDF A And T elnet P ort Identification

diculties arise, since no pt y device le is assigned b efore the connection to the device is established. DDF A makes this connection setup pro cess transparent to the application. All the application needs to do is to issue standard HP-UX op en() , read(), write() , close() and io ctl() calls to the kno wn pt y . Whenev er a MUX-connected terminal logs on to a system, the device le asso ciated with the session is alwa ys the same. The user can nd out what MUX p ort the terminal is connected to b y typing the tty command. In the example b elow, the device le name is sho wn to b e /dev/tty2p3 for MUX card 2, p ort 3. tty /dev/tty2p3 The T elnet daemon ( telnetd) assigns a pt y to the connection when a user logs in to the system from a terminal on a DTC. The pt y device les refer to logical devices, and the T elnet daemon selects them randomly from the p o ol of free pt ys in the /dev directory and its sub directories. Ev en though y ou can use the HP-UX who or tty command to nd the name of the device le asso ciated with y our T elnet session, the result do es not sho w whic h DTC p ort is y ours. The assigned pt y is dieren t eac h time y ou login, ev en from the same terminal. Figure 2-2 illustrates the system and DTC in teraction on an incoming connection with T elnet p ort iden tication. When the system accepts an incoming T elnet connection, it asks the calling DTC to give it the b oard and p ort n um b ers of the DTC p ort. If a mapping b et w een the DTC p ort and a pt y device le w as dened in the /etc/ddfa/dp le, then the dened pt y device le is used to service the incoming connection. Ov erview of DDF A And T elnet P ort Identification 2-7

Figure 2-2. Incoming Connection Using T elnet P ort Identification 2-8 Ov erview of DDF A And T elnet P ort Identification

DDF A File Directories and Setup DDF A is automatically installed along with In ternet Services when y our system receiv es HP-UX 10.0. There are four basic steps to setting up DDF A on y our system: 1. Use the installation/up date utility on y our system to install HP-UX and In ternet Services. Refer to the Instal ling and Up dating HP-UX, HP-UX System A dministr ation T asks , andInstal ling and A dministering Internet Servic es man uals. After installing HP-UX, the follo wing DDF A lesets m ust b e on y our system: INETSVCS-DTC for DDF A /usr/sbin/dpp /usr/sbin/o cd /usr/sbin/o cdebug /usr/examples/ddfa/dp /usr/examples/ddfa/p cf INETSVCS-RUN for T elnet P ort Iden tication /usr/lbin/telnetd Only telnetd is mo died for T elnet P ort Iden tication. INETSVCS-MAN for DDF A References /usr/share/man/man1m/dpp.1m /usr/share/man/man1m/o cd.1m /usr/share/man/man1m/o cdebug.1m /usr/share/man/man4/dp.4 /usr/share/man/man4/p cf.4 /usr/share/man/man7/ddfa.7 Refer to the ab ov e man uals for information on installation and migration from releases prior to 10.0. 2. If up dating to HP-UX 10.0, up date the lo cation of older DDF A device les. DDF A no w supp orts the HP-UX 10.0 le lay out con v en tions, as w ell as ha ving pseudon ym (pty) device les in a sp ecial Ov erview of DDF A And T elnet P ort Identification 2-9

directory called /dev/telnet . A migration script ( /usr/con trib/bin/ddfa device mig ) has b een provided to facilitate the mov emen t of device les to this sp ecial directory . 3. Congure the dedicated p ort (dp) les of DDF A. See Chapter 3, Conguring DDF A Connections and Chapter 4, Dening and Executing DDF A P arameters. 4. Congure the b oard and p orts of the DTC(s). The DTC m ust b e congured and do wnloaded b efore actually making a connection. Refer to y our DTC man ual. If another terminal serv er is used, then congure it according to man ufacturer's instructions, in conjunction with step 3 ab ov e. The imp ortant p oint is that the DTC or other terminal serv er has certain parameters whic h m ust b e congured to match with the corresp onding ones in the system DDF A conguration. These m ust b e do wnloaded b efore a connection is actually made. Note that in releases prior to HP-UX 10.0, the In ternet Services w ere called ARP A Services. The DDF A lesets used at that time w ere called ARP A-A UX, ARP A-R UN, and ARP A-A UX-MAN. Later they w ere relo cated to re ect c hanges to In ternet Services as w ell as the op erating system's A TT System V.4 compliance. 2-10 Ov erview of DDF A And T elnet P ort Identification

3 Configuring DDF A Connections This c hapter explains the tasks necessary to congure DDF A for incoming and outgoing connections. Both primary and related conguration tasks in v olving DTCs and other terminal serv ers are describ ed. The terms terminal serv er or serv er will b e used to refer to either. More details on individual parameters and explanations for DDF A conguration and execution are given in Chapter 4. DDF A Master Files DDF A includes the following conguration les, executable les, and daemon: /etc/ddfa/dp The Dedicated P ort (dp) conguration le is an ASCI I le whic h con tains the mapping information for eac h ph ysical terminal serv er p ort and its asso ciated pt y device le. /etc/ddfa/p cf The P ort Conguration File (p cf ) is an ASCI I le whic h con tains default p ort conguration parameters used b y o cd pro cesses. The p cf is referenced inside the dp le. /usr/sbin/dpp The Dedicated P ort P arser (dpp) is an executable le whic h parses the /etc/ddfa/dp le and spa wns Configuring DDF A Connections 3-1

an Outb ound Connection Daemon ( o cd) for eac h outgoing and incoming connection sp ecied in the dp le The dpp can b e run man ually from the Shell, or automatically eac h time the system is b o oted. /usr/sbin/o cd The Outb ound Connection Daemon (o cd) manages the connection and data transfer to eac h serv er p ort. Normally , o cds are spa wned b y the dpp. Ho w ev er, an o cd can also b e run from the Shell with all the parameters from the dp le sp ecied on the command line. /usr/sbin/o cdebug The Outb ound Connection Daemon in debug mo de ( o cdebug) is a sp ecial debugging v ersion of o cd and p erforms the same tasks as o cd. In addition, the o cdebug daemon logs debug messages to the log le /v ar/adm/o cd for troublesho oting purp oses. (The term ' ' refers to o cd's pro cess iden tication n um b er.) After the system administrator runs the dpp program on the dp conguration le, an o cd daemon is created for eac h congured p ort for whic h an outgoing connection is desired. When the daemon is spa wned, it takes a pt y from the pt y p o ol in the /dev directory (or its sub directories). The daemon then creates a device le with the same ma jor and minor n um b er as the pt y slav e, and gives it the name listed in the dp le. The new device le is kno wn as the \pseudon ym". User applications should use this pseudon ym to access the serv er p ort when calling standard HP-UX in trinsics (suc h as op en, close , io ctl , read and write). The 3-2 Configuring DDF A Connections

daemon listens on the pt y un til an application do es an op en call using the pseudon ym. The daemon manages the connection to the serv er p ort un til it is closed. All of this activit y is transparent when y ou use a terminal or prin ter on the DTC or other terminal serv er. Related Configuration T asks This section assumes that the DTC or other terminal serv er is congured and can b e accessed ov er the LAN b efore attempting to congure DDF A on the system. If this is not the case, then refer to the man uals for the DTC Manager/UX pro duct (HP J2120A) or the Op enView DTC Manager pro duct (HP D2355A) for instructions on ho w to congure the DTC. F or non-DTC serv ers, refer to the man ufacturer's do cumen tation for information on conguration and addressing formats used. Once all of the serv er device p orts are congured and do wnloaded, y ou will b e ready to congure DDF A. First, y ou m ust record some net w ork information ab out the DTC or other terminal serv er, whic h will b e required for the next section, DDF A Conguration T asks. It includes: No de name used b y the DTC or other terminal serv er, in the form name.domain.organization.company , or an alias name as congured in the /etc/hosts le or domain name serv er of the system. IP address used b y the DTC or other terminal serv er. P ort addressing information for eac h ph ysical p ort on the serv er to b e congured b y DDF A. F or a DTC p ort, this is its b oard n um b er and p ort n um b er, or its IP address. F or a p ort on a non-DTC serv er, it may b e its IP address or its TCP address. P ort typ e (direct connection or mo dem). Configuring DDF A Connections 3-3

Connection typ e (outgoing or incoming connection). DDF A Configuration T asks HP recommends k eeping a bac kup of y our HP-UX softw are in order to reco v er from p oten tial problems in the future. In addition, b e sure to read an y READ ME FIRST les supplied with y our system. 1. Log on as ro ot or sup eruser to p erform these DDF A conguration steps. 2. Chec k to see if a w orking directory for DDF A already exists. ls /etc/ddfa 3. If it do es not, create a directory for the DDF A les. HP recommends /etc/ddfa. mkdir /etc/ddfa 4. Chec k to see if a dedicated p ort conguration le already exists. ls /etc/ddfa/dp 5. If it do es not, cop y the master template dedicated p ort le, dp, to the DDF A directory . cp /usr/examples/ddfa/dp /etc/ddfa/dp Do not alter /usr/examples/ddfa/dp, the master template dp le. Instead, mo dify the le /etc/ddfa/dp as explained b elow. 6. Cop y the master template p ort conguration le, p cf , to the DDF A directory . Use this cop y as the generic p cf le whic h w orks for most DTC and serv er devices. cp /usr/examples/ddfa/pcf /etc/ddfa/pcf Do not alter /usr/examples/ddfa/p cf , since that is the master template p cf le. Instead, y ou should go 3-4 Configuring DDF A Connections

to the /etc/ddfa directory , and make one cop y of the p cf template le for eac h typ e of pt y device needed (printer, plotter, etc.). Y ou should give the new p cf le in /etc/ddfa a name whic h describ es the typ e of device (for example, /etc/ddfa/laserjet), and mo dify the con ten ts as needed. Configuring Outgoing Connections (Printers) F or eac h terminal serv er output device (suc h as a prin ter) , p erform the follo wing steps to assign a pt y device le: 1. F or a DTC, determine its No de Name, its IP address, the b oard n um b er, and the p ort n um b er on the DTC to whic h the device is connected. F or a non-DTC serv er, determine its No de Name, its IP address and the TCP p ort n um b er on the serv er to whic h the device is connected. 2. Dene a device le name that y ou will use for this output device. It is helpful to select a name whic h describ es the sp ecic device p ort. F or example, use the pt y le name /dev/telnet/dtc72b3p2 for a device on a DTC 72MX terminal serv er, b oard 3, p ort 2. Note Note the following ph ysical p ort congurations and n um b ering con v en tions often recommended for DTCs: DTC 48s may ha v e up to 6 async hronous b oards (n um b ered slots 0-5), and 6 mo dem p orts (n um b ered 0-5) or 8 direct connect p orts (n um b ered 0-7). DTC 16s may ha v e up to 2 async hronous b oards (n um b ered slots 0-1), and 6 mo dem p orts (n um b ered 0-5) or 8 direct connect p orts (n um b ered 0-7). DTC 16TNs, DTC 16MXs and DTC 16RXs ha v e a single async hronous b oard (called slot 1 or 01); it supp orts 16 mo dem or direct connect p orts (n um b ered 0-15). Configuring DDF A Connections 3-5

m ust separate the b oard and p ort parameters, whic h are unique to the DTC. / / b. F ormat 3 is accepted b y most terminal serv ers, including DTCs, for outgoing connections only . The XX ( XX) indicates a n ull v alue. XX/ XX/ c. F ormats 4 and 5 are used for addressing a serv er where the connection go es to the default TCP p ort address of 23; this feature is supp orted on DTCs and some other terminal serv ers. XX/XX XX/XX 5. Rep eat steps 1-4 for eac h outgoing connection device un til all en tries are congured. 3-6 Configuring DDF A Connections

6. Sa v e the mo died le /etc/ddfa/dp le. It is no w ready for parsing b y dpp. Conguration Example 1 - Let's congure a prin ter p ort whic h is on b oard 3 p ort 2 of a DTC 72MX whose IP address is 192.101.23.72. Y ou wish to refer to this prin ter as /dev/dtc72b3p2 . The en try in the dp le w ould b e: 192.101.23.72 03/02 /dev/telnet/dtc72b3p2 /etc/ddfa/pcf Note: F or a DTC 16MX,TN or RX, the b oard n um b er will alwa ys b e '1' or '01'. Conguration Example 2 - Let's congure a prin ter p ort on a non-DTC terminal serv er, whose no de name is serv er.d.o.com and whose default p ort TCP address is 23. Y ou wish to refer to this prin ter as /dev/telnet/tserver1p2. The en try in the dp le w ould b e: server.d.o.com XX/XX /dev/telnet/tserver1p2 /etc/ddfa/pcf T o congure a DTC prin ter with the HP-UX sp o oler, follow the steps listed ab ov e, then execute the dpp command. Pro ceed with the conguration steps used for a normal prin ter (MUX-connected prin ter), but instead of using a standard device le, y ou substitute the name of the device le that y ou dened in the /etc/ddfa/dp le (e.g., /dev/telnet/dtc72b3p2). Y ou may also use SAM to add the prin ter, using the standard system mo del scripts. Refer to Chapter 5, in the section \Setting Up Printers with the HP-UX Sp o oler," for a sp ecic example. Also refer to the HP-UX System A dministr ation T asks Manual for additional information on the HP-UX prin ter sp o oler. Configuring DDF A Connections 3-7

m ust separate the b oard and p ort parameters. F or example, a terminal is on b oard 3 p ort 4 of a DTC 72MX whose IP address is 192.101.23.72. Y ou wish to refer to this terminal as /dev/telnet/dtc72b3p4 . The en try in the dp le w ould b e: 192.101.23.72 03/04 /dev/telnet/dtc72b3p4 Note that no p cf reference is necessary for input devices suc h as a terminal. 5. Rep eat steps 1-4 for eac h incoming connection device un til all en tries are congured. 6. Sa v e the mo died le /etc/ddfa/dp le. It is no w ready for parsing b y dpp. 3-8 Configuring DDF A Connections

Starting Up the ocd Daemons 1. After y ou ha v e nished editing the /etc/ddfa/dp le, execute the Dedicated P ort P arser ( /usr/sbin/dpp) to scan the /etc/ddfa/dp le. This starts up the o cd daemon and assigns the dedicated p orts for T elnet P ort Iden tication. /usr/sbin/dpp /etc/ddfa/dp -k 2. Chec k to see that the o cd pro cesses are running b y using the ps command as follo ws: ps -ef | grep ocd There should b e one o cd pro cess running for eac h outgoing dedicated p ort congured. Incoming dedicated p orts do not use o cd pro cesses. Note Y ou should always run dpp ev ery time y ou ha v e added or remov ed an y en tries in the dp le. F or more DDF A conguration information, y ou may read on to Chapter 4, Dening and Executing DDF A P arameters. Refer also to the DDF A on-line man ual reference pages (man pages), whic h may b e prin ted from y our system. Configuring DDF A Connections 3-9

4 Defining and Executing DDF A P arameters This c hapter explains the conguration and execution parameters for the dp (dedicated p ort le), p cf (p ort conguration le), and dpp (dedicated p ort parser) in more detail. The dp le denes the asso ciation of ph ysical p orts on a terminal serv er to logical HP-UX pt y device les. A serv er p ort asso ciated in this manner is referred to as a dedicated p ort, b ecause of its xed corresp ondence to a sp ecic device le. Using Dedicated P orts The HP-UX system administrator denes the one-to-one mapping of DTC or non-DTC serv er devices with pseudon yms in this dedicated p ort le. Later, application congurators or system programmers will use these pt y names to refer to these serv er devices. Defining and Executing DDF A P arameters 4-1

The Dedicated P ort File, dp Dedicated p orts are congured in the dedicated p ort le, /etc/ddfa/dp. The dp le is an ASCI I le whic h consists of en tries, one for eac h dedicated p ort, using one of the formats b elow. F or outgoing connections (p orts for output devices suc h as prin ters and plotters): / / XX/XX XX/XX XX/ 4-2 Defining and Executing DDF A P arameters

F or incoming connections (p orts for input devices suc h as terminals): / / The elds are dened as: DTC IP Addr The IP address assigned to the DTC, or to one of its p orts. The IP address is congured on the serv er and its p orts b y using the DTC Manager. DTC Node Name The No de Name assigned to the DTC or one of its p orts. The No de Name is congured on the serv er and its p orts b y using the DTC Manager. board The ph ysical DTC b oard of the p ort to b e dedicated. Refer to the DTC hardw are do cumen tation for n um b er of b oards p er eac h DTC typ e. If XX/XX is sp ecied for / , then the sp ecied IP address or no dename references a p ort on the serv er and not the serv er itself. / A slash m ust separate the b oard and p ort n um b ers. port The p ort n um b er of the DTC p ort to b e dedicated. Refer to the DTC hardw are do cumen tation for n um b er of p orts p er b oard for eac h DTC typ e. port TCP addr The p ort TCP address of the serv er p ort to b e dedicated. Refer to the serv er man ufacturer's do cumen tation for the typ e of addressing format used. Defining and Executing DDF A P arameters 4-3

pseudonym The name of a pseudon ym that will b e used to access the dedicated serv er p ort. The device le name can b e from 1 to 14 c haracters. The name of this le is created b y the system administrator, and m ust not b e the name of a le whic h already exists, or is already in use b y the system. This le is created and managed solely b y the DDF A Utilities and/or the T elnet daemon. HP recommends using a name whic h helps iden tify the DTC p ort b eing referenced, suc h as /dev/telnet/dtc1b2p4 for DTC1, b oard 2, p ort 4. pcf Used for outgoing connections only . The /etc/ddfa/p cf le con tains the p ort conguration whic h is used for the T elnet connection to the DTC or non-DTC p ort. Refer to Chapter 5 for examples of ho w dedicated p ort ( dp) les are used b y DDF A. The P ort Configuration File, pcf The p ort conguration le ( /etc/ddfa/p cf ) con tains timer, connection, and data information for the related output device. The outgoing connection daemon, o cd, uses this information to manage outgoing T elnet connections from the HP-UX device le to the serv er p ort. The p cf le is required only for outgoing connections. Eac h en try in the dp le whic h denes an outgoing dedicated p ort m ust refer to a p ort conguration le. In most cases, it is appropriate to use the default p ort 4-4 Defining and Executing DDF A P arameters

conguration le, /etc/ddfa/p cf . Y ou can use the same p ort conguration le for more than one dedicated p ort. Therefore, most en tries in the dedicated p ort le will con tain /etc/ddfa/p cf as the last eld. Whenev er a p cf parameter or en try is c hanged, the o cd pro cess created b y that en try m ust b e restarted in order to activ ate those c hanged parameters. Eac h en try in the p cf le is a eld-v alue pair on a separate line. Eac h eld-v alue pair is separated b y a colon (:) or one or more spaces. The master p cf le is in /usr/examples/ddfa/p cf . The master le should alw ays b e copied to another directory , suc h as /etc/ddfa/p cf . The cop y should b e mo died and referenced in the dp le. HP recommends that y ou create the /etc/ddfa directory to con tain the p cf and dp les. The p cf le con tains the following en tries and defaults: telnet_mode: enable P erforms data transfer using the T elnet proto col. This option must b e enabled when used with the DTC. timing_mark: enable Uses the T elnet timing mark negotiation at the end of the data transfer. If this is enabled, then all data is output from the serv er buers to the device b efore the buers are ushed. telnet_timer: 120 Sets the timeout for the timing mark and binary negotiation to 120 seconds. If the negotiation do es not complete within 120 seconds, an error message is logged to /v ar/adm/syslog/syslog.log , Defining and Executing DDF A P arameters 4-5

and the error is sen t to the user application program. Its range is 1 to MAXINT. binary_mode: disable T ransfers data in ASCI I mo de when this is disabled. Do not ignore pro cessing of sp ecial c haracters suc h as X ON/X OFF. If set to \enable," the data transfer ov er the net w ork will b e in binary mo de and treatment of sp ecial c haracters (for example X ON and X OFF) will not o ccur. Because there is no o w con trol, data in tegrit y cannot b e guaranteed when binary mo de is enabled. If binary mo de is disabled, it may still b e negotiated b y the application program setting IX ON to 0 (zero) in the TERMIO data structure. open_tries: 1500 Sets the n um b er of connection retries to 1500. If the retry pro cess fails to make a connection, an error message is logged to /v ar/adm/syslog/syslog.log . The error message is also transmitted to the user application program. The retry pro cess can b e in terrupted b y sending the SIGUSR2 signal to the o cd pro cess using the kill -17 4-6 Defining and Executing DDF A P arameters

command. Its range is 1 to MAXINT. Zero causes exp onen tial incremen ts for times b et w een retries, suc h as 1, 2, 4, 8, 16 and so on. open_timer: 30 Sets the time b et w een retries for making a connection to 30 seconds. Its range is 1 to MAXINT. Zero causes innite retries. close_timer: 5 Sets the time b et w een an application program's close call and the actual close of the connection to zero (0) seconds. The connection will b e closed and op ened after ev ery le is sen t to the device. Setting the timer to a v alue other than zero av oids the ov erhead of op ening and closing the connection when a sp o oler sp o ols sev eral les at a time. The connection closes after the sp ecied length of time. Setting the timer to a high v alue eectively leav es the connection p ermanen tly op en. Its range is 1 to MAXINT. status_request: disable Disables the sending of a status request to a device. If enabled, a status request is sen t to the device. The device replies with a status suc h as busy or ready . status_timer: 30 Sets the timeout for receipt of a status reply to 30 seconds. Defining and Executing DDF A P arameters 4-7

If no status reply is receiv ed in that time p erio d, an error message is logged to /v ar/adm/syslog.syslog.log . An error is also sen t to the user application program. Its range is 1 to MAXINT. Zero causes MAXINT retries. eightbit: disable Causes the eigh th data bit (bit 7) to b e stripp ed b y the pt y . If enabled, the eigh th data bit is not stripp ed. tcp_nodelay: enable Causes data to b e sen t to the LAN as so on as it is receiv ed b y TCP . If disabled, data will b e sen t using normal TCP timing. 4-8 Defining and Executing DDF A P arameters

Managing Outgoing Dedicated P orts With dpp and ocd Eac h outgoing dedicated p ort is managed b y an outgoing connection daemon, o cd. Once all outgoing dedicated p orts ha v e b een dened in the dedicated p ort le, /etc/ddfa/dp, the DDF A Utilities can b e started with the dpp command (see next paragraph). The result of this step will b e that one outgoing connection daemon ( o cd) pro cess will b e running for eac h v alid outgoing en try dened in the dedicated p ort le. The dedicated p ort parser, dpp, scans the dedicated p ort le and spa wns an o cd pro cess for eac h outgoing en try in the le. The dpp program can b e run man ually , or to start it up automatically at system b o otup, set the system v ariable DDF A (to 1) in the /etc/rc.cong.d/netdaemons le. The syn tax for dpp is: dpp [-l ] [-c] [-k] [-p] dp_file Name of the dedicated p ort conguration le to use. T ypically , the dp le is /etc/ddfa/dp. -l logfile Name of the log le to whic h dpp should log errors. If not sp ecied, the error messages are logged to standard error (stderr) screen. -c P arses the dp le and logs all bad en tries without executing dpp fully . It is useful to debug the dp le b efore starting the o cds. The -p option is ignored if -c is used. -k Remo v es eac h device le from the /dev/telnet directory whic h is also in Defining and Executing DDF A P arameters 4-9

the dp le. Then, dpp spa wns an o cd daemon for eac h v alid en try in the dp le. Refer also to \Using dpp" later in this c hapter. The o cd daemon normally creates and remov es the pt y device les asso ciated with serv er p orts. Ho w ev er, if the o cd pro cess is killed improp erly , a device le may remain. If the system is reb o oted, the -k option may b e sp ecied to delete an y remaining device les and to restart all the dp le en tries correctly . -p The default path for o cd is /usr/sbin/o cd. If the path is dieren t, it m ust b e sp ecied with the -p option. The o cd m ust ha v e execute p ermission set. F ull path names m ust b e sp ecied for the dp le and log les. The dpp command p erforms the following actions for e ach outgoing dedicated p ort dened in the dp le: Chec ks the v alidit y of the device le name. Runs an o cd pro cess on the pt y whic h w as created. The o cd pro cess manages the outgoing T elnet connection to the serv er p ort, establishing it when the pt y le is op ened. In addition, o cd maps the predened pseudon yms to the pt ys in the pt y p o ol (in /dev/pt y and /dev/pt ym). Therefore, it is imp ortant to ensure that the n um b er of pt ys dened in the system p o ol in the uxgen le is sucien t. Consult the insf command man page for more information on creating pt ys for the system p o ol. 4-10 Defining and Executing DDF A P arameters

After running dpp, y ou can c hec k to see that the o cd pro cesses are running b y using the HP-UX ps -ef command from the Shell prompt as follo ws: ps -ef | grep ocd After the o cd pro cesses ha v e b een started, accessing the pseudon ym (op ening the slav e side of the pt y) results in access to the asso ciated device. Preparing to Use dpp Dpp cannot execute an o cd pro cess for an en try in the dp le if the pt y device le sp ecied in that en try already exists. The existence of suc h a le could indicate that an o cd pro cess is already running for that en try , or that another application is already using the device le. Therefore, it is imp ortant to kill all running o cd daemons prop erly and remov e the device les they use b efore using dpp to start or restart the o cd daemons. Stopping the DDF A Utilities in v olves tw o steps. First, the o cd pro cesses m ust b e killed. Second, the device les that the o cd pro cesses use m ust b e deleted from the le system. Sending a signal 15 to an o cd pro cess causes b oth of these things to happ en automatically . F or example, kill -15 The pid is the pro cess iden tication n um b er of the o cd daemon. It can b e found b y executing ps -ef . The kill -9 command also kills the o cd pro cess, but do es not remov e the device le. If the kill -9 command is used, y ou will ha v e to remov e the device le man ually from the /dev/telnet directory using the HP-UX rm command. Therefore, the kill -15 command is more complete. Defining and Executing DDF A P arameters 4-11

Using dpp to Kill and Restart ocds Running the dpp program with the -k option causes dpp to kill all o cd pro cesses for p orts dened in the dp le and remov e their asso ciated pt y device les. In addition, it restarts o cd pro cesses. Using dpp -k at system startup time is an excellen t w ay to start up the o cd pro cesses. Then all o cd pro cesses dened in the dp le are started prop erly and old les remov ed ev en if the o cd pro cesses w ere previously ab orted. The syn tax is: /usr/sbin/dpp /etc/ddfa/dp -k Using dpp to Start Up New ocds After adding en tries for outgoing dedicated p orts to the dp le, run dpp without the -k option. The -k option causes o cd pro cesses for existing en tries to b e killed. Ab orting the existing o cd pro cesses disrupts service to an y curren t active sessions. T o start o cd pro cesses for the newly added en tries to the dp le, execute dpp without the -k option. The syn tax is: /usr/sbin/dpp /etc/ddfa/dp Ocd pro cesses will b e started only for the newly added en tries. Dpp will ignore en tries that already exist. Using dpp to Remo v e Existing ocds If y ou remov e outgoing en tries from the dp le b y running dpp, b e sure to kill their asso ciated o cd pro cesses using the kill -15 command. This command will ensure that the o cd pro cesses and their asso ciated device les are remov ed prop erly . The syn tax is: 4-12 Defining and Executing DDF A P arameters

kill -15 The is the pro cess iden tication n um b er of the o cd daemon whose en try w as remov ed from the dp le. Managing Incoming Connections b y telnetd Incoming connections are initiated b y the DTC (and not b y the system) and are handled b y the T elnet daemon ( telnetd). The T elnet daemon uses the P ort Iden tication feature to assign a pseudon ym for incoming DTC connections based on en tries in the dp le. If an incoming dedicated p ort is dened in the dp le, telnetd alwa ys uses the pseudon ym sp ecied there. If the pseudon ym dened there is already in use, telnetd refuses the connection. If an incoming T elnet connection is not from a DTC, or if the DTC P ort is not dened in the dp le, then telnetd assigns a pt y to the connection in the traditional manner, whic h is randomly from a p o ol of pt ys. Using dpp to Update T elnet P ort Identification Info The dpp pro cess creates a binary le whic h enco des the information for the incoming dedicated p ort mappings dened in the dp le. Therefore, it is imp ortant to run dpp after making c hanges to the dp le. The syn tax is: /usr/sbin/dpp /etc/ddfa/dp Incoming connections on dedicated p orts do not rely on the use of o cd. Ho w ev er, telnetd do es require dpp, Defining and Executing DDF A P arameters 4-13

b ecause dpp creates the binary lo okup le that telnetd uses. 4-14 Defining and Executing DDF A P arameters

5 Application Examples This section provides the follo wing conguration examples for common uses of the DDF A Utilities and T elnet P ort Iden tication. Setting up prin ters with the HP-UX Sp o oler Accessing DTC or non-DTC p orts programmatically Using DTC p orts with CSLIP or SLIP incoming mo dem connections Setting Up Printers with the HP-UX Spooler One v ery common use of DDF A Utilities is sending HP-UX sp o oler output to prin ters attached to DTCs or other terminal serv ers. Refer to the HP-UX System A dministr ation T asks Manual for prin ter sp o oler information. Recall that when the HP-UX sp o oler is used with MUX-based prin ters, the prin ter is iden tied b y its device le, suc h as /dev/lp . Eac h prin ter also requires the conguration of a mo del script, whic h denes the manner in whic h the sp o oler communicates with a sp ecic prin ter typ e. The system administrator congures this information using SAM, or using the following HP-UX commands from the Shell prompt: lpadmin, lpsc hed, lpstat , accept, enable, and disable. The HP-UX sp o oler can b e congured to use DTC or other serv er-based prin ters in exactly the same w ay as MUX-based prin ters are. The follo wing tasks m ust b e completed b efor e conguring the HP-UX sp o oler: Application Examples 5-1

1. The dedicated p ort le ( /etc/ddfa/dp) m ust con tain a dedicated p ort en try for the serv er prin ter. 2. An o cd pro cess m ust b e running for that p ort. When conguring the HP-UX sp o oler, the pseudon ym dened in the dedicated p ort le ( /etc/ddfa/dp) iden ties the prin ter. As usual, the system administrator selects a standard system mo del script that matches the prin ter connected to the DTC or other terminal serv er. HP-UX Spooler Example Y ou wish to congure the HP-UX sp o oler so that the default system prin ter is a DTC prin ter. Afterwards, test the conguration b y prin ting a le to the DTC prin ter using the HP-UX lp command. Use either SAM ( System Administration Managemen t ) to ol or the HP-UX lpadmin command to congure the HP-UX sp o oler. Use the HP-UX System A dministr ation T asks Manual to nd the sp ecic men u paths. Steps to congure the HP-UX sp o oler from SAM: 1. After en tering SAM, go to the screen for lo cal prin ter/plotter. 2. Select the option for adding a prin ter/plotter requiring a nonstandard device le. 3. SAM scans the system hardw are and lists all the MUX cards on the system. Select an y MUX card and an y p ort on that MUX card. Y ou will later c hange the MUX device le name to another device le name asso ciated with the DTC or non-DTC serv er p ort. 4. Complete the screen for adding a prin ter as follo ws: Prin ter name: Assign a name to the prin ter. Prin ter mo del / in terface: With this eld selected, press the En ter k ey . Select the appropriate prin ter from the list display ed. 5-2 Application Examples

Prin ter device le name: En ter the prin ter device le name that y ou en tered in the le /etc/ddfa/dp for the DTC or other terminal serv er p ort. This replaces the MUX device le name that SAM supplied. 5. Complete the other elds as desired. 6. Exit from SAM. Another w ay to congure the prin ter is to use the command line metho d with the follo wing commands: lpshut lpadmin -pdtcprinter -v/dev/dtc1b1p2 -mhp2235a accept dtcprinter enable dtcprinter lpsched lpstat -t If desired, y ou can make dtcprin ter b e the system default prin ter: lpadmin -ddtcprinter No w use the lp command to v erify that y our prin ter conguration w ork ed: lp /etc/ddfa/dp Accessing DTC or non-DTC P orts Programmatically Programs that communicate with devices on a MUX use the tty names dened in the /dev directory . Programmatic access to DTC or non-DTC serv er p orts relies up on using outgoing dedicated p orts. whic h are dened in the dp le, and ha v e an o cd pro cess running for that p ort. Then the standard HP-UX calls read(), write() , op en() , close() , and io ctl() can b e used. When using the op en() call, the name of the device le for the path parameter should b e a pseudon ym dened Application Examples 5-3

in the dp le. When the op en() executes, the outb ound connection daemon, o cd, initiates a connection to the serv er p ort sp ecied in the dp le. Then, read and write calls to the device can b egin. Here is a sample application for outgoing connections: #include #include #include #include #include #include main() { char msg [ 80] ; char i; int fd; if ( ( fd = open ( "/dev/telnet/dtcb1p4", O_RDWR ) ) == -1 ) { printf ( "Unable to open device file: error %d: %s\n", errno, strerror ( errno ) ); exit ( 1 ); } for ( i = 0; i <= 'z' - 'a'; i++ ) { sprintf ( msg, "Character %1d is %c\n", i + 1, 'a' + i ); write ( fd, msg, strlen ( msg ) ); } if ( ioctl ( fd, TCSBRK, 0 ) == -1 ) { printf ( "Unable to send break to device: error %d: %s\n", errno, strerror ( errno ) ); exit ( 1 ); } if ( close ( fd ) == -1 ) { printf ( "Unable to close device file\n" ); exit ( 1 ); } exit ( 0 ); } Use of the io ctl() call and the TERMIO structure is limited to actions whic h are supp orted b y the terminal serv er hardw are and whic h are allo w ed ov er a net w ork ed connection. 5-4 Application Examples

Note The main TERMIO restrictions include mo dem signal con trol and parity c hec king. Refer to the ddfa man ual reference page for more details on io ctl and TERMIO limitations. Refer to the termio man ual reference page for details on terminal input/output, io ctl, and TERMIO structures. Configuring Incoming Connections for CSLIP/SLIP Compressed Serial Line In ternet Proto col (CSLIP) and Serial Line In ternet Proto col (SLIP) are serial proto cols whic h are used to facilitate TCP/IP net w orking ov er an async hronous line. A common use is for a lo cal system to dial in ov er mo dems to a DTC, whic h completes the connection to a remote HP 9000 system on the net w ork. Here are the steps required to set up an HP 9000 dial-in connection using the DTC, CSLIP or SLIP and T elnet P ort Iden tication. Refer to the appropriate pro duct do cumen tation for ho w to congure sp ecic parts of the connection. 1. Set up the DTC p ort using the Op enView DTC Manager. (The connection m ust ha v e binary mo de enabled on the DTC mo dem p ort. This can only b e done on a DTC that is managed b y a PC-based DTC Manager.) 2. Assign a dedicated pt y for the incoming connection b y conguring the dp en try in the /etc/ddfa/dp le. Run dpp on the dp le to activ ate the c hanges. This step m ust b e done on the remote host. 3. Fill in the en tries in the CSLIP or SLIP conguration les ( ppl.remotes) on b oth the lo cal and remote hosts. In the ppl.remotes le on the remote host, for the serial line parameter, en ter the name of the dedicated Application Examples 5-5

device le, as dened in the previous step. Remem b er that this device en try need not con tain a p cf . Use the Using Serial Line IP Pr oto c ols man ual for examples of conguring lo cal and remote ppl.remotes les. 4. Congure the HA YES-compatible mo dem attached to the DTC according to man ufacturer's instructions. The maximum dial-in sp eed supp orted b y HP for CSLIP or SLIP ov er DTC connections is 9600 baud. The mo dem should also b e congured for o w con trol o. 5. Run ppl on the lo cal host on the IP address of the remote host, as describ ed in the SLIP man ual. ppl -o CSLIP/SLIP dial-in connections ov er DTCs are supp orted in binary mo de, at sp eeds of up to 9600 baud for HP 9000 Series 700 and 800 hosts running either HP-UX 9.x or 10.0. They are only supp orted in DIAL-IN mo de, since DTC p orts cannot b e used to dial out. See the SLIP man ual for other applications, suc h as dialing in and out ov er HP-MUXes. 5-6 Application Examples

6 Simple DDF A Troubleshooting DDF A connection problems are often due to improp er use and conguration of DDF A, application softw are, or faults in the device or terminal serv er connection. This man ual fo cuses on simple tasks the user can p erform to c hec k for simple conguration faults and to test the DDF A to DTC terminal serv er connection. A rule of th um b in simple troublesho oting is to divide and conquer. Iden tify the problem and break it in to a set of smaller, easier to test comp onen ts. F or eac h symptom, try to isolate p ossible causes and nd w ays to eliminate them. F or example, if an error message is display ed in the log le, nd its description in App endix B and p erform the suggested action. Simple DDF A Troubleshooting 6-1

Troubleshooting Checklist Is the serv er device op erational? F or a prin ter, c hec k to b e sure that it is p ow ered on, is not out of pap er, and is on-line. Can the DTC or other terminal serv er p ort b e accessed through the LAN? Ping the IP address of the serv er. If successful, it means that the net w ork data path is w orking correctly . Are there an y conguration mismatc hes b et w een the dp le on the host and the DTC or other serv er? If so, correct them and try again. In the dp le, the following parameters should match the DTC or non-DTC serv er p ort settings: DTC or serv er IP address, DTC or serv er no de name, b oard/p ort n um b ers (for DTCs only), and the p ort's TCP address. Are the device p ort c haracteristics like direct connect or mo dem, o w con trol, baud rate and parity correct? If not, then correct them, since they do impact the connection, esp ecially one with mo dems. If the problem con tinues, go to the follo wing sections, based on whether it is an incoming or an outgoing connection. If the problem still cannot b e resolved, collect the diagnostic information listed at the end of this c hapter, and call y our Hewlett P ac k ard supp ort engineer. 6-2 Simple DDF A Troubleshooting

Troubleshooting Outgoing Connections Outgoing connections use o cds to send output to serial devices suc h as prin ters and plotters. Use this list of tasks to isolate problems due to syn tax errors, incorrect p ort addresses, telnet op eration, o cd pro cesses, pt y device les, or the system data path. Check for Syntax Errors Because dpp parses the dp le and tries to execute an o cd pro cess for eac h v alid en try , problems asso ciated with dpp usually in v olv e incorrect command line syn tax, or references to illegal or non-existen t les on the dpp command line. This class of problem will usually aect al l p orts congured in the dp le. The dpp error messages are listed in App endix A of this man ual. Check for Incorrect Addresses DDF A supp orts sev eral dieren t p ort addressing formats (See Chapter 3). If a ping to the IP address of the DTC or other terminal serv er fails, then y ou may ha v e an IP conguration problem. V erify the correct IP address of the DTC or other terminal serv er b y cross-c hec king the dp le, and the serv er conguration. V erify the TCP p ort asso ciated with a DTC p ort to whic h y ou are trying to connect using the formula. TCP_port = ( 32 * board + port + 1 ) * 256 +23 Check T elnet Operation V erify that y ou can use telnet to access the p ort: telnet If this command fails, then the p ort is probably in use, is not set up correctly , or may b e broken. If the telnet connection succeeds, then o cd should also succeed. Simple DDF A Troubleshooting 6-3

V erify ocd Chec k to see if the o cd pro cess is running. ps -ef | grep ocd Lo ok at the o cd command line to make sure y ou ha v e the correct syn tax and v alues for IP address of the DTC or non-DTC serv er. (Note: Board and p ort apply to DTCs only .) Check the pty Make sure the pt y has a c haracter sp ecial device le with access rights of rw-rw-rw and a ma jor n um b er of 17. The minor n um b ers will always b e dieren t. ll /dev/telnet/ The resulting display should lo ok something like this: crw-rw-rw- 1 root sys 17 0x000030 Jan 20 10:15 /dev/telnet/dtc1b0p0 Check System Lev el Data P ath V erify that system lev el pro cesses are w orking prop erly . cat /etc/services > /dev/telnet/ A t the system lev el, o cd, cat and all other applications use the same outb ound data path. If this data is sen t to the device correctly , it prov es that it is p ossible to detect the op ened device le, op en a connection to the DTC or non-DTC serv er, and send the data to the desired p ort. If this fails, then it indicates the need to troublesho ot o cd. Refer to the o cdebug man page for details. 6-4 Simple DDF A Troubleshooting

). Make sure to execute the dpp utility after ev ery up date of the dp le. Dpp creates a binary le whic h is used b y telnetd to assign the prop er device les to incoming connections. Chec k the v ersion of the DTC Manager whic h manages DTC serv er p orts. If the DTC Manager is PC-based, y ou should ha v e v ersion A.14.00 or later. If it is the host-based DTC Manager, y ou should ha v e v ersion A.03.00 or later. Chec k the v ersion of telnetd on the HP 9000 using the HP-UX what command. what /usr/lbin/telnetd On the $Header line display b y the what command, the telnetd v ersion should b e 1.22.110.10 or later. $Header: telnetd.c, v 1.22.110.10 Make sure that a T elnet connection can succeed. telnet Simple DDF A Troubleshooting 6-5

Remem b er that the assignment of dedicated pt ys on the HP 9000 dep ends up on the successful exc hange of DTC p ort information b y the DTC T elnet subsystem and the T elnet daemon on the HP 9000 at connection establishment time. Only the correct v ersions of softw are are capable of exc hanging this information. If Y ou Ha v e to Call Hewlett-P ackard If y our troublesho oting indicates that a serious problem has arisen and y ou need to call y our Hewlett-Pac k ard supp ort engineer, please ask y our system administrator to help y ou collect as man y of the follo wing items as p ossible. This list of items will greatly assist the supp ort engineer in isolating and resolving DDF A problems. A description of the problem and the conditions under whic h it o ccurred. F or example, did it o ccur on a previous release of DDF A or HP-UX, can it b e replicated, do es the same problem o ccur with a MUX connection? The follo wing data taken while the problem is o ccurring: 1. a log le of an o cdebug run ( /v ar/adm/o cd) 2. the syslog.log le from /v ar/adm/syslog 3. a nettl trace (see man pages for ho w to use nettl) 4. prin tout of sp o oler information b y typing lpstat -t 5. prin tout of pro cess information b y typing ps -ef 6. prin tout of net w ork status information from netstat -n The complete DDF A data path conguration: 1. prin tout of the /etc/lp/interface le asso ciated with the oending prin ter 2. listing of the dp les and p cf les used 3. v ersion n um b er of HP-UX b y typing uname -a 6-6 Simple DDF A Troubleshooting

4. hardw are platform, suc h as HP 9000 Series 800 or 700, and the mo del n um b er 5. v ersion of DDF A used b y typing what 6. list of installed DDF A patc hes from typing what 7. DTC Manager v ersion. Refer to the appropriate DTC Manager man ual for details. 8. map of y our DTC or non-DTC conguration do wn to the p ort lev el 9. typ e of device to whic h y ou wish to send outgoing or transmit incoming data 10. map of y our net w ork b et w een the system and the DTC or non-DTC terminal serv er 11. Non-DTC serv er information, including man ufacturer, hardw are and softw are v ersions and serv er conguration settings. Refer to the man ufacturer's pro duct do cumen tation. Simple DDF A Troubleshooting 6-7

A Appendix A: dpp Error Messages Error Numb er Message Reason 0 dp le is mandatory No dp le w as found when dpp w as started. 1 dp le must b e the rst argumen t The dp le must b e sp ecied as the rst argumen t when dpp is started. 2 Cannot read dp le The dp le men tioned do es not exist or cannot b e accessed with curren t access rights. 3 No log le dened (-l option) The -l option has b een detected with no argumen t. 4 Cannot create log le (-l ) The log le cannot b e created b ecause of inv alid path or insucien t access rights. 5 Cannot access log le (-l ) The log le cannot b e accessed b ecause of inv alid path or insucien t access rights. 6 No o cd le dened in program option The option -p has b een detected with no argumen ts. Appendix A: dpp Error Messages A-1

Error Numb er Message Reason 7 Cannot execute o cd program (-p The o cd program do es not exist or is not an executable le with correct access rights. 8 Cannot purge device le (/dev/xxx ) The option -k has b een selected and the device le exists but cannot b e purged b ecause of insucien t access rights. 9 Cannot execute default program (/usr/sbin/o cd) The o cd program cannot b e executed b ecause of insucien t access rights or b ecause it has not b een prop erly installed. 10 En try ignored (Bad IP address) The men tioned en try of the dp le do es not ha v e a v alid IP address. 11 En try ignored (No p ort/b oard info) The en try is ignored b ecause b oard/p ort information w as not men tioned in the dp le. 12 En try ignored (Bad p ort n umb er) The p ort men tioned in the display ed en try is not either a decimal v alue, or a string comp osed of x or X c haracters. 13 En try ignored (Bad b oard n umb er) The b oard men tioned in the display ed en try is not a decimal v alue, or it is not a string comp osed of x or X c haracters. 14 No more pro cesses av ailable on system The o cd program cannot b e started b ecause no more pro cesses can b e started on the system. A-2 Appendix A: dpp Error Messages

Error Numb er Message Reason 15 En try ignored (No device name) The device le name has not b een congured in the dp le. 16 En try ignored (Bad device name) The display ed device le cannot b e created b ecause of inv alid path or insucien t access rights. 17 En try ignored (Bad cong name) The display ed conguration le cannot b e read b ecause of inv alid path or insucien t access rights. 18 En try ignored (In v alid log lev el) The logging lev el w as not set b ecause of inv alid v alues (Must b e 0-3). 19 En try ignored (Bad no de name) The display ed conguration le cannot b e read b ecause of inv alid no de name. 30 T o o many login en tries (Limited to 2000) More than 2000 dedicated p orts for T elnet P ort Iden tication w ere sp ecied. 31 Cannot access dpp login le (/v ar/adm/ dpp login.bin) P ort Iden tication feature is disabled due to a dpp login le with insucien t access rights. 50 Device le not sp ecied in /dev/telnet Man y commands (suc h as ps) may not display the correct device le in their output unless device le is lo cated in /dev/telnet. 99 Unkno wn error Error of unkno wn origin. Appendix A: dpp Error Messages A-3

B Appendix B: ocd Logging Messages The outb ound connection daemon ( o cd or o cdebug ) sends its system logging messages to the le syslog.log in the directory /v ar/adm/syslog . Refer to the man ual pages for ho w to use o cd and o cdebug logging for basic troublesho oting. The o cd logging messages are classied in to log lev els 0 through 3 (critical, serious, w arning or informational). Eac h error message is describ ed b y error n um b er and lists a cause and suggested action. Appendix B: ocd Logging Messages B-1

Critical Messages Critical logging messages are issued when quitting o cd or o cdebug is caused b y the use of in v alid options, argumen t v alues, or pseudon yms, or the reception of SIGINT (signal in terrupt). Usage logging messages are caused b y syn tax errors. usage: ocd -n -f [-b] [-p] [-c] [-l] usage: ocdebug -n -f [-b] [-p] [-c] [-l] [-d] CAUSE: Ocd or ocdebug was executed with an illegal or missing option. ACTION: Restart ocd or ocdebug using the correct syntax and note that: 1. Legal options for both ocd and ocdebug are -n, -f, -b, p, -c, and -l. 2. Option -d is a legal option only for ocdebug. 3. Options -n and -f are mandatory for both ocd and ocdebug. 4. Each option requires an argument. (100) ERROR: Invalid node name : system error : CAUSE: The node name argument specified with the -n option could not be resolved into an IP address due to the system error given. ACTION: Restart ocd or ocdebug using a valid node name and note that: 1. The node name specified with the -n option must be defined in a name database. 2. The node name specified with the -n option must have an IP address assigned to it in that name database. 3. The access to that name database must not be impeded in any way. One way of validating the node name is to execute the nslookup command. B-2 Appendix B: ocd Logging Messages

(101) ERROR: Invalid board number CAUSE: The board number argument specified with the -b option was not in the range 0 to 7 for a DTC, or it was not a string consisting of "X" or "x". ACTION: Restart ocd or ocdebug using a DTC board number in the range 0 to 7, or a string consisting of "X" or "x". (102) ERROR: Invalid port number CAUSE: The port number argument specified with the -p option was not correct as follows: If the board number argument contained a value 0 to 7 for a DTC, then the port number argument was not in the range 0 to 31. If the board number argument was a string consisting of "X" or "x", then the port number argument was not an integer value representing a TCP service port, or a string consisting of "X" or "x" (which refers to the default TCP port address of 23 for the node name specified). ACTION: Restart ocd or ocdebug using a port number that is an integer value of a valid DTC port number in the range 0 to 31 or a TCP service port number, or a port number that is a string consisting of "X" or "x". (103) ERROR: Pseudonym has become invalid CAUSE: The pseudonym in use ceased to exist (most likely because another process deleted it) or was not in use by ocd or ocdebug and possibly was in use by another process. NOTE: This message is followed by message (403). ACTION: Make sure that no other process is using the pseudonym and restart ocd or ocdebug. (104) ERROR: Pseudonym no longer exists CAUSE: The pseudonym specified ceased to exist (most likely because another process deleted it). ACTION: Restart ocd or ocdebug. Appendix B: ocd Logging Messages B-3

(105) ERROR: Pseudonym unavailable CAUSE: The pseudonym specified was in use by another process and was not available for use by ocd or ocdebug. ACTION: Determine if the process using the pseudonym is necessary and restart ocd or ocdebug if it is not (after stopping that process and removing the pseudonym). (106) ERROR: Pseudonym in use but not by DDFA CAUSE: The pseudonym specified was in use by or created by a process other than ocd or ocdebug. ACTION: Determine if the process using the pseudonym is necessary and restart ocd or ocdebug if it is not (after stopping that process and removing the pseudonym). (107) ERROR: Pseudonym in use by DDFA with process identifier CAUSE: The pseudonym specified was in use by another ocd or ocdebug. ACTION: Determine if the process using the pseudonym is necessary and restart ocd or ocdebug if it is not (after stopping that process and removing the pseudonym). (108) ERROR: Received SIGINT signal (109) ERROR: Cleaning up daemon for pseudonym and device at node board port CAUSE: Ocd or ocdebug received a SIGINT signal and closed its connection and deleted its pseudonym. NOTE: These messages are followed by messages (403) and (432). ACTION: Restart ocd or ocdebug. B-4 Appendix B: ocd Logging Messages

(150) ERROR: Unable to allocate pty because no pty available for use CAUSE: There were no ptys available for use on the system. ACTION: Allocate more ptys on the system or wait to restart ocd or ocdebug until there are fewer processes running. (151) ERROR: Unable to obtain file information for pty : system error : CAUSE: There was no information available for the pty specified due to the system error given. ACTION: Look up what the stat(2) man page states about the system error given and make the correction as appropriate. (152) ERROR: Unable to create pseudonym with device identifier : system error : CAUSE: The pseudonym specified was not created due to the system error given. ACTION: Look up what the mknod(2) man page states about the system error given and make the correction as appropriate. (153) ERROR: Pseudonym does not belong to this daemon CAUSE: The pseudonym specified was not in use by ocd or ocdebug and possibly was in use by another process. ACTION: Determine if the process using the pseudonym is necessary and restart ocd or ocdebug if it is not (after stopping that process and removing the pseudonym). (154) ERROR: Unable to obtain information concerning availability of pseudonym : system error : CAUSE: There was no information available for the pseudonym specified due to the system error given. ACTION: Look up what the stat(2) man page states about the system error given and make the correction as appropriate. Appendix B: ocd Logging Messages B-5

(155) ERROR: Unable to free pseudonym : system error : CAUSE: The pseudonym specified was not freed from use by another process due to the system error given. ACTION: Look up what the kill(2) man page states about the system error given and make the correction as appropriate. (156) ERROR: Pseudonym is not pty slave CAUSE: The pseudonym specified was not a device special file. ACTION: Delete the pseudonym and restart the ocd or ocdebug. (157) ERROR: Unable to delete pseudonym left by previously run process: system error : CAUSE: The pseudonym specified was not deleted for use by a fresh ocd or ocdebug due to the system error given. ACTION: Delete the pseudonym and restart ocd or ocdebug. MESSAGE(S) THAT ACCOMPANY ALL CRITICAL ERROR MESSAGES: (199) ERROR: Terminating daemon CAUSE: Ocd or ocdebug was shutdown due to a critical error. ACTION: Take action based on cause indicated by preceding error messages. B-6 Appendix B: ocd Logging Messages

Serious Messages Serious logging messages are issued after: 1. o cd closes a connection or pseudon ym that has broken the communication path b et w een the application and the device. 2. Unexp ected conditions impact o cd or other pro cesses. (200) ERROR: Unable to obtain data from network: system error : CAUSE: There was no data to receive from the network due to the system error given. NOTE: This message is followed by messages (296), (297), (298), and (299). NOTE: System error 232 - A transport reset was received from the remote terminal server. System error 238 - A transport connection timeout was received from the remote terminal server. ACTION: Determine if the terminal server and device are operational and enable the printer or restart the application if they are. (201) ERROR: Binary negotiation failed on opening connection CAUSE: The binary negotiation was not completed successfully on opening a connection to the device on the remote terminal server. NOTE: This message is followed by message (296), (297), and (299). ACTION: Determine if the terminal server and device can accept binary data and restart the application if they can. (202) ERROR: Invalid initial status request received CAUSE: The initial status request to the device on the remote terminal server failed. NOTE: This message is followed by message (296), (297), and (299). ACTION: Determine if the terminal server and device are operational and restart the application if they are. Appendix B: ocd Logging Messages B-7

(203) ERROR: Connection failed CAUSE: A connection to the remote terminal server was not made. NOTE: This message is followed by messages (296), (297), and (298). ACTION: Determine if the terminal server and device are operational and enable the printer or restart the application if they are. (204) ERROR: Invalid terminating status request received CAUSE: The final status request to the device on the remote terminal server failed. NOTE: This message is followed by message (296), (297), and (299). ACTION: Determine if the terminal server and device are operational and restart the application if they are. (205) ERROR: Give up trying to obtain connection as number of open connection tries has been exhausted CAUSE: The number of tries to open a connection to the device on the remote terminal server was exhausted. NOTE: This message is followed by messages (296), (297), and (298). ACTION: Determine if the terminal server and device are operational and enable the printer or restart the application if they are. (206) ERROR: Unable to obtain timing mark negotiation from network: system error : CAUSE: There was no timing mark negotiation to receive from the network due to the system error given. NOTE: This message is followed by message (298). ACTION: Determine if the terminal server and device are operational and enable the printer if they are. B-8 Appendix B: ocd Logging Messages

(207) ERROR: No timing mark negotiation to obtain from network within time interval allowed CAUSE: There was no data and thus no timing mark negotiation to receive from the network during the time to wait for such negotiations (most likely because of the load on the terminal server, network, or system). NOTE: This message is followed by message (298). ACTION: Determine if the terminal server and device are operational and enable the printer if they are. (208) ERROR: No timing mark negotiation received in data during time interval allowed CAUSE: There was no timing mark negotiation in the data received from the remote terminal server. NOTE: This message is followed by message (298). ACTION: Enable the printer. (209) ERROR: Unable to obtain status reply from device: system error : CAUSE: There was no status reply to receive from the network due to the system error given. NOTE: This message is followed by messages (296), (297), (298), and (299). ACTION: Determine if the terminal server and device are operational and enable the printer or restart the application if they are. (210) ERROR: No status reply to obtain from device within time interval allowed CAUSE: There was no data and thus no status reply to receive from the network during the time to wait for that status reply (most likely because of the load on the terminal server, network, or system). NOTE: This message is followed by messages (296), (297), (298), and (299). ACTION: Determine if the terminal server and device are operational and enable the printer or restart the application if they are. (211) ERROR: Printer busy CAUSE: The printer on the remote terminal server was busy with another request. ACTION: Wait for the printer to free up before sending the next printer request. (212) ERROR: Printer out of paper CAUSE: The printer on the remote terminal server was out of paper. Appendix B: ocd Logging Messages B-9

ACTION: Add paper to the printer, put it on-line, and send the printer request. (213) ERROR: Printer off-line CAUSE: The printer on the remote terminal server was off-line. ACTION: Put printer on-line and send the printer request. (214) ERROR: Printer data error CAUSE: The printer on the remote terminal server had a data error. NOTE: This message is followed by messages (296), (297), (298), and (299). ACTION: Determine if the printer is operational and enable printer and send the printer request if it is. (215) ERROR: Unknown status reply CAUSE: No known status reply was received in the data from the device on the remote terminal server. ACTION: Refer to the manual for the device for an explanation of the status reply. (216) ERROR: Printer problem not fixed within time interval allowed CAUSE: The printer on the remote terminal server was not made ready during the time to wait for a status reply. NOTE: This message is followed by messages (296), (297), (298), and (299). ACTION: Put printer on-line, enable printer, and send the printer request. B-10 Appendix B: ocd Logging Messages

(217) ERROR: Unable to obtain binary negotiation from network: system error : CAUSE: There was no binary negotiation to receive from the network due to the system error given. NOTE: This message is followed by message (296), (297), and (299). ACTION: Determine if the terminal server and device are operational and restart the application if they are. (218) ERROR: No binary negotiation to obtain from network within time interval allowed CAUSE: There was no data and thus no binary negotiation to receive from the network during the time to wait for such negotiations (most likely because of the load on the terminal server, network, or system). NOTE: This message is followed by message (296), (297), and (299). ACTION: Determine if the terminal server and device are operational and restart the application if they are. (219) ERROR: Binary negotiation not completed on time CAUSE: There was no binary negotiation in the data received from the remote terminal server. NOTE: This message is followed by message (296), (297), and (299). (220) ERROR: Received SIGUSR2 signal (221) ERROR: Give up trying to obtain connection at request of user CAUSE: Ocd or ocdebug received a SIGUSR2 signal and any more tries to open a connection to the device on the remote terminal server were stopped. ACTION: Determine if the terminal server and device are operational and restart the application if they are. Appendix B: ocd Logging Messages B-11

MESSAGES COMMONLY SEEN WITH NON-STANDARD (USER-WRITTEN) APPLICATIONS: (222) ERROR: Control device request rejected as connection not open CAUSE: A control device request was received before an open request was received and after a close request was received. NOTE: This message is followed by messages (296) and (297). ACTION: Have all control device requests for a pseudonym sandwiched between an open request for that pseudonym and a close request for that pseudonym. (223) ERROR: Unable to obtain control device request argument: system error : CAUSE: The parameters to set for a set parameters control device request could not be obtained due to the system error given. ACTION: Determine if the correct structure (termio) is used and the correct parameters are being set and make any changes necessary. (224) ERROR: Unable to toggle binary mode off CAUSE: The binary mode was not turned off successfully. NOTE: This message is followed by message (296), (297), and (299). ACTION: Determine if the terminal server and device are operational and whether binary mode can be toggled off for the terminal server and restart the application if all conditions are met. (225) ERROR: Unable to toggle binary mode on CAUSE: The binary mode was not turned on successfully. NOTE: This message is followed by message (296), (297), and (299). ACTION: Determine if the terminal server and device are operational and whether binary mode can be toggled off for the terminal server and restart the application if all conditions are met. B-12 Appendix B: ocd Logging Messages

(226) ERROR: Unable to obtain send break request argument: system error : CAUSE: The parameter for a send break control device request could not be obtained due to the system error given. ACTION: Determine if the correct structure (termio) is used and the correct parameters are being set and make any changes necessary. (227) ERROR: Unable to obtain flow control request argument: system error : CAUSE: The parameter for a flow control device request could not be obtained due to the system error given. ACTION: Determine if the correct structure (termio) is used and the correct parameters are being set and make any changes necessary. (228) ERROR: Give up trying to obtain connection as connection already established CAUSE: A connection to the device on the remote terminal server was already established. ACTION: Establish only one connection for each device on a remote terminal server. (229) ERROR: DO binary negotiation rejected by remote side CAUSE: The idea of binary mode data transfers was rejected by the remote terminal server. NOTE: This message is followed by message (296), (297), and (299). ACTION: Determine if binary mode can be toggled on for the terminal server and restart the application if it can. (230) ERROR: DONT binary negotiation rejected by remote side CAUSE: The idea of non-binary mode data transfers was rejected by the remote terminal server. NOTE: This message is followed by message (296), (297), and (299). ACTION: Determine if binary mode can be toggled off for the terminal server and restart the application if it can. Appendix B: ocd Logging Messages B-13

(250) ERROR: Unable to obtain data from network or pty CAUSE: There were no data or events to be passed on the network or through the pseudonym due to a system error. NOTE: This message is followed by message (296), (297), and (299). ACTION: Restart ocd or ocdebug and restart the application. (251) ERROR: Unable to obtain data: system error : CAUSE: There were no data or events to be passed on the network or through the pseudonym due to the system error given. ACTION: Look up what the select(2) man page states about the system error given and make the correction as appropriate. (252) ERROR: Unable to obtain data from pty: system error : CAUSE: There were no data to receive from the pty due to the system error given. NOTE: This message is followed by message (296), (297), and (299). ACTION: Look up what the read(2) man page states about the system error given and make the correction as appropriate. (253) ERROR: Unable to obtain request information from pty: system error : CAUSE: There was no control request data to receive from the pty due to the system error given. NOTE: This message is followed by message (296), (297), and (299). ACTION: Look up what the ioctl(2) man page states about the system error given and make the correction as appropriate. (254) ERROR: Unknown Telnet state CAUSE: A Telnet state discovered while processing a Telnet command was not a known Telnet state. NOTE: This message is followed by message (296), (297), and (299). ACTION: Determine if the terminal server is using the Telnet protocol correctly and restart the application if it is. B-14 Appendix B: ocd Logging Messages

(255) ERROR: Unknown internal parameter in port configuration file CAUSE: The internal port configuration parameter discovered while processing the port configuration file is not a known parameter. ACTION: No action. (256) ERROR: Give up trying to obtain connection: system error : CAUSE: Any more tries to open a connection to the device on the remote terminal server were stopped due to the system error given. NOTE: This message is followed by messages (296), (297), and (298). ACTION: Look up what the connect(2) man page states about the system error given and make the correction as appropriate. (257) ERROR: Unable to obtain out-of-band data: system error : CAUSE: There was no out-of-band data to receive from the network due to the system error given. ACTION: Look up what the select(2) man page states about the system error given and make the correction as appropriate. (258) ERROR: No timing mark negotiation to obtain from network CAUSE: Unexpected data was received from a place other than the network before there was a timing mark negotiation to receive from the network. NOTE: This message is followed by message (298). ACTION: Enable the printer and send the printer request. (259) ERROR: Unable to read timing mark negotiation from network: system error : CAUSE: There was no timing mark negotiation to read from the network due to the system error given. NOTE: This message is followed by message (298). ACTION: Look up what the read(2) man page states about the system error given and make the correction as appropriate. Appendix B: ocd Logging Messages B-15

(260) ERROR: Unknown Telnet state during timing mark negotiation CAUSE: A Telnet state discovered while processing a Telnet timing mark negotiation was not a known Telnet state. NOTE: This message is followed by message (296), (297), and (299). ACTION: Determine if the terminal server is using the Telnet protocol correctly and restart the application if it is. (261) ERROR: Unable to read status reply from device: system error : CAUSE: There was no status reply to read from the network due to the system error given. NOTE: This message is followed by messages (296), (297), (298), and (299). ACTION: Look up what the read(2) man page states about the system error given and make the correction as appropriate. (262) ERROR: No status reply to obtain from device CAUSE: Unexpected data was received from a place other than the network before there was a status reply to receive from the network. NOTE: This message is followed by messages (296), (297), (298), and (299). ACTION: Restart the application, enable the printer, and send the printer request. (263) ERROR: No binary negotiation to obtain from network CAUSE: Unexpected data was received from a place other than the network before there was a binary negotiation to receive from the network. NOTE: This message is followed by message (296), (297), and (299). ACTION: Restart the application. (264) ERROR: Unable to read binary negotiation from network: system error : CAUSE: There was no binary negotiation to read from the network due to the system error given. NOTE: This message is followed by message (296), (297), and (299). ACTION: Look up what the read(2) man page states about the system error given and make the correction as appropriate. B-16 Appendix B: ocd Logging Messages

(265) ERROR: Unable to get terminal parameters: system error : CAUSE: There were no device file parameters to obtain from the pty due to the system error given. ACTION: Look up what the ioctl(2) man page states about the system error given and make the correction as appropriate. (266) ERROR: Unable to set terminal parameters: system error : CAUSE: The device file parameters were not set on the pty due to the system error given. ACTION: Look up what the ioctl(2) man page states about the system error given and make the correction as appropriate. (267) ERROR: Unable to write data to pty: system error : CAUSE: There were no data to send to the pty due to the system error given. ACTION: Look up what the write(2) man page states about the system error given and make the correction as appropriate. (268) ERROR: Unable to write data to network: system error : CAUSE: There were no data to send to the network due to the system error given. ACTION: Look up what the send(2) man page states about the system error given and make the correction as appropriate. (269) ERROR: Unable to delete pseudonym for recreation and use: system error : CAUSE: The pseudonym was not deleted due to the system error given. ACTION: Delete the pseudonym and restart ocd or ocdebug. (270) ERROR: System returned error while disabling printer: system error : CAUSE: The disable command had an error as given. This does not affect the disabling of the printer queue. ACTION: No immediate action is necessary although enabling the Unix spooler printer queue in the future is required to restart the printing process for that printer queue. Appendix B: ocd Logging Messages B-17

MESSAGE(S) THAT ACCOMPANY SOME SERIOUS ERROR MESSAGES: (296) ERROR: Recreating pseudonym with new pty CAUSE: The pseudonym was recreated and linked to a new pty opened for it. NOTE: This message accompanies messages (200), (201), (202), (203), (204), (205), (209), (210), (214), (216), (217), (218), (219), (222), (224), (225), (229), (230), (250), (252), (253), (254), (256), (260), (261), (262), (263), and (264). ACTION: No action is necessary. (297) ERROR: Removing pseudonym and closing pty CAUSE: The pseudonym was deleted and its associated pty was closed due to a serious error with the pseudonym. NOTE: This message accompanies messages (200), (201), (202), (203), (204), (205), (209), (210), (214), (216), (217), (218), (219), (222), (224),(225), (229), (230), (250), (252), (253), (254), (256), (260), (261), (262), (263), and (264). NOTE: This message is followed by message (432). ACTION: No action is necessary. (298) ERROR: Printer disabled CAUSE: The Unix spooler printer queue associated with the outbound connection daemon was disabled. NOTE: This message accompanies messages (200), (203), (205), (206), (207), (208), (209), (210), (214), (216), (256), (258), (259), (261), and (262). ACTION: No immediate action is necessary although enabling the Unix spooler printer queue in the future is required to restart the printing process for that printer queue. (299) ERROR: Closing connection due to error with data path CAUSE: The connection to the device on the remote terminal server was closed due to a serious error with the connection or with the pseudonym. NOTE: This message accompanies messages (200), (201), (202), (204), (209),(210), (214), (216), (217), (218), (219), (224), (225), (229), (230), (250), (252), (253), (254), (260), (261), (262), (263), and (264). ACTION: No action is necessary. B-18 Appendix B: ocd Logging Messages

W arning Messages W arning logging messages are issued when an unexpected condition o ccurs that do es not aect normal op eration of o cd or other pro cesses. Usage messages are caused b y syn tax errors. USAGE MESSAGE: ocd: unknown option: (ignored) CAUSE: The option given was not a valid option. ACTION: Remove the option from the command line. (300) WARNING: Invalid logging level (valid values are 0, 1, 2, or 3) CAUSE: The logging level given was not 0, 1, 2, or 3. ACTION: Use a logging level of 0, 1, 2, or 3. (301) WARNING: Port configuration file not specified or not specified correctly CAUSE: The -c option was not specified. NOTE: This message is followed by message (350). ACTION: Use a correct configuration file name. (302) WARNING: Timing mark negotiation disabled because Telnet mode disabled CAUSE: Timing mark negotiation was enabled but the Telnet mode was disabled. ACTION: Either enable the Telnet mode or disable the timing mark negotiation. Appendix B: ocd Logging Messages B-19

(303) WARNING: Pseudonym not specified in /dev/telnet CAUSE: The pseudonym specified was not to be placed into the directory /dev/telnet set aside for all pseudonyms. ACTION: Place all pseudonym names in /dev/telnet. (304) WARNING: Unable to change permissions of pseudonym to : system error : CAUSE: The permissions of the pseudonym were not changed to optimal values (0666) due to the system error given. ACTION: Look up what the chmod(2) man page states about the system error given and make the correction as appropriate. (305) WARNING: Unable to enable packet mode on pty: system error : CAUSE: Packet mode on the pty could not be enabled due to the system error given. ACTION: Look up what the ioctl(2) man page states about the system error given and make the correction as appropriate. (306) WARNING: Unable to enable non-blocking mode on pty: system error : CAUSE: Non-blocking mode on the pty could not be enabled due to the system error given. ACTION: Look up what the ioctl(2) man page states about the system error given and make the correction as appropriate. (307) WARNING: Application canceled open request CAUSE: The application closed the pty before the open request had completed. ACTION: Restart the application. (308) WARNING: Unable to enable non-blocking mode on network socket: system error : CAUSE: Non-blocking mode on the network could not be enabled due to the system error given. ACTION: Look up what the ioctl(2) man page states about the system error given and make the correction as appropriate. B-20 Appendix B: ocd Logging Messages

(309) WARNING: Close not completed as data processing not complete CAUSE: There was still data to send to the device on the remote terminal server as the close was requested. ACTION: No action is necessary. (310) WARNING: Close request ignored as connection not open CAUSE: The close request was received and ignored as the connection was not open. This occurred because of an application sending a close request at the wrong time or because of an error that previously closed the connection. ACTION: Generally, no action is necessary unless a close request is not sent after an open request. (311) WARNING: Binary mode cannot be turned off as permanently turned on CAUSE: The application requested that the binary mode be turned off when the binary mode is turned on for the connection using the port configuration file and thus cannot be turned off. ACTION: Determine if the binary mode is necessary at all times and disable it if it is not. (312) WARNING: Unable to perform flush operation CAUSE: The application requested a flush operation and ocd and ocdebug do not support that operation. ACTION: Determine if a flush operation is necessary by the application and do not perform it if it is not. (313) WARNING: Cannot open port configuration file: system error : CAUSE: The open of the port configuration file failed due to the system error given. NOTE: This message is followed by message (350). ACTION: Verify the port configuration file name, location, and permissions. Appendix B: ocd Logging Messages B-21

(314) WARNING: Unknown parameter in port configuration file (ignored) CAUSE: The port configuration parameter specified is not valid and has been ignored. ACTION: Verify the port configuration parameter name. (315) WARNING: Unable to set keep alive option on network socket: system error : CAUSE: The keep alive option on the network could not be set due to the system error given. ACTION: Look up what the setsockopt(2) man page states about the system error given and make the correction as appropriate. (316) WARNING: Unable to set option on network socket as unable to obtain protocol attributes: system error : CAUSE: The no delay option on the network could not be set as the protocol could not be obtained due to the system error given. ACTION: Look up what the getprotobyname(3N) man page states about the system error given and make the correction as appropriate. (317) WARNING: Unable to set no delay option on network socket: system error : CAUSE: The no delay option on the network could not be set due to the system error given. ACTION: Look up what the setsockopt(2) man page states about the system error given and make the correction as appropriate. (318) WARNING: Unable to reply to control device request: system error : CAUSE: The control device reply to the control device request could not complete due to the system error given. A reply is made for each request sent by an application and must be made for the application to continue. ACTION: Look up what the ioctl(2) man page states about the system error given and make the correction as appropriate. B-22 Appendix B: ocd Logging Messages

(319) WARNING: Unable to obtain negotiation from network: system error : CAUSE: There was no Telnet negotiation to receive from the network due to the system error given. ACTION: Look up what the select(2) man page states about the system error given and make the correction as appropriate. (320) WARNING: No negotiation to obtain from network within time interval allowed CAUSE: There was no data and thus no Telnet negotiation to receive from the network during the time to wait for such negotiations (most likely because of the load on the terminal server, network, or system). ACTION: Determine if the terminal server and device are operational and make them operational if they are not. (321) WARNING: Unable to read negotiation from network: system error : CAUSE: There was no Telnet negotiation to read from the network due to the system error given. ACTION: Look up what the read(2) man page states about the system error given and make the correction as appropriate. (322) WARNING: No negotiation to obtain from network CAUSE: Unexpected data was received from a place other than the network before there was a Telnet negotiation to receive from the network. ACTION: No action is necessary. (323) WARNING: No status reply from device CAUSE: No status reply was received in the data from the device on the remote terminal server. ACTION: No action is necessary. Appendix B: ocd Logging Messages B-23

(324) WARNING: Status reply received characters CAUSE: A status reply of more than one character was received in the data from the device on the remote terminal server. ACTION: No action is necessary. (325) WARNING: Unable to send interrupt signal to application: system error : CAUSE: An interrupt could not be sent to the application due to the system error given. ACTION: Look up what the ioctl(2) man page states about the system error given and make the correction as appropriate. (326) WARNING: Unable to send break to application: system error : CAUSE: A break could not be sent to the application due to the system error given. ACTION: Look up what the ioctl(2) man page states about the system error given and make the correction as appropriate. (327) WARNING: Unable to write bytes to pty CAUSE: An attempt to write all data to the pty failed because the pty had no room for the amount of data specified. ACTION: Determine if the application is running correctly and draining data from the pty regularly and restart the application if it is not. (328) WARNING: Unable to write bytes of normal data to network CAUSE: An attempt to write all data to the network failed because the network had no room for the amount of data specified. ACTION: Determine if the network, terminal server, and device are running correctly and draining data regularly and correct the situation as necessary. B-24 Appendix B: ocd Logging Messages

(329) WARNING: Unable to write bytes of urgent data to network CAUSE: An attempt to write all data to the network failed because the network had no room for the amount of data specified. ACTION: Determine if the network, terminal server, and device are running correctly and draining data regularly and correct the situation as necessary. (330) WARNING: Unable to obtain information concerning existence of pseudonym : system error : CAUSE: There was no information available for the pseudonym specified due to the system error given. ACTION: Look up what the stat(2) man page states about the system error given and make the correction as appropriate. (331) WARNING: Unable to delete pseudonym when terminating daemon: system error : CAUSE: The pseudonym was not deleted due to the system error given. ACTION: Delete the pseudonym. (332) WARNING: Unknown logging level CAUSE: A log message with an unknown logging level was encountered. ACTION: No action is necessary. MESSAGE(S) THAT ACCOMPANY SOME WARNING MESSAGES: (350) WARNING: Using default port configuration values CAUSE: The hard-coded default port configuration values were invoked for use as the port configuration file could not be used due to the warning given in the accompanying message (either message (301) or message (313)). ACTION: No action is necessary. Appendix B: ocd Logging Messages B-25

Informational Messages Informational messages are issued when an exp ected condition o ccurs during normal pro cessing. No action is required. (400) NOTE: Target device at node board port TCP port CAUSE: Indicates the location of the device on the remote terminal server. (401) NOTE: Created pseudonym CAUSE: Indicates the name of the pseudonym created for use. (402) NOTE: Linked pseudonym to master slave file descriptor CAUSE: Indicates the association of the pseudonym with a pty. (403) NOTE: Closing connection CAUSE: Indicates the closing of a network connection to the remote terminal server due to the serious error given in the accompanying message (either message (103) or message (108)). (404) NOTE: Received open request from application CAUSE: Indicates the reception of an open request for a pseudonym by the application specified. (405) NOTE: Set pty characteristics CAUSE: Indicates the setting of the initial pty characteristics. (406) NOTE: Sending initial status request to device CAUSE: Indicates the sending of a status request to the device on the remote terminal server before any data is sent to that device. B-26 Appendix B: ocd Logging Messages

(407) NOTE: Received close request from application CAUSE: Indicates the reception of a close request for a pseudonym by the application specified. (408) NOTE: Received control device request from application CAUSE: Indicates the reception of a control device request for a pseudonym by the application specified. (409) NOTE: Sending terminating status request to device CAUSE: Indicates the sending of a status request to the device on the remote terminal server after all data is sent to that device. (410) NOTE: Sent Telnet break to device CAUSE: Indicates the sending of a Telnet break sequence to the remote terminal server. (411) NOTE: Sent STOP character to device CAUSE: Indicates the sending of a STOP data flow character (usually control-S) to the device on the remote terminal server. (412) NOTE: Sent START character to device CAUSE: Indicates the sending of a START data flow character (usually control-Q) to the device on the remote terminal server. (413) NOTE: Sent are you there sequence to device CAUSE: Indicates the sending of a response to a Telnet are you there sequence to the remote terminal server. (414) NOTE: Aborted output for application CAUSE: Indicates the abortion of output from the application to the device on the remote terminal server. Appendix B: ocd Logging Messages B-27

(415) NOTE: Erased character or line for application CAUSE: Indicates the erasure of a character or line of data from the device on the remote terminal server to the application. (416) NOTE: Received terminal type subnegotiation CAUSE: Indicates the reception of the device type from the device on the remote terminal server. (417) NOTE: Connected to device at node TCP port number CAUSE: Indicates the location of the device on the remote terminal server to which connected. (418) NOTE: Sent timing mark negotiation CAUSE: Indicates the sending of a timing mark negotiation request to the remote terminal server. (419) NOTE: Waiting seconds for timing mark negotiation reply CAUSE: Indicates the number of seconds to wait for a timing mark negotiation reply from the remote terminal server. (420) NOTE: Timing mark negotiation reply received CAUSE: Indicates the successful completion of a timing mark negotiation. (421) NOTE: Waiting seconds for Telnet negotiation reply CAUSE: Indicates the number of seconds to wait for a Telnet negotiation reply from the remote terminal server. (422) NOTE: Sent status request CAUSE: Indicates the sending of a status request to the device on the remote terminal server. (423) NOTE: Waiting seconds for status reply CAUSE: Indicates the number of seconds to wait for a status reply from the device on the remote terminal server. (424) NOTE: Printer ready CAUSE: Indicates that the printer is ready for print requests. B-28 Appendix B: ocd Logging Messages

(425) NOTE: Sent binary negotiation CAUSE: Indicates the sending of a binary negotiation request to the remote terminal server. (426) NOTE: Waiting seconds for binary negotiation reply CAUSE: Indicates the number of seconds to wait for a binary negotiation reply from the remote terminal server. (427) NOTE: Binary negotiation accepted by remote side CAUSE: Indicates the successful completion of the binary negotiation. (428) NOTE: Sent interrupt signal to application CAUSE: Indicates the sending of an interrupt to the application. (429) NOTE: Sent break to application CAUSE: Indicates the sending of a break to the application. (430) NOTE: Pseudonym does not exist CAUSE: Indicates the non-existence of the pseudonym specified and its availability for use. (431) NOTE: Deleted pseudonym to make it available for use CAUSE: Indicates the successful deletion of the pseudonym specified and its availability for use. (432) NOTE: Deleted pseudonym CAUSE: Indicates the successful deletion of the pseudonym specified. NOTE: This message accompanies messages (108) and (297). Appendix B: ocd Logging Messages B-29

(433) NOTE: Closed pty CAUSE: Indicates the closure of the pty specified after the deletion of its associated pseudonym. (434) NOTE: Closing connection due to application completion CAUSE: Indicates the clean closure of the connection to the remote terminal server after the close timer had expired. (435) NOTE: Received and (436) NOTE: Received and CAUSE: Indicate the reception of a Telnet command and option. (437) NOTE: Sent (438) NOTE: Sent CAUSE: Indicate the sending of a Telnet command and option. B-30 Appendix B: ocd Logging Messages

Index A accessing DTC or non-DTC p orts programmatically, 5-3 accessing MUX, 2-1 applications programmer, 1-2 B binary mo de, 4-6 binary mo de, 4-6 C call close(), 5-3 io ctl(), 5-3 op en(), 5-3 read(), 5-3 write(), 5-3 close, 1-2, 2-2 , 3-2 close call, 4-7, 5-3 close timer, 4-7 commands HP-UX, 5-1 tt y, 2-7 what, 6-5 commands, HP-UX disable, 5-1 enable, 5-1 insf, 4-10 kill, 4-11 lpadmin, 5-1 mkno d, 2-5 ps, 4-11 commands, HP-UX , insf, 2-5 conguration examples, 5-1 congure dedicated p ort les, 2-10 Index-1

conguring b oard, 2-10 Conguring Incoming Connections for CSLIP/SLIP, 5-5 conguring p orts, 2-10 connection retries, 4-7 connections incoming T elnet, 4-13 outgoing, 2-6, 6-3 CSLIP, 5-5 CSLIP connections ov er DTCs, 5-1 D daemon, 3-2 Datacomm unications and T erminal Controller (DTC), 1-1 data transfer, 4-6 DDF A, 3-1 DDF A conguration tasks, 3-4 DDF A le directories, 2-9 DDF A lesets, 2-9 DDF A installation and migration, 2-9 ddfa manual reference page, 5-5 DDF A migration, 2-9 DDF A Utilities, 4-4, 5-1 dedicated p ort, 2-5 dedicated p ort conguration le, 4-9 Dedicated P ort conguration le, 3-1 dedicated p ort le, 4-2 dedicated p ort le (dp), 2-5 dedicated p ort les conguration, 2-10 dedicated p ort parser, 4-9 Dedicated P ort P arser, 3-1 , 3-9 dedicated pt ys, 6-6 dedicated serv er p ort, 4-4 default p ort conguration le, 4-5 /dev, 2-6 device le remo ving, 4-9 device le names, 2-5 device les, 1-1 /dev/pt y, 4-10 /dev/pt ym, 4-10 /dev/telnet, 2-10 Index-2

disable, 5-1 dp, 3-1 , 4-1, 4-2 dp (dedicated p ort le), 2-5 dp le, 4-5, 4-13, 5-3 , 6-5 killing and restarting o cds, 4-12 remo ving existing o cds, 4-12 starting the o cds, 4-11 starting up new o cds, 4-12 up dating T elnet P ort Iden tication Info, 4-13 dpp, 4-1 syn tax, 4-9 dppj , 3-1 dpp -k option, 4-12 dpp outgoing connections, 6-3 dpp pro cess binary le, 4-13 DTC, 1-4, 2-6 DTC 16, 1-4 DTC 16MX, 1-4 DTC 16RX, 1-4 DTC 16TN, 1-4 DTC 48, 1-4 DTC 72MX, 1-4 DTC b oard, 4-3 DTC b oard n umb er, 3-5 DTC input device, 3-8 DTC manager, 2-10 DTC Manager, 6-5 v ersion, 6-5 DTC Manager/UX, 1-2 DTC No de Name, 3-5, 4-3 DTC p ort, 2-2, 3-5, 4-3 DTC p ort n umb er, 3-5 E eight bit, 4-8 enable, 5-1 error messages, 4-9 /etc/ddfa/dp, 3-1, 4-2, 5-2 /etc/ddfa/p cf, 4-5 /etc/rc.cong.d/netdaemons le, 4-9 Index-3

F o w con trol, 4-6 H HP 2340A, 1-4 HP 2345A, 1-4 HP 2360A, 1-4 HP 2363A, 1-4 HP 2364A, 1-4 HP 2370A, 1-4 HP 3000 systems, 1-3 HP 9000 ARP A, 1-1 HP 9000 In ternet Services, 1-1 HP 9000 Series 700, 1-3 HP 9000 Series 800, 1-3 HP 9000 systems, 1-3 HP D2355A, 1-2 HP J2120A, 1-2 HP-UX , 2-7 HP-UX command what, 6-5 HP-UX commands, 5-1 disable, 5-1 enable, 5-1 lpadmin, 5-1 rm, 4-11 who, 2-7 HP-UX op erating system v ersion, 1-3 HP-UX sp o oler, 3-7 , 5-1 setting up prin ters, 5-1 I incoming connections, 2-2 , 4-3 managing, 4-13 troublesho oting, 6-5 Incoming Connections , 5-5 Incoming Connections ov er DTCs, 5-5 incoming T elnet connections, 4-13 incomng connections, 2-6 INETSV CS-DTC, 2-9 INETSV CS-MAN, 2-9 INETSV CS-RUN leset, 2-9 insf command, 2-5 , 4-10 Index-4