Install a CA Gen Generated Application in NonStop

Using the NonStop Setup Tool in CA Gen › Install a CA Gen Generated Application in NonStop

Install a CA Gen Generated Application in NonStop

An application generated by CA Gen and targeted for NonStop must contain a database remote file, an RI triggers remote file, and at least one load module remote file.

The following sections explain the activities that you must follow to build an application for the first time:

Log on to the Setup Tool
Create a target configuration
Build the application
Review the build results

Note: It is assumed that the Setup Tool has already been started at this point.

More information

Testing and Running Applications in NonStop

Log On to the Setup Tool

Logging on to the Setup Tool is the first step in building an application.

Follow these steps:

Set your current volume to the location where the Setup Tool is installed by issuing the following command.
```
VOLUME $<setvol>.<setsubvol>
```
Enter the SETUP command.
The main splash screen appears.

Note: After you log on to the Setup Tool, you have access to the online help system. From the main splash screen, you can press the SF1 function key to access the main menu online help. If you press the SF1 function key again, the online help's Table of Contents is displayed. The Table of Contents provides information for all the features in the Setup Tool.
Enter your TACL logon credentials and press the F1 function key. You may use your UserId or Safeguard alias. Both UserIds and aliases must conform to Safeguard naming conventions.
You are logged on to the Setup Tool and the main menu appears.

Note: You can press the F1 function key on any screen (except for the main splash screen) to access online help for fields on that particular screen.

Create a Target Configuration

Creating a target configuration is the second step in building an application.

Follow these steps:

Press the F1 function key from the main menu.
The Target Configuration screen appears.
Enter the configuration details. Optionally, you can modify the Pathway parameters, compiler options, and location details. Defaults have been provided for these settings.
Press F4 to save the target configuration.
The target is configured with your settings.

Note: The Setup Tool configures certain Pathway parameters based on the number of servers being installed.

More information:

Modify Pathway Parameters

Modify Compiler Options

Modify Location Details

Modify EAB Locations

Modify Pathway Parameters

You can accept the default parameter settings in the Target Configuration screen or update the parameters according to your requirements.

Follow these steps:

Press the F5 function key to modify the default Pathway parameters.
Press the F6 function key to modify the Pathway TCP parameters.
Press the F7 function key to modify the Pathway Server parameters.
Press the F4 function key to save changes.
Press the F2 function key to return to the Target Configuration screen.
The target configuration contains the updated Pathway parameters.

Modify Compiler Options

You can accept the default compiler options in the Target Configuration screen or update the options according to your requirements.

Follow these steps:

Press the F7 function key to modify the default compiler options. You can modify the C compiler options and the SQL compiler options.
Press the F4 function key to save changes.
Press the F2 function key to return to the Target Configuration screen.
The target configuration contains the updated compiler options.

Modify Location Details

You can accept the default target locations in the Target Configuration screen or update the locations according to your requirements.

Follow these steps:

Press the F6 function key to modify the default target locations. You can modify the $vol.$subvol locations for the set of files that are split out of the remote files and created as a result of the build.
Press the F4 function key to save changes.
Press the F2 function key to return to the Target Configuration screen.
The target configuration contains the updated location details.

Modify EAB Locations

You can add EAB locations according to your requirements.

Follow these steps:

Press F6 from the Target Configuration screen.
Press the F5 function key on the Location Details screen to provide an EAB library or libraries that will be bound into an application. You can add the $vol.$subvol.file name for the EAB library that you need for the build.
Press the F4 function key to save changes.
Press the F2 function key to return to the previous menu from where you navigated to the Location Details screen.
The target configuration contains the updated EAB location details.

Build the Application

You must perform the following steps in the Target Configuration screen to build an application.

Follow these steps:

Press the SF8 function key after you update the target configuration details.
The Install IPs screen appears. A list of IPs for the specified target will be listed.
Enter Y in the Select All IPs field if this is the first time the application is being installed. This will build all IPs. For subsequent installations, see Rebuild an Application. If you need to build a subset of the set of IPs, tab to each IP of choice and enter an X to select.
Press the F4 function key to start building the application.
Press the F5 function key to display the Install Status screen where you can monitor the progress of the build.
The application is built as displayed in the Install Status screen.

The following events occur during the build:

The base environment for the target is built. This includes setting up an application SQL catalog if none exists. Files and programs are also copied from the IT to your target location.
The remote files are validated by verifying that their control information matches the information for the target configuration (language, DBMS, and so on). The Setup Tool database is then populated with that information.
The remote files are split into their various component parts (procedure steps, actions blocks, and so on) and stored in their appropriate locations.
The source code is compiled into object code.
The object code is linked with the appropriate libraries to produce the executable load module.
The transaction table is loaded with application trancodes.

Review the Build Results

You can view the build results after the application is built. This helps you identify problems when builds fail.

Follow these steps:

Press the F3 function key from the main menu.
The Install Status screen appears.
Select the target you need to review.
Press the F8 or F9 function key to traverse down any of the IPs to view details of the build results, including compilation listings, binding listings, SQL listings, EMS log files, TMT load listings, and so on.

More information:

