=;The OpenVMS Frequently Asked Questions (FAQ)D

The OpenVMS Frequently Asked Questions (FAQ)



 r \ ^  
PreviousContentsIndex

p

14.27 What connectors and wiring adapters are available?



FThe H8571-B and H8575-B convert the (non-2000-series) MicroVAX DB9 to Gthe DECconnect DEC-423 Modified Modular Jack (MMJ) pin-out; to the MMJ DECconnect wiring system.HThe MicroVAX 2000 and VAXstation 2000 requires a BCC08 cable (which has fthe 8-9 short, see Section 14.26) and the H8571-C or the H8571-D ,DB25-to-MMJ adapter for use with DECconnect.H(For a discussion of the console bulkhead on the MicroVAX II series and ion other closely-related series systems, please see Section 14.3.3.4.)

GSomewhat less ancient HP (HP, Compaq or DIGITAL logo) systems will use Eeither the DECconnect MMJ wiring directly or---on most (all?) recent Gsystem designs---the PC-compatible DB9 9-pin pin-out; the PC-style COM %serial port interface and connection.

FThere are two DB9 9-pin pin-outs, that of the H8571-B and similar Afor the MicroVAX and other and older <systems, and that of the H8571-J for the PC-style COM port, EAlphaStation, Integrity, and other newer systems. The older MicroVAX >DB9 and the PC-style DB9 pin-outs are not compatible.

r   >                                                          
Table 14-8 DECconnect MMJ Connectors and Adapters
Part Converts BC16E MMJ male to fit into
H8571-A F EIA232 DB25 25-pin female (common). Functionally similar to the ; H8575-A, though the H8575-A has better ESD shielding.
H8571-B L Older MicroVAX (other than the MicroVAX 2000) DB9 EIA232 serial port. M Functionally similar to the H8575-B, though the H8575-B has better ESD  shielding.F Note: Cannot be used on a PC, Alpha nor Integrity DB9 9-pin  connector.
H8571-C + 25 pin DSUB Female to MMJ, Unfiltered
H8571-D & EIA232 25 pin male (modem-wired)
H8571-E ) 25 pin DSUB Female to MMJ, Filtered
H8571-J F PC, Alpha, Integrity 9 pin (DB9) male (PC-style COM serial port)M Note: Cannot be used on the older MicroVAX DB9 9-pin connector
H8572-0 , BC16E MMJ double-female (MMJ extender)
H8575-A F EIA232 DB25 25-pin female (common). Functionally similar to the ; H8571-A, though the H8575-A has better ESD shielding.
H8575-B L Older MicroVAX (other than the MicroVAX 2000) DB9 EIA232 serial port. M Functionally similar to the H8571-B, though the H8575-B has better ESD  shielding.F Note: Cannot be used on a PC, Alpha nor Integrity DB9 9-pin  connector
H8575-D . 25 Pin to MMJ with better ESD Protection
H8575-D 2 25 Pin to MMJ with better and ESD Protection
H8575-E 7 25 Pin Integrity rx2600 Management Processor (MP) & & & / port to MMJ, with ESD Protection
 H8577-AA " 6 pin Female MMJ to 8 pin MJ
 BC16E-** = MMJ cable with connectors, available in various lengths


HNumerous additional adapters and cables are available from the (now out =of print) OPEN DECconnect Building Wiring Components and GApplications Catalog, as well as descriptions of the above-listed parts.

HThe DECconnect wiring system has insufficient signaling for modems, and 5particularly lacks support for modem control signals.

EThe H8571-A and H8575-A are MMJ to DB25 (female) and other connector wiringBdiagrams and adapter-, cable- and pin-out-related discussions are available at:



JamecoF has offered a USB-A to PS/2 Mini DIN 6 Adapter (as part 168751), for > those folks wishing to (try to) use PS/2 Keyboards via USB-A connections.

The LK463 USBF keyboard is also a potential option, for those wishing to connect an G OpenVMS keyboard to USB systems or (via the provided adapter) to PS/2 G systems. The LK463 provides the classic OpenVMS keyboard and keyboard F layout on USB-based system configurations, including operations with I the USB connection on specific Alpha systems (and specifically on those : with supported USB connections) and on Integrity servers.

GFor information on the Alpha console COM port(s) or on the VAX console Dport, please see Section 14.3.h

14.28 What is flow control and how does it work?



%XON/XOFF is one kind of flow control.

DIn ASCII, XON is the [CTRL/Q] character, and XOFF is the [CTRL/S].

