search cancel

Netmaster 12.2 showing IPDI5278 and IPDI5279 errors

book

Article ID: 112604

calendar_today

Updated On:

Products

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

Issue/Introduction

Bringing up Netmaster 12.2 and seeing this error in the log

IPDI5277 Error: UNIX environment could not be established
IPDI5278 Warning: UNIX command failed, RC/FDBK=8/5, reason=Unix call failed
IPDI5279 Warning: UNIX call failure: Call=connect, errno=129, errnojr=053B-006C

Cause

The 129 error is ENOENT , jrFileNotThere.
 

Environment

Release: SLOPFC00200-12.2-NetMaster-File Transfer Management
Component:

Resolution

Possible solutions:
1. The IEESYSAS has not built the UNIX path for the server – it’s the /tmp/netmaster.unix.aaaa file where aaaa is the NetMaster ASID. 
    Solution in this case is to - allow the Netmaster region STC userid READ/WRITE access to the /tmp directory 
                                             - ensure a userid is defined to the IEESYSAS  - see this section in the Release notes for details
                                               https://docops.ca.com/ca-netmaster-network-management-for-tcpip/12-2/en/release-notes#ReleaseNotes-EnhancedSupportforUNIXSystemServices(USS)Commands 



  2.  Ensure that the hlq.CC2DLINK is both in the LINKLST and APF authorized.

If you do SHOW UNIX=SERVER – You can see what the IEESYSAS address space is up to. 

To validate correct functionality of the server after making changes, go to the CMD screen in the Netmaster region and issue
SH UNIX=SERVER 

You should see something like
N2U701 UNIX Server ASID=019B State=UP APPLNAME=OMVSAPPL 
N2U702 EnvID Conversation State 
N2U703 00000148 CONNECTED 
N11907 *END*