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

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

book

Article ID: 38324

calendar_today

Updated On:

Products

RC Compare for DB2 for z/OS

Issue/Introduction

 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 

 

 

.

 

 

 

Environment

Release:
Component: RCQ

Resolution

In order to use Secondary Authorization ID's, the DB2 exit DSN3@ATH must be customized to allow for secondary authorization ID usage

as documented by IBM

IBM DB2 V12 doc on DSN3@ATH:

routines-connection-sign