GXON/XOFF flow control is typically associated with asynchronous serial Gline communications. XON/XOFF is an in-band flow control, meaning that +the flow control is mixed in with the data.

ACTS/RTS is another type of flow control, and is sometimes called Ghardware flow control. Out-of-band means that seperate lines/pins from <the data lines (pins) are used to carry the CTS/RTS signals.

HBoth kinds of flow control are triggered when a threshold is reached in >the incoming buffer. The flow control is suppose to reach the Etransmitter in time to have it stop transmitting before the receiver Ebuffer is full and data is lost. Later, after a sufficient amount of Ethe receiver's buffer is freed up, the resume flow control signal is (sent to get the transmitter going again.

GDECnet Phase IV on OpenVMS VAX supports the use of asynchronous serial $communications as a network line; ofD asynch DECnet. The communication devices (eg. modems, and drivers) @ must not be configured for XON/XOFF flow control. The F incidence of these (unexpected) in-band characters will corrupt data H packets. Further, the serial line device drivers might normally remove H the XON and XOFF characters from the stream for terminal applications, B but DECnet configures the driver to pass all characters = through and requires that all characters be permitted. (The C communication devices must pass through not only the XON and XOFF H characters, they must pass all characters including the 8-bit E characters. If data compression is happening, it must reproduce the G source stream exactly. No addition or elimination of null characters,  and full data transparency.

DAn Ethernet network is rather different than an asynchronous serial Fline. Ethernet specifies the control of data flow on a shared segment Gusing CSMA/CD (Carrier Sense Multiple Access, with Collision Detect) AnGEthernet station that is ready to transmit listens for a clear channel B(Carrier Sense). When the channel is clear, the station begins to Gtransmit by asserting a carrier and encoding the packet appropriately. BThe station concurrently listens to its own signal, to permit the Cstation to detect if another station began to transmit at the same Gtime---this is called collision detection. (The collision corrupts the Csignal in a way that can reliably be detected.) Upon detecting the Gcollision, both stations will stop transmitting, and will back off and Etry again a little later. (You can see a log of this activity in the DECnet NCP network counters.)

DECnetHprovides its own flow control, above and beyond the flow control of the Ephysical layer (if any). The end nodes handshake at the beginning to Destablish a transmit window size---and a transmitter will only send Gthat much data before stopping and waiting for an acknowledgement. The Hacknowledgement is only sent when the receiver has confirmed the packet Dis valid. (A well-configured DECnet generally avoids triggering any 1underlying (out-of-band) flow control mechanism.)_

14.29 CD and DVD device requirements?



HRead access to DVD-ROM, DVD+R/RW, DVD-R/RW, CD-ROM, and CD-R/RW devices on ATAPI (IDE) connections isGgenerally handled transparently by SYS$DQDRIVER, and SYS$DQDRIVER will Gtransparently de-block the media-native 2048 byte disk blocks with the C512-byte blocks expected by OpenVMS and by native OpenVMS software.

HRead access to DVD-ROM, DVD+R/RW, DVD-R/RW, CD-ROM, and CD-R/RW devices 3on SCSI is handled by DKDRIVER, though SYS$DKDRIVERFwill not transparently de-block the native 2048-byte disk blocks into Hthe 512-byte blocks expected by OpenVMS. The drive or external software Fis expected to provide this de-blocking, thus either a 512-byte block Gcapable drive (such as all RRD-series SCSI CD-ROM drives) is required, For host software is required for a 2048-byte block drive. Third-party HSCSI drives with UNIX references in their support documentation or with Gexplicit 512-byte selectors or swiches will generally (but not always, of course) operate with OpenVMS.

HAt least some of the Plextor PlexWriter SCSI drives can be successfully "accessed (for read and write) fromHOpenVMS, as can at least one Pioneer SCSI DVD drive (for CD media). The PioneerB SCSI DVD drive switches to 2048 byte blocks for DVD media, and a I block-size conversion tool (written by Glenn Everhart) or other similar  tool can be applied.

AOpenVMS also has supported HP DVD drives for the ATAPI (IDE) bus.

CFor some related information (and details on a commercial DVDwrite package), please see:



CNo device driver currently presently permits direct block-oriented ?recording on DVD-RAM nor DVD+RW media, nor other recordable or rewritable media.

HRecording (writing) of CD and DVD optical media requires a recording or =media mastering application or tool, and both commercial and fnon-commercial options are available. See Section 9.7 for related Fdetails on CDRECORD (both non-DVD and DVD versions are available, and Eat least one commercial version is available), and also see DVDwrite ((commercial) or DVDRECORD (open source).

.For information on the GKDRIVER (SYS$GKDRIVER)6generic SCSI device driver and of the the IO$_DIAGNOSEC$qio[w] interfaces (of SYS$DKDRIVER, SYS$DNDRIVER and SYS$DQDRIVER)Fthat are utilized by most CD and DVD recording tools to send commands Bto SCSI, USB or ATAPI devices (most USB and ATA devices---or more Dcorrectly, most ATAPI devices---can use SCSI-like command packets), -please see the SYS$EXAMPLES:GKTEST.C example,-and see DECW$EXAMPLES:DECW$CDPLAYER.C exampleBand please see the various associated sections of the OpenVMS I/O User's Reference Manual.

FFor information on creating bootable optical media on OpenVMS, please ;see Section 9.7.3.p

14.30 Office-Friendly (Quieter) Integrity rx2620 series?



HThe part number for the so-called Office-Friendly or Office Environment "Integrity rx2620 series is AD244A.

DThe AD244A option is incompatible with and eliminates the redundant Hcooling and power supply capabilities of, but greatly reduces the sound Doutput from, the Integrity rx2620 rack-mount computer-room variant. D(Server rack-mount configurations are rated for sound output in the @range of 70dB, per the HP QuickSpecs. Suitable for the intended Hinstallation into a computer room of course, but likely rather loud for $an office environment installation.)

FIf you wish to retrofit this option into an existing Integrity rx2620 Eseries, you must also order the HA113A1 (#53E) installation service; @the option reportedly can not be installed by an end-user. Also Hreportedly, the option can be factory-ordered on custom configurations. FIf configuring for or converting an existing rack-mount configuration Bfor the office environment, also consider acquiring the available (pedestal-mounting option for the series.n

14.31 KVM switches for AlphaServer and Integrity Servers?



EVarious folks have reported success with the Raritan series KVM (and >specifically APKME the), and with the HP-branded KVM switches.

GIf you choose a KVM for use with Alpha or Integrity servers, do ensure Cit provides either Unix compatibility, X Windows compatibility, or Fspecifies the Alpha or Integrity system. (This all usually means that Cthe switch supports keyboards that use the so-called scanset three Gkey-down and key-up sequences---key-down and key-up are key to the way %X Windows and thus DECwindows works.)

jAlso see the discussion in Section 14.18 for related information, and Fparticularly for older pinouts---for those keyboard and mouse devices 7that pre-date the PS/2 DIN connections, the PC VGA/SVGABvideo connection, and such. Almost all VAX systems pre-date these Cpinouts, and peripherals intended for the older Alpha systems also pre-date these pinouts.m

14.32 Changing processor (CPU) identification codes?



GThere are various common motherboards used in a series of VAX systems, Hand these have a selectable id value. The enclosure and options differ, Gbut the system boards are---save for the setting of the response---the !same within certain pairings.

d  / * &                      
Table 14-9 Shared/paired VAX Boards
MicroVAX 3100 series VAX 4000 series Part Number
 Model 90/KA50  Model 100/KA52  54-21797-01
 Model 95/KA51  Model 105/KA53  54-21797-02
 Model 96/KA54  Model 106/KA56  54-21797-03
 Model 98/KA57  Model 108/KA59  54-24695-01


GTo change the system identification within the pairings, use a console Dcommand specifying the target CPU identification. For instance, the Hfollowing command will set a 54-21797-01 series processor module to the KA50 response:

 

"
   >>> T 9D 50    confirm (y/n)? y 




CThese commands solely alter the identification returned within the Hspecified pairings. These commands do not alter the system performance, Gand the commands can not and do not allow, for instance, a 54-21797-01 0motherboard to become a 54-24695-01 motherboard.

fSee Section 14.14 for a more complete list of KA-series codes for various VAX processors.


V

Chapter 15
Information on Networks and Clusters


A

If you are searching for something here, please (consider using the text-format FAQ.



FThe following sections contain information on OpenVMS Networking with @IP and DECnet, and on clustering and volume shadowing, on Fibre 4Channel, and on related products and configurations.]

15.1 How to connect OpenVMS to a Modem?



FPlease see the Ask The Wizard area topics starting with (81), (1839), (2177), (3605), etc.



HFor additional information on the OpenVMS Ask The Wizard (ATW) area and Bfor a pointer to the available ATW Wizard.zip archive, please see iSection 3.8. ATW has been superceded (for new questions) by the ITRC <discussion forums; the area remains available for reference.V

15.2 OpenVMS and IP Networking?



=The following sections contain information on OpenVMS and IP *networking, as well as IP printing topics.J

15.2.1 How to connect OpenVMS to the Internet?



ESome tutorial information and tips for connecting OpenVMS systems to the Internet are available at:

A

15.2.2 Connecting to an IP Printer?



FTo connect a printer via the IP telnet or lpr/lpd protocols, you will Hneed to install and configure an IP stack on OpenVMS, and configure the appropriate print queue.

AWith current OpenVMS IP implementations, the choice of telnet or Glpr/lpd really amounts to determining which of these works better with the particular printer involved.

ETo support network printing, the printer must include an internal or externalE NIC or JetDirect; an adapter connecting the network and the printer.

EWhile it is normally possible to use a host-connected printer---when Fthe host supports an LPD or telnet daemon, and OpenVMS and most other Foperating systems have the ability to serve locally-attached printers Hto other hosts on the network---it is generally far easier and far more Heffective to use a printer that is directly attached to the network. If Dyour present printer does not have a NIC or a JetDirect, acquire an Einternal (if available) or external NIC or JetDirect. Or replace the Eprinter. And obviously, most any operating system that can serve its Elocal printers usually also provides a client that can access remote network-connected printers.

FPlease see the Ask The Wizard (ATW) area topics---starting with topic A(1020)---for additional information on IP-based network printing.



HFor additional information on the OpenVMS Ask The Wizard (ATW) area and Bfor a pointer to the available ATW Wizard.zip archive, please see iSection 3.8. ATW has been superceded (for new questions) by the ITRC <discussion forums; the area remains available for reference.

ePlease see Section 15.2.3 for information on Postscript printing.U

15.2.3 How do I connect a PostScript printer via TCP/IP?



CUsing TCP/IP Services (UCX) as the TCP/IP stack, it is possible to Cconfigure queues using the UCX$TELNETSYM (TCP/IP Services prior to DV5.0) or TCPIP$TELNETSYM (with V5.0 and later) in order to print to FPostscript printers. This assumes however that the printer itself can Dconvert whatever is passed to it into something intelligible. As an Fexample, if the printer has an IP address of 123.456.789.101 and jobs $should be passed to port 9100 then :

 

"
/$ INITIALIZE/QUEUE/ON="123.456.789.101:9100" -      /PROCESSOR=UCX$TELNETSYM  -     my_ip_queue 




 

"
/$ INITIALIZE/QUEUE/ON="123.456.789.101:9100" - "    /PROCESSOR=TCPIP$TELNETSYM  -     my_ip_queue 




DThe port number of 9100 is typical of HP JetDirect cards but may be (different for other manufacturers cards.

FAs a better alternative, DCPS Version 1.4 and later support IP queues Husing either HP TCP/IP Services for OpenVMS software or Process Software MultinetG for OpenVMS. The usage of this type of interface is documented in the D DCPS documentation or release notes, and the DCPS$STARTUP.TEMPLATE  startup template file.

EFor general and additional (non-Postscript) IP printing information, Bplease see topic (1020) and other topics referenced in that topic )elsewhere within the Ask The Wizard area.



HFor additional information on the OpenVMS Ask The Wizard (ATW) area and Bfor a pointer to the available ATW Wizard.zip archive, please see iSection 3.8. ATW has been superceded (for new questions) by the ITRC <discussion forums; the area remains available for reference. Also see:



nPlease see Section 15.2.2 for pointers to an introduction to IP printing.[

15.2.4 How do I set a default IP route or gateway on OpenVMS?



FIf you have TCP/IP Services, then use the command for TCP/IP Services V5.0 and later:

 

"
$ TCPIP )SET ROUTE/GATE=x.x.x.x/DEFAULT/PERMANENT 




:And for earlier TCP/IP Services versions, use the command:

 

"
$ UCX )SET ROUTE/GATE=x.x.x.x/DEFAULT/PERMANENT 


X

15.2.5 How can I set up reverse telnet (like reverse LAT)?



FThough it may seem obvious, Telnet and LAT are quite different---with (differing capabilities and design goals.

DPlease see the documentation around the TCP/IP Services for OpenVMS ETELNET command CREATE_SESSION. This command is the equivilent of the Eoperations performed in LTLOAD.COM or LAT$SYSTARTUP.COM. There is no GTELNET equivilent to the sys$qio[w] control interface for LTDRIVER (as Adocumented in the I/O User's Reference Manual) available, though Bstandard sys$qio[w] calls referencing the created TN device would likely operate as expected.




 r Y \ ^  
PreviousNextContentsIndex