Xnet / PXNPROC Misleading OEVB003 error message, followed by ICH408I and IRR013I INVALID PASSWORD messages
Article ID: 191738
Updated On:
Products
Bind Analyzer for DB2 for z/OS
SQL-Ease for DB2 for z/OS
SYSVIEW Performance Management Option for DB2 for z/OS
Plan Analyzer for DB2 for z/OS
Subsystem Analyzer for DB2 for z/OS
Database Management for DB2 for z/OS - Performance Suite
Database Management for DB2 for z/OS - SQL Performance Suite
Insight Performance Monitor for DB2 UDB for z/OS
Issue/Introduction
It is documented in the hlq.SYSVDB2.CDBAPARM(PXNPARM)that the OEVN003 health check summary message, could report a false PROBLEM with the passticket configuration (*PTKT*).
So, we are using a USERID as the authorized ID to run all the Broadcom STC's and it is defined as NOPASSWORD.
We have set the procedure, as shown below, to avoid this misleading/false message:
* To eliminate the false reporting of passticket problems, update the
* OPSPTCKTID parameter below, substituting a valid user ID for
* "mytsoid", and then removing the asterisk from column 1 to activate
* the parameter statement. As the administrator of this parameter
* member, it is safe to specify your own user ID in the OPSPTCKTID()
* parameter.
*----------------------------------------------------------------------
OPSPTCKTID(CAUSER)
*NOOPSU2X
NOOPSOFA
*----------------------------------------------------------------------
However, we are continuing to see the misleading/false error message, followed by the error messages below:
OEVN003I OPSEVENT-Status: PROBLEM Reason: Xnet TCPok XMGRok *PTCKT* PXNok U2Xok IDB2ok NOOFA
ICH408I USER(USERID ) GROUP(STC ) NAME(USERID FOR Broadcom TASKS )
LOGON/JOB INITIATION - INVALID PASSWORD
IRR013I VERIFICATION FAILED. INVALID PASSWORD GIVEN.
We then tried to fix this problem using a regular TSO UserID in the OPSPTCKTID(USERID)and it did fix the problem. However we cannot have anyone's TSO UserID in a system PROC. How should we address this?
So, we are using a USERID as the authorized ID to run all the Broadcom STC's and it is defined as NOPASSWORD.
We have set the procedure, as shown below, to avoid this misleading/false message:
* To eliminate the false reporting of passticket problems, update the
* OPSPTCKTID parameter below, substituting a valid user ID for
* "mytsoid", and then removing the asterisk from column 1 to activate
* the parameter statement. As the administrator of this parameter
* member, it is safe to specify your own user ID in the OPSPTCKTID()
* parameter.
*----------------------------------------------------------------------
OPSPTCKTID(CAUSER)
*NOOPSU2X
NOOPSOFA
*----------------------------------------------------------------------
However, we are continuing to see the misleading/false error message, followed by the error messages below:
OEVN003I OPSEVENT-Status: PROBLEM Reason: Xnet TCPok XMGRok *PTCKT* PXNok U2Xok IDB2ok NOOFA
ICH408I USER(USERID ) GROUP(STC ) NAME(USERID FOR Broadcom TASKS )
LOGON/JOB INITIATION - INVALID PASSWORD
IRR013I VERIFICATION FAILED. INVALID PASSWORD GIVEN.
We then tried to fix this problem using a regular TSO UserID in the OPSPTCKTID(USERID)and it did fix the problem. However we cannot have anyone's TSO UserID in a system PROC. How should we address this?
Environment
Release : 20.0
Component : CA Insight Database Performance Monitor for DB for z/OS
Cause
The uid associated with Xnet needs to be a logon-able tso ID for passticket verification during the healthcheck. In lieu of specifying a valid TSO uid NOOPSPTCKT can
be specified in the pxnpam member.
be specified in the pxnpam member.
Resolution
Recommending NOOPSPTCKT in the XNET's PXNPARM parmlib member in lieu of the OPSPTCKTID parm.
Feedback
Yes
No
Powered by
