

	Software
	Release
	Announcement
	
BNet II Cluster Access
(BCA)
R3.0
To order additional copies of this document
	United States customers, call Unisys Direct at 18004481424.
	All other customers, contact your Unisys Sales Office.
	Unisys personnel, use the Electronic Literature Ordering (ELO) system.
	
Distribution lists:
SA, SN, SU, SW, PR5
System:	CTOS
Release:	R3.0
	November 1993
Part Number:	4179 6921000
The names, places, andor events used in this publication are not intended to correspond to any individual, group, or association existing, living, or otherwise.  Any similarity or likeness of the names, places, andor events with the names of any individual, living or otherwise, or that of any group or association is purely coincidental and unintentional.
NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT.  Any product or related information described herein is only furnished pursuant and subject to the terms and conditions of duly executed agreement to purchase or lease equipment or to lease software.  The only warranties made by Unisys, if any, with respect to the products described in this document are set forth in such agreement.  Unisys cannot accept any financial or other responsibility that may be the result of your use of the information in this document or software material, including direct, special or consequential damages.
You should be very careful to ensure that the use of this information andor software material complies with the laws, rules, and regulations of the jurisdictions with respect to which it is used.
The information contained herein is subject to change without notice.  Revisions may be issued to advise of such changes andor additions.
Correspondence regarding this publication may be addressed directly to Unisys Corporation, Round Valley Development Center, Route 22 and Werner Way, Lebanon, NJ  08833, U.S.A.
RESTRICTED RIGHTS LEGEND.  Use, reproduction, or disclosure is subject to the restrictions set forth in DFARS 252.2277013  and FAR 52.22714 for commercial computer software.
Copyright  1993 Unisys Corporation
All Rights Reserved
Unisys is a registered trademark of Unisys Corporation
CTOS is a registered trademarks of Convergent Technologies, Inc.
Contents
Section 1
General Description	1
1.1	Introduction	1
1.2	Product Description	2
Section 2
Release Functionality3
2.1	Introduction	3
2.2	Component Summary	3
2.3	Feature Summary	4
Section 3
Product Interdependencies	5
3.1	Introduction	5
3.2	Hardware Requirements	5
3.3	Software Requirements	6
Section 4
Migration Requirements	7
4.1	Introduction	7
4.2	Compatibility with Previous Versions	7
Section 5
Corrections	9
5.1	Introduction	9
Section 6
Restrictions and Known Limitations	11
6.1	Introduction	11
Section 7
Support	13
7.1	Warranty	13
7.2	Support Category	13
7.3	Support Discontinuance	14
7.4	Product Assistance	14
7.4.1	Instructions	14
7.4.2	Environment	14
7.4.3	Software Components	15
7.4.4	Hardware Components	15
7.4.5	Circumstances	16
Section 8
Customer Product Information	17
8.1	Introduction	17
Section 9
List of Files on Product Media	19
9.1	Introduction	19
9.2	List of Files	19
Section 10
Ordering Procedure	21
10.1	Introduction	21
Section 1	
General Description	
1.1	Introduction
This Software Release Announcement describes BNet II Cluster Access R3.0, a subset of BNet II enabling any workstation in a CTOS cluster configuration to access client workstations in the same CTOS cluster configuration.
Unisys publishes Software Release Announcements (SRAs) to announce the release of a new product.  This Software Release Announcement 
	Provides you with technical details and ordering information on the new product
	Describes interdependency and migration considerations 
	Complements marketing, sales, and other customer product information
	Lists additional sources of information
1.2	Product Description
BNet II Cluster Access (BCA) allows any workstation in a CTOS cluster configuration to access client workstations in the same CTOS cluster configuration.  A CTOS cluster configuration consists of a CTOS server and one or more attached client systems.
The client systems are CTOS workstations.  The server can be either a workstation or a shared resource processor.
The standard CTOS cluster architecture is clientserver oriented.  The server constantly polls the client workstations and serves their requests.  The client workstations have access to resources on the server.  However, the server does not have access to client resources, and client workstations do not have access to one another.
BCA allows any workstation in a CTOS workstation cluster to access any client workstation in the cluster.
Section 2	
Release Functionality	
2.1	Introduction
This section describes the components and features of BNet II Cluster Access.
2.2	Component Summary	
BCA includes the following components:
	Server BNet
	This system service resides on the server and establishes BNet sessions with client workstations running Cluster BNet in your CTOS cluster configuration.  Server BNet includes both Net Server and Net Agent components. Server BNet
	Cluster BNet
	This system service resides on client workstations and responds to requests from Server BNet.  Cluster BNet includes both Net Server and Net Agent components. Cluster BNet
	Network Configuration Utility (NCU)
	The Network Configuration Utility allows you to monitor sessions, and deinstall BCA services. Network Configuration Utility NCU
