IBM Books

Migrating to VisualAge Generator


Appendix C. Migrating from Cross System Product Interpretive to C++

The following are some special considerations that apply when migrating from Cross System Product to VisualAge Generator WorkGroup Services.

All C++ environments in VisualAge Generator (OS/2, AIX, CICS/6000, CICS for Windows NT, and Windows NT) are new. For more information on the compatibility considerations, refer to the VisualAge Generator Reference document.


Member Names

The following are considerations for member names:


Language Element Compatibility Considerations

The following gives an overview of the compatibility considerations for language elements. The language elements include the following:

Mapping Support

Migration considerations for mapping support are as follows:

CONVERSE Process Option

Migration considerations for the CONVERSE process option are as follows:

EZE Special Function Words

Migration considerations for EZE special function words are as follows:

Transferring Among Applications

Migration considerations for transferring among applications are as follows:

File Support

Migration considerations for file and database support are as follows:

Relational Database (SQL) Support

Migration considerations for SQL applications are as follows:

DL/I Database Support

Migration considerations for DL/I applications are as follows:

Data Values

Migration considerations for data values are as follows:

User Message Files

Migration considerations for user message files are as follows:


Transferring Control in the CICS Environment

For the CICS environment, the X'FFFFFFFF' fullword at the end of the parameter list is consistent with the CSP/AE CALL interface. The length of the COMMAREA does not include this fullword unless /ENDCOMMAREA is specified as a C++ generation option for the calling application. If the generation option /ENDCOMMAREA was specified and the parameter format COMMPTR is in effect, the length specified for COMMAREA on the EXEC CICS LINK command is automatically increased by 4 bytes. Under certain conditions, CICS passes a copy of the COMMAREA to the called application. Specify /ENDCOMMAREA to ensure that the X'FFFFFFFF' fullword is included when a copy of the COMMAREA is made.


National Language Codes

The NLS code has been extended to 3 characters. The first two characters define the base language (for example, EN is for English). The third character can either represent natural continuation or identifies variation, script, or dialect. The NLS codes are as follows:

Table 11. Language Support Suffixes
Description V3.3 VisualAge Generator
Default language D See note.
U.S. English (Mixed case English) E ENU
Uppercase English U ENP
Simplified Chinese C CHS
German (Germany) G DEU
German (Switzerland) W DES
Japanese J JPN
Korean K KOR
Portuguese (Brazilian) P PTB
Note:The default language is specified as an installation option. A unique code for the default language is no longer required.


CSP/AE Invocation Parameters

CSP/AE invocation parameters have been replaced with generation options, installation options, or are no longer supported.

Table 12 shows how CSP/AE invocation parameters are supported when using generated C++ applications.

Table 12. Invocation Parameter Migration for CSP/AE
Parameter Corresponding Function in VisualAge Generator
P=yyyy The application developer can specify an alternate print destination by adding an entry for EZEPRINT in the resource association file. The application can dynamically change the print destination by using the special function word EZEDESTP.
NLS=n The NLS code for VisualAge Generator WorkGroup Services is specified at run time with the EZERNLS environment variable.
SEG The application switches between segmented and nonsegmented mode by setting EZESEGM.
DMODE=S|D|A In the C++ environments, only DB2 SQL statements are generated.
RT=zzzz The RT option is specified at generation time through the /RT generation option. The application user no longer has to press attention interrupt to go on to the next transaction; the transaction is started automatically.
TSMS The /WORKDB generation option specifies whether auxiliary or main temporary storage is used for saving working storage across segments.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]