Sysview for DB2 encounters PTT1130E UNAUTHORIZED REQUEST PLAN SECURITY CHECK FAILED FOR PLAN PTTF1900 RC=00000004-00F30034 attempting to cancel threads
Article ID: 131908
Updated On:
Products
CA Bind Analyzer for DB2 for z/OS
CA Detector
CA SQL-Ease for DB2 for z/OS
CA Sysview Performance Management Option for DB2 for z/OS
CA Database Detector for DB2 for z/OS
CA Plan Analyzer for DB2 for z/OS
CA Subsystem Analyzer for DB2 for z/OS
Issue/Introduction
Sysview for DB2 encounters PTT1130E UNAUTHORIZED REQUEST. PLAN SECURITY CHECK FAILED
FOR PLAN PTTF1900 RC=00000004-00F30034 when attempting to cancel threads.
FOR PLAN PTTF1900 RC=00000004-00F30034 when attempting to cancel threads.
Cause
The Sysparm parameter Thread-Cancel-Authid=User (default) was being used, but the particular TSO ID's
had not been granted execute authority on the PTTFxxxx plan. When Thread-Cancel-Authid=DC was stated
the 8 byte IDB2 DC UserID was granted execute authority on all of the PTT plans (including PTTFxxxx),
but without the ptf SO00484 applied only the first 7 bytes of the ID were being used to issue the cancel,
and that ID had not been granted execute authority on the PTTFxxxx plan.
had not been granted execute authority on the PTTFxxxx plan. When Thread-Cancel-Authid=DC was stated
the 8 byte IDB2 DC UserID was granted execute authority on all of the PTT plans (including PTTFxxxx),
but without the ptf SO00484 applied only the first 7 bytes of the ID were being used to issue the cancel,
and that ID had not been granted execute authority on the PTTFxxxx plan.
Environment
Release:
Component: IDB2
Component: IDB2
Resolution
With Thread-Cancel-Authid=DC specified, and without the application of IDB2 ptf SO00484 to support 8 character Userids,
it was necessary to use the first 7 bytes of the DC's ID when granting execute authority on plan PTTFxxxx.
it was necessary to use the first 7 bytes of the DC's ID when granting execute authority on plan PTTFxxxx.
Feedback
Powered by
