MainframeKit

2063

MQRC_SECURITY_ERROR (X'080F')MQ REASON CODE

A security error occurred while checking the call, coming from the security manager, AMS, LDAP or token checks, rather than a simple no-access.

MOST LIKELY

On z/OS bindings, a Java or JMS program passed a user name longer than 8 characters or a password longer than 100.

FIRST CHECK

Note the error from the security manager and pass it to the security administrator.

TRY IT ▸

MainframeKit assistant

What it means

2063 is different from 2035. With 2035, the check worked and said no. With 2063, the security check itself ran into an error. Typical sources are the external security manager on z/OS, Advanced Message Security setup, an LDAP server used for connection authentication, or a token setup problem.

Typical causes

  • On z/OS bindings, a Java or JMS program passed a user name longer than 8 characters or a password longer than 100.
  • The external security manager on z/OS returned an error.
  • AMS is not set up right: missing or invalid certificate, or a bad policy.
  • The queue manager cannot reach its LDAP server, or LDAP returned an error.
  • Token authentication is set up wrongly on the queue manager.

How to fix it

  1. Note the error from the security manager and pass it to the security administrator.
  2. On z/OS, check user name and password lengths, and the queue manager and AMS job logs.
  3. For AMS, check certificates, policies and SYSTEM.PROTECTION.ERROR.QUEUE.
  4. For LDAP, run DISPLAY QMSTATUS to see the LDAP connection state and read the error log.

Example

Illustrative only; names and values are invented.

MQCONNX failed  CompCode=2  Reason=2063  QMgr=QM01