Testing and Running Applications in NonStop

Setup Tool and EMS

By default, the Setup Tool uses its own EMS template files to correctly display messages generated during the installation of CA Gen applications within its own EMS viewer. In this mode and within this viewer other NonStop sub systems' messages that interface with EMS will display with unresolved text. This is because the Setup Tool's internal EMS viewer is unaware about other subsystem's EMS templates. Commenting out the SET SERVER DEFINE for =_EMS_TEMPLATES for the SVIEWEMS server will cause SVIEWEMS's EMSDIST processes to use the non resident template file provided by the operating system, that is, $SYSTEM.SYSxx.TEMPLATE.

Note: Using $SYSTEM.SYSxx.TEMPLATE causes the Setup Tool's EMS viewer to display Setup Tool's related events with unresolved text.

Generally, you should use the INSTTMPL macro supplied with the Setup Tool to merge its EMS templates into the system templates so that all the EMS log retrieval utilities have access to all templates for all sub systems' reporting messages to the EMS log files (through the default $0 collector process). After INSTTMPL macro is run successfully, the Setup Tool's EMS viewer will display all events and messages in a resolved manner.

Note:

You must be logged on as SUPER.SUPER to run the INSTTMPL macro.
For more information about installing the Setup Tool EMS templates, see the Distributed Systems Installation Guide.

More information:

Testing and Running Applications in NonStop

CA Gen Specific Parameters Included in Pathway Server Configuration Files

When an application is built, a set of Pathway server configuration files are created—one per load module. These files are accessed when the application is cold-loaded using the PWCOLD command. These configuration files contain SET SERVER commands that define the Pathway servers. The Pathway servers created through the Setup Tool contain several additional SET SERVER commands that are specific for CA Gen applications.

The following table lists the additional commands:

Param or Define	Name	Description
Param	charset-id	Specifies the character set identification number to be used with double byte character set (DBCS) applications. This parameter is not modifiable.
Param	codepage	Specifies which codepage was used at generation. This information is used internally for translation purposes. This parameter is not modifiable.
Param	Iefgxtp	Location of the codepage tables used by applications at runtime to resolve translations between clients and servers. Note: This parameter is only used for Distributed Processing Servers.
Param	trace-log	Specifies the level of information logged to an internal trace file. This log file is created in the base target subvolume and is named lgxxxxxx (where xxxxxx is the process ID of the running server). A value between 1 and 31 is provided—the higher the value, the more information will be traced. A trace value of 31 may consume a large amount of disk space, which can significantly slow processing. Therefore, you must use the trace-log field carefully in production systems. This value should be left commented out for production systems, and should only be used to help debug a problem with the server. By default, this value is commented out. Note: This parameter is only used for Distributed Processing Servers. Block Mode servers use the Snap Trace field on the AEF screen.
Param	ptopt	Specifies that flat-file profiling is used with the server. This parameter is not modifiable.
Param	pthome	Specifies the location of the flat-file profile that is associated with the server. Default: $vol.appm If modified, all servers must specify the same location.
Define	=ovflow	Specifies the name of the overflow file used when large views are passed between procedure steps and cannot be transferred in a single input/output (I/O) operation. The load module that contains the procedure step initiating the flow writes the views into this file after they are compressed. The load module containing the receiving procedure step reads the file define by =ovfile, uncompresses the data, and continues with the execution of the flow. Default: $vol.appm.overflw1 If modified, all servers must specify the same file name.
Define	=tmt_e	Tells the DPSTMTC GAEF server where to find the transaction mapping file used by distributed processing server applications. This file is a flat file version of the TMT SQL table. This option is only available for distributed processing server applications. Default: $vol.app.tmte If modified, all servers must specify the same file name.
Define	=application_ini	Specifies the fully qualified name of the initialization file used with the Diagram Trace Utility (DTU). This file contains settings that must be modified to enable tracing with the Diagram Trace Utility. By default, the entries in this file are commented out. Default: $vol.appx.applini If modified, all servers that intend to communicate with the Diagram Trace Utility must specify the same file name.
Define	=tcpip^process^name	Specifies the name of the TCP/IP process running a pair of Listener and Telnet processes on the system. This TCP/IP process is used by the servers to communicate with the remote Diagram Trace Utility. Default: $ZTC0 If modified, all servers that intend to communicate with the Diagram Trace Utility must specify the same TCP/IP process. For the name of this process, contact your system administrator.
Define	=codepage_ini	Specifies the fully qualified name of the codepage translation file. This file contains specifications for code pages used in CA products and generated applications. Default: $vol.app.codepage

Rebuild Pathway Configuration Files

You can modify the application's Pathway configuration files any time after your application is built; you do not need to rebuild the application using the Setup Tool.

Follow these steps:

Update the Pathway configuration information for the specific application in the Pathway Parameters, TCP Parameters, or Server Parameters screens.
Press the SF12 function key to rebuild the Pathway configuration files.
The Pathway configuration files are rebuilt. For these changes to take effect, you must cold-load your application.

Important! Using this option after you have edited and updated the Pathway configuration files outside of the Setup Tool will cause all those changes to be lost.