Execute SQL Statements

Migration Information › Execute SQL Statements

Execute SQL Statements

You must now execute special sets of SQL statements to modify some of the DB2 objects used by the CA Repository. These statements are contained in upgrade statement files, which you can run from an option on the Installation Upgrade Customization Menu.

The purpose of these files is as follows:

File	Contains Statements That ...
1	Create view, primary key and foreign key for the DBX_WORKSTATION_D table. Create views for Webstation Option
2	Create additional indexes for elements and workstation table Create tablespace and table 'TEMP_SUBTYPES'
4	Create History tables and Triggers for the text, cross reference and workstation cross reference tables. NOTE: If you have created History tables in r7 you can skip executing the DDL in this file.
10	Add APPREQ information to DBX SYSTEM table.
19	Add new datatype NVARCHAR,NCHAR to DBX DDL ELEMENTS table. The DDL will set the datatype to NVARCHAR and NCHAR where it is currently USER and the picture clause is nvarchar, nchar, NVARCHAR or NCHAR.

To execute the statement files

At the Installation Upgrade Customization Menu, select option 3 SQL.
The Execute Release Statements screen appears.
Enter values into the fields as follows:
- Release Statement File
  Specify 1.
- Set SQLID to
  The SQLID you want to use when creating the DB2 objects. If you enter a value in this field, a SET CURRENT SQLID statement is added to the beginning of the DB2 statements.
- Edit or Submit
  Specify E.
- Save Output
  Specify Y to save the generated JCL in the partitioned data set specified in Output Data Set (below).
  
  Specify N to discard the JCL after submission.
- Output Data Set
  The fully qualified name (without quotation marks) of the partitioned data set you want to use to save the JCL that this step generates. Ensure that you change the names if you do not want to overwrite any previously saved JCL.
- Batch Job Card
  The batch Job statement you want included with the JCL stream generated by this procedure. Any of these fields left blank defaults to a JCL comment (//*).
Press Enter to generate the JCL.
Check the generated JCL before submission and correct any conflicts with your system environment.
Submit the job and review the results for successful completion codes (0). Errors you may encounter are listed in the following table.

Error	Occurs when	And can be resolved by
+100	No rows are found.	Ignore this error.
+162	A tablespace is in check pending status.	Removing the check pending status from the tablespace. For information, see the DB2 documentation or contact your DB2 DBA.
+541	Constraint is a duplicate.	Ignore this error if the referential constraint WKSN$ID exists.
+562	A grant is ignored because the grantee already has the requested privilege.	Ignore this error.
-454	The create function already exists.	Ignore this error.
‑601	The object already exists.	Ignore this error.
-624	Table already contains constraint.	Ignore this error if the DBX_WORKSTATION_D table already contains a primary key.

Investigate any other errors with CA Technical Support.

Press PF3 once to return to the CA Repository for z/OS Execute Release Statements panel.
Repeat Steps 2 through 5. When setting up the parameters for Copy Members to Custom Libraries, change the value of the Release Statement File from:
1. 1 to 2
2. 2 to 4
3. 4 to 10
4. 10 to 19
Press PF3 twice to return to the Installation Customization Menu.

Email CA about this topic