You can run applications generated with CSP/370AD 4.1 for the CICS OS/2 environment with VisualAge Generator WorkGroup Services. However, these applications must be prepared using the VisualAge Generator WorkGroup Services preparation utility.
This section provides information on:
CSP/370AD generation usually produces the following output files:
The parts control file, normally located in the userid.OS2CICS.EZEPCTL data set, is a record of all generated materials. The preparation utility for CSP/370AD applications uses the parts control file to determine which files, or parts, must be transferred to the workstation and prepared for the CICS OS/2 environment.
Each of the files, or parts, is transferred to a workstation where VisualAge Generator WorkGroup Services is installed. The map group format modules and COBOL source programs need to be prepared. Data files might require conversion for the workstation environment.
After the application has been generated, you can transfer the application to the workstation and prepare the application to run in CICS OS/2.
The generated parts of an application must be transferred to the workstation and prepared to run in the CICS OS/2 environment. You can use the preparation utility for CSP/370AD applications to transfer and prepare the generated parts.
This section provides an example of how to use the interactive VisualAge Generator WorkGroup Services/2 preparation utility.
To prepare the application to run in the CICS OS/2 environment, complete the following steps:
Note: | It is possible that the preparation process will not be quick, especially if you have several maps in the application. |
Note: | If you want to review the messages from the most recent preparation activities, select Open preparation log from the Prepare pull-down menu. |
Note: | Press F3 to exit the preparation utility for CSP/370AD applications. |
The Micro Focus COBOL source files produced by CSP/370AD generation must be converted from EBCDIC to ASCII before they can be used on the workstation. The preparation utility for CSP/370AD applications automatically does this conversion when it downloads the files to the workstation. The preparation utility for CSP/370AD applications removes any embedded shift-out/shift-in (SO/SI) control characters from the source files that contain DBCS characters.
Because the object file produced for the map group format module is converted to ASCII when it is generated on the MVS host system, the preparation utility for CSP/370AD applications does not convert this file when it downloads it to the workstation.
For each application, you must configure the workstation so it can do the following:
To configure your workstation, you must set a combination of OS/2 environment variables and CICS OS/2 resource tables.
The following sections provide information on configuring your workstation.
To work properly, several environment variables must be set, for VisualAge Generator WorkGroup Services and CICS OS/2. For information on these environment variables, refer to the Installation Guide for VisualAge Generator WorkGroup Services document.
If you generated your application using CSP/370AD, table program dynamic link libraries must also be in CICSWRK.
Note: | The LIBPATH statement can be defined only in the CONFIG.SYS file. |
CSP/370AD requires the following standard OS/2 environment variables for the preparation utility for CSP/370AD applications:
Note: | The LIBPATH statement must be set in the CONFIG.SYS |
The preparation utility for CSP/370AD applications requires the following product-specific environment variable:
You can customize the following product-specific environment variables for the preparation utility for CSP/370AD applications:
For the CICS OS/2 table entries that VisualAge Generator WorkGroup Services requires, refer to the Running VisualAge Generator Applications on OS/2, AIX, and Windows document.
All map group programs generated with CSP/370AD require a PPT entry.
You must build an access plan for each database an application uses before an SQL application can run successfully. The process is called binding the application. The access plan can be built at three different times:
SQLBIND applname.BND databasename /M=applname.SQB
Note: | If the application is being prepared on the same workstation that it will run on, the plan can be built as part of the preparation. |
This method will only build the plan for the database that the application is compiled against. Another method must be used for databases that are accessed using EZECONCT.
If you are using CSP/370AD to generate your application, the preparation procedure, ELARXCOB.CMD, runs the SQLBIND if the :symparm BINDPARM is set to YES. You can set the :symparm BINDPARM to YES during application generation. For more information on setting symparms at generation time, refer to the Generating VisualAge Generator Applications document.
For applications that are already generated using CSP/370AD, you can set the :symparm BINDPARM in the parts control file by adding the following line:
:SYMPARM SYMBOL=BINDPARM VALUE="YES".
If you have multiple applications that contain the same map groups and tables, you might want to generate the map group and table separately from the application. Then, use a command file to have the preparation utility for CSP/370AD applications noninteractive command prepare all the parts of the application.
Start your database manager before you start VisualAge Generator WorkGroup Services so that it is already initialized and ready for use. Otherwise, performance will be slow when the preparation utility attempts to start it the first time it processes an SQL statement.
VisualAge Generator WorkGroup Services provides two utilities to perform the following preparation activities for CSP/370AD-generated applications:
The two preparation utilities provided are as follows:
Both ELAPREP and ELAPREPR use command files and control files when running.
VisualAge Generator WorkGroup Services provides an interactive preparation utility, ELAPREPR. You can start the ELAPREPR interactive utility by doing one of the following:
You can specify the parameters for ELAPREPR:
VisualAge Generator WorkGroup Services provides a noninteractive command, ELAPREP, corresponding to the interactive preparation utility ELAPREPR. The ELAPREP command can be started from the OS/2 command prompt or from another program.
You can start the ELAPREP noninteractive utility by entering the following command at an OS/2 command prompt: ELAPREP.
The following diagram shows the syntax of the ELAPREP command:
>>-ELAPREP--/PARTFile=part_control_file-------------------------> >----+----------------------------------+-----------------------> '-/DIRectory=preparation_directory-' >----+-----------------------+----------------------------------> '-/HOSTPds=dataset_name-' >----+-----------------------------------+----------------------> '-/CONtrol=preparation_control_file-' .-/NODOWnload--. >----+---------------------+----+--------------+----------------> '-/SESsion=session_id-' '-/DOWnload----' .-/NOPREpare--. .-/NOREPLace--. .-/STop---. >-----+-------------+---+-------------+---+---------+-----------> '-/PREpare----' '-/REPLace----' '-/NOSTop-' .-/LOGActivity---. .-/NOCREATEListing--. >-----+----------------+---+-------------------+----------------> '-/NOLOGActivity-' '-/CREATEListing----' .-/NOIGNORETimestamp--. >-----+--------------------+---+---------------------+----------> '-/PROfile=file_name-' '-/IGNORETimestamp----' >-----+-----------------------+---+----------+----------------->< '-/DBname=database_name-' '-/NLS=xxx-'