     	  Software   Product  Description  D  ___________________________________________________________________  D  PRODUCT NAME:  DECserver 200 for VMS, Version 3.3      SPD 27.53.07    DESCRIPTION  H  The DECserver 200 Terminal Server is a network terminal switch for Eth-J  ernet Local Area Networks. The DECserver 200 provides a convenient methodG  to logically connect up to eight Digital asynchronous terminals to one H  or more service nodes (hosts) on an Ethernet. Once the terminal is con-D  nected, a user, with a few exceptions, can utilize application pro-F  grams and utilities as though the terminal were directly connected toD  a host via a DZ11, DMF32, or DHU11 device. Thus, it may be possibleG  to utilize the DECserver 200 to connect all terminals, except for host G  console terminals to service nodes in place of traditional interfaces. 9  Remote connection via dial-in modems is fully supported.   E  The DECserver 200 also allows for OpenVMS host-initiated connections F  to serial printers. A special print symbiont on OpenVMS service nodesG  can initiate connections to serial printers connected to DECserver 200 F  ports. This allows the printers to be distributed throughout a facil-E  ity and accessed transparently by service node users. Incoming host- F  initiated connect requests may be queued first in/first out (FIFO) at  the server.  D  The DECserver 200 also provides the capability to connect host sys-G  tems that do not support the LAT (Local Area Transport) protocol, Dig- F  ital personal computers, and dial-out modems directly to ports on theG  server. Interactive server users can issue commands to connect to ser- F  vices that are offered on such ports. Port-to-port connections on the   same server are also supported.        D                                DIGITAL                    April 1994  D                                                          AE-JC42H-TE       H  The DECserver 200 implements the Local Area Transport protocol for com-G  munication with service nodes that implement this protocol on the same G  Ethernet. This interface has been optimized for high terminal I/O per- F  formance over an Ethernet, while reducing host CPU cycles required toD  handle interrupts. Hence, under most I/O loading conditions, a sig-E  nificant performance gain may be realized by using the DECserver 200 .  versus direct terminal connections via DZ11s.  K  The DECserver 200 also implements and supports the Terminal Device/Session D  Management Protocol (TD/SMP) to manage multiple sessions at the de-G  vice level. The DECserver 200 provides the ability to communicate with F  devices that also implement this protocol, and assists in the manage-G  ment of multiple sessions for these devices. By implementing this pro- H  tocol, the DECserver 200 can permit attached devices to maintain screenG  and keyboard context for multiple LAT sessions, as well as allow these 3  devices to run multiple LAT sessions concurrently.   D  The DECserver 200 implements the ODL (On Demand Loading) font load-F  ing protocol which allows Asian terminals that implement the ODL pro-E  tocol to communicate with an OpenVMS host via a terminal server. The G  Asian terminals will be able to request font definitions from an Open- ,  VMS host when connected to a DECserver 200.  D  Software that runs on the DECserver 200 is downline loaded over theD  network from a Phase IV DECnet load host. Terminal access using theH  DECserver 200 does not require DECnet running in the same service node;F  LAT uses the Ethernet addressing mechanism to transport terminal mes-D  sages. The DECserver 200 server software will operate with all Dig-3  ital service nodes which support the LAT protocol.   G  Features such as login load balancing, multiple terminal sessions, au- F  tomatic failover, and remote printer support can lead to greater user  productivity.  D  For wide area network communications, terminal users can connect toD  a local service node running DECnet, where they can "SET HOST" to aE  remote system via the DECnet network terminal protocol. If this sys- H  tem has the requisite X.25 or SNA 3270 access routines, a terminal user    #                                   2        E  could communicate to a remote SNA or X.25 host through the appropri- E  ate gateway and this intervening host. A DECserver 200 terminal user F  cannot communicate directly to remote hosts through DECnet Routers orG  X.25/SNA Gateways. Wide area network traffic will not provide the same D  high level of performance as local terminal connections, due to the2  additional DECnet and Internet protocol overhead.  	  Features     Terminal Connection Management   H  Through the use of a simple command, users can establish a logical con-G  nection, called a session, to any service node that implements the LAT D  protocol on the same Ethernet LAN. This connection makes the termi-G  nal appear as if it were physically connected to the service node, and E  the terminal user can use standard system utilities and applications G  supported by that node. Each terminal connected to the server can con- G  nect to the same or a different service node on the Ethernet. Further- F  more, several servers can be used to connect many terminals to one or  more service nodes.  F  A service node can have one or more services that are offered to DEC-G  server 200 users. Services and nodes are identified by name. Users al- G  ways connect to services, not to nodes, although often one of the ser- "  vice names will be the node name.  D  In a VAXcluster environment, the DECserver 200 sees each VAXclusterH  on the Ethernet as a collection of service nodes offering a common ser-F  vice. Each cluster node may also offer a service whose name is equiv-F  alent to its node name. In this case, a terminal user can connect ei-D  ther to the cluster service or a service associated with a particu-  lar cluster node.    Non-LAT Host Support   F  The DECserver 200 can be used to provide logical terminal connectionsF  to hosts that do not implement the LAT protocol. In this type of con-D  figuration, the server becomes the Ethernet connection and protocolD  support for these hosts. This expands the LAT network accessibilityD  to the terminal user to include LAT hosts directly connected to the  #                                   3        G  same Ethernet and hosts connected to the LAT network via the DECserver   200.   F  A host that supports XON/XOFF, ASCII standards and EIA RS-232-C/CCITTF  V.24/V.28 interfaces can be connected to the DECserver 200. This pro-E  vides the terminal user with a transparent connection to the non-LAT D  host. It is strongly recommended that server port and the host sideD  port utilize modem control signals to automatically signal the host  upon session disconnection.  D  In this configuration, there is a one-to-one correspondence betweenG  the port on a DECserver 200 and the connection on the host. The server E  manager assigns service names to individual ports or groups of ports /  that connect the host interface to the server.     Load Balancing   E  When a connection is made to a service, the actual node for the con- E  nection is determined by load balancing. Load balancing is a process F  the server uses when more than one node offers the same service. Ser-G  vice nodes do not have to be configured in a cluster in order for load D  balancing to be used. Service nodes with the same names may be run-D  ning different operating systems. Using the load balancing process,E  the server connects to the node with the highest rating for the ser- G  vice desired. This rating is based on the current loading on the nodes   that offer the service.    Multiple Sessions  E  The DECserver 200 allows each user to establish and maintain up to 8 F  sessions to one or more service nodes, up to a maximum of 64 per DEC-G  server 200. Only one session per user can be active at a time. Through F  simple switching commands, the user can access the different sessionsG  without repeating a login dialog each time. Some operating systems may F  impose limits on the number of LAT sessions such a host will support.    Multiple Session Management      #                                   4        G  The DECserver 200 server allows direct communication with devices that D  support the TD/SMP protocol. This protocol provides the ability forD  the attached device to maintain screen and keyboard context for theF  multiple LAT sessions which the DECserver 200 provides. By implement-F  ing the ability to directly communicate with this protocol to the at-E  tached device, the DECserver 200 can now assist in the management of D  context of these multiple sessions, as well as allow for simultane-D  ous output to multiple LAT sessions being maintained by the device.    Outbound Connection Queues   H  If a terminal user requests a connection to a server, and the requestedG  service is currently in use, the terminal server users may opt to have D  the connection requested queued to the remote service. This featureD  will happen automatically whenever a connection fails for this rea-D  son, if the user's port has been appropriately configured. The con-I  nection request is queued at the service node end and is processed first E  in/first out until such time as the user's connection request can be G  completed. This feature assists in the fair management of limited net- F  work resources. Once queued for connection, the user also has the op-@  tion to cancel the queue entry and proceed with other sessions.    Welcome Identification   F  The DECserver 200 server standard welcome banner, which includes ter-D  minal server type, version number, internal baselevel, and protocolF  version number, is issued whenever a user successfully logs in to theE  server. The server will also print a server manager settable identi- E  fication string. This can be useful for automatic server identifica- G  tion, or for small daily messages used for communication with the ter-   minal server users.    Local Mode and Service Mode  D  For the most part, the environment provided by the DECserver 200 isD  identical to that the user would experience if attached directly toF  the service node. When operating in this mode, the user is said to beD  in Service Mode. Occasionally, such as during connection establish-E  ment, the user interacts directly with the DECserver 200. When oper- /  ating in this mode, the user is in Local Mode.   #                                   5        F  In Local Mode, the terminal input is interpreted directly by the DEC-E  server 200 as commands to be performed by the server. The local mode G  prompt can be modified by a privileged command and can be changed from :  LOCAL> to any printable characters (up to 16 characters).  H  Additional commands and displays to support the features available withE  the TD/SMP protocol are usable in Local Mode. These commands will be E  used to enable or disable server recognition of the TD/SMP commands.   E  Local Mode has three different levels of privilege: privileged, non- H  privileged, and secure. Privileged mode is provided for the Server Man-F  ager to control the environment of the server and the terminal users.F  Access to this mode is password protected. Nonprivileged commands al-E  low terminal users to control their service sessions, set their ter- D  minal characteristics, and show server information. The Server Man-F  ager can set the server to secure mode on a per-terminal basis, whichD  further limits the commands and displays of services and nodes thatF  users can enter to only those which directly relate to the user's own
  terminal.  F  The Server Manager environment is a logical extension of the user en-G  vironment. The Server Manager is treated as a server user with a priv- E  ileged status. The Server Manager sets a terminal to this status us- D  ing a command which requires a password. This privileged status al-D  lows the Server Manager to enter commands not normally available toF  server users. These commands set server characteristics, provide con-D  trol over server port usage, and provide the ability to control the2  user's access to the server and network services.  H  In Service Mode, the terminal input is passed directly to the connectedD  service node with several exceptions. One exception, called the lo-D  cal switch character, allows the user to enter Local Mode from Ser-G  vice Mode. The BREAK key may also be used for this function. Other ex- G  ceptions, called the forward and backward switch characters, allow the F  user to switch between sessions without the need to enter local mode.D  The switch characters are disabled by default but may be enabled byE  command. Both CTRL/S and CTRL/Q are normally interpreted locally but 5  flow control using these characters can be disabled.     #                                   6          Autoconnection   E  Autoconnection is a function that automatically connects a user ter- D  minal to a service node when connection failures occur or upon userD  login to the server. In conjunction with this function, a dedicated>  or preferred service can be specified for each terminal user.  D  If a dedicated service is specified, the DECserver 200 will attemptE  to connect to that service when a character is typed on the terminal D  keyboard or when an existing connection fails. In dedicated serviceF  mode, only one session is available. As this mode is designed to sim-G  ulate a direct terminal connection, no local mode commands or messages E  are available to the terminal user. Ports with dedicated service can D  be automatically logged out of the server when the user logs out of  the service node.  D  If a preferred service is specified, the DECserver 200 will attemptE  to connect to that service as with the dedicated service mode of op- D  eration. However, the terminal user can enter local mode and estab-  lish other sessions.     Automatic Session Failover   E  If a service is available on two or more service nodes and a connec- E  tion to a service fails, the server will attempt to connect the user E  to another service node offering the same service. The user does not D  have to be already connected to that service node. Furthermore, theD  user's context at the time of failure is not automatically restored*  and login to the new service is required.    Groups   D  Every terminal and service node in a LAT network is a member of oneH  or more groups, which are specified by a list of numbers from 0 to 255.D  Groups allow an easy means of subdividing the network into what ap-D  pears to be many smaller networks. A terminal user is only aware of=  the services that are offered by nodes in the same group(s).       #                                   7        G  The Server Manager can specify the authorized group(s) in which a ter- D  minal is a member. The authorized groups define the set of servicesD  that the user is allowed to access. In addition, a user can furtherG  restrict access to services by disabling some of the authorized groups G  using a nonprivileged group command. The user-settable group codes are #  a subset of the authorized groups.   G  Groups provide a restrictive view of the network. This restricted view E  is mainly for user convenience and, although it also provides a form E  of security, it is not intended to be the primary form of access au- +  thorization or system security for a node.   	  Security   D  The DECserver 200 provides functions that enhance security featuresH  already available in the service nodes. DECserver 200 security includesE  the ability to lock a terminal's keyboard from other users, optional E  login protection, and nonprivileged local mode of operation as a de-   fault.   D  A user may lock the terminal using a lock password. This allows theE  user to leave sessions running at the terminal without fear of secu- D  rity violations. When a terminal is locked, all input from the ter-E  minal is ignored until the lock password is reentered. The lock fea- ,  ture may be disabled by the Server Manager.  H  Each terminal port can be set to operate in a secure mode, which causesF  all commands that relate to other users to be disabled for that port.  F  Login passwords can be enabled on a per-line basis by the Server Man-G  ager. If enabled, the terminal user must enter a login password to ac-_  cess server functions.   D  DECserver 200 users normally have access to the nonprivileged localD  mode. In this mode, users may only issue commands that affect theirF  own terminal environment. The server has a privileged mode for server/  manager's use. The mode is password protected.     Online HELP Facility   #                                   8  E  r  F  A full online reference HELP facility is available. The server's HELPE  command provides information on the correct syntax and details about D  each command. In addition, a tutorial HELP feature allows new usersF  to quickly learn the basics of DECserver 200 operation. Tutorial HELP-  may be entered upon logging into the server.s    Directory Service  D  Any DECserver 200 user can obtain a directory of services availableG  to that user with a SHOW SERVICES command. Services for which the usern)  is not authorized will not be displayed.A    Permanent Characteristics  E  The DECserver 200 maintains permanent characteristics in nonvolatiledE  memory which is retained even when the power is disconnected. Perma-tF  nent characteristics are maintained for service and server parametersE  as well as per-port parameters. Permanent characteristics can be re-fE  set to factory defaults by pressing the software reset button on thee0  hardware unit while plugging in the power cord.  #  Port Characteristics Configuration)  E  Characteristics governing the operation of an individual port can betH  displayed by nonprivileged terminal users interactively from their ter-G  minal. Many of the characteristics may be set up by the user, but cer-cJ  tain characteristics are privileged and may only be changed by the Server	  Manager.D  E  Port parameters that can be set and displayed include speed, charac- D  ter size, group codes, parity, terminal type, access, autobaud, mo-  dem, and password protection.    Port Access  D  A port on a DECserver 200 may be set up in different ways dependingG  on the device attached to the port and its intended use. DECserver 200rD  supports EIA-RS-232-C and DECconnect asynchronous devices operating  at speeds up to 19.2K bps.c  #                                   9  -  n  E  Port access is the characteristic that determines how a port may ac-r<  cess or be accessed by interactive users and service nodes.  D  o  Access Local-Designed for interactive terminals. This allows theF     device (typically an interactive terminal) attached to the port toG     CONNECT to LAT services. This type of access is also used for dial-a     in modems.  H  o  Access Remote-Designed for applications-driven devices such as asyn-D     chronous printers which are allocated by a service node process.E     This allows the implementation of certain shared printers by mul- E     tiple service nodes. This type of access is also used for connec-e7     tions to dial-out modems, and non-LAT host systems.e  E  o  Access Dynamic-Designed for devices such as personal computers oriG     printers with keyboards which require both Local and Remote access.p  G  o  Access None-Designed to allow the Server Manager to disable the useq     of a port.  H  With printer support capabilities, the setup procedure of remote print-D  ers needs to be done once and is automatically reconfigured on sys-F  tem startup. The particular server port must be configured for remoteH  access and set up to match the characteristics of the printer. The sys-H  tem startup command file must be modified to call the two command filesD  provided with the service node software. Finally, the command filesH  themselves must be customized to reflect the environment of their node.G  The server can optionally queue remote connects if these connects can-tG  not be satisfied immediately. This queue management can be enabled forrG  the server by the Server Manager. Note that this is a connection queuee  only.    Terminal Operationy  E  The DECserver 200 software supports the simultaneous operation of upoF  to eight asynchronous devices at speeds from 75 bps to 19.2K bps. The  software also supports:  6  o  Full modem control support (DECserver 200/MC only)    o  Data leads only support5  #                                  10w a  t    o  XON/XOFF flow controlr  <  o  CTS/RTS and DSR/DTR flow control (DECserver 200/MC only)  9  o  Split speed (transmit and receive) terminal operation   3  o  Modem fallback features (DECserver 200/MC only)     o  Block Mode transfers  "  o  Automatic line speed detection  +  o  Digital personal computer file transferF    o  Data transparency mode  :  o  Ability to pass break character and error notification  ?  o  Ability to assist in multiple session management via TD/SMPr    Server Management  E  Several facilities exist for managing and troubleshooting server op-hG  eration. The Server Manager in privileged mode can set up server iden-oF  tification information, change port characteristics, or fine tune theE  operating characteristics of the server. The Server Manager can alsorG  assign service names to groups of one or more ports that are connected.E  to non-LAT hosts or modems. Troubleshooting facilities include diag-s?  nostic tests, a remote console feature, and online statistics.o  I  A privileged user can diagnose Ethernet communications problems by loop-eG  ing messages to an Ethernet host and through the Ethernet hardware in-oD  terface at the server. To diagnose terminal problems, users can ex-G  ecute a command to transmit test data to their terminal, or the serverr,  manager can send test data to any terminal.  D  The capability also exists for the Server Manager to test a serviceH  connection by sending data from the initiating port to the service nodeD  and back again. The data is then compared and any discrepancies re-D  ported. At the service node, the data can be looped back by the LATE  protocol, or internally or externally at the service port. This fea-tD  ture is supported only by DECserver 200 service nodes; OpenVMS ser-<  vice nodes do not support this service loopback capability.  #                                  11s h  e  D  The server maintains a variety of statistics and counters includingE  Ethernet data link statistics, LAT protocol statistics, and port er- E  ror statistics. These data can be displayed and zeroed by the Server F  Manager. Server parameters that can be modified and displayed includeD  the server identification, circuit timer, session limits, and login  limits.    Remote Server Managementt  D  The DECserver 200 implements the console carrier feature, which en-D  ables access to the DECserver 200 local mode from a Phase IV DECnetE  host on the same LAN. With the exception of remote console port con- F  figuration, the entire local mode user interface is accessible to theD  remote console carrier user. This includes the privileged commands,D  if the user knows the server's privileged password. This capabilityB  allows centralized server management and remote server diagnosis.    Communicationsn  G  DECserver 200 software is designed to run exclusively on DECserver 200 G  hardware that includes an Ethernet interface for connection to an Eth-   ernet transceiver cable.t  D  The DECserver 200/MC has eight EIA RS-232-C/CCITT V.24 asynchronous6  line interfaces for connecting terminals to the unit.  H  The DECserver 200/DL has a single 36-pin DECconnect connector for eight  ports.   F  On the DECserver 200/MC, each port on the server can be set up by theD  Server Manager to operate using full-duplex modem control. The DEC-E  server 200/MC is compatible with Digital's family of modems and with F  Bell 100 and 200 series modems and their equivalents. A BREAK featureF  is available and can be set on a per-port basis. This allows the DEC-D  server 200/MC to force a break condition on connections to host in-E  terfaces. BREAK can also be passed through from a terminal connectedc;  on the server to the non-LAT host connected on the server.     DECserver 200 Operation  #                                  12r       D  The DECserver 200 ROM-based firmware provides the necessary mainte-F  nance operation protocols for downline loading DECserver 200 softwareD  from a Phase IV DECnet load host over the Ethernet into server mem-G  ory. All self-test diagnostics are in DECserver ROM, so downline load-tE  ing is not a precondition for DECserver self-test. In the event of awD  bugcheck caused by a fatal error, the unit will normally attempt toE  upline dump server memory to a DECnet Phase IV host. Following this,ED  the unit will automatically initialize itself and invoke a downline  load.  ,  DECserver 200 Configuration and Performance  J  The process of configuring the DECserver 200 is based primarily on trade-E  offs of cost and performance within the realm of satisfying user ap-eH  plication requirements. Network applications will range from low-speed,D  low-cost situations (e.g., connecting remote terminals through low-F  speed modems) to those of relatively high performance (e.g., connect-G  ing high-speed local terminals to local hosts within a local area net-gJ  work or connecting to non-LAT systems). The performance of a given serverD  is a function of the expected network traffic, the load on hosts toD  which terminals are connected, and resultant processing pursuant toF  the dedicated function of the unit. Thus, performance depends on sev-  eral factors:    o  Number of terminalsu  @  o  Number of host systems with active connections to the server  1  o  Number of active connections to non-LAT hostse    o  Terminal speeds     o  Terminal user applications  #  o  Number and size of host buffersr    o  Terminal workloade  D  The DECserver can sustain an aggregate character throughput of overF  11520 characters per second. This is equivalent to running four ports$  at 19200 bps, and four at 9600 bps.  #                                  13u       D  In order to achieve a viable configuration, the user and/or a Digi-D  tal software specialist should perform a level of application anal-H  ysis that addresses the factors above. The actual maximum data through-H  put cannot be calculated by multiplying the number of lines by the lineD  speed, since many factors already discussed in this section may re-  duce the actual throughput.  $  Restrictions on DECserver 200 Usage  F  While terminal connections using the DECserver 200 have been designedH  to simulate direct terminal connections as much as possible, a few dif-E  ferences necessarily exist because of the nature of the product. Un-eD  der most circumstances, these differences are not noticed by termi-F  nal users or service node application programs. However, applicationsD  which are directly dependent on the following functions may not op-#  erate as with a direct connection:T  F  o  Applications that depend on reading or setting the terminal speed,E     character size, and parity by manipulating system data structuresl  E  o  Applications that depend on an extremely fast response time (typ-e'     ically less than 200 ms) to operated  F  o  Applications that utilize an alternate terminal driver in the ser-
     vice nodes  F  o  Applications that expect incoming connections to have fixed device	     namesr    Other DECserver 200 Systems  E  Refer to the following Software Product Descriptions for informationn*  on other supported DECserver 200 systems:  ?  o  DECserver 200 for RSX-11M-PLUS and Micro/RSX (SPD 15.72.xx)m  +  o  DECserver 200 for ULTRIX (SPD 27.54.xx)o      #                                  14i d  c    HARDWARE REQUIREMENTS    Processors Supportedr  /  Alpha AXP:  DEC 2000 Model 300 AXP Workstationh*              DEC 2000 Model 300 AXP Server/              DEC 3000 Model 300 AXP Workstation *              DEC 3000 Model 300 AXP Server/              DEC 3000 Model 400 AXP Workstation *              DEC 3000 Model 400 AXP Server/              DEC 3000 Model 500 AXP Workstationl*              DEC 3000 Model 500 AXP Server/              DEC 3000 Model 600 AXP Workstation *              DEC 3000 Model 600 AXP Server/              DEC 3000 Model 800 AXP Workstationa  *              DEC 4000 Model 610 AXP System  *              DEC 7000 Model 610 AXP System  +              DEC 10000 Model 610 AXP Systeme    VAX:      VAXft Model 110,l            VAXft Model 310,             VAXft Model 410,             VAXft Model 610,e            VAXft Model 612              VAX 4000 Model 100,            VAX 4000 Model 200,            VAX 4000 Model 300,            VAX 4000 Model 400,            VAX 4000 Model 500,            VAX 4000 Model 600e  %            VAX 6000 Model 200 Series,y%            VAX 6000 Model 300 Series,n      #                                  15t    n    %            VAX 6000 Model 400 Series, %            VAX 6000 Model 500 Series, $            VAX 6000 Model 600 Series  $            VAX 7000 Model 600 Series  (            VAX 8200, VAX 8250, VAX 8300,(            VAX 8350, VAX 8500, VAX 8530,(            VAX 8550, VAX 8600, VAX 8650,(            VAX 8700, VAX 8800, VAX 8810,'            VAX 8820, VAX 8830, VAX 8840m              VAX 9000 Model 110,            VAX 9000 Model 210,%            VAX 9000 Model 300 Series,e$            VAX 9000 Model 400 Series  %            VAX 10000 Model 600 Series   "            VAX-11/730, VAX-11/750,!            VAX-11/780, VAX-11/785b  &  MicroVAX: MicroVAX II, MicroVAX 2000,&            MicroVAX 3100 Model 10/10E,&            MicroVAX 3100 Model 20/20E,"            MicroVAX 3100 Model 30,"            MicroVAX 3100 Model 40,"            MicroVAX 3100 Model 80,"            MicroVAX 3100 Model 90,(            MicroVAX 3300, MicroVAX 3400,(            MicroVAX 3500, MicroVAX 3600,'            MicroVAX 3800, MicroVAX 3900a              #                                  16r a  s    +  VAXstation:VAXstation II, VAXstation 2000,e$            VAXstation 3100 Model 30,$            VAXstation 3100 Model 38,$            VAXstation 3100 Model 40,$            VAXstation 3100 Model 48,$            VAXstation 3100 Model 76,,            VAXstation 3200, VAXstation 3500,+            VAXstation 3520, VAXstation 3540o  $            VAXstation 4000 Model 60,$            VAXstation 4000 Model 90,            VAXstation 4000 VLC  (  VAXserver: VAXserver 3100 Model 10/10E,'            VAXserver 3100 Model 20/20E, :            VAXserver 3300, VAXserver 3400, VAXserver 3500,:            VAXserver 3600, VAXserver 3602, VAXserver 3800,            VAXserver 3900e  $            VAXserver 4000 Model 200,$            VAXserver 4000 Model 300,#            VAXserver 4000 Model 500   $            VAXserver 6000 Model 210,$            VAXserver 6000 Model 220,$            VAXserver 6000 Model 310,$            VAXserver 6000 Model 320,$            VAXserver 6000 Model 410,$            VAXserver 6000 Model 420,$            VAXserver 6000 Model 510,$            VAXserver 6000 Model 520,$            VAXserver 6000 Model 610,$            VAXserver 6000 Model 620,#            VAXserver 6000 Model 630r    Processors Not Supporteds  B  MicroVAX I, VAXstation I, VAX-11/725, VAX-11/782, VAXstation 8000  #                                  17h e  r    Processor Restrictionsi  E  A TK50 Tape Drive is required for standalone MicroVAX 2000 and VAXs-   tation 2000 systems.e  G  The DECserver 200 software runs on any of the following packaged hard-   ware options:    o  DSRVB-**  E  ** Denotes product variant models. For additional information, refera"     to the appropriate price book.  F  Use the following SHIELDED cables with each of the physical lines de-B  pending on the connection required beyond the cable concentrator:  A  BC22D     Null modem cable for local terminal or printer connec-r            tions.p  C  BC22E     Full modem straight through cable for modem connections.a  C  BC22F     Full modem straight through cable for modem connections.a  B  BC22R     Recommended null modem cable for host systems and otherB            devices, including those that use CTS/RTS flow control.  C  BC17D     Null modem cable for host systems and other devices that +            do not use CTS/RTS flow control.e    OPTIONAL HARDWARE    Terminals Supported  G  The DECserver 200 software supports the following Digital terminal de-b  vices that have keyboards:n     o  LA12, LA34, LA35, LA36, LA38    o  All VTxxx terminalse  #  Supported terminal parameters are:t  -  o  Character size: 7 or 8 bits per characters  #                                  18e    n    o  Parity: Even, Odd, or None  G  The automatic line speed detection (Autobaud) feature is supported foreE  either 7-bit characters with even parity or 8-bit characters with no   parity.  D  The DECserver 200 software also supports Digital Asian terminal de-E  vice variants when accessed from OpenVMS/Hanzi systems. Please refer D  to the appropriate OpenVMS/Hanzi Software Product Description for a'  complete listing of supported devices.e  D  The DECserver 200 software also supports Digital Asian terminal de-F  vice variants when accessed from OpenVMS/Japanese systems. Please re-E  fer to the appropriate OpenVMS/Japanese Software Product Descriptiond-  for a complete listing of supported devices.z  D  The DECserver 200 software also supports the following Digital Per-F  sonal Computers (PCs) in both terminal emulation mode and file trans-
  fer mode:    o  Professional 325, 350, 380  !  o  Rainbow 100A, 100B, 100+, 190r    o  DECmate II    o  DECmate IIIa    o  VAXmatee    o  DECstation  H  Note: This product is NOT WARRANTED to support non-Digital terminal de-E  vices or personal computers. However, terminals supporting VT100- ornD  VT200-like characteristics and personal computers supporting IBM[R]E  PC, IBM PC/XT and IBM PC/AT[R] characteristics may operate with thisl	  product.p    Printers Supporteds  #                                  19  y     G  The DECserver 200 software supports the following Digital asynchronoust-  printers when accessed from OpenVMS systems:h  ;  o  All LJ, LA, LQP, LXY, LN0, LG, and DTC printing devicess  F  The DECserver 200 software also supports Digital Asian printer deviceG  variants when accessed from OpenVMS/Hanzi systems. Please refer to thesF  appropriate OpenVMS/Hanzi Software Product Description for a complete  listing of supported devices.  F  The DECserver 200 software also supports Digital Asian printer deviceF  variants when accessed from OpenVMS/Japanese systems. Please refer toD  the appropriate OpenVMS/Japanese Software Product Description for a'  complete listing of supported devices.a    Modems Supportedc    For DECserver 200/MC:  D  o  DF03, DF112, DF124, DF224, DF242, DFM X.29 pad, and DECmodem V32G     full-duplex asynchronous modems for either dial-in or dial-out use.cF     Also supported are private or leased line modem applications, how-D     ever, connections to data switches are NOT WARRANTED but may op-     erate with this product.  1  Disk Space Requirements (Block Cluster Size= 1):e  &  Disk space required for    900 blocks  installation:  *                             (435.2K bytes)  &  Disk space required for    764 blocks  use (permanent):o  *                             (391.7K bytes)  H  These counts refer to the disk space required on the downline load hostF  system disk. The sizes are approximate; actual sizes may vary depend-F  ing on the user's system environment, configuration, and software op-  tions.a  #                                  20r e  u    CLUSTER ENVIRONMENT  D  This layered product is fully supported when installed on any validG  and licensed VAXcluster* configuration without restrictions. The HARD-mF  WARE REQUIREMENTS section of this Software Product Description detail/  any special hardware required by this product.a  D  *  V5.x - V6.x VAXcluster configurations are fully described in theF     VAXcluster Software Product Description (29.78.xx) and include CI,4     Ethernet, and Mixed Interconnect configurations.    SOFTWARE REQUIREMENTS  %  o  OpenVMS AXP Operating System V1.5s    o  DECnet for OpenVMS AXP V1.5l     or  ,  o  OpenVMS VAX Operating System V4.7 - V6.0    o  DECnet-VAX V4.7 - V6.0    OpenVMS Tailoring  F  For OpenVMS V5.x -V6.x systems, the following OpenVMS classes are re-7  quired for full functionality of this layered product:n    o  OpenVMS Required Saveset    o  Network Supporte  
  o  Utilitiess  D  For more information on OpenVMS classes and tailoring, refer to theJ  OpenVMS VAX Operating System Software Product Description (SPD 25.01.xx).    OPTIONAL SOFTWARE     o  Terminal Server Manager V2.0  #                                  21o p       GROWTH CONSIDERATIONS  E  The minimum hardware/software requirements for any future version ofnD  this product may be different from the requirements for the current	  version.i    DISTRIBUTION MEDIAi  .  TK50 Streaming Tape, 9-track 1600 BPI Magtape    ORDERING INFORMATIONr    Software Licenses: QL-VCBA*-**   Software Media: QA-VCBA*-H*$  Software Documentation: QA-VCBAA-GZ'  Software Product Services: QT-VCBA*-**s(  LAT Networks Concept Guide: AA-LD84B-TK  G  *  Denotes variant fields. For additional information on available li-nD     censes, services, and media refer to the appropriate price book.    SOFTWARE LICENSINGt  F  This software is furnished only under a license. For more informationF  about Digital's licensing terms and policies, contact your local Dig-
  ital office.b  I  The DECserver 200 software license applies to the DECserver 200 on which,D  the server software runs, not to service host node CPUs in the net-  work.  F  This product does not provide support for the OpenVMS License Manage-E  ment Facility. A Product Authorization Key (PAK) is not required forp4  installation or use of this version of the product.            #                                  22g c  s    SOFTWARE PRODUCT SERVICES  F  A variety of service options are available from Digital. For more in--  formation contact your local Digital office.     SOFTWARE WARRANTY  H  Warranty for this software product is provided by Digital with the pur-G  chase of a license for the product as defined in the Software Warrantyo  Addendum of this SPD.  G  The above information is valid at time of release. Please contact yourv:  local Digital office for the most up-to-date information.  ;   1994 Digital Equipment Corporation. All rights reserved.   C  [R] IBM and AT are registered trademarks of International Businessn     Machines Corporation.r  <  [TM]The DIGITAL Logo, CI, DECconnect, DECmate, DECnet, DEC-C     server, DECstation, LA, LAT, LXY, Micro/RSX, MicroVAX, OpenVMS,eC     RSX-11M-PLUS, TK, ULTRIX, VAX, VAXft, VAXmate, VAXserver, VAXs-c>     tation, VMS, and VT100 are trademarks of Digital Equipment     Corporation.                                #                                  23 