2.3	Feature Summary	
This release adds the following new features to the CTOS BNet II Cluster Access product:
	Inclusion of the Network Configuration Utility
	This is the standard configuration utility used with BNet II.  It allows you to monitor sessions and deinstall BCA services.
	Migration of command form parameters to the BNet configuration file
	This change in BNet II and BCA configuration eases the task of installing BCA services into memory.
	All components use message files, for nationalization without relinking.
	All system services generate events when they are installed, deinstalled, and suffer fatal errors.
	BNet II nodes may have one or more alias nodenames.
	The Net Agent and Server now keep track of the current and maximum usage of several configuration parameters.  This information may now be displayed by NCU to aid in troubleshooting the network.
	NCU now displays status information on the Net Agent and Server, including information on the run file version, which communication stacks are available, and options currently in use.
In addition to the new features, this release of the CTOS BNet II retains the following features from previous releases:
	Ability to access client workstation resources from the server and from other client workstations in a CTOS cluster configuration
	BCA can provide access to any workstation in a CTOS workstation cluster from any other workstation in the cluster.
	Compatibility with BNet II
	You can run BCA or BNet II nodes on a server and client interchangeably.
	Compatibility with Software Distribution (SWD).  You can use SWD to install BCA from a remote system.
Section 3	
Product Interdependencies	
3.1	Introduction
This section contains information on:
	Hardware and memory requirements to use the various functional components in the BNet II Cluster Access package.
	Supported software release levels of all required products.
3.2	Hardware Requirements	
This release of BCA runs on CTOS workstations with 286 or higher level processors.  This includes XBus, SuperGen 5000, EISA, and ISA workstations.  BCA also runs on XE530 shared resource processors.
BCA requires RS422 and RS485 cluster cable for all workstation and shared resource processor connections.
RAM and Disk Sizes of BCA Files
	

	K bytes	Disk Size
File	Memory	(Sectors)
	
BNetClstr.run
69
97
BNetConfig.sys

3
BNetInitMsg.bin

5
BNetMsg.bin

5
BNetSrvr.run
113
111
NcuForm.Lib

59
NcuMsg.bin

7
Ncu.run

397
	
3.3	Software Requirements	
The following software is required to use this product:
Software
Release Level
Component
BTOS II
3.0 or higher
XBus workstation (286 or higher)
CTOS II
3.3 or higher
XBus workstation (286 or higher) or SuperGen 5000
CTOS III
1.1 or higher
EISA or ISA workstation
CTOSXE
3.0 or higher
XE530 shared resource processor
Section 4	
Migration Requirements	
4.1	Introduction
This section describes the tasks required to migrate from prior releases of BNet II Cluster Access.
4.2	Compatibility with Previous Versions	
This version of BCA is not backward compatible with earlier versions.  You must use the same version of BCA on both the client workstations and the server.
If you are configuring BCA in a network using BNet II, you must install BNet II 3.0.  This version of BCA is not compatible with earlier versions.
Section 5	
Corrections	
5.1	Introduction	
The following corrections have been made to this version of BNet II Cluster Access:
	When a request originates from a cluster node, the source nodename of that request is now properly identified as the cluster's nodename, not the server's nodename.
	You can configure multiple large Xblocks, as well a small Xblocks, resulting in better performance.
	On CTOS II 3.3 and higher, BCA now does its user termination and abort processing through the CTOS Quiet User function, resulting in better performance.
	The maximum client request block is now configurable.  Previously, the maximum size was 64 bytes.
	This version allows simultaneous file access by a single user to multiple open files.  Previous versions allowed a user to access only one file at a time.
	This version allows a system service to reduce the size of the last Cb of a request block before responding to it, in which  case, BCA will limit the amount of response data sent.
	Certain internal BNet requests which had an odd number of bytes in the central field have been modified.  These requests caused problems on the XE530.
	This version correctly handles a client request containing a null Pb but nonnull Cb field.
	In cases of multiple paths using extended routing to a remote node, if one path fails after the first hop, BCA now tries to use the other paths.  This makes the network less sensitive to incorrect NCU entries.
	A bug that could cause a protection fault when using BCA has been corrected.
	Problems caused by the client trying to send a request that was larger than the maximum message size BNet was handling, have been addressed.
Section 6	
Restrictions and Known Limitations	
6.1	Introduction	
BCA contains the following software limitations:
	You do not need to register BCA nodes at other nodes on the same LAN.  If you are unable to reach a BCA node from a remote node, you may need to register the BCA node at the remote node.  You should not register BCA nodes clustered to a BNet server at that server.  Also, you should not register BCA nodes at a remote node that is on the same LAN as the BCA node you are trying to reach.
	If you are using BCA with CTOS 3.3 and receive status code 5153 frequently, or if BCA indicates a large number of Xblock waits for a user, edit the system's Config.sys file to include the following parameters:
	:XBlocks:(Number=50,Size=4096)
:MaxXBlocksOut:12
	If you still receive status code 5153, then make the XBlocks Number and MaxXBlocksOut values larger.
	Before you can load Net Agent and Net Server on a diskless cluster workstation, you must customize the operating system by setting the nNetUsers parameter to the maximum number of remote users the cluster workstation is to support.  If you try to load Net Agent and Net Server on an unmodified system, the system displays status code 5020.
