These release notes support Version 4.4.1 of the ptx®/OSI Transport communications software. We recommend that you read these release notes before installing this software on your NUMA system.
The following software products are prerequisites for ptx/OSI Transport V4.4.1:
DYNIX/ptx® V4.4.2 or later
If using the transports over LAN media devices: ptx/LAN V4.5.1 or later
If using the transports over X.25: ptx/X.25 V4.4.0 or later
The ptx/OSI Transport V4.4.1 product contains the following changes to the previous release:
Year 2000 problems have been fixed.
Support for VME Fast Ethernet devices has been added.
All (#include statement) user.h, proc.h, and session.h files have been removed to maintain the integrity of the data structures.
The COFF compatibility development environment has been removed (mailbug #230737). The COFF libraries present in earlier versions of DYNIX/ptx are no longer available.
COFF binaries will continue to work unless one or more of the following conditions exists:
Refer to the ptx/INSTALL Software Installation Guide and the DYNIX/ptx and Layered Products Software Installation Release Notes for installation information and procedures. These documents are located on the HTML documentation CD ROM that shipped with your 4.4.x product.
Documents for OSI, ptx/FTAM, ptx/VT, and ptx/X.400 are located on the HTML documentation CD ROM that shipped with your 4.4.x product.
This section describes the known problems in the ptx/OSI Transport software. The number that appears in parentheses in the title of each problem report is the problem-tracking-system number assigned to the report.
All inclusions (with #include statement) of user.h, proc.h, and session.h files have been removed to maintain the integrity of the data structures.
The problems of MAKEDEV.osi failing and the OSI attachment to the menus failing have been fixed.
All known two-digit year notation problems (also known as "year 2000" problems) have been fixed.
The OSI code now supports VME Fast Ethernet devices. (/dev/net/fe*).
Problem: Alternate disk installation of ptx/OSI is not supported from DYNIX/ptx V4.1.5.
Workaround: None.
Problem: Using the OSI daemon osid -v repeatedly to debug the OSI configuration can result in a panic.
Workaround: Before invoking osid -v, make sure that ptx/OSI Transport is not running. Use the menu system to stop the transports.
If you upgrade from ptx/OSI Transport V4.4.0, the preview.log file for ptx/OSI Transport V4.4.1 will have several DELETE and CONFLICT DELETE entries for files that have since been removed. These files are related to COFF support, which is not provided in DYNIX/ptx V4.4. The files should not have been in the previous release of ptx/OSI Transport on DYNIX/ptx V4.4 and are being removed in this maintenance release to correct that oversight. These DELETE entries should be expected only if you are upgrading; they require no action by the system administrator.
The man pages for pseudodevices are missing.
This section of the Release Notes provides information that was too late to be included in the published manuals.
The osistat utility can only show up to 400 endpoints.
The ositrace utility can only display valid PDUs, such as CR. Invalid PDUs may cause the utility to loop.
In cases of high numbers of connections or heavy usage (load), the following kernel parameter values are recommended for ptx/OSI Transport to operate properly. Use the menu system to modify the parameter values.
OSI_TP0_PCB 1000
OSI_TP0_NSAP 100
OSI_TP0_ROUTE 64
OSI_TP4_PCB 1000
OSI_TP4_NSAP 100
OSI_TPCL_PCB 1000
OSI_TPCL_NSAP 4
OSI_CLNP_SUBNET 16
OSI_CLNP_REASM 64
OSI_CLNP_ROUTE 128
OSI_SNDCF_VC 128
OSI_SNDCF_SNET 50
For ptx/OSI Transport V4.4.1 to operate over FDDI, the per device must be configured by editing the file /usr/osi/etc/osid.cfg directly) to include the following line:
PORT0 type=perlink=0
Two changes have been made to the internal NPI network layer interface: UNITDATA and BIND.
ATTENTION The NPI interface is an undocumented and unsupported interface.
The NPI interface for UNITDATA has been changed. The DEST_length structure member is now set to the length of the NSAP address. Previously, DEST_length was set to the length of the NSAP structure, which included the length of the address.
The NPI interface for BIND has been changed. You can now pass just the network selector to the bind interface. Passing only the selector causes it to be concatenated with the network address. Previously, the NPI interface required both the network address and selector.