conflicting messages in xmanager start-up

Document ID : KB000093130
Last Modified Date : 09/05/2018
Show Technical Document Details
Issue:
My startup specifies xman=0004 - and this appears to be confirmed by PXM0410 XMANAGER MSLOGGER INIT ENTERED XMID=0004 PXM0411 XMANAGER MSLOGGER INIT COMPLETE XMID=0004 but yet later in the startup user sees SETUP00 The XMAN connection will use XMANID(0000) (it used to say 0001 until i deleted the line from setup00. who is telling the truth?? if i am running with xmanid 0004, i would prefer to NOT see a message that suggests otherwise. Also, we are not licensed for PDA - yet i see messages at startup:
"PDA Informational message that one or more parm keywords were not found. Return code set minimally to 4. Parmlib member possibly from previous release and has not been updated". User tried deleting the member (different message) and then just creating a blank member (back to same msg) - how can he stop this message from appearing??
Resolution:
The xmanager log user sent us showed the xmanid in use is XMID=0004.which is his TEST PDT/PSA/TT environment. The STATUS command in this environment was going to confirm that but user couldn't issue it based on their shop policies.
The SETUP00 The XMAN connection will use XMANID(0000)
PDA Informational message that one or more parm keywords were not found. Return code set minimally to 4. Parmlib member possibly from previous release and has not been updated. ... is coming from healthcheck. The Healthcheck is done at the LPAR level. Since you have more than one xmanager, you'll see this kind of messages.