With Version 3 Release 4 and later, you can specify a server name of up to 18 characters. See Choosing an Application Server Name.
Before Version 3 Release 4 an application program could only access one database. In Version 3 Release 4 and later, up to 36 application servers can be active at the same time in your VSE system.
To make use of this new facility, you must remove the SET XPCC command and use the SET APPCVM command. For details on this command, see Chapter 5, Operating the Online Support.
However, if you continue to access only one database, the SET XPCC command can still be used.
After migration, the database manager sets the application server default CHARNAME to ENGLISH, and sets the application server CCSID values as follows:
You can change the value of the default CHARNAME, which in turn determines the values for the three application server default CCSIDs. These four values are stored in the VALUE column of the SYSTEM.SYSOPTIONS catalog table. The corresponding values in the SQLOPTION column for these defaults are CHARNAME, CCSIDSBCS, CCSIDMIXED, and CCSIDGRAPHIC.
The value you choose for the default CHARNAME should accurately reflect the type of data that will be stored in the database: that is, the type of code page and character set that describes the data, and whether or not the database manager is to support DBCS characters or MBCS characters, or both. For more information, see Character Set Considerations at Startup, Determining CCSID Values, and CCSID Conversion. For a summary of the considerations for changing these values, see Considerations when changing default CHARNAME and CCSID.
After choosing your default CHARNAME, you must also set your CCSID values for character and graphic data that existed before the migration to Version 3 Release 4. The CCSID value of character and graphic data stored in tables that were created before Version 3 Release 4 are specified by the three other rows (with SQLOPTION value MCCSIDSBCS, MCCSIDMIXED and MCCSIDGRAPHIC) in the SYSTEM.SYSOPTIONS catalog table. The migration CCSID values (MCCSIDSBCS, MCCSIDMIXED, and MCCSIDGRAPHIC) are used for single byte, mixed, and graphic data that was created prior to Version 3 Release 4 and therefore does not have a CCSID associated with it. The database manager sets the migration CCSID values as follows:
If the code page and character set used to create the migrated data (that is, the data that was inserted into the database prior to Version 3 Release 4) is not CP/CS 37/697, these settings are not correct for your installation and must be changed. You can determine the CCSIDs for migrated data from the code page and character set that was used to generate the terminal controller where the data was entered.
For an example of how your choice of migration CCSID value affects the characters displayed, refer to page ***.
To determine if your database contains graphic or mixed data, issue the following query:
SELECT COUNT(*) FROM SYSTEM.SYSCOLUMNS
WHERE COLTYPE = 'GRAPHIC' OR
COLTYPE = 'VARGRAPH' OR
COLTYPE = 'LONGVARG' OR
SUBTYPE = 'M'
If the query returns a result of zero rows, the database contains neither graphic nor mixed data; a nonzero result indicates the number of columns in your database that do contain such data.
If your database contains only SBCS data (that is, the above query returns a result of zero) prior to Version 3 Release 4, the migrated CCSID values for mixed and graphic data (MCCSIDMIXED and MCCSIDGRAPHIC) must remain 0.
If the MCCSIDSBCS value of 37 is not correct for your installation, this must be changed to correspond to the code page and character set used to create the migrated data. For example, if the data was created with CP/CS 273/697 (GERMAN), the CCSID value you should use is 273. For a list of some of the SBCS CCSIDs and their character set and code page values, see Table 19.
The row that you must update for data in tables created before Version 3 Release 4 is:
Change the value in the VALUE column to the appropriate SBCS CCSID (for example, 273 for GERMAN). The following statements show how to update or insert the row using this value:
UPDATE SYSTEM.SYSOPTIONS SET VALUE = '273'
WHERE SQLOPTION = 'MCCSIDSBCS'
|
INSERT INTO SYSTEM.SYSOPTIONS VALUES
('MCCSIDSBCS', '273',
'DEFAULT CCSID FOR MIGRATED SBCS CHARACTER COLUMNS')
|
If your database contains graphic or mixed data prior to Version 3 Release 4, you must update the VALUE column of SYSTEM.SYSOPTIONS for the row where SQLOPTION='MCCSIDMIXED' with the appropriate nonzero CCSID value. You must also update the row where SQLOPTION='MCCSIDSBCS' to the value of the SBCS component of the mixed CCSID, and the row where SQLOPTION='MCCSIDGRAPHIC' to the value of the DBCS component of the mixed CCSID. If these CCSIDs do not correspond to the components of the mixed CCSID, the wrong conversion selection tables are being used. For a list of some of the mixed CCSIDs and their component SBCS and DBCS CCSIDs, see Table 19.
The rows that you must update for data in tables created before Version 3 Release 4 are:
Change the value in the VALUE column to the appropriate mixed CCSID. If you used DBCS characters before Version 3 Release 4, specify the appropriate CCSID value. For example, if you used Kanji characters, specify the value 5035. The following statements show how to update or insert the row using this value:
UPDATE SYSTEM.SYSOPTIONS SET VALUE = '5035'
WHERE SQLOPTION = 'MCCSIDMIXED'
|
INSERT INTO SYSTEM.SYSOPTIONS VALUES
('MCCSIDMIXED', '5035',
'DEFAULT CCSID FOR MIGRATED MIXED CHARACTER COLUMNS')
|
Change the value in the VALUE column to the appropriate SBCS CCSID. If you used DBCS characters before Version 3 Release 4, you must specify the SBCS component CCSID of the MCCSIDMIXED value. For example, if MCCSIDMIXED is set to 5035, specify 1027. The following statements show how to update or insert the row using this value:
UPDATE SYSTEM.SYSOPTIONS SET VALUE = '1027'
WHERE SQLOPTION = 'MCCSIDSBCS'
|
INSERT INTO SYSTEM.SYSOPTIONS VALUES
('MCCSIDSBCS', '1027',
'DEFAULT CCSID FOR MIGRATED SBCS CHARACTER COLUMNS')
|
Change the value in the VALUE column to the appropriate graphic CCSID. If you used DBCS characters before Version 3 Release 4, this value must be the DBCS component CCSID of the MCCSIDMIXED value that you used. For example, if you used Kanji characters, specify 4396. The following statements show how to update or insert the row using this value:
UPDATE SYSTEM.SYSOPTIONS SET VALUE = '4396'
WHERE SQLOPTION = 'MCCSIDGRAPHIC'
|
INSERT INTO SYSTEM.SYSOPTIONS VALUES
('MCCSIDGRAPHIC', '4396',
'DEFAULT CCSID FOR MIGRATED GRAPHIC COLUMNS')
|
If you are migrating from Version 3 Release 1 or Version 3 Release 2, the value of CCSID in SYSTEM.SYSKEYCOLS is NULL. For some primary keys, this value is not correct. In this case, you should drop and recreate the primary keys, which you can identify by running the ARIS341D procedure after migrating. (For information on this procedure, see the DB2 Server for VSE Program Directory manual.)
Several changes and enhancements were made to the EXPLAIN tables in Version 3 Release 4. If you have existing EXPLAIN tables they must either be renamed, or, dropped and recreated before using the EXPLAIN statement.
An IBM-supplied macro, ARISEXP, recreates the EXPLAIN tables for you.
For additional information on using EXPLAIN tables, see the DB2 Server for VSE & VM Performance Tuning Handbook manual.
VSE batch applications can access an application server on VM that is either remote or local. If the application server is in a remote network, the SET XPCC TARGET SYSARI command in the VSE IPL procedure must be replaced by the SET APPCVM TARGET command. If the application server is local, the SET XPCC TARGET SYSARI command in the VSE IPL procedure is not needed, and can be deleted.
Regardless of whether the application server is remote or local, an entry in the DBNAME directory may also be necessary to map the DBNAME to the resid when the DBNAME is greater than 8 characters, or when the DBNAME and the resid are different. For more information on the DBNAME directory, see Setting Up the DBNAME Directory.