CSP/AD 3.3 required CSP/370RS 1.1 to generate COBOL programs. The following sections list the considerations for migrating CSP/370RS 1.1 using generated COBOL programs to using VisualGen Host Services.
VisualGen Host Services can replace CSP/370RS 1.1 as a runtime environment. You can modify any JCL (batch, IMS, CICS, or MVS/TSO) or CLIST that allocated the CSP/370RS 1.1 load library to use the VisualGen Host Services load library.
VisualGen Host Services must be installed in a separate SMP/E zone and have different target libraries from CSP/370RS 1.1. VisualGen Host Services does not include any of the COBOL generation function that was included in CSP/370RS 1.1, so do not delete CSP/370RS 1.1 from your system until you have migrated both the COBOL generation and runtime services functions to VisualGen.
If you placed any CSP/370RS 1.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 1.1 load library will cause unpredictable results. The code being run will be a combination of CSP/370RS 1.1 code from the load library and VisualGen Host Services code from the LPA.
The preparation procedures are shipped in VisualGen Host Services. The procedure names are not changed from CSP/370RS 1.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 the VisualGen application generator. The VisualGen Host Services procedures do not work with the preparation JCL generated using CSP/370RS 1.1. If you plan to use CSP/370RS 1.1 for program generation, keep a copy of the CSP/370RS 1.1 cataloged procedures for use with applications generated with CSP/370RS 1.1.
In general, applications, tables, and map groups generated with CSP/370RS 1.1 do not have to be generated again to use them with VisualGen Host Services. The VisualAge Generator application generation facility supports unnamed map variables in a map group. In addition, VisualAge Generator 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/370RS 1.1 and an application generated with VisualAge Generator application generation facility depends on the following:
The rules for using tables and map groups are as follows:
Notes:
Tables generated under CSP/370RS 1.1 might have used AMODE(24). If you use these tables under MVS CICS, you must link them again as AMODE(31). If you use these tables for non-CICS environments, you can use AMODE(24), but AMODE(31) is recommended.
Running a generated CSP/370RS 1.1 application in the same run unit with a generated VisualAge Generator application where both applications access the same table can cause an abend or wrong data to be retrieved from the table. CSP/370RS 1.1 and VisualAge Generator generated programs handle tables differently. To avoid problems, define the table as resident.
If EZEFEC is set to 1 and there is an error routine specified, VisualGen Host Services returns control to the application on OPEN and CLOSE errors. CSP/370RS 1.1 does not. The application does not have to be generated again to use this function.
The ELAPCB macro for VisualGen Host Services supports only the work database. PSBs for applications generated using CSP/370RS 1.1 might also have used a message database. If you generate the PSB for these applications again, you must use the ELAPCB macro from CSP/370RS 1.1.
If you used a DL/I message database with CSP/370RS 1.1, you included ELAMSG as a PCB in the PSB. ELAMSG is supported by VisualGen Host Services for compatibility with CSP/370RS 1.1.
If any SQL applications in a run unit were generated on CSP/370RS to use a DB2 message database, then include the database request module DBRM module ELADBRM2 in the plan associated with the run unit.
The message utility is not shipped with VisualAge Generator. User messages are no longer in VSAM files, DL/I databases, or DB2 tables. Instead, they are in VisualAge Generator tables. Applications generated under CSP/370RS 1.1 to use a message file or database are supported by VisualAge Generator. However, if you need to change the text of a message in message database, you will need to use the CSP/370RS 1.1 message utility.