NetMaster - $NM USS parameter group fails with N2U301 UNIX Server spawn() failed errno=111

book

Article ID: 195515

calendar_today

Updated On:

Products

CA CMDB for z/OS CA NetSpy Network Performance CA NetMaster Network Automation CA NetMaster Network Management for SNA CA NetMaster Network Management for TCP/IP CA NetMaster File Transfer Management CA SOLVE

Issue/Introduction

We are upgrading our Network Management region from Netmaster 12.2. INC03 level to Netmaster 12.2. GA level. 
During the startup the $NM USS parameter group issues a USS command to validate the OMVS setup within the region . 
This always fails - with the messages below: 

IAIN0126 Processing for parameter group $NM USS started                      

IAIN0122 Parameter UNIXDBUG not set, can only be set during phase INIT       

IPDI5200 TCP/IP Details for NWKOPD02 using IBM z/OS Communications Server    

IPDI5270 Checking UNIX System Services Interface for MXNETW1                 

BAINWI49 Region user MXNETW1 has OMVS home /u/MXNETW1                        

IPDI5272    Checking access to /tmp using /tmp/netmaster.unix.testpath.NWKOPD0

IPDI5276    Access to /tmp verified successfully                             

N2U301 UNIX Server spawn() failed errno=111 reason code=0B1B-011F path=/u/MXNETW1/NM129

IPDI5277    Error: UNIX environment could not be established                 

IPDI5278    Error: UNIX OPEN failed, RC/FDBK=8/8, reason=UNIX server start failed

Environment

Release : 12.2

Component : CA NetMaster Network Management for TCP/IP

Resolution

Regarding errors………..
N2U301 UNIX Server spawn() failed errno=111 reason code=0B1B-011F path=/u/MXNETW1/NM129
IPDI5277 Error: UNIX environment could not be established
IPDI5278 Error: UNIX OPEN failed, RC/FDBK=8/8, reason=UNIX server start failed

Run a SELFTEST UNIX
Also run a  SELFTEST UNIXBSYS

Reading the message HELP for N2U301. The important part being..... 
If copying files from the install zFS using the UNIX cp command specify the -p option to preserve special attributes.

Use the OMVS ls -l to check the contents of the path. NM129 entry should look like this -

-r-xr-xr-t 1 STCSYS 38 6136 Aug 23 2017 NM129

The t on the end of the attribute list is the important part.


SELFTEST UNIXBSYS command shows:

IPDI5270 Checking UNIX System Services Interface for MXNETW1
BAINWI49 Region user MXNETW1 has OMVS home /u/MXNETW1
IPDI5272 Checking access to /tmp using /tmp/netmaster.unix.testpath.NWKOPD02
IPDI5276 Access to /tmp verified successfully
IPDI5277 Error: UNIX environment could not be established
IPDI5278 Error: UNIX OPEN failed, RC/FDBK=8/8, reason=UNIX server start
failed
IPDI5299 TCP/IP details complete, 2 errors and 0 warnings.
IPDI529A For more help, place cursor on warning/error message and press F1


D02>ls -l
total 16
dr-xr-xr-t 2 MXNETW1 MXNETW 8192 Mar 10 12:49 NM129

-----
The ls -l output attributes start with 'd'. A leading 'd' indicates a directory and not a file. This would explain the 011F errnojr.
Is this the install path? Don't know how you would get a directory instead of a file. Was a Unix 'cp' used to copy from an install path?

Answer to this error:
Change NM129 to a file instead of a directory - and the $NM USS parameter group will work fine.