IBM Books

Migrating to VisualAge Generator


CSP/370AD 4.1 to VisualAge Generator Developer

This chapter lists the considerations for migrating from CSP/370AD 4.1 to VisualAge Generator Developer.

To migrate from CSP/370AD 4.1 to VisualAge Generator Developer, first migrate your MSLs to VisualAge Generator and save the external source file used for migration.


MSLs

If you are migrating from CSP/370AD 4.1, you need to complete the following steps to convert the Member Specification Library (MSL) members:

  1. Export, in external source format, the entire MSL from CSP/370AD 4.1.
    Note:Be sure to save the exported external source format for use in migrating resource association information to VisualAge Generator Developer.

  2. Download the export file to OS/2

  3. Import the export file into VisualAge Generator

    CSP/370AD 4.1 MSL members do not require conversion.


Message File Conversion

See Appendix F. Using the Message File Conversion Utility for more information on the conversion utility.


Test Facility Limitations

The VisualAge Generator test facility emulates the /MATH=COBOL method of storing intermediate results for arithmetic calculations. The VisualAge Generator test facility does not emulate the Cross System Product method /MATH=CSPAE.

Testing TSO CICS

If your applications call non-CSP programs, you need to plan for testing of the calling application. Some techniques that you might use, depending on your old CSP environment and what the non-VisualAge Generator program does, are as follows:


Definition Limitations

Cross System Product has a limit of 4096 rows in a table. You can define larger tables with VisualAge Generator. However, if you exceed the 4096 row limit, you cannot import the table back into a Cross System Product MSL on the host. CSP/370AD 4.1 member definitions are fully compatible with VisualAge Generator except for table size.

See CSP/370RS 2.1 to VisualGen Host Services for considerations that might also apply to development and generation.


Generation Options

In CSP/370AD 4.1, some generation options were saved in the application MSL member and some options were specified in COBOL generation options files.

Generation Options in the MSL

In VisualAge Generator, generation information is not saved in the application MSL member. If you want to use the same generation options for more than one generation, you must specify the options in generation control files, such as the generation options file and the resource association file.

Generation Options File

Generation options that were specified in a generation options file used in CSP/370AD 4.1 can be migrated for use with the VisualAge Generator application generation facility. The file format for the generation options files is similar to that of other workstation products. You must convert any host options files that you want to use to this format. The migration utility EZERCNVO.CMD is provided to perform this conversion. See Appendix H. Host Options File Conversion Utility for more information on migrating host options files.


Resource Associations

In CSP/370AD 4.1, information associating application record definitions with physical files in the target environment was saved in the application MSL member from one generation to the next. With VisualAge Generator, if you want to use the same file resource association information across more than one generation, you must specify the information in a resource association file.

CSP/370AD 4.1 resource association information saved in application MSL members can be converted for VisualAge Generator by doing the following:

Note:The resource association file used by the VisualAge Generator Developer is not compatible with the resource association file used by the Interactive Test Facility (ITF). There is no method for migrating CSP/370AD 4.1 resource association information for use by ITF.

Migrating SETGEN Information

In CSP/370AD the SETGEN batch command enabled the developer to choose which map groups and tables to generate with an application. The SETGEN command also enabled the application developer to set table related options, such as SHARED, RESIDENT, and KEEP AFTER USE, during generation. VisualAge Generator Developer provides the following:


Tables

The generation options RESIDENT, SHARED, and KEEP AFTER USE were generation options in CSP/370AD 4.1. They are specified at definition time with VisualAge Generator SHARED and RESIDENT are specified within table definition. KEEP AFTER USE is specified on the Tables and Additional Record panel in application definition.


Linkage Tables

No migration is necessary for linkage tables. You can transfer the linkage tables from the host and use them without changes.


Command Interface

The CSP/370AD 4.1 command interface is similar to the format used for the VisualAge Generator Developer commands. If you have CSP/370AD commands that you want to use, you must convert them to the workstation format. Utilities are not provided to do this conversion.


Reserved Word File

No migration is necessary for the reserved word file. You can transfer the file from the host and use it without changes. The default reserved word file for VisualAge Generator Developer is EFK2RSV.RSV.

