This is part of the larger task of setting up security on z/OS.
The user ID of the person running the DB2 configuration jobs needs UPDATE access to the component PDSE, READ/EXECUTE access to the installation directory, and READ/WRITE/EXECUTE access to the broker-specific directory.
A user needs SYSADM or SYSCTRL authority to run the DB2 configuration jobs.
table_owner.table_namewhere table_owner is known as the table owner.
select * from SYSIBM.SYSTABLES; select * from SYSIBM.SYSSYNONYMS; select * from SYSIBM.SYSDATABASE;and resolve any problems.
SET CURRENT SQLID='WMQI'; select * from SYSIBM.SYSTABLES; select * from SYSIBM.SYSSYNONYMS; select * from SYSIBM.SYSDATABASE;and resolve any problems (WMQI is the name of the group). You might need to connect the TSO user IDs of the DB2 administrators to the group.
If you have a unique group for each broker (and not a unique started task user ID), the started task user ID must be connected to the group for the ODBC request set currentsqlid to work successfully.
The DB2 administrator user ID must have access to one of the programs DSNTEP2 or DSNTIAD, or equivalent.
RLIST DSNR *
The started task user ID needs EXECUTE authority to the DSNACLI plan or equivalent.
The DB2 subsystem started task user ID needs authority to create data sets with the high level qualifier specified in the DB2_STOR_GROUP_VCAT value.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ae14070_ |