CONFLICTING MESSAGES IN XMANAGER START UP
search cancel

CONFLICTING MESSAGES IN XMANAGER START UP

book

Article ID: 93130

calendar_today

Updated On:

Products

RC Compare for DB2 for z/OS Database Analyzer for DB2 for z/OS Fast Unload for DB2 for z/OS Fast Check for DB2 for z/OS Fast Index for DB2 for z/OS Rapid Reorg for DB2 for z/OS Database Management for DB2 for z/OS - Administration Suite Database Management for DB2 for z/OS - Performance Suite Database Management for DB2 for z/OS - Recovery Suite Database Management for DB2 for z/OS - SQL Performance Suite Database Management for DB2 for z/OS - Utilities Suite

Issue/Introduction


The startup specifies xmanid=0004 - and this appears to be confirmed by the following message: 
PXM0410 XMANAGER MSLOGGER INIT ENTERED XMID=0004 PXM0411 XMANAGER MSLOGGER INIT COMPLETE XMID=0004 but yet later in the startup  the following is seen:
SETUP00 The XMAN connection will use XMANID(0000).
Who is telling the truth?
Also, though PDA is not licensed, the following messages displayed at the startup of Xmanager:
"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".
How can these  be stopped from appearing?

Environment

Release:
Component: PXM

Resolution

The xmanager log showed the xmanid in use is XMID=0004 which is from the  TEST PDT/PSA/TT environment. The STATUS command in this environment should confirm that but was not provided.

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 there are more than one xmanager,  these kind of messages are expected.