Execute Preload SQL Statements

Migration Information › Execute Preload SQL Statements

Execute Preload SQL Statements

You must now execute the SQL statement prior to loading new control data. This statement is contained in the upgrade statement file, which you can run from an option on the Installation Upgrade Customization Menu.

The purpose of the file is as follows:

File	Contains Statements That ...
6	Update OO Model objects Update Entity 27521 RETURNS. Change Association to Relationship. Set Target object to 27509 Update Entity 27504 CL IN FL. Change Association To Relationship. Set Source object to 27517 Update Entity 27507 CL MB FU. Change Association To Relationship. Set Source object to 27517
11	Install WSO DB2 Objects. Note: New WSO tables in r7.2 have been added
17	Add items new to r7.2 Add APPROVAL REQUIRED flag to ENT TYPE DESC Table Add approval table Add new stored procedures

File

Contains Statements That ...

Update OO Model objects

Update Entity 27521 RETURNS. Change Association to Relationship. Set Target object to 27509

Update Entity 27504 CL IN FL. Change Association To Relationship. Set Source object to 27517

Update Entity 27507 CL MB FU. Change Association To Relationship. Set Source object to 27517

Install WSO DB2 Objects.

Note: New WSO tables in r7.2 have been added

Add items new to r7.2

Add APPROVAL REQUIRED flag to ENT TYPE DESC Table

Add approval table

Add new stored procedures

To execute the statement files

At the Installation Upgrade Customization Menu, select option 3 SQL.
The Execute Release Statements screen appears.
Enter field values as follows:
- Release Statement File
  Specify 6.
- 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 field 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 as follows.

Error	Occurs when	And can be resolved by
+562	A grant is ignored because the grantee already has the requested privilege.	Ignore this error.
‑601	The object already exists.	Ignore this error.

Investigate any other errors with CA Technical Support.

Press PF3 twice to return to the Installation Customization Menu.
Repeat Steps 2 through 5. When setting up the parameters for Step 2,
change the value of the Release Statement File from:
1. 6 to 11
2. 11 to 17
Press PF3 twice to return to the Installation Customization Menu.

Email CA about this topic