Why do I receive a -553 doing a DB L using a secondary SQLID?
Article ID: 38324
Updated On:
Products
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
Component: RCQ
Resolution
Feedback
Yes
No
Powered by
