Migrating to VisualAge Generator
This section lists considerations for migrating from CSP/2RS 1.1
to VisualAge Generator WorkGroup Services in the CICS OS/2 environment.
CSP/2RS and VisualAge Generator WorkGroup Services cannot be used
concurrently on the same machine. CSP/2RS should be removed from
the machine before VisualAge Generator WorkGroup Services is installed.
If this is not practical, remove all references to CSP/2RS from the
CONFIG.SYS while you are using VisualAge Generator WorkGroup
Services.
If you customized any of the files associated with CSP/2RS 1.1,
you need to perform similar customizations on VisualAge Generator command
files and templates.
- ELARUNC.CMD
- This file is provided with VisualAge Generator WorkGroup Services to start
CICS OS/2 with VisualAge Generator WorkGroup Services support.
However, the file has been significantly modified. Most modifications
are placed in the ELAENV.CMD file. Review versions of the
ELARUNC.CMD and ELAENV.CMD files supplied with VisualAge Generator
WorkGroup Services to determine if any customizations need to be
migrated.
- ELAPRSET.BAK
- The ELAPRSET.CMD file (shipped as ELAPRSET.BAK) is not
provided with VisualAge Generator WorkGroup Services. Make runtime
modifications to the workstation environment in the ELAENV.CMD
file. If any customizations were made to ELAPRSET.CMD, review
ELAENV.CMD to determine if any of these customizations need to be
migrated.
- ELARXCIC.CMD, ELARXCOB.CMD, ELARXLNK.CMD, and ELAPRCTL.CTL
- If you customized these files for CSP/2RS and intend to use the
VisualAge Generator application generation facility, you might need to migrate
your customizations to the templates supplied with VisualAge Generator
Developer. Specifically, determine if the templates
EFKOOPCO.TPL, EFKOOPFO.TPL, and EFKOOPPO.TPL require any
customization.
For more information on these templates, refer to the Generating
VisualAge Generator Applications document.
If you will be using the preparation utility for CSP/370AD members,
you might need to migrate your customizations to the versions of these files
provided with VisualAge Generator WorkGroup Services.
- ELACNxxx.DLL
- Data conversion files that were customized can be used with VisualAge
Generator.
- ELAxxx.ESF and ELACxxx.ESF
- If you customized these files for CSP/2RS and intend to use
VisualAge Generator Developer, you might need to migrate your customizations
to the templates supplied with VisualAge Generator Developer.
If you will be using the preparation utility for CSP/370AD members,
you might need to migrate your customizations to the versions of these files
provided with VisualAge Generator WorkGroup Services.
Note: | CSP/2RS 1.1 supported distributing customized files by uploading
them to the host and overwriting the CSP/2RS installation files on the
host. VisualAge Generator does not support this method of
distribution.
|
During CSP/2RS installation, users added CICS OS/2 table
entries under the application group ELA110. VisualAge Generator
WorkGroup Services adds several entries with the same name under the
application group ELAWGS. If both application groups exist on the same
CICS OS/2 system, CICS OS/2 uses the entries associated with
ELAWGS because it is listed after ELA110 alphabetically.
If you want to remove the duplicate entries from your system, use the CEDA
transaction to delete them. See Table 4 for the duplicate entries:
Table 4. Table of Duplicate Entries
Table
| Entry
| Group Name
|
DCT
| ELAD
| ELA110
|
FCT
| ELACFIL
| ELA110
|
PCT
| ELAC
| ELA110
|
PCT
| ELAM
| ELA110
|
PCT
| ELAN
| ELA110
|
PCT
| ELAU
| ELA110
|
PCT
| ELAZ
| ELA110
|
In general, applications, tables, and map groups generated with
CSP/370AD 4.1 do not have to be generated again to use them with
VisualAge Generator WorkGroup Services. The application generation
facility eliminates the mapping services program for terminal maps. 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:
- Whether the generation was done by CSP/370AD 4.1 or the
VisualAge Generator Developer
The rules for using tables and map groups are as follows:
- If you generate an application with VisualAge Generator, you must also
generate any edit tables and map groups with VisualAge Generator that the
application uses.
- If you generate the map groups for the application, you must also generate
any other applications with VisualAge Generator that use the map
groups.
- If you generate a map group with VisualAge Generator, you must also
generate all tables that are specified as edit routines for any map variable
field in the map group with VisualAge Generator. Any applications that
use the map group must be generated with VisualAge Generator.
- If you generate a table with VisualAge Generator, you do not need to
generate any applications or map groups with VisualAge Generator that use the
table.
Notes:
- As soon as any application, table, or map group is generated with
VisualAge Generator, VisualAge Generator WorkGroup Services must be
used.
- If you do not follow these rules, you might receive the messages
ELA00046P, ELA00051P, or ELA00208P, or receive ABEND code ELAW in MVS
CICS. 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 ]