Execute DB2 Catalog Customization Tasks
Execute the DB2 catalog customization tasks on each DB2 subsystem where the productgroup are installed after you have executed the product-specific customization tasks.
Execute the DB2 catalog customization tasks on
eachDB2 subsystem where the
CA Database Management Solutions for DB2 for z/OSare installed after you have executed the product-specific customization tasks.
These customization tasks require and interact with the DB2 subsystems that you identified in the SETUP global parmlib members. DB2 SYSADM authority is required.
Review the instructions for each DB2 catalog customization task before execution. In some instances, it might not be necessary to execute a task, especially when you are applying maintenance.
We recommend that you have at least two people available to execute the DB2 tasks. If a problem is encountered on one subsystem during execution, the second installer can submit and verify the DB2 tasks while the other installer tracks down problems and performs subsystem checkout.
To prevent contention errors like MIM1099, only one user at a time can access the Executing DB2 Tasks online dialog for a specific environment.
Follow these steps:
- Access the Post-Install Tailoring menu.
- Select option3(Tasks - Execute DB2 catalog customization tasks) and press Enter.A list of defined DB2 subsystems appears on the Select DB2 Subsystems panel.
- Select one or more DB2 subsystems and press Enter. (Select all subsystems using the ALLS command. Reorder rows using the SORT SSID (by DB2 subsystem) or SORT SETUP commands.)Execute the DB2 tasks on each of the listed subsystems.
- Review the instructions for each DB2 task using the V line command or ALLV command. The instructions describe when to execute the task and provide other useful information. In some instances, execution is not required.
- Select a task or multiple tasks and press Enter.For base installs, all tasks are typically executed. For maintenance upgrades, typically only the install (INS) related tasks are executed.The JCL for each DB2 task is generated in a member named with the subsystem ID and a task number.
You can change the member names if needed; however, if you are performing a distributed installation, retain the numerical order of the suffixes to ensure proper job submission order at the remote site.To prevent the member names from being overwritten when a subsystem name is used on multiple systems and you are using the same output data set, we recommend that you copy the members or target a different output data set before generating new jobs.
- If you selected multiple subsystems, the task appears for each subsystem selected.
- If additional information is needed to create the JCL for the task, you are prompted to provide this information before the JCL is submitted.
- Submit the generated JCL for execution.You can browse and edit the generated JCL before submission.The member name where the job is stored in thehlq.CDBASAMP library appears in the Member field for the currently selected DB2 subsystem. If the job has been generated for more than one subsystem, MULTIPLE appears instead. N/A appears if the task is informational and does not generate a JCL member.To reinitialize the task completion status, select a subsystem and specify RESET on the command line. If you change the product selection list after some DB2 tasks have already been processed, the task completion status will no longer be synchronized with the list of products.