J06.07 Software Installation and Upgrade Guide

If the CLIM is in the STARTED state, you can determine the CLIM software version by using OSM
Low Level Link, OSM Service Connection or by entering:
SCF-> VERSION CLIM $ZZCIP.clim-name
If the CLIM is not in the STARTED state, you can use the CLIMCMD command with the Linux cat
subcommand by entering:
TACL>climcmd clim-name cat /etc/vproc
Multiple versions of CLIM software are allowed on a system as long as all CLIMs have CLIM SPRs
that are compatible with the host RVU. See the NonStop CLuster I/O Module (CLIM) Software
Compatibility Reference for all CLIM and host RVU compatibility information.
See the Cluster I/O Protocols (CIP) Configuration and Management Manual for troubleshooting
tips about identifying an incompatibility in CLIM and host CIP software.
J06.05
AF_UNIX Release 2 Migration and Fallback
Migrating to AF_UNIX Release 2
AF_UNIX Release 2 software completely replaces earlier versions of AF_UNIX Release 1 software.
There is no application migration required for AF_UNIX Release 2. The AF_UNIX Release 1
semantics remain available along with the AF_UNIX Release 2 semantics. AF_UNIX Release 1
semantics are the default semantics. You can choose which semantics to use either programmatically
or by setting the Guardian DEFINE =_AFUNIX_PROCESS_NAME.
AF_UNIX Release 2 software replaces the $ZPLS process pair with a per-processor process, $ZLSnn,
where nn is the processor number.
When migrating to AF_UNIX Release 2 (J06.05 and later RVUs):
• If you start $ZPLS in a startup script using the SCF START SERVER command, and failure to
start $ZPLS causes the script to be aborted and steps following the failing one to be omitted,
modify the script to remove the command to start $ZPLS.
NOTE: In AF_UNIX Release 2, any changes to the #ZPLS attributes will have no effect.
• If you use the STARTOSS utility to start OSS processes, modify the
target-volume.ZOSSINS.OSSINFIL file by changing the line
SERVER #ZPLS
to
* SERVER #ZPLS
NOTE: target-volume is normally $SYSTEM.
NOTE: #ZPLS cannot be deleted from ZOSSSERV but can be deleted from OSSINFIL.
Commenting out the #ZPLS statement from the OSSINFIL prevents the STARTOSS utility from
issuing an error during execution.
The $ZLSnn processes are started automatically when the processors start; do not add them to any
startup or shutdown scripts.
32 Installation, Migration, and Fallback Considerations for This RVU