The DFHCSDUP MIGRATE command is enhanced to support migration of temporary storage tables to TSMODEL resource definitions in the CSD.
If you decide to migrate TST entries to the CSD, first reassemble your TST with the MIGRATE option specified on the TYPE=INITIAL macro, as follows:
DFHTST TYPE=(INITIAL,MIGRATE)
This ensures that the table is assembled and link-edited with AMODE(24), which is required by the MIGRATE function of the DFHCSDUP utility program. Failing to specify MIGRATE on the TYPE=INITIAL macro causes the DFHTST macro to force AMODE(31), which causes errors when you run DFHCSDUP with the MIGRATE command for the TST.
Use the DFHCSDUP utility program to migrate TSTs to the CSD, specifying the following command:
MIGRATE TABLE(tablename) TOGROUP(groupname)
Note the following points when migrating from a TST to TSMODELs:
This means that DFHCSDUP cannot migrate a TST TYPE=SHARED entry without its supporting TYPE=REMOTE entry, because it has no means of knowing the DATAID from which to create the corresponding PREFIX attribute in the TSMODEL. The following recommendations are made to help you to migrate your TST to TSMODELs successfully:
If you are using TS data sharing, supported by both TYPE=REMOTE and TYPE=SHARED entries, DFHCSDUP migrates these as data sharing TSMODELs with the pool name as the shared attribute. If temporary storage API requests do not specify a SYSID, CICS matches the queue name with PREFIX in the migrated TSMODEL, and shared TS works as in the earlier release.
Potential problems connected with TYPE=SHARED entries are addressed by the PTF for APAR PQ30438, which adds a new warning message to DFHCSDUP. This message serves two purposes:
You can use RDO support for TSODELs and a TST if you use the TST system initialization parameter to specify a TST suffix. To use a TST as well as RDO, the specified TST load module must be assembled with the MIGRATE option. If the TST was not assembled with the MIGRATE option, CICS loads the TST only and does not provide any RDO support for TS queues, and any attempts to install TSMODELs are rejected.
If you use both a TST and TSMODELs, the use of the TST is limited to the following:
The replacement CSD resource definition type for TST entries is the TSMODEL, which provides equivalent function for most of the various DFHTST macro types. However, the TSMODEL resource definition does not provide support for application programs that rely on the mapping of SYSIDNTs to SHARED TST entries for queues held in a TS pool. If an application program explicitly specifies a SYSID on a TS queue request for a queue that resides in a TS data sharing pool, it requires the support of a TST. Until an alternative mapping of explicit SYSIDs is provided by a new CSD resource definition type, IBM® will continue to support the use of the TST for TYPE=SHARED entries.
[[ Contents Previous Page | Next Page Index ]]