This section discusses general considerations for migrating applications from host environments supported by Cross System Product or VisualAge Generator to VisualAge Generator WorkGroup Services. In addition, refer to the compatibility consideration information in the online helps.
The ASCII collating sequence is different from the EBCDIC collating sequence. Therefore, VisualAge Generator functions that are affected by collating sequence might give different results on the workstation than on the host. For example, because table contents are converted to ASCII, a range check might give a different result on the workstation than on the host. Similarly, the record retrieved after doing a SET record SCAN might be different than on the host.
VisualAge Generator WorkGroup Services handles abends differently than CSP/370RS or VisualGen Host Services. For example, if a VisualAge Generator application calls a non-VisualAge Generator application, which in turn calls another VisualAge Generator application, then the non-VisualAge Generator application must handle the abend.
DL/I database access is not supported by VisualAge Generator WorkGroup Services.
VisualAge Generator WorkGroup Services supports CICS OS/2 and COBOL file access.
Data files used by applications that are run on the host can be converted to a format that can be used on the workstation.
A conversion utility is provided to convert data formatted for use on the host to data formatted for use on the workstation. The conversion utility requires two files to do this conversion:
For information on the conversion utility, refer to the Running VisualAge Generator Applications on OS/2, AIX, and Windows document.
The following are considerations you must be aware of when migrating SQL applications to the workstation:
If you are a CSP 3.3 VM SQL user and wish to migrate the database environments, APAR PN76454 (CSP/AD 3.3) and PN75537 (CSP/AE 3.3) provide you with VM static module support. With VM static module support, you can move your host SQL data to the database in other systems through SQL DRDA protocol.