IBM Support

Why am I seeing the error message IST1927I with RC=156 and RSN=0B0C00FB?

Question & Answer


Question

Issuance of an F NET,VTAMOPTS,SNAMGMT=YES command, to specify that the ISTMGCEH subtask be attached and the Network Management Interface socket be opened for use, resulted in the display of the following messages: 

 IST097I MODIFY ACCEPTED                                                 
 IST223I MODIFY COMMAND COMPLETED                                        
 IST1926I SNAMGMT SERVER IS UNABLE TO ACCEPT CONNECTION REQUESTS 648     
 IST1927I SOCKET MKDIR CALL FAILED - RC = 156 RSN = 0B0C00FB             
 IST314I END                                                             
 IST1926I SNAMGMT SERVER IS UNABLE TO ACCEPT CONNECTION REQUESTS 649     
 IST1927I SOCKET SOCKET CALL FAILED - RC = 156 RSN = 0B0C00FB            
 IST314I END                                                             
 IST1926I SNAMGMT SERVER IS UNABLE TO ACCEPT CONNECTION REQUESTS 650     
 IST1927I SOCKET SELECT CALL FAILED - RC = 156 RSN = 0B0C00FB            
 IST314I END                                                             
 IST1930I SOCKET CLOSED BY SNAMGMT SERVER SUBTASK

Answer

In message IST1927I, the RC (return code) 156 indicates a Process Initialization error and the reason code 0B0C00FB indicates that the user ID is not authorized to use OMVS.

Many TCP/IP Services components in z/OS Communications Server use z/OS UNIX services in both the native MVS environment and in the z/OS UNIX environment. For example, all TCP/IP socket APIs and TCP/IP applications (whether they are provided by z/OS Communications Server, z/OS, other IBM and non-IBM products, or written by users) make use of z/OS UNIX services.

Use of z/OS UNIX services requires a z/OS UNIX security context, referred to as an OMVS segment, for the user ID associated with any unit of work requesting these services. In other words, most user IDs requiring access to TCP/IP functions now require an OMVS segment to be defined in Resource Access Control Facility (RACF).

Several tasks must be performed to define everything properly, including authorizing the user ID to use OMVS .

NOTE: The tasks, examples, and references in this information assume that you are using the z/OS Communications Server Security Server (RACF). If you are using a security product from another vendor, read the documentation for that product for instructions on task performance.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Component":"","Version":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Product Synonym

ZOSCS COMMSERVER

Document Information

Modified date:
26 July 2016

UID

dwa1290465

Page Feedback