Why do I receive a -553 doing a DB L using a secondary SQLID?

book

Article ID: 38324

calendar_today

Updated On:

Products

CA RC Compare for DB2 for z/OS

Issue/Introduction

Question:

Why do I receive a -553 doing a DB L report and the SQLID on the main panel has an SQLID which is a secondary authorization ID;

DSNT408I SQLCODE = -553, ERROR: SECID SPECIFIED IS NOT ONE OF THE VALID AUTHORIZATION IDS FOR REQUESTED OPERATION 

 

Answer:

In order to use Secondary Authorization ID's, the DB2 exit [email protected] must be customized to allow for secondary authorization ID usage

as documented by IBM.

 

 

 

Environment

Release:
Component: RCQ

Resolution

IBM DB2 V12 doc on [email protected]:

https://www.ibm.com/support/knowledgecenter/SSEPEK_12.0.0/seca/src/tpc/db2z_connectionsignonroutine.html