Troubleshooting
Problem
On some LPARs, Network Security Server Daemon (NSSD) messages seen at NSSD initialization are prefixed by the USS message prefix BPXM023I. (On most LPARs, NSSD messages are not prefixed with BPXM023I). The BPXM023I prefix to the NSSD messages may impact started task automation.
Symptom
BPXM023I (NSSD) EZD1359I NETWORK SECURITY SERVICES (NSS) SERVER RELEASE CS V1R12
SERVICE LEVEL CS110301 CREATED ON Mar 1 2011
BPXM023I (NSSD) EZD1357I NETWORK SECURITY SERVICES (NSS) SERVER INITIALIZATION SEQUENCE HAS BEGUN
BPXM023I (NSSD) EZD1373I NSS IPSEC DISCIPLINE ENABLED
BPXM023I (NSSD) EZD1373I NSS XMLAPPLIANCE DISCIPLINE DISABLED
BPXM023I (NSSD) EZD1353I NSS SERVER CONFIG PROCESSING COMPLETE USING FILE filename
BPXM023I (NSSD) EZD1358I NSS SERVER INITIALIZATION SEQUENCE HAS COMPLETED
Diagnosing The Problem
Some NSSD messages that are seen at NSSD initialization, such as EZD1373I, are prefixed by the USS message prefix BPXM023I because, on those LPARs, the NSSD ID is not defined with READ access to the BPX.CONSOLE CLASS(FACILITY).
In the z/OS UNIX Programming Assembler Callable Services Reference, see these notes for __console() service:
1. An invoker is deemed to have appropriate privileges for this service if the BPX.CONSOLE resource in the FACILITY class is defined and the invoker is permitted to that resource, or if the invoker is running with an effective UID of 0.
2. If the invoker does not have appropriate privileges, a message ID (BPXM023I) and the invoker's login name are prefixed to the specified message text.
Resolving The Problem
Define the NSSD ID with READ access to BPX.CONSOLE CLASS(FACILITY).
For more information, see "Authorization" in z/OS UNIX System Services Programming: Assembler Callable Services Reference .
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21574447