Section 7	
Support	
7.1	Warranty	
BNet II Cluster Access is a warranted Unisys software product.  
Unisys warrants that BNet II Cluster Access, in its unaltered form, will substantially conform to Unisys current published functional specifications when used in Unisys supported configurations.  The customer is responsible for reporting suspected deviations using the User Communication Form (UCF) process within ninety (90) days following delivery.  The product is neither field repairable nor field modifiable.  Corrections to reported deviations are provided to the user via updated code files.
This standard warranty is not a substitute for Unisys Service Agreement offerings.
7.2	Support Category	
BNet II Cluster Access is fully supported by Unisys.
Support services for BNet II Cluster Access are offered under the SURETY (United States) or A la Carte (International) support programs and are consistent with the support services offered for the entire CTOS Hardware and Software family of products.
Unisys SureNet is an electronic bulletin board service, providing customers in the United States access to technical information seven days a week, 24 hours a day.  SureNet Technical Information Services are available at no additional cost to customers with a current Unisys service agreement or software license and include access to system alerts, customer technical bulletins and online UCF entry.  Registration is required.  SureNet Support Services are available on an annual subscription basis.  For more information, contact Unisys Direct at 18004481424, prompt 5.  You may register for Technical Information Services andor Support Services either online (by dialing 18008288796 with 8 data bits, 1 stop bit, no parity, asynchronous, VT100 emulation) or by calling Unisys Direct.
If you need further assistance or information regarding support services, please contact your Unisys representative or your local Unisys office.
7.3	Support Discontinuance	
Unisys supports the current release level and one level back.  Prior levels are not supported.
7.4	Product Assistance
7.4.1	Instructions
Should you encounter a problem with a Unisys product, please contact your local Customer Service Center.  Your Customer Service Center representative will have a more definitive set of problem reproduction requirement guidelines specific to the application you are running.  So that your questions may be answered in a timely manner, please collect all information which applies to your problem.  A guideline for gathering information is listed below or you may reference the PVP appendix at the end of this SRA for more product specific UCF submission requirements.
7.4.2	Environment
In order to assist us in determining the nature of your problem, please be prepared to describe the environment in which the problem occurs.
7.4.3	Software Components
If you suspect the problem is software related, be prepared to provide the following information concerning the software being used:
1.	Version number of the software in which the problem occurs
2.	Version of the operating system software
3.	Installation parameters used for the failing software
4.	Configuration files used
5.	Other software installed at the time of failure
6.	Recent changes to the system software (updates, etc.)
7.	Any messages associated with the failure that appear in the system log file (accessed through the Plog command)
8.	Connectivity of the software (is your system part of a network?)
7.4.4	Hardware Components
If you suspect the problem is hardware related, be prepared to provide the following information concerning your hardware platform:
1.	Type of processor being used
2.	Workstation components (hard drives, communication modules, CDROM drive, etc.)
3.	Any peripherals attached to the workstation (printers, scanners, modems, plotters, etc.)
4.	Connectivity of the hardware (is your system part of a network?)
5.	Recent changes to the hardware platform
6.	Amount of memory installed
7.4.5	Circumstances
Be prepared to provide the following information about the circumstances under which the failure occurs:
1.	Is the problem reproducible?
2.	What are the exact steps required to reproduce the problem?
3.	Under what circumstances does the problem not occur?
Section 8	
Customer Product Information	
8.1	Introduction	
The following product information is shipped with BNet II Cluster Access and can be ordered separately from the software:
BNet II Cluster Access Administration Guide
See Section 10, Ordering Procedure, for part number information.
Section 9	
List of Files on Product Media	
9.1	Introduction
This section describes the software distribution media.
9.2	List of Files
<Sys>BadBlk.sys
<Sys>Cluster Access BNet II 1 of 1
<Sys>CrashDump.sys
<Sys>FileHeaders.sys
<Sys>Install.cmds
<Sys>Install.cntrl
<Sys>Install.jcl
<Sys>Log.sys
<Sys>Mfd.sys
<Sys>SysImage.sys
<Unisys>BNet.fls
<Unisys>BNetClstr.run
<Unisys>BNetConfig.sys
<Unisys>BNetIIC.cmds
<Unisys>BNetIIM.cmds
<Unisys>BNetInitMsg.bin
<Unisys>BNetMsg.bin
<Unisys>BNetSrvr.run
<Unisys>Ncu.run
<Unisys>NcuForm.lib
<Unisys>NcuMsg.bin
<Unisys>Request.BNet.Apnd
<Unisys>SRA.odd
<Unisys>SRA.def
Section 10	
Ordering Procedure	
10.1	Introduction
Please complete and return the attached Update Service Request (USR) form to order this product.  Media provided by Unisys Corporation may not be returned for credit.
The Style IDs to order BNet II Cluster Access are:
	B25CV2	CTOS III Package
	B25CVP	CTOS III Promotional Package
	B25CP3	CTOS II Package
	B25CX3	CTOSXE Package
You can order manuals from the following address:
Unisys Corporation
Publications Distribution Center
13250 Haggerty Road North
Plymouth, Michigan 48170
