Unless otherwise indicated, this section lists considerations that apply to CICS OS/2 and native OS/2 when you are migrating from CSP/AD 3.3 with EZ-PREP/EZ-RUN to VisualAge Generator WorkGroup Services.
EZ-RUN users who structured applications so that common member names were used across separate workstation subdirectories must revise their member naming scheme. In CICS OS/2 and OS/2 environments under VisualAge Generator WorkGroup Services, each application, map group, and table accessed in the same CICS OS/2 or OS/2 runtime environment must have a unique name.
EZ-PREP/EZ-RUN applications are not supported in the CICS OS/2 or OS/2 environment. The applications, map groups, and tables managed by EZ-PREP/EZ-RUN are not the same objects created by generating VisualAge Generator applications, map groups, and tables for the CICS OS/2 or OS/2 environment.
EZ-RUN applications cannot interact with COBOL or C++ applications. If any EZ-RUN application is generated again to run under VisualAge Generator WorkGroup Services, then all applications that interface with that application with CALL, DXFR, and XFER must also be generated again.
An EZ-PREP/EZ-RUN application can coexist on the same OS/2 system with the same application generated as a COBOL or C++ program. Therefore, a called application that is needed as a subroutine by EZ-RUN, COBOL, and C++ applications can be generated as an EZ-RUN called application, a COBOL called application, and a C++ called application .
Storage requirements for EZ-RUN, COBOL, and C++ applications might differ. EZ-RUN applications are run interpretively. The entire application does not have to be loaded into storage for the application to run. The size of the COBOL and C++ programs are limited by the storage available on the OS/2 system.
On CICS OS/2 applications, the personal computer function keys are mapped to the 3270 function key values returned in EZEAID according to the CICS OS/2 programmable workstation setup table (WSU). The user can modify this table.
On C++ applications, the personal computer function keys are mapped to the 3270 function key values returned in EZEAID. You cannot modify the definitions.
The file format supported by EZ-RUN is different from that supported by VisualAge Generator WorkGroup Services.
Use the EZ-RUN EXPFMAIN utility to create a sequential, host-format file. You can then use the conversion utility for host data files to create a VisualAge Generator WorkGroup Services workstation-format file.
Depending on whether you specify the T option when using the EXPFMAIN utility to translate the file to EBCDIC, you might need the conversion utility for host data files to perform code page conversion:
Note: | It is recommended that you do not translate the file to EBCDIC when you use the EXPFMAIN utility because the code pages that EXPFMAIN and the conversion utility for host data files use might be different. |
You can specify no code page conversion on either the Conversion Options window or with the /NOCONVERT parameter for the noninteractive ELACONV command.
You can specify code page conversion on the Conversion Options window or with the /CONVTAB parameter for the noninteractive ELACONV command.
To use a VisualAge Generator WorkGroup Services data file with EZ-RUN, convert the VisualAge Generator WorkGroup Services file to a host-format file using the conversion utility for host data files. You can then use the EZ-RUN IMPFMAIN utility to load the host-format file into an EZ-RUN file.
Depending on whether you request code page conversion to EBCDIC when using the conversion utility for host data files, you might need to use the T option with the IMPFMAIN utility:
Note: | It is recommended that you do not specify code page conversion to EBCDIC when using the conversion utility for host data files because the code pages that the conversion utility for host data files and the IMPFMAIN utility use might be different. |
You can specify no code page conversion on either the Conversion Options window or with the /NOCONVERT parameter for the noninteractive command ELACONV.
To install generated applications for CICS OS/2, all main transaction, main batch, dynamically called applications, print service programs, map group format modules, and table programs can have an entry in the PPT. However, a PPT entry is only required for the following:
PPT entries are also useful for the distribution of applications using the CICS OS/2 export and import facilities.
Each application to be started by entering a transaction code started from CICS OS/2 or with XFER, CREATX, or EZESEGTR as the result of a segmented converse must have a unique transaction ID assigned and have an entry in the PCT.