SQL/MX 3.2.1 Management Manual (H06.26+, J06.15+)

3. Use the DISPLAY USE OF command to identify which user modules are associated with this

object. See the similarity check criteria in the SQL/MX Programming Manual for C and COBOL

to determine if your changes are likely to cause similarly check to fail and force automatic

recompilation. If they will, you should SQL compile these modules after making the changes

to avoid expensive automatic recompilations at run time. SQL applications that are running

while you make these changes will still undergo automatic recompilation.

For more information about explicit and automatic recompilation, see the SQL/MX Programming

Manual for C and COBOL. For more information about using DISPLAY USE OF, see “Checking

Module Dependencies with DISPLAY USE OF” (page 226) and the SQL/MX Reference Manual.

4. Use the MODIFY utility to alter the partition. (See “Using MODIFY to Manage Table and Index

Partitions” (page 184).)

5. Revise the application source code as needed to reflect your changes to the database. Process

and compile the updated source file. For more information, see the SQL/MX Programming

Manual for C and COBOL.

For more information, see “Using MODIFY to Manage Table and Index Partitions” (page 184).

Altering SQL/MP Aliases

To alter an SQL/MP alias, use the ALTER SQLMP ALIAS statement.

You can change the physical name of an SQL/MP table to which an existing alias is mapped

using the ALTER SQLMP ALIAS statement.

For more information, see the SQL/MX Reference Manual.

Steps for Altering an SQL/MP Alias

1. Start an MXCI session. Enter a LOG command to initiate a log file for statements and commands

entered in this session. Keep the log for your records.

2. Determine the name of the SQL/MP alias you want to alter.