ptx/INSTALL provides an installation procedure for installing DYNIX/ptx®, layered products, and the system software. The installation procedure is invoked from the ptx/ADMIN® menu system. You do not need to install the ptx®/INSTALL product; it is installed on your system automatically.
The ptx/INSTALL installation procedure is invoked from the ptx/ADMIN menu system. (Use System Administration -> Software Management.) It provides four installation methods: ALT DISK DELTA, INIT ALT DISK DELTA, ROOT, and SCRATCH. Chapter 3 describes these methods.
DYNIX/ptx and Layered Products Software, Volume 1 CD |
|
cfwdl-Compatible Firmware Bundle V1.3.2 |
ptx/RAID V2.2.0 |
DYNIX/ptx V4.6.1 |
ptx/SESMON V1.2.0 |
edb Debugger V3.4.3 |
ptx/SNA 3270 V4.7.0 |
EES V1.2.2 |
ptx/SNA APPC V4.7.0 |
Encryption V4.6.1 |
ptx/SNA LU0 API V4.7.0 |
ptx/AGENT V1.5.0 |
ptx/SNA LU6.2 V4.7.0 |
ptx/ATM V4.7.0 |
ptx/SNA PU2.1 Base Server V4.7.0 |
ptx/BaseComms V1.3.0 |
ptx/SNA RJE (3770) V4.7.0 |
ptx/C++ V5.2.5 |
ptx/SNA SDLC & LLCI V4.7.0 |
ptx/C++ Runtime V5.2.5 |
ptx/SNA TN3270 Client V4.7.0 |
ptx/CFS V1.2.1 |
ptx/SNA TN3270 Server V4.7.0 |
ptx/CLUSTERS V2.3.1 |
ptx/SPDRIVERS V4.1.0 |
ptx/Configuration Assistant V1.1.0 |
ptx/SVM V2.3.1 |
ptx/CTC V1.3.0 |
ptx/SYNC V4.6.0 |
ptx/EFS V1.5.1 |
ptx/TCP/IP V4.7.1 |
ptx/ITX V4.5.1 |
ptx/X.25 V4.5.1 |
ptx/JSE V1.18.0 and V3.0.2 |
ptx/XWM V4.6.3 |
ptx/LAN V4.8.0 |
SequentLINKTM V4.3.2 |
ptx/LICENSE V2.0.0 |
Fibre Channel Switch V1.6c3 (V1.6.3) |
ptx/NFS® V4.8.1 |
Fibre Channel Switch a2.2.1a (V2.2.1) |
ptx/PDC V1.5.0 |
NUMA Online Diagnostics Dispatcher V2.8.1 |
DYNIX/ptx Layered Products Software, Volume 2 CD |
|
CommandPointTM Admin V4.6.1 |
CommandPoint SVM V2.3.0 |
CommandPoint Base V4.6.0 |
Public Software V4.6.1 |
CommandPoint Clusters V2.3.0 |
ptx/XWM Contributed V4.6.3 |
Other CDs |
|
Backup Toolkit V4.4.4 |
Software for DLT7000E/DLT8000 Tape Drivesa |
ptx/LAE V1.0.0 |
a. This CD contains SAN Data Gateway Software V3.42.12, ptx/SPDRIVERS V4.1.1, cfwdl-Compatible Firmware Bundle V1.3.2, and DYNIX/ptx V4.6.1 fastpatch #255357, all of which are required when using DLT7000E or DLT8000 tape drives on systems running DYNIX/ptx V4.6.1.
The following installation changes have been made in the V4.6 release:
Disk labels are now provided to identify the disks in your system. A label specifies the node or cluster that owns the disk. The operating system uses labels to control disk access. Each disk must have a label; if there is not a label, the disk cannot be opened. A disk label is created automatically for the root disk during the installation.
If your system is currently running DYNIX/ptx V4.4 or V4.5, you will need to create the /etc/devlabel file after installing DYNIX/ptx V4.6 but before booting to multiuser mode. This file specifies the label for each disk on your system. If your system is currently running DYNIX/ptx V4.6, creating the file is optional. See "Create the /etc/devlabel File," following each installation procedure, for the contents and syntax of this file.
The root filesystem can now be located on a shareable disk attached to the Fibre Channel. On a system with multiple quads, the disk must be accessible from the first four quads. Disks that require the installation of a layered product, such as rd disks supported by ptx/RAID, cannot be used. The system must be booted on V4.6 before installing the root filesystem on a shareable disk or moving the root filesystem to a shareable disk.
ATTENTION Booting on shareable disks attached to the Fibre Channel is only supported for IBM Enterprise Storage Subsystems (ESS), IBM FAStT200TM Storage Servers, and Pbay storage subsystems.
This feature is not supported for EMC® Symmetrix® storage subsystems or HDSTM disk arrays from Hitachi Data Systems.
The version of DYNIX/ptx currently on your system determines the method that can be used to install on a shareable disk:
Scratch installations. Single-node systems can install directly onto a shareable disk only by booting from the distribution CD and then performing a scratch install. If you perform a scratch installation on a clustered system, you must install on a local disk.
Systems running DYNIX/ptx V4.4 or V4.5.
To upgrade from DYNIX/ptx V4.4 or V4.5, you must install DYNIX/ptx V4.6 on a local disk. After booting V4.6 on that disk, you can move the root filesystem to a labeled, shareable disk.
Systems running DYNIX/ptx V4.6. Single-node systems can upgrade directly onto a shareable disk if they are already running DYNIX/ptx V4.6. Clustered systems can upgrade directly onto a shareable disk only if each node is already running DYNIX/ptx V4.6 and the rolling_upgrade flag is set to "false" in the /etc/system/boot file on each node.
A custom VTOC can now be installed on the root disk during a scratch installation.
When ptx/INSTALL has selected a product for automatic installation, you can now deselect the product.
A Master ID and Node ID are now required. The Node ID is specified in your service contract. On a single-node system, the Master ID should match the Node ID. Each node on a clustered system must have the same Master ID, which should be the lowest-numbered Node ID assigned to the cluster. These IDs must be set before installing DYNIX/ptx V4.6. If you do not set the IDs, the system will stop at the stand-alone kernel when it is booted.
Changes to physical path specifiers for the bootpath provide alternate ways to specify the root and swap partition. Previously, only physical path specifiers could be used in the bootpath. In DYNIX/ptx V4.6, you can alternatively use the disk's user_defined_name or a combination of its vendor ID, product ID, and serial number as the physical specifier. For more information about boot syntax, refer to the "System Booting" section of the online document DYNIX/ptx System Administration.
The following installation changes were made in the V4.5 releases:
/usr/ssw cannot be a separate filesystem.
/usr cannot be a separate filesystem. If you currently have separate root and /usr filesystems, you must use the INIT ALT DISK DELTA installation procedure to upgrade to V4.6.1. This procedure will combine root and usr into a single root filesystem.
Increased disk space requirement. The minimum size for the root filesystem is now 2 GB. If your root filesystem is smaller than 2 GB, you will need to increase it before starting the upgrade. Appendix C contains procedures to do this.
New distribution CDs. DYNIX/ptx and most layered products are now distributed on two CDs, volume 1 and volume 2. Volume 1 must be installed first. Volume 2 and any other CDs (for example, ptx/LAE and Backup Toolit) can then be installed with either of the following procedures:
ALT DISK DELTA. After completing the ALT DISK DELTA (or INIT ALT DISK DELTA) to install Volume 1 and before booting the kernel, use ALT DISK DELTA to install the appropriate layered products from Volume 2 or other layered product CDs.
ROOT. After booting on the V4.6.1 kernel, use the ROOT procedure to install the appropriate layered products from Volume 2 or other layered product CDs.
NUMA Online Diagnostics Dispatcher Software. This software has been moved from the NUMA Console Software CD to the DYNIX/ptx OS and Layered Products Software, Volume 1 CD. You no longer need to do a separate install pass to install this software.
Common firmware downloader. ptx/SPDRIVERS now provides a utility, cfwdl, that is used to download FC Bridge and Host Adapter firmware, as well as various other types of firmware. The ffutil, dltutil, fwdl, and fcdl utilities are now obsolete.
The FC Bridge and Host Adapter are no longer provided as separate products on the CD. Instead, they are included in the "cfwdl-Compatible Firmware Bundle" product.
New systems are shipped with the following software and firmware already installed. You do not need to reinstall this software.
Software |
Firmware |
DYNIX/ptx |
Fibre Channel Bridge |
ptx/BaseComms |
Fibre Channel Host Adapter |
ptx/Configuration Assistant |
Fibre Channel Switch |
ptx/LAN |
|
ptx/PDC |
|
ptx/SPDRIVERS |
|
ptx/TCP/IP |
|
cfwdl-Compatible Firmware Bundle |
|
edb Debugger |
|
EES |
|
NUMA Online Diagnostics Dispatcher |
|
SequentLINK |
To complete the installation, perform the following steps:
[ ] | Set the Node ID and Master ID. See "Set the Node ID and Master ID" in Chapter 2. |
[ ] | Install and flash the console software. Then run the sysdef command in the VCS CLI window to define the system. See the NUMA Console Software Release Notes. |
[ ] | Boot the operating system. |
[ ] | Create an /etc/devlabel file that specifies the disk labels for all disks in the system. See "Create the /etc/devlabel File" in Chapter 7 for the contents and syntax of this file. |
[ ] | Install the appropriate layered products with the ROOT installation method. |
[ ] | Build the kernel and reboot the operating system. |
[ ] | Install the "Best Recipe" CD. This CD must be installed after all additional layered products have been installed. Refer to the README file on the CD for installation directions. |
[ ] | Complete product-specific tasks. See Chapter 10. |
[ ] | Add a user-defined name and a comment to the disk label for the root disk. See "Modify the Disk Label on the Root Disk" in Chapter 7. |
[ ] | Create a custom miniroot. See the DYNIX/ptx V4.6 System Recovery and Troubleshooting Guide. |
[ ] | Synchronize the time on all system clocks. See "Synchronize System Clocks" in Chapter 10. |
[ ] | If you want to move the root and swap partitions to a shareable disk, see Chapter 11, "Move Root and Swap to a Fibre Channel (Shareable) Disk." |
Rolling upgrades of clustered systems can be performed only on two-node systems with both nodes of the cluster currently running DYNIX/ptx V4.5.1 or V4.5.2 and the corresponding layered products and firmware. If the nodes are running earlier versions of software, they must be upgraded one-at-a-time.
Rolling upgrades can be performed only by Customer Service personnel. Contact your customer service representative for more information.
Upgrades to DYNIX/ptx V4.6.1 are supported only from the following releases:
If you are currently running a version of DYNIX/ptx earlier than V4.4.6, you must either do a scratch installation, or first upgrade to a supported version and then upgrade to V4.6.1.
ATTENTION The first time you boot the system on DYNIX/ptx V4.6, disk labels are written to the boot and swap disks. Additionally, disk labels may be written to other disks. If you should then need to reboot on your original V4.4/V4.5 root filesystem and the disk containing this filesystem is labeled, the boot will fail because DYNIX/ptx V4.4/V4.5 does not use disk labels. To enable DYNIX/ptx V4.4/V4.5 to boot properly in this scenario, refer to Appendix D, "Revert to the Previous V4.4/V4.5 Root Disk."
[ ] | If your system is currently running DYNIX/ptx V4.4.x or V4.5.x, install the "Software Patches for Upgrading from DYNIX/ptx V4.4.x/V4.5.x to V4.5.x/V4.6.x" CD. The patches on this CD fix problems in V4.4.x and V4.5.x that prevent the upgrade to V4.6.1 from completing successfully. The CD must be installed before upgrading the operating system. For details about the installation, consult the README file on the CD. |
[ ] | Gather the materials needed for the installation. See "Installation Materials" later in this chapter. |
[ ] | Gather current information about your system. See "Obtain System Information" later in this chapter. |
[ ] | Determine the software products that need to be installed. See "Upgrade Notes" later in this chapter. Also review the later section "Software Dependencies," which lists layered products that require the installation of other products. |
[ ] | Verify that your system meets the requirements for running DYNIX/ptx V4.6.1. See "System Requirements" in Chapter 2. Also review "Operational Restrictions" in Chapter 2. |
[ ] | If your system includes an EMC disk storage subsystem, verify that it is running the correct version of the EMC firmware. See "Requirements for EMC Disk Subsystems" in Chapter 2. |
[ ] | Back up your current software. See "Back Up System Files and Configuration Information" in Chapter 2. |
[ ] | Gather your license key information for those software products that require licensing. See "Software Licensing" in Chapter 2. |
[ ] | Deinstall any unsupported software. See "Deinstall Unsupported Software" in Chapter 2. |
[ ] | Modify the local site file to remove obsolete kernel parameters and to rename certain parameters. See "Modify the Local site File" in Chapter 2. |
[ ] | Set the Node ID and Master ID from VCS. See "Set the Node ID and Master ID" in Chapter 2. |
[ ] | Perform pre-installation tasks for the products that you will be installing. Be sure to complete the steps in the section for ptx/TCP/IP. See "Product-Specific Information" in Chapter 2. |
[ ] | Determine the type of installation you will be performing and plan your installation strategy. If you are not familiar with the installation types, see Chapter 3. |
[ ] | Review the installation log file and resolve any errors. Output from the installation is written to the screen and to the log file /usr/options/<product>/progress_log.<installation_date-time>. This log file is placed on the target installation disk when the installation is complete. | ||||
[ ] | During the installation, ptx/INSTALL will attempt to update the /etc/vfstab file on the target disk to point to the new root disk. If it is unable to do so, it will write a warning message to the screen and to the log file. If you see this message, be sure to update the /installmnt/etc/vfstab file manually on the target disk. | ||||
[ ] | If you are upgrading from V4.4 or V4.5, create an /etc/devlabel file that specifies the disk labels for all disks in the system. See "Create the /etc/devlabel File," following your installation procedure, for the contents and syntax of this file. | ||||
[ ] | Modify the /etc/inetd.conf file if necessary. See "ptx/TCP/IP" in the section "Product-Specific Tasks" in Chapter 10. | ||||
[ ] | Resolve file conflicts if you have not done so already. See Appendix B. | ||||
[ ] | If auditing is enabled on your system, ensure that the root account has a password and that at least one other user account exists and has a password.
| ||||
[ ] | If you broke a ptx/SVM mirror and installed on a plex, return the device where the installation was performed to the rootdg. See "Prepare to Reboot the System" in Chapter 4. | ||||
[ ] | If you have not yet installed the console software, shut down the operating system and install and flash the software, including the stand-alone kernel (sak.dat) and bootstrap program (ptxldr.elf), from the NUMA Console Software CD. See the NUMA Console Software Release Notes.
| ||||
[ ] | Reboot the operating system.
| ||||
[ ] | Add a user-defined name and a comment to the disk label for the root disk. See "Modify the Disk Label on the Root Disk" following the installation procedure in Chapter 4 or 5. If ptx/CLUSTERS is installed, you must run the rolling_upgrade_complete script before you modify the disk label for the root disk. See "Complete the Installation on a Clustered System" following the installation procedure in Chapter 4 or 5. | ||||
[ ] | Perform a ROOT installation of any remaining layered products. See Chapter 6. Review the installation log files to resolve any errors. | ||||
[ ] | Build the kernel and reboot the operating system. See Chapter 8, "Build a Custom Kernel." | ||||
[ ] | Install the "Best Recipe" CD. This CD must be installed after DYNIX/ptx V4.6.1 and all applicable layered products have been installed. Refer to the README file on the CD for installation directions. | ||||
[ ] | Install any other patch CDs distributed with DYNIX/ptx. Any patches must be installed after DYNIX/ptx V4.6.1 and all applicable layered products have been installed. Refer to the README file on the CD for installation directions. | ||||
[ ] | Download the Fibre Channel firmware and any other firmware. For the FC Switch, see the DYNIX/ptx V4.6.x Fibre Channel Software Release Notes. For the FC Bridge, FC Host Adapter, and other firmware downloaded with cfwdl, see Chapter 9, "Download Firmware with cfwdl" in these release notes. | ||||
[ ] | Remove installation directories that are no longer needed. See "Remove Unneeded Installation Directories" in Chapter 10. | ||||
[ ] | For installations on an alternate disk, sync files between the original root disk and the alternate disk. (This step is optional. It locates files on the original root disk that were changed after the image of the root filesystem was copied to the alternate disk.) See "Sync Files Between the Original Root Disk and the Alternate Disk" in Chapter 10. | ||||
[ ] | Complete other post-installation steps as described under "Product-Specific Tasks" in Chapter 10. | ||||
[ ] | Create a custom miniroot for your system. See "Create a Custom Miniroot" in Chapter 10. Also see Chapter 1 in the DYNIX/ptx V4.6 System Recovery and Troubleshooting Guide. | ||||
[ ] | If you installed on a mirrored plex, reestablish the mirror of the root volume. See "Mirror the Original Root Partition to the Upgraded Root Volume" in Chapter 4.
| ||||
[ ] | Synchronize the time on all system clocks. See "Synchronize System Clocks" in Chapter 10. | ||||
[ ] | If you want to move the root and swap partitions to a shareable disk, see Chapter 11, "Move Root and Swap to a Fibre Channel (Shareable) Disk." |
After upgrading all nodes in a cluster from DYNIX/ptx V4.4/V4.5 to V4.6 and booting them to multiuser mode, you will need to run the rolling_upgrade_complete script on each node. See "Complete the Installation on a Clustered System" following the installation procedure in Chapter 4 or 5.
The following CDs are needed for the installation:
Software Patches for Upgrading from DYNIX/ptx V4.4.x/V4.5.x to V4.5.x/V4.6.x, 03/01, Revision C.
This CD must be installed on systems running DYNIX/ptx V4.4.x or V4.5.x before the upgrade to V4.6.1. Consult the README file on the CD for installation information.
DYNIX/ptx V4.6.1 OS and Layered Products Software, Volume 1, 06/01, Revision B.
DYNIX/ptx V4.6.1 Layered Products Software, Volume 2, 03/01, Revision A.
Best Recipe, 06/01, Revision A
NUMA Console Software V1.7.6 , 06/01, Revision B.
ptx/LAE V1.0.0 for DYNIX/ptx V4.6.1, 03/01, Revision A (needed if you will be using the LinuxTM Application Environment)
Red Hat Linux V6.2 CD (needed if you will be using ptx/LAE)
ATTENTION This CD is not provided by IBM. Obtain it directly from any retailer of your choice. You can use any one of the Red Hat V6.2 releases; the Standard, Deluxe, and Professional releases will all work with ptx/LAE.
Backup Toolkit V4.4.4, 03/01, Revision A (needed if you will be using SAMS:AlexandriaTM)
In addition to these release notes, you will also need the following documents:
You may also need to refer to layered product release notes for configuration information.
Gather the following information about your system:
Currently installed software and firmware. Check /etc/versionlog or use the ptx/ADMIN "List Software Packages" option (select System Administration -> Software Management -> List Software Packages).
The current version of the console software.
Whether auditing is enabled. Run the audit command with no options.
The kernel environment type. Check the value of the environment directive in the file /etc/conf/uts/symmetry/unix.<kernel_name>.
The current root partition. Run the /etc/bootflags command and check the setting for the n0 string.
The "Software Patches for Upgrading from DYNIX/ptx V4.4.x/V4.5.x to V4.5.x/V4.6.x" CD must be installed before the upgrade to V4.6.1. Consult the README file on the CD for more information.
DYNIX/ptx must be upgraded to V4.6.1. If the following products are installed on your system, upgrade them with the new versions.
Backup Toolkit |
ptx/BaseComms |
ptx/PDC |
cfwdl-Compatible Firmware Bundle |
ptx/C++ |
ptx/RAID |
CommandPoint Admin |
ptx/CFS |
ptx/SESMON |
CommandPoint Clusters |
ptx/CLUSTERS |
ptx/SNA |
CommandPoint SVM |
ptx/Configuration Assistant |
ptx/SPDRIVERS |
edb Debugger |
ptx/CTC |
ptx/SVM |
EES |
ptx/EFS |
ptx/SYNC |
Encryption |
ptx/ITX |
ptx/TCP/IP |
FC Switch |
ptx/JSE |
ptx/X.25 |
NUMA Online Diagnostics Dispatcher |
ptx/LAN |
ptx/XWM |
ptx/AGENT |
ptx/LICENSE |
Public Software |
ptx/ATM |
ptx/NFS |
SequentLINK |
The console software must also be upgraded.
If ptx/C++ V5.2.3 or earlier is installed, you must either upgrade by selecting ptx/C++ V5.2.5 during the installation, or if ptx/C++ is no longer desired, deinstall it prior to the DYNIX/ptx V4.6.1 upgrade. If ptx/C++ V5.2.3 is not upgraded or deinstalled, the installation of DYNIX/ptx V4.6.1 will fail with the following error message:
c++ requires base of version not above 4.5.x base of version V4.6.1 selected FOR installation
If ptx/C++ V5.2.5 or ptx/JSE V3.0.2 are already installed, these products do not need to be upgraded as these versions are the supported versions for DYNIX/ptx V4.6.1.
The "Software Patches for Upgrading from DYNIX/ptx V4.4.x/V4.5.x to V4.5.x/V4.6.x" CD must be installed before the upgrade to V4.6.1. Consult the README file on the CD for more information.
DYNIX/ptx must be upgraded to V4.6.1. If the following layered products are installed on your system, update them with the new versions.
Backup Toolkit |
ptx/CFS |
ptx/RAID |
CommandPoint Admin |
ptx/CLUSTERS |
ptx/SESMON |
CommandPoint Clusters |
ptx/CTC |
ptx/SNA |
CommandPoint SVM |
ptx/EES |
ptx/SPDRIVERS |
edb Debugger |
ptx/EFS |
ptx/SVM |
Encryption |
ptx/ITX |
ptx/SYNC |
FC Switch |
ptx/JSE |
ptx/TCP/IP |
NUMA Online Diagnostics Dispatcher |
ptx/LAN |
ptx/X.25 |
ptx/AGENT |
ptx/LICENSE |
ptx/XWM |
ptx/ATM |
ptx/NFS |
Public Software |
ptx/BaseComms |
ptx/PDC |
SequentLINK |
ptx/C++ |
The console software must also be upgraded.
The new product cfwdl-Compatible Firmware Bundle must be installed.
If the host is using any of the CommandPoint products, you must also install the new product CommandPoint Base.
Most layered products require that DYNIX/ptx V4.6.1 be installed on your system. Certain layered products also require that other layered products be installed. Table 1-5 lists those dependencies.
When you select a product for installation, ptx/INSTALL verifies that other products required by that product have also been selected for installation. It also determines whether the products currently on the system are compatible with the products being installed.
Layered Product |
Dependencies |
CommandPoint Admin |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP, ptx/JSE, ptx/XWM, CommandPoint Base |
CommandPoint Base |
ptx/XWM |
CommandPoint Clusters |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP, ptx/CLUSTERS, ptx/CTC, CommandPoint Base |
CommandPoint SVM |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP, ptx/JSE, ptx/SVM, ptx/XWM, CommandPoint Base |
ptx/AGENT |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP |
ptx/ATM |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP, ptx/EES |
ptx/CFS |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP, ptx/EFS, ptx/CLUSTERS |
ptx/CLUSTERS |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP |
ptx/CTC |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP, ptx/CLUSTERS |
ptx/EES |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP |
ptx/ITX |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP, ptx/SYNC, ptx/X.25 |
ptx/JSE |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP, ptx/XWM |
ptx/LAE |
ptx/Base_Comms, ptx/TCP/IP |
ptx/LAN |
ptx/Base_Comms |
ptx/LICENSE |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP |
ptx/NFS |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP |
ptx/PDC |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP |
ptx/SNA 3270 Terminal Emulator |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP, ptx/XWM |
ptx/SNA APPC |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP |
ptx/SNA LU6.2 |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP |
ptx/SNA PU2.1 Base Server |
ptx/Base_Comms, ptx/SYNC and/or ptx/LAN |
ptx/SNA RJE (3770) |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP |
ptx/SNA SDLC & LLCI |
ptx/Base_Comms, ptx/SYNC and/or ptx/LAN |
ptx/TCP/IP |
ptx/Base_Comms, ptx/LAN |
ptx/XWM |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP |
ptx/XWM Contributed |
ptx/Base_Comms, ptx/LAN, ptx/TCP/IP, ptx/XWM |
ptx/X.25 |
ptx/Base_Comms, ptx/LAN, ptx/SYNC |