Migration From SPG, TPG or AAS to Full Function Server for CICS Transactions

How to:

If you are migrating from a CICS Stored Procedure Gateway (SPG), a new synonym will have to be created using the Web Console. If a COBOL FD is available, then the synonym will be created from it. Otherwise, the Web Console will create a skeleton synonym which you will have to edit to add field definitions.

For TP Gateway (TPG) and Application Adapter Server (AAS) users, we provide a migration utility to convert the transaction descriptions (Master Files) to Full Function Server synonyms.
Top of page
x
Syntax: How to Run the Migration Utility for TP Gateway

For TP Gateway, use the following procedure which you can run from the Web Console procedures pane. Cut and paste the following three lines of code:

DYNAM ALLOC FILE SPG2SPG DA tgp_repository_vsam SHR REU
-RUN
EX TPG2FFS OUTAPP=output_app,CONNNAME=cics_connection

where:

tpg_repository_vsam

Is the fully-qualified dataset name of the VSAM repository that the TP Gateway server is using.

output_app

Is the name of the application in which the converted descriptions will be stored.

cics_connection

Is the Adapter for CICS connection name to be used for all the entries found in the repository.
Top of page
x
Syntax: How to Run the Migration Utility for an Application Adapter Server

For an Application Adapter Server, use the following command which you can execute from the Web Console procedures pane. 

ENGINE CICSTRAN MIGRATE aas3mnt.cfginput_appoutput_app

where:

aas3mnt.cfg

Is the fully-qualified path and name of the aas3mnt.cfg control file. The value should be:

.../ibi/srv52/aas/bin/aas3mnt.cfg
input_app

Is the name of the application in which the descriptions of the CICS transactions found in the aas3mnt.cfg file can be found. Usually this will be baseapp.

output_app

Is the name of the application in which the converted descriptions will be stored.

This must be a different application than that specified for input_app.

iWay Software