The reserved word file for CSP/370AD 4.1 was the file specified by the EZEWORD DD statement in your generation JCL.


Templates

The template names are different between CSP/370AD and VisualAge Generator. All templates and procedures used for preparing generated objects have changed for workstation generation to use system input files instead of partitioned data sets for source objects.

Any templates and procedures that you modified must be modified again when migrating from CSP/370AD to the VisualAge Generator application generation facility.

See Table 3 for the CSP/370AD template names and the corresponding application generation facility template names. The procedure names have not changed.

The contents of the templates used by VisualAge Generator Developer might be different from CSP/370AD, so you should not use the CSP/370AD generation templates with VisualAge Generator Developer. If you customized your templates and want to make the same changes to the VisualAge Generator Developer templates, the following information is provided to assist you in migrating CSP/370AD-generated applications.

Table 3. CSP/370AD Template Names and and the Corresponding VisualAge Generator Developer JCL Template Names
CSP/370AD Template Names VisualAge Generator Developer Template Names
EZEACL EFK2MMCA
EZEBCL EFK2MPIA
EZEBIND EFK2MBDB
EZEBINDA EFK2MBDA
EZEBINDN EFK2MBDD
EZEBINDR EFK2MBDC
EZEBMP EFK2MEIB
EZEBMP2 EFK2MEIA
EZEBPCLB EFK2MPIB
EZECALL EFK2MEBA
EZECCL EFK2MPCB
EZECPCLB EFK2MPCA
EZEDPCLB EFK2MPBB
EZEGSDDI EFK2MGSI
EZEGSDDO EFK2MGSO
EZEICL EFK2MPIC
EZEICLB EFK2MPID
EZEIPCLB EFK2MPIE
EZELINKR EFK2MPRE
EZEMBACH EFK2MEBE
EZEMCL EFK2MPBA
EZEMDB2 EFK2MEBD
EZEMDBAL EFK2MTDL
EZEMDBDD EFK2MDLI
EZEMDBS EFK2MEBB
EZEMDEST EFK2MEZD
EZEMDGSM EFK2MIMS
EZEMDLI EFK2MEBC
EZEMFSCL EFK2MMCB
EZEMFST EFK2MMST
EZEMFSU EFK2MMSU
EZEMPCLB EFK2MPBC
EZEMXAPP EFK2MCAL
EZEMXEAP EFK2MEZA
EZEQSALI EFK2MTSI
EZEQSALO EFK2MTSO
EZESQDDI EFK2MSDI
EZEQSDDO EFK2MSDO
EZETCALL EFK2META
EZETCL EFK2MPTA
EZETDB2 EFK2METC
EZETDEST EFK2MTED
EZETDLI EFK2METB
EZETPCLB EFK2MPTB
EZETSO EFK2METD
EZETXAPP EFK2MTCL
EZETXEAP EFK2MTEA
EZEVSALI EFK2MTVI
EZEVSALO EFK2MTVO
EZEVSDDI EFK2MVSI
EZEVSDDO EFK2MVSO


Generation Output Libraries on the Host

When you generate for an MVS target environment, the generation outputs created by VisualAge Generator Developer are transferred to data sets that use the same default naming conventions that were used by CSP/370AD 4.1.

Specify /CICSENTRIES=RDO if you want to generate model resource definition online (RDO) program and transaction definitions. Specify /CICSENTRIES=MACRO if you want to generate model PPT and PCT table entries.


Arithmetic Operations

When calculations are done with the /MATH=COBOL option, truncation and rounding occur on the final result. In the test facility or in run time with the /MATH=CSPAE option, calculations are handled differently.

When you specify /MATH=CSPAE and a calculation or an assignment statement is done, one of the following occurs:

To ensure that the results are the same, specify /MATH=CSPAE and /NUMOVFL, and use EZEOVER and EZEOVERS to check for overflow. Alternatively, specify /MATH=CSPAE and define your variables so overflows cannot occur.

Maximum value overflow occurs whenever an intermediate result in an arithmetic operation exceeds 18 significant digits. This means that overflow can occur more often for generated applications than for applications run using CSP/AE.


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