IBM Books

Migrating to VisualAge Generator


CSP/370RS 2.1 to VisualGen Host Services

You can use VisualGen Host Services to replace CSP/370RS 2.1 as a runtime environment. You can modify any JCL (batch, IMS, CICS, or MVS/TSO) or CLISTs that allocated the CSP/370RS 2.1 load library to use VisualGen Host Services load library.


Installation Considerations

VisualGen Host Services must be installed in a separate SMP/E zone and have different target libraries from CSP/370RS 2.1 and CSP/370AD 4.1. If you do not have CSP/370AD 4.1 installed on your system, you can delete CSP/370RS 2.1 after you migrate all your generated applications to the VisualGen Host Services runtime environment. If you have both CSP/370AD 4.1 and CSP/370RS 2.1 installed on your system, you cannot delete CSP/370RS 2.1 until you do the following:

Once you have completed the above procedures, you can then delete both CSP/370AD 4.1 and CSP/370RS 2.1.

If you placed any CSP/370RS 2.1 load modules in the LPA, replace them with the VisualGen Host Services load modules before migration is complete. If you removed the CSP/370RS load modules from the SELALMD load library when you placed the load modules in the LPA, you must put them back in the SELALMD load library when the load modules are removed from the LPA. Otherwise, any JCL or CLISTs that allocate the CSP/370RS 2.1 load library will cause unpredictable results. The code being run will be a combination of CSP/370RS 2.1 code from the load library and VisualGen Host Services code from the LPA.


Procedures

The procedure names for program preparation have not changed from CSP/370RS 2.1 to VisualGen Host Services. The cataloged procedures for program preparation shipped with VisualGen Host Services work only with preparation JCL generated on the workstation using VisualAge Generator Developer. The VisualGen Host Services procedures do not work with the preparation JCL generated using CSP/370AD 4.1. If you plan to use CSP/370AD 4.1 for program development and generation, keep a copy of the CSP/370RS 2.1 cataloged procedures for use with applications generated with CSP/370AD 4.1.


Upward Compatibility

Generating Applications, Tables, and Map Groups Again

In general, applications, tables, and map groups generated with CSP/370AD 4.1 do not have to be generated again to use them with VisualGen Host Services. The application generation facility eliminates the mapping services program for terminal maps in all environments and adds a map group format module for the IMS environments. The application generation facility also adds information to tables that can be used as edit routines, such as match valid, match invalid, and range match valid tables. The ability to share tables and map groups between an application generated with CSP/370AD 4.1 and an application generated with the application generation facility depends on the following:

The rules for using tables and map groups are as follows:

Notes:

  1. As soon as any application, table, or map group is generated with VisualAge Generator, VisualGen Host Services must be used.

  2. If you do not follow these rules, you might receive the messages ELA00046P, ELA00051P, or ELA00208P, or ABEND code ELAW in MVS CICS or ABEND code 1632 in non-CICS environments. Refer to the Running Applications on MVS document for more information on this ABEND code.


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