Override plan and package owner from default TSO ID running the Db2 tools ssid0002 Post Install bind job
Article ID: 47087
Updated On:
Products
Issue/Introduction
When binding all packages and plans in the Database Management for Db2 for z/OS Post Install ssid0002 job, is there a straightforward way to designate a userid,
other than the user submitting the bind job, to be owner of the packages and plans in the Db2 catalog.
Resolution
Use the PLANOWN parm in the SETUPxx member of the hlq.CDBAPARM library.
There is one for each SSID entry.
e.g. at the bottom of each SSID entry in SETUPxx.
SSID (ssid)
SSIDDESC (DB2 12)
SSIDVERF (V12R1M500)
SSIDVERC (V12R1M500)
.
.
.
.
.
DATABASE (PTDB)
PLANOWN (authid) <-----------
DSGROUP ()
The Post Install bind job ssid0002 will generate Bind control cards that include an OWNER parameter which is populated with the value specified in the PLANOWN parm field.
On the online screens used to generate the Post Install where SETUPxx is modified this value can be seen as "Bind Owner" for each specific SSID.
Type the information in the fields below.
STOGROUP Name.............> PTSG
STOGROUP Volume...........> '*'
Database Name.............> PTDB
Bind Owner................> authid (Optional) <--------------------------------
Data Sharing Group Name...> (If part of a Data Sharing Group)
Field: Bind Owner
Description: Enter the owner of the DB2 products' plan names.
Note that if PLANOWN is blank like this PLANOWN () , then the plan owner becomes the ID of the person running the BIND job which may not be what you want at all.
Think about what authid should be the plan owner at your site for all of the Database Management for Db2 for z/OS tools.
It should be a group ID that has SYSADM that is not tied to one person specifically in case that person leaves your organization.
Feedback
