Problems with USS after upgrade to 12.2 - the parameter group fails with
N12802 SYSPARMS OPERAND UNIXATH=/tmp IS INVALID OR OUT OF RANGE.
even though the path is correct as shown in the HOME directory of the ACF2 definition for the Netmaster userid.
Release : 12.2
Component : CA NetMaster Network Management for TCP/IP
Maintenance mismatch between the CC2DPLD and the EXEC libraries/ VSAM files.
Cycling with the correct CC2DPLD in both the region and the NETMSSI corrected the problem.
Additional symptoms experienced:
1) Review of the /tmp directory should show these entries
-r-xr-xr-t 1 CSNM ADMNDGRP 0 May 03 21:04 NM129
srw-rw-rw- 1 CSNM ADMNDGRP 0 May 08 06:10 netmaster.unix.01CB
but contains only entries for other products.
2) The ZFS parameter group points to /u/usrs/CA/NETM
The filesystem is mounted, but while the ZFS ILOG does not show errors, it is incomplete.
Several messages are missing.
Time Log Data
00.02.07 IAIN0126 Processing for parameter group $NM ZFS started
00.02.07 HFS SET ROOT= /u/usrs/CA/NETM
00.02.07 N10001 HFS Root: /u/usrs/CA/NETM
00.02.07 IAIN0178 Processing for parameter group $NM ZFS ended. Status is Completed.
**END**
5) There are anomalies in the UNIX SYSPARMS.
When issuing SHOW SYSPARMS=UNIX from the NetMaster region, customer's environment shows
Show sysparms=unix
N22201 SYSPARM VALUE SOURCE NAME/USER LINKNAME
N22202 UNIXAPID OMVSAPPL DEFAULT -
N22202 UNIXBUSR NO DEFAULT -
N22202 UNIXDBUG NO CUSTOMIZER USS
N11907 *END*
Broadcom environment shows
Show sysparms=unix
N22201 SYSPARM VALUE SOURCE NAME/USER LINKNAME
N22202 UNIXAPID OMVSAPPL DEFAULT -
N22202 UNIXDBUG NO CUSTOMIZER USS
N22202 UNIXPATH /tmp CUSTOMIZER USS
N11907 *END*
3) Review of the activity log shows these messages every minute
00.58.37 N3AN90 TCP/IP SERVER REGISTER FAILED. PATH: /tmp/solve RC:8 FB: 0 ERR
00.58.37 N3AE01 37 - EADDRINUSE - ADDRESS ALREADY IN USE
4) The region and NETMSSI show a LEVEL of 1904. That is base level through June 2020.
Maintenance levels of Jun 30th 2020 and beyond should show LEVEL 00 or higher - it is 2 digits instead of 4.
5) Checked two modules from SO15228 to verify fixes are on that move NM129 out of the CC2DZFS.
$$SYSPRO APAR $NMINWIZ checks a module from the fix in the CC2DEXEC library.
The result is correct.
Name APAR Type Ddname Dataset
$NMINWIZ SO15228 OML COMMANDS <hlq>.D81.CC2DEXEC
SHOW PTF - NM0002u2 from that same PTF for a module contained in the CC2DPLD shows
sh ptf=nm0002u2
N14510 PTF LEVEL FOR MODULE NM0002U2 IS SO05668 VER: 0801 ADT: 2018/09/27-20.39
So the maintenance levels in the EXEC files are higher than those in the CC2DPLD.