IBM OS/2 LAN Server 3.0 Product Overview
Reprint Courtesy of International Business Machines Corporation, © International Business Machines Corporation
- 1 Preface
- 2 1.0 Introduction
- 3 2.0 IBM OS/2 LAN Server Version 3.0
- 3.1 2.1 Technical Update
- 3.2 2.1 Technical Update
- 3.3 2.3 New Features Common to Entry and Advanced
- 3.3.1 2.3.1 Network Transport Services/2
- 3.3.2 2.3.2 Redirected Installation enablement
- 3.3.3 2.3.3 Peer Service
- 3.3.4 2.3.4 Optional Client Full-Screen Interface
- 3.3.5 2.3.5 System Management
- 3.3.6 220.127.116.11 First Failure Support Technology/2* (FFST/2)*
- 3.3.7 18.104.22.168 Performance Hooks to Support PERFVIEW
- 3.3.8 22.214.171.124 Softcopy Publications
- 3.3.9 126.96.36.199 SNAP DUMP Facility
- 3.3.10 188.8.131.52 All Domain Control Database (DCDB) Access via Remote API
- 3.3.11 2.3.6 DOS LAN Requester Virtual DOS LAN API Support
- 3.3.12 2.3.7 DOS LAN Requester Support of DOS 5.0 Task Switching
- 3.3.13 2.3.8 TCP/IP Coexistence
- 3.4 2.4 Features Unique to the Advanced Server
- 4 3.0 Standard Features
- 4.1 3.1 Administration
- 4.2 3.2 Installation
- 4.3 3.3 Security
- 4.4 3.4 Fault Tolerance
- 4.5 3.5 DOS Requester Functions
- 4.6 3.6 Application Coexistence
- 5 4.0 Machine Requirements
- 5.1 4.1 LAN Server 3.0 - Entry or LAN Server 3.0- Advanced
- 5.2 4.2 OS/2 LAN Requester
- 5.3 4.3 DOS LAN Requester
- 5.4 4.4 OEM Systems
- 5.5 4.5 OS/2 LAN Server for Macintosh Version 1.0
- 5.6 4.6 Hardware Adapter Support
- 6 5.0 Migration Considerations
- 7 6.0 Product Direction
- 8 Notices
This document provides information concerning the latest version of IBM* OS/2* LAN Server from the Personal Software Products organization in Austin, Texas USA. The Technical Update section covers items to be announced in this release of the product.
This release of IBM OS/2 LAN Server Version 3.0 delivers functions and features that have been gathered from customers, industry experts, and shaped by keen competition in the LAN industry. This release confirms IBM's commitment to be the leader in LAN systems. IBM OS/2 LAN Server Version 3.0 is the first LAN system to exploit the power of OS/2 2.0 and take advantage of the evolving processor technology. With this release IBM becomes the industry leader in network operating system (NOS) performance on DOS, Windows**, and OS/2.
The Austin Personal Software Products organization has been involved with LAN systems from the PC LAN Program (PCLP) to LAN Server 3.0. IBM has the technology, skills, and strategy required to provide world class LAN solutions that fit users' needs today and guarantee their investment in the future.
IBM OS/2 LAN Server Version 3.0 is the first network server product to fully exploit the power of OS/2 2.0. With the advent of OS/2 2.0, the client-server model of networked workstations changed dramatically. OS/2 2.0 provides a true preemptive multiprocessing environment that benefits both client and server. No longer are you limited to a single client on a workstation, a dedicated server, or fragile communications. On top of this solid base is a user interface that allows transparent network access - no more groping on that foreign command-line interface.
When combined with Extended Services for OS/2* (Communications Manager and Database Manager), IBM OS/2 LAN Server Version 3.0 provides the most comprehensive integrated network solution in the industry. Allowing a single workstation to access a wealth of resources including files, printers, serial devices, applications, relational databases, and communications with the largest of mainframes. At the same time, while operating flawlessly with IBM solutions, IBM OS/2 LAN Server Version 3.0 provides interoperability with industry solutions (Novell NetWare**, Microsoft LAN Manager**, Bayan VINES**, and Artisoft Lantastic**).
IBM OS/2 LAN Server Version 3.0 release is available in two separate packages. The Entry server is a price competitive offering that includes new system management features and redirected installation support. This version is an ideal choice if you are just entering the world of networking. The next step is the Advanced server. It contains all the features available in the Entry server, plus the 386 high performance file system and enhanced Fault Tolerance. The Advanced server provides industry performance leadership, rated highly overall in a recent LANQuest survey (LAN Server, NetWare and LAN Manager, Performance Benchmark Comparison, LANQuest, June 1992). The fault tolerance capabilities provide comprehensive protection for mission-critical applications and data.
IBM OS/2 LAN Server Version 3.0 is a single byte character set (SBCS) / double byte character set (DBCS) converged product. That means there is a single source and single object code for the worldwide product. This allows rapid delivery of the product throughout the world and delivers the strongest national language support in the server business. National Language Versions (NLVs) of IBM OS/2 LAN Server Version 3.0 are provided to support the user's native language.
Note: When the term DBCS is used in this document, the intent is to address the DBCS considerations of the product in the Japanese (Japan), traditional Chinese (Taiwan), and the Korean (Korea) versions of the product.
2.0 IBM OS/2 LAN Server Version 3.0
2.1 Technical Update
The following new features are included in both the Entry and Advanced versions: NTS/2, Enhanced multi-adapter, Redirected installation enablement, Full domain control database API, Peer service, Optional client full-screen interface, and OS/2 TCP/IP coexistence.
The Advanced server product now running on the OS/2 2.0 base, provides the benefits of the 386 high performance file system, includes improved disk fault tolerance, and, combined with the IBM PS/2* Server 295, provides an asymmetrical multiprocessing environment.
Available with OS/2 LAN Server Version 3.0 are the DOS LAN Requester (DLR) and the OS/2 Requester. DOS LAN Requester and the IBM LAN Support Program Version 1.31, offer significant performance improvements over the previous DOS LAN Requester. The OS/2 Requester has been enabled for redirected installation and has numerous performance improvements.
Both DOS LAN Requester (DLR) and OS/2 Requester are available separately as Distributed Features. Distributed Features allow the purchase of a client license without regard to the number of of servers accessed and purchase of the exact number of licenses required. A distributed feature only provides the license to copy the client in your LAN Server package, no additional diskettes or publications are provided.
OS/2 LAN Server for Macintosh** Version 1.0 broadens the scope of support for the IBM OS/2 LAN Server product. With LAN Server for Macintosh, DOS, OS/2 and Mac clients can access files created by each other. LAN Server for Macintosh will provide the AppleTalk** File Server, Print Server functions, and Macintosh Print Monitor (over Token-Ring or Ethernet), which may be integrated into the OS/2 LAN Server environment.
2.1 Technical Update
OS/2 LAN Server Version 3.0 Entry and Advanced share numerous new features over previous versions of OS/2 LAN Server. These features are as follows:
- Network Transport Services/2
- Redirected installation enabled
- Peer service
- Enhanced multi-adapter support
- Optional client full-screen interface
- System management enhancements
- DOS LAN Requester Virtual DOS LAN API support
- DOS LAN Requester Support of DOS 5.0 task switching
- DOS LAN Requester Windows DBCS-enabled user interface
- DOS LAN Requester performance enhancements
- TCP/IP coexistence
OS/2 LAN Server Version 3.0-Advanced has the following unique features
- 386 high performance file system
- Supports greater than 16MB of memory
- Improved disk fault tolerance (mirroring and duplexing)
- Remirror without format
- Mirror of the boot drive
- Local security
2.3 New Features Common to Entry and Advanced
2.3.1 Network Transport Services/2
NTS/2 is an IBM product that provides network support for IBM 1.3 and IBM OS/2 2.0 operating systems and is included with IBM OS/2 LAN Server Version 3.0. The network support is based on the NDIS 2.01 specification. This product supplies the NETBIOS and IEEE 802.2, protocol NETBIOS VDD, and many network adapter drivers to support, networking applications. In addition to NETBIOS and 802.2 protocol support two additional features, which were not previously available, are supplied. This includes Novell ODI interface support and 802.2 VDD support. By supplying the ODI compatible protocol, Novell requesters, can be integrated on a hardware platform giving the Novell requester, the IBM LAN requester, and other applications the ability to share adapters with no difficulty.
802.2 VDD support eliminates the need for a dedicated network adapter for 802.2 DOS and Windows applications. This support allows sharing of adapters between 802.2 DOS and Windows applications, DOS and Windows NETBIOS applications, and OS/2 2.0 networking applications.
Other features of NTS/2 include a configuration utility, enhanced multi-adapter support, and remote installation support.
The configuration utility, called LAN Adapter and Protocol Support, (LAPS) has a simple-to-use Presentation Manager interface to aid in the configuration of adapters and protocols. The LAPS eliminates the need for manual, update of the PROTOCOL.INI and CONFIG.SYS files.
The LAN Configuration Installation Distribution Utility (LAN CID Utility) provides for the redirected (network) installation of OS/2 2.0, Extended Services, OS/2 LAN Server, and other applications. The redirected installation supports unattended modes for installation and configuration.
The enhanced multi-adapter support, when combined with the support in IBM OS/2 LAN Server Version 3.0, enables up to 1016 LAN Requesters to connect to a LAN Server across multiple adapters.
2.3.2 Redirected Installation enablement
The IBM OS/2 LAN Server Version 3.0 product makes possible the installation of requesters and servers in a remote and unattended manner. Remote installation is a form of redirected installation which supports the loading of code on workstations over the LAN from a designated code server. The code server can use the existing transport or can use the Service Installable File System (SRVIFS) provided by Network Transport Services/2 and can be either an OS/2 LAN Server or an OS/2 workstation with a Server Installable File System (SRVIFS). This second option can be achieved by installing:
- NetView Distribution Manager/2 Version 2.0, which provides the unattended installation of OS/2 and DOS system and application software on standalone and host-connected LANs. In host connected LANs, when used with NetView Distribution Manager for MVS, the distribution and installation can be initiated from the host.
- Network Transport Services/2, which provides the lightly attended installation of OS/2 software on the LAN.
2.3.3 Peer Service
The Peer service feature gives a requester some of the capabilities of a server. This feature may be used with the server or in a standalone environment.
Once the Peer service is running, use of requester resources is no longer limited to the owner of the requester. The owner can create shares for the requester, just as a network administrator creates shares for a server. Other users can NET USE the peer server resources just as with a full server (the peer server name is the same as the requester name). The server code is not required to be present on the requester to benefit from the Peer service function.
The Peer service allows the owner to share directories, one printer, and one communication-device queue with other users on the network. It lets one user at a time connect to (that is, create a session with) the peer server. This differs from an OS/2 LAN Server, which allows sessions with multiple requesters. Peer named pipes are also supported, but are not limited to a single session.
The NET SESSION command has been enhanced to allow users to see who is connected to a server. This allows a user who is denied access to a peer server because of the session limit to find out who is currently connected to the peer server.
2.3.4 Optional Client Full-Screen Interface
Often, workstations are used by general users who have no need to perform server administrator tasks. In this case, there is no need for users to install the LAN Requester full screen interface (FSI) on the hard disk. These users may load the full-screen interface from a server. This allows the users to conserve approximately 2.5MB of disk space on their workstation.
2.3.5 System Management
184.108.40.206 First Failure Support Technology/2* (FFST/2)*
FFST/2 provides superior and consistent RAS functions to the customer. In the event of an error, error data can be captured and reported.
The intent is to migrate the current detection points to FFST/2. OS/2 LAN Server 3.0 contains software detection points that interrogate return codes, and if an error condition is indicated, an entry is made in the LAN error log. The code has been modified so each current detection point will write the error information into an FFST/2 structured error log. This enables LAN Server to comply with the standard IBM RAS structure.
220.127.116.11 Performance Hooks to Support PERFVIEW
OS/2 2.0 supports an architected performance hook technology and collection mechanism known as "Perfview". The Perfview performance hook types consist of counters, timers, and queues. A set of APIs are supported that allow applications, device drivers, and file system drivers to register information with the kernel. System Performance Monitor/2 (SPM/2) relies on this capability to monitor and manage system performance. This allows the administrator to tune a LAN system.
18.104.22.168 Softcopy Publications
The publications for IBM OS/2 LAN Server Version 3.0 are offered separately in displayable softcopy form. The files are shipped on the same media type as the basic machine-readable material.
These displayable manuals can be used with the BookManager* READ licensed programs in any of the supported environments.
22.214.171.124 SNAP DUMP Facility
The SNAP DUMP facility enables a customer having a software problem to easily capture all the related information requested by the support personnel. This information is typically dispersed throughout the system and require. Many steps to capture completely. A generic ASCII file will define what should be dumped and allow the system data to be captured in a single file.
126.96.36.199 All Domain Control Database (DCDB) Access via Remote API
This API allows application developers to use published interfaces to manipulate user information on the domain Controller. This API simplifies the migration of OS/2 LAN Server into the Distributed Computing Environment (DCE). It also allows application developers to create system management tools.
2.3.6 DOS LAN Requester Virtual DOS LAN API Support
The DOS LAN Requester Virtual DOS LAN API Support enables DOS applications running in the Virtual DOS Machine environments of OS/2 2.0 (including WIN-OS/2)* to call the LAN APIs without having to load the DOS LAN Requester code.
2.3.7 DOS LAN Requester Support of DOS 5.0 Task Switching
One of the features of the IBM DOS Shell is the ability to run two or more application programs at one time. A limited (Suspend/Resume) application task switcher called Task Swapper is provided in the shell, which allows the customer to switch from one application to another without closing applications. DOS LAN Requester supports this application task-swapping.
The Active Task List displays the names of programs that have been started. Programs are added to the Active Task List by starting the program from the IBM DOS Shell. Switching to active programs is done through the Active Task List or by cycling through the programs in the Active Task List using the ALT and TAB keys. To remove a program from the Active Task List, the user must exit the program.
2.3.8 TCP/IP Coexistence
OS/2 LAN Server 3.0 coexists with the existing IBM TCP/IP product. In addition the LAN Server can use the IP network to communicate. In this environment, both the sever and requester are required to use the IP protocol provided by TCP/IP for OS/2 and NETBIOS for TCP/IP products from IBM.
The current release of TCP/IP from IBM shares the common LAN Adapter and Protocol Support with the LAN Server. In the past, customers have used this Support, provided by the NETBIOS for TCP/IP program with the IBM TCP/IP program. In this release, the environment is supported.
NETBIOS is a programming interface used in a large inventory of PC-based local area network (LAN) customer application programs. TCP/IP is a networking protocol used in LAN and wide area networks (WANs) to facilitate communications among heterogeneous, multi-vendor system environments. The TCP/IP protocol has standards defined, specifically request for comments (RFC) 1001 and RFC 1002, which provide the ability to encapsulate NETBIOS application traffic and send it over the TCP/IP network.
Installing this module onto the workstation effectively replaces the native NETBIOS module normally used for NETBIOS-to-NETBIOS traffic on the LAN. Therefore, once installed, only the TCP/IP path is used for communication.
Note: Remote IPL is not supported in this environment.
2.4 Features Unique to the Advanced Server
2.4.1 386 HPFS on OS/2 2.0
The Advanced product runs on an OS/2 2.0 operating system and is a highly optimized network server designed for advanced 386/486-based platforms with very large hard drives. It consists of an optimized Ring 0 server tightly coupled with bootable installable high performance file system (386 HPFS) and customized device drivers to accelerate network file I/O.
2.4.2 Greater than 16MB Support
OS/2 2.0 allows access to greater than 16MB of memory. OS/2 1.3 allowed a maximum of 16MB. Because the 386 HPFS is capable of using massive amounts of memory for its cache, its performance is greatly improved by allowing access to memory beyond 16MB.
2.4.3 Fault Tolerance
Fault Tolerance now provides two new key features: remirror without format and the capability to mirror the boot drive. Remirror without format simplifies the recovery of a detached secondary drive. The process is as simple as using the FTSETUP program to recover the drive and rebooting the system, saving time and steps required to back up and restore the complete drive.
2.4.4 Local Security
The Local Security feature of the 386 high performance file system (HPFS) provides file protection against unauthorized access to any server file. This protection cannot be evaded by rebooting the server and is functional even when the LAN Server code is not running. This protection applies to all files stored on the 386 HPFS file partition.
3.0 Standard Features
3.1.1 Single System Image
A domain is the logical grouping of one or more servers in a local area network. This grouping is referred to as a Domain and is defined by a network administrator. This association allows a user to log on to a domain and gain access to resources on the individual servers. The single systems image allows the user, when logged on, to view both local and remote resources as if the resources were all part of the local workstation.
3.1.2 Remote Administration
The network administrator can perform administrative tasks on a given domain from an OS/2 requester on the LAN. The network administrator creates and maintains the domain definitions centrally stored in the domain control database on the domain controller, a role given to one of the senders in the domain at server installation time.
3.1.3 Server Monitoring
Extensive capabilities allow the network administrator to determine the status of server resources, list utilization statistics, view error logs, identify logged-on users, monitor attempts to log on with an invalid password, or invalid attempts to access resources, receive alerts (informative messages) when events of interest occur, and so on. OS/2 LAN Server provides not only security related information but also diagnostic and resource usage information to the network administrator.
3.1.4 Remote Initial Program Load (IPL)
Remote IPL supports workstations with or without local media in both a DOS and an OS/2 environment. The remote IPL feature mimics the normal boot process of a PC Booting from a local drive with several slight variations, which allow the boot information to come from the network, rather than from the computer's hard disk or diskette drive. Remote IPL for both DOS and OS/2 is supported over Token Ring, PC Net, and Ethernet. A single server can provide this Remote IPL service to workstations connected to the network via IBM bridges. A full screen interface is provided to support the remote IPL function. The remote IPL function supports DOS 3.3, 5.0, and OS/2 2.0. This remote IPL facility allows the Remote IPLing of additional functions, such as Extended Services features, via network administrator manipulation of the product-provided standard IPL definitions. The requesters shipped with OS/2 LAN Server 3.0 are supported as part of the remote IPL process, as are the DOS and OS/2 LAN Transports and adapter drivers.
In the remote IPL environment, the user-selected boot configuration function provides, via a Presentation Manager application, a means to request an alternate boot to an OS/2 remote IPL requester. For example, the function provides the capability of remote IPLing a different version of OS/2 than is installed at the remote IPL server, a PS/2 reference diskette, or an occasionally used DOS application that does not run in the OS/2 MVDM.
There are three basic user types: USER, GUEST, and ADMINISTRATOR. A USER can access LAN resources as defined by the ADMINISTRATOR. The GUEST is a special user type that permits USER IDs not explicitly defined in the domain to have access to a specified set of LAN resources. The ADMINISTRATOR type is the network administrator and has overall control of domains on the LAN. The ADMINISTRATOR can delegate management of any of the following areas to an OPERATOR (e.g. any USER ID) by specifying (via the /OPERATOR parameter of the NET USER command) the appropriate sub-level of authority:
|Server||Lets a user control shared resources on a server, read and clear the errorlog, and close sessions and files that are open. User control is through the command-line interface.|
|Accounts||Lets a user control user and group accounts (for example add, delete, and modify user accounts, and update logon requirements for the user accounts database). This operator privilege does not allow a user to grant administrative privilege or assign operator privilege. User control is through the command-line interface and User Profile Management.|
|Print Queues||Lets a user control shared serial communication devices. User control is through the command-line.|
|Communications Queues||Lets a user control shared serial communication devices. User control is through the command-line interface.|
This feature allows a domain controller to be designated as the network time server. This function is provided for use by applications that need to synchronize their time with a designated time source server. A bit is set (SV_TYPE_TIME_SOURCE) that identifies a server as the time source. This bit can be queried through use of either the NetServerEnum or NetServerGetlnfo APIs. NetServerEnum2 can be used to obtain a list of the time servers in up to four other domains by specifying these domains on the /OTHDOMAINS line in the IBMLAN.INI file or in the /OTHDOMAINS parameter on the NET START REQUESTER command. NetRemoteTOD can be used to obtain the time and date information from the time server.
3.1.7 Replicator Service
LAN Server provides a powerful Replicator service that helps make network administration easier and more efficient. This service allows a set of files stored on one server to be selectively replicated to other servers or OS/2 LAN requesters on the network. Replication can be used to distribute any administrative or application-related files.
3.2.1 OS/2 (Server/Requester)
A Presentation Manager application provides the capability to install, configure, and remove the LAN Server and OS/2 LAN Requester on all supported hardware platforms.
Installation of the LAN Server 3.0 product requires the OS/2 2.0 operating system.
3.2.2 DOS LAN Requester
An installation program is also provided for the installation of DOS LAN Requester.
3.3.1 User Profile Management
User Profile Management (UPM) performs the user ID and password validation function at logon time. UPM also provides facilities for the management of user IDs and Groups within the domain.
A network administrator has a wide range of mechanisms with which to control and manage user access to the network. A network administrator has the ability to define:
|Valid logon times||Permitted logon times can be specified in weekly intervals, such as Monday, Wednesday and Friday between 9 A.M. And 7 P.M.|
|Valid workstations||By default, a user can log on from any workstation on the network; however, the administrator can specify one to eight workstations to which a user is restricted.|
|Account expiration date||Individual accounts can be set to expire on specified dates. This is useful for temporary employees and classroom environments.|
|Forced logoff||When a user's account expires or the limits of a valid logon time are reached, the system can be set to force the user to logoff immediately, grant the user a specified grace period before an automatic logoff occurs or ignore the expiration and let the user continue working.|
3.3.2 Password Encryption
OS/2 LAN Server uses the U.S. Government Data Encryption Standard (DES) encryption algorithm to encrypt passwords. Network administrators can also use the following system-wide settings to control the use of passwords:
|Minimum password length||Specifies the required number of characters.|
|Maximum password age||Forces users to change their password at specified intervals.|
|Minimum password age||Stop users from altering their passwords until a specified interval has passed.|
|Unique password history||Ensures that a password chosen by a user is different from as many as eight of the user's previous passwords.|
3.3.3 Access Control Profiles
Once a user is logged on to a domain, the user's access to a given resource is controlled by the access control profile for that given resource. The permissions which follow can be specified in an access control profile allowing flexibility in that combinations of appropriate permissions may be constructed to give very specific control to a user:
|None||No access to the resource.|
|Execute||Use the resource (an application program), but not able to copy to your diskette or hard disk.|
|Create||Create a file or directory.|
|Delete||Delete a file or directory.|
|Attribute||Change the attributes of a file.|
|Permission||Gives a User the ability to grant other users access to this resource.|
By default, all resources are protected. A network administrator can grant permissions to groups as well as individual users. Creating groups of users with similar resource needs makes it easier to grant access permissions. New users added to an existing group inherit the permissions previously given to the group. An administrator can effectively manage the resources in the network by using a combination of group designations and permissions.
3.3.4 Local Security
There are several facilities available to secure an OS/2 LAN Server that may not be locked away in a room of its own. The PS/2 hardware provides a power-on password facility, which disables the machine on startup until the correct password is provided. Another password facility allows the locking of the keyboard for those times when the operator is temporarily away. A Server Mode function is also available, which automatically disables input at startup but allows the machine to come to full readiness without operator interaction. The 386 high performance file system (HPFS) provides file protection against unauthorized access to any server file. This protection cannot be evaded by rebooting the server and is functional even when the LAN Server code is not running. This protection applies to all files stored on the 386 HPFS file partition. The 386 HPFS is available with-the Advanced server only.
3.3.5 Audit Trail
A comprehensive audit trail facility enhances security by enabling administrators to keep track of selected server resources. Any network resource, such as a directory, individual file, a named pipe, or a printer queue, can be designated to audit resources. Resource audit can provide data on the type of access (open, close, read, write, and so on), user name, accessing workstation, date and time of occurrence, outcome of the access, and descriptive information about the event. Server audit can keep track of when the sender is started, stopped, paused, or continued; all logons and logoffs; and all remote administration connections. The administrator also has the ability to audit changes to the user and group accounts database and to audit changes to the access control list.
3.3.6 Alert Support
Detailed, informative messages (alerts) are sent to designated users or administrators on the LAN when events of interest occur. Alerts are sent for printer or disk problems (printer out of paper, server disk is almost full); security problems, such as attempts to violate security (excessive password violations); or excessive entries in the error log (error log nearly full). When alerts are sent, all pertinent data is recorded, including the server name, date and time of alert, a description of the problem, and the recommended action.
First Failure Support Technology (FFST/2) provides superior and consistent reliability and serviceability (RAS) functions to the customer. If an error occurs, FFST/2 Supports the capturing and recording of error data and reporting of the error. This facility removes the necessity of having to recreate problems in the defect correction process. FFST/2 functions include:
- Error logging
- Message logging
- Dump process
- Generic alert building
Generic alerts are generated, formatted in Network Management Vector Transport (NMVT) format, and then sent to IBM LAN Network Manager or NetView when critical system situations occur. Generic alert supports detection points to detect the critical situations, generates and builds the NMVT formatted alert, and transports the alert to a host system or focal point.
3.4 Fault Tolerance
3.4.1 UPS Support
The Uninterruptible Power Supply (UPS) support provides warning and orderly server shutdown facilities when used with a compatible uninterruptible power supply available from a variety of vendors. The power supply signals the software through the serial port.
3.4.2 Disk Mirroring and Duplexing
Disk mirroring allows the duplication of data on another drive attached to the same disk controller. Disk duplexing allows this duplication on a drive attached to another disk controller. This feature also provides error logging, alerting, and monitoring of disk activity in a mirrored, duplexed, or standard server disk subsystem. Both mirroring and duplexing are available with the Advanced product only. This is in addition to the HOTFIX service available on both products, which provides for an automatic attempt to recover from an initial data write error by transferring data from flawed disk areas to writable disk space.
3.5 DOS Requester Functions
An improved synergy between DOS LAN Requester (DLR) and Microsoft Windows is provided. This allows users of Windows to access network files, printers, applications, and other services available on a LAN Server domain through the graphical user interface of Windows. The DLR user can do the following through Windows:
- Log on and log off a LAN Server domain and modify logon assignments.
- View, connect, and disconnect available LAN Server shared filesets.
- View, connect, and disconnect available LAN Server shared printers.
- View, install, and use available LANT Server shared applications.
- Send messages to other network users.
DOS LAN Requester is able to accept double byte character set (DBCS) characters in command-line parameter strings.
The DBCS printer support makes possible the use of those printers unique to the DBCS environment.
3.6 Application Coexistence
3.6.1 LAN Server Applications
Applications written to the OS/2 LAN Server 2.0 APIs will be compatible with the LAN Server 3.0 product. The OS/2 LAN Server 2.0 command line commands are compatible with those in the LAN Server 3.0 product.
A Domain Control Database (DCDB) Migration Utility is provided to assist in the Migration of a PC LAN Program Version 1.3 environment to a LAN Server 3.0 environment. The Migration Utility preserves the data integrity and consistency of the definitions in the domain. A migration guide provides scenarios with step-by-step procedures for completing the migration. Upgrading from LAN Server 1.3 or LAN Server 2.0 does not require the execution of the migration utility.
3.6.2 Microsoft LAN Manager
LAN Server 3.0 will interoperate with the requesters from Microsoft LAN Manager 2.1. The requesters from LAN Server 3.0 will interoperate with Microsoft LAN Manager 2.1.
Note: Names are restricted to eight characters on LAN Server.
4.0 Machine Requirements
4.1 LAN Server 3.0 - Entry or LAN Server 3.0- Advanced
IBM OS/2 LAN Server 3.0-Entry and Advanced support the appropriately configured hardware platforms that are supported by OS/2 2.0. Besides supporting appropriately configured IBM hardware, the Entry and Advanced products also support selected OEM equivalent hardware that has passed the OS/2 compatibility test. The approved platforms are listed in numerous forums and publications.
4.2 OS/2 LAN Requester
OS/2 LAN Requester supports the appropriately configured hardware platforms supported by OS/2 2.0.
4.3 DOS LAN Requester
DOS LAN Requester supports the appropriately configured hardware required to support the DOS 3.3 or 5.0 operating systems, or approved equivalents.
4.4 OEM Systems
IBM certification testing has been completed on various OEM hardware. LAN Server 3.0 is supported on those OEM platforms that are listed in Prodigy, CompuServ,, and under OS/2 forums.
4.5 OS/2 LAN Server for Macintosh Version 1.0
OS/2 LAN Server for Macintosh Version 1.0 supports the appropriately configured hardware platforms supported by LAN Server 3.0- Entry or LAN Server 3.0 - Advanced. The Macintosh workstations must be configured to support AppleTalk.
4.6 Hardware Adapter Support
Multiple adapter support consists of the ability to manage four logical networks concurrently. Token-Ring, Ethernet, and PC Network adapters are supported. The multiple adapter support is expected to be used primarily on servers; however, this support is available on requesters as well. A maximum of 254 NETBIOS sessions is supported per adapter card.
OS/2 LAN Server's support of the Network Driver Interface Specification (NDIS) makes it possible to support LAN adapter cards with NDIS compliant device drivers. Drivers for the OS/2 environment are shipped with the OS/2 LAN Server 3.0 products for the currently supported LAN adapters. The NDIS interface is publicly documented and supported. In addition to support of NDIS compliant adapters, a loop back driver is included for communication back to the same system.
4.6.1 PC Network and Token-Ring Support
The IBM PC Network adapter must be the primary network adapter if it is the only adapter on the workstation.
A workstation equipped with one of the following combinations of IBM PC Network and IBM Token-Ring Network adapters cannot have any other IBM PC Network adapter or IBM Token-Ring Network adapter:
- Two IBM Token-Ring Network adapters
- Two IBM PC Network adapters
- One IBM PC Network adapter and one IBM Token-Ring Network adapter
- One IBM PC Network adapter and one IBM Token-Ring Network adapter (the IBM PC Network adapter must be the primary adapter)
Note: Only four instances of the IBM Token-Ring Network 16/4 Busmaster Server Adapter/A can be installed on the same workstation.
4.6.2 Ethernet Support
A workstation cannot have more than two SMC (formerly Western Digital) adapters, two Ungermann-Bass* adapters, or two instances of the IBM PS/2 Adapter for Ethernet Networks.
4.6.3 3174 Peer Communications
The 3174 Peer Communications function provides peer-to-peer communication for programmable workstations connected to an IBM 3174 Control Unit through IBM 3270 communication adapters using coaxial cable or telephone twisted-pair wire. An OS/2 LAN Server or OS/2 LAN Requester workstation can support up to two 3270 communication adapters configured for 3174 Peer Communications at a time.
4.6.4 Remote IPL Support
Servers providing the Remote IPL service can be equipped with any adapter supported by OS/2 LAN Server 3.0. that has Remote IPL capability.
Remote IPL requesters must be equipped with at least one of the following network adapter types (assuming that the adapter has a RIPL** ROM chip or diskette drive to remote IPL from a diskette);
- IBM Token-Ring Network adapter
- IBM PC Network baseband adapter
- IBM PC Network broadband adapter
- IBM PS/2 Adapter (Micro Channel only) for Ethemet Networks
4.6.5 Device Driver Support of Additional LAN Adapters
In OS/2 LAN Server Version 3.0, IBM has implemented the 3Com*/Microsoft LAN Manager Network Driver Interface Specification (NDIS) for support of adapters. In addition, IBM has extended the NDIS specification in its implementation of NDIS drivers. The specific details of IBM's implementation of NDIS media access control (MAC) driver development is available on request to:
- IBM Corporation
- Department 483 Zip 9131
- 11400 Burnet Road
- Austin, Texas 78758
5.0 Migration Considerations
This section describes the compatibility among various IBM server and requester products on a LAN. For a complete detailed summary of the steps required to migrate from any previous release to LAN Server 3.0, refer to the IBM OS/2 LAN Server Version 3.0 Network Administrator Reference Volume I: Planning and Installation (S96F-8428-00).
5.1 Coexistence of LAN Servers in a Single Domain
Servers with different OS/2 LAN Server 3.0 packages installed can coexist in a single domain. For example, a domain could have an OS/2 LAN Server - Advanced domain controller and two OS/2 LAN Servers - Entry additional servers.
OS/2 LAN Server 2.0 and 3.0 servers can coexist with OS/2 LAN Server 1.3 servers on the same domain (with either as the domain controller), provided the OS/2 LAN Server 1.3 servers are at Corrective Service diskette (CSD) level , WR05050 or greater.
5.2 Interoperability between LAN Servers and LAN Requesters
Table 1 and Table 2 describe access capabilities of various IBM LAN Requester products to resources on IBM LAN Server domains. the following three areas are covered:
- Logging on to a domain
- Administering a domain
- Accessing external resources across domains.
The IBM LAN Server domains illustrated are:
- PC LAN Program 1.31 (or later) Extended Services
- OS/2 LAN Server 1.3
- OS/2 LAN Server 2.0
- OS/2 LAN Server 3.0.
The IBM LAN Requester products addressed are:
- PC LAN Program 1.31 (or later) Base Services Requester (also requires IBM LAN Support Program)
- PC LAN Program 1.31 (or later) Extended Services Requester (also requires IBM LAN Support Program)
- OS/2 LAN Requester shipped with OS/2 Extended Edition 1.3
- OS/2 LAN Requester shipped with LAN Server 2.0 and LAN Server 3.0
- DOS LAN Requester shipped with OS/2 LAN Server 1.3, 2.0, and 3.0 (also requires IBM LAN SupportProgram).
- LAN Enabler 2.0 (includes OS/2 LAN Requester and DOS LAN Requester).
5.3 Logon and Administrative Capabilities
Table 1 illustrates the logon (L) and administrative (A) capabilities of various requester products.
For example, a user can use a PC LAN Program 1.31 (or later) Base Services requester to log on to a domain controlled by an OS/2 LAN Server 3.0 server and can access domain resources available to that user ID. However, this user is not able to perform any administrative tasks in that domain.
TABLE 1. LOGON AND ADMINISTRATIVE CAPABILITIES
|LAN Requesters||PCLP 1.31 (or later) (ES)||OS/2 LAN Server 1.3 (on EE 1.3)||OS/2 LAN Server 2.0(on SE 1.31 or OS/2 2.02)||OS/2 LAN Server 3.0 (on OS/2 2.0)|
|PCLP 1.31 (or later) (BS) running on a DOS or an OS/2 workstation||L3||L3,4||L3,4||L3,4|
|PCLP 1.31 (or later) (ES) running on a DOS or an OS/2 workstation||L, A
OS/2 LAN Requester (shipped with EE 1.3)
|OS/2 LAN Requester (shipped with LAN Server 2.0)running on OS/2 1.3 or OS/2 2.0||L,A5||L,A||L,A6,7|
|OS/2 LAN Requester (shipped with LAN Enabler 2.0)||L,A5||L,A||L,A6|
|OS/2 LAN Requester (shipped with Lan Server 3.0) running on OS/2 2.0||L,A5||L,A||L,A|
|DOS LAN Requester (shipped with OS/2 LAN Server 1.3, 2.0, or 3.0 or LAN Enabler 2.0) running on a DOS or an OS/2 workstation.||L,A4,8||L,A4,8||L,A4,8|
- A = administrative capabilities
- BS = Base Services
- EE = OS/2 Extended Services
- L = logon capability
- PCLP = PC LAN Program
- SE = Standard Edition
- OS/2 Standard Edition 1.3 must be at CSD level XR5050 (or greater).
- LAN Server 2.0-Advanced runs only on OS/2 Standard Edition 1.3.
- The network administrator defines a user ID that matches the machine name of the PC LAN Program Base Services workstation. When the workstation issues a NET USE command, the machine name is validated against the defined user IDs.
- Access to serial devices is not supported.
- LAN Server 1.3 must be at CSD level WR05050 (or greater).
- Administration of new functions, such as Fault Tolerance, is not supported.
- LAN Server 3.0 does not support the remote IPL of OS/2 1.3 requesters.
- You have administrative capability from a DOS LAN Requester workstation only if you have loaded an API that performs the desired administrative task. A large number of API categories that support remote network administration are supported. For detailed information, refer to the LAN Server Application Programmer's Reference. To load the APIs, run DOS LAN Requester with the/API parameter set in the DOSLAN.INI file.
5.4 Access to External Resources
Table 2 illustrates the access capabilities of various IBM LAN Requester products to resources on domains other than the logged-on domain. Access to resources across domains is accomplished through an external resource-definition function, through the use of appropriate APIs, or by using explicit NET SHARE and NET USE commands. Once a user's ID and password are validated, that user can access resources in another domain provided the network administrator of that domain has shared the resources and granted the appropriate access permissions.
For example, if a user of OS/2 LAN Requester is logged on to an OS/2 LAN Server 1.3 domain and requires access to resources in an OS/2 LAN Server 3.0 domain, the following resource definition must exist:
- The desired resource in the OS/2 LAN Server 3.0 domain must be defined as shared.
- The resource must be defined as an external resource in the OS/2 LAN Server 1.3 domain.
- The user ID and password, if applicable, must be defined in the OS/2 LAN Server 3.0 domain.
Setting up a guest account is an alternative method of providing access to external resources.
TABLE 2. ACCESS TO EXTERNAL RESOURCES ACROSS DOMAINS
|External Resource Domain to Be Accessed||Requester
|PCLP 1.31 (or later) (ES)||OS/2 LAN Server 1.3||OS/2 LAN Server 2.01||OS/2 LAN Server 3.01|
|PCLP 1.31 (or later) (BS)||Not applicable||X||X2||X2||X2|
|PCLP 1.31 (or later) (ES)||PCLP 1.31 (or later)||X||X2||X2||X2|
|OS/2 LAN Requester||OS/2 LAN Server 1.3, 2.0, or 3.0||X||X||X||X|
|DOS LAN Requester||OS/2 Lan Server 1.3, 2.0, or 3.0||X||X2||X2||X2|
- BS = Base Services
- ES = Extended Services
- PCLP = PC Lan Program
X indicates access capability.
- Applies to both LAN Server-Entry and LAN Server-Advanced.
- Access to serial devices is not supported.
6.0 Product Direction
The following details IBM's directions for the OS/2 LAN Server product.
- Server function on other platforms: for example, resource sharing for OS/2 and DOS clients extended to other systems such as IBM hosts that have certain performance and capacity advantages.
- Merge and exploit other future security subsystems.
- Evolve OS/2 LAN Server from using its native protocols and technologies to using Distributed Computing Environment (DCE) protocols and exploiting DCE technologies.
As IBM pursues these directions, we intend to fully protect current customer investments in client server applications by maintaining compatibility with current application interfaces and by providing interoperability between existing clients and new servers and new clients with existing servers.
6.1 Distributed LAN System Evolution
IBM's strategy is to upgrade, migrate, and evolve all IBM LAN solutions to a distributed LAN System environment based on the DCE and Distributed Management Environment (DME) technologies selected by the Open Software Foundation (OSF).
This migration will affect all of the key functions of OS/2 LAN Server including remote file, remote print, access control, DOS file system namespace support, and distributed application support via remote application interfaces and remote interprocess communications. The DCE technologies that LAN Server will exploit include the DCE Directory and the DCE User Registry; and LAN Server win migrate to the protocols that define the DCE Distributed File System (DSF) and the DCE Distributed Print implementation. Since some of these technologies are not completely defined or implemented, OS/2 LAN Server will migrate in a stepwise fashion, continuing to utilize its current native facilities until the new facilities are available. For example, OS/2 LAN Server will continue to provide remote file support with its current protocols until the DCE DFS technology is fully available for inclusion in an IBM product. If the DCE User Registry is available sooner, OS/2 LAN Sender will migrate to this technology in the appropriate OS/2 LAN Server release. The eventual target is to continue the stepwise migration until OS/2 LAN Server is entirely based on OSF DCE technologies.
6.2 The Future
In the future, a majority of IBM's customers will have the need for simple workgroup computing - sharing LAN resources, accessing host data and applications, and transferring files between desktop computers and hosts.
Some businesses are currently implementing LAN distributed solutions based on the level of client-server computing currently available in the market. In the case of LAN Server 3.0 a rich set of remote file and print capabilities are available to multiple servers working together as a workgroup. However, there is a need for workgroups of servers to participate in enterprise-wide management domains that include common user management and definition, enterprise-wide (and beyond) navigation to remote resources including distributed application services and interfaces, and data storage facilities featuring location independence that enables data replication and redundancy. There is also a very strong need for distributed system and network management tools that provide performance, configuration, and distribution services for the enterprise-wide LAN system. IBM is actively participating in the definition of the technology base for both DCE and DME to address these requirements.
There are several factors that will effect the movement from the current level of client-server participation and implementation in the enterprise.
- Increased reliance on PC LANs will require LAN distributed solutions to be demanded earlier than expected.
- The downsizing of host-based applications to LAN implementations will require that centralized management and host-based tools be provide in the LAN environment.
- A desire to take advantage of the LAN's capabilities and the power of the PC to improve productivity will require that additional functionality be provided for workstation-based LAN solutions.
IBM will be an active participant in all phases of this movement with OS/2 LAN Server 3.0 and future releases based on OSF technologies as the strategic product for achieving the desired enterprise LAN solutions.
Personal Software Products
11400 Burnet Road
Austin, Texas 78758
First Edition (September 1992)
Second Edition (May 1993)
The following paragraph does not apply to the United Kingdom or any country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This publication could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or program(s) described in this publication at any time.
It is possible that this publication may contain reference to, or information about, IBM products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that IBM intends to announce such IBM products, programming, or services in your country.
© Copyright International Business Machines Corporation 1992, 1993. All rights reserved.
Note to U.S. Government Users - Documentation related to restricted rights - Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.
References in this products to IBM products, programs or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program or service is not intended to state or imply that only IBM's product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any of the intellectual property rights or other legally protectible rights of IBM may be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, programs, or services, except those expressly designated by IBM, are the user's responsibility.
IBM may have patents or pending patent applications covering subject matter this document. The furnishing of this document does not give you any license to these patents. You can inquire, in writing, to the IBM Director of Commercial Relations, IBM Corporation, Purchase, NY 10577 - USA.
The following terms, denoted by an asterisk (*) in this publication, are trademarks of the IBM Corporation in the United States and/or other countries:
|AT||Personal Computer AT|
|FFST/2||First Failure Support Technology/2|
The following terms, denoted by a double asterisk (**) in this publication, are trademarks of other companies as follows:
|BootWare||Lanworks Technologies Inc.|
|EtherCard PLUS||Standard Microsystems Corporation|
|EtherLink Intel||3Com Corporation|
|Lotus||Lotus Development Corporation|