OpenTP1 Version 7 Operation

[Contents][Index][Back][Next]

3.15.2 Registering a scenario

To register a scenario template in JP1/AJS2 - Scenario Operation, you need to import the following scenario template definition file in the scenario library folder of JP1/AJS2 - Scenario Operation Manager:

Scenario template definition file
/BeTRAN/jp1_template/ScenarioTemplate/TP1_ServerBase.sjis.xml

Destination scenario library folder
/ScenarioLibrary/OpenTP1/TP1_ServerBase

For details about how to import the scenario template definition file in the scenario library folder of JP1/AJS2 - Scenario Operation Manager, see the relevant JP1/AJS2 - Scenario Operation manuals.

The following subsection explains the scenario variables that need to be set when a scenario is registered.

Organization of this subsection
(1) Scenario variables

(1) Scenario variables

Some information changes depending on the operating environment. Scenario variables represent such information, and they are preset for each scenario. For example, you can set a host name and a file name as scenario variables, and specify values for those scenario variables when the scenario is registered. In this way, you can execute a scenario that matches the operating environment.

The scenario templates provided by OpenTP1 determine the values of environment variables and the user who executes the scenario based on the scenario variables that are entered (input scenario variables).

The following table lists the environment variables whose values are determined from input scenario variables.

Table 3-34 Environment variables whose values are determined from input scenario variables

Environment variable Description Value to be set when scenario is executed#1
DCDIR OpenTP1 directory#2 ?DCDIR?
DCCONFPATH Directory containing the OpenTP1 definition file#3 ?DCCONFPATH?

#1
The character string enclosed by question marks (?) indicates the input scenario variable of JP1/AJS2 - Scenario Operation whose value needs to be set.

#2
Specify a full path name not exceeding 50 bytes. You cannot use symbolic links.

#3
Specify a full path name.

When these environment variables are set as the system environment variables of the execution user, you need to set the values of the system environment variables for the input scenario variables as well. For details about operation when both input scenario variables and system environment variables are specified, see the description of the environment variables in the manual Job Management Partner 1/Automatic Job Management System 2 Setup Guide.

System environment variables consists of the following variables:

For UNIX:
  • Variables defined in the script file that is specified when a scenario job is defined by JP1/AJS2 - Scenario Operation
  • Variables defined in the local login script
  • Variables defined in the system login script

For Windows:
  • System environment variables

Specify the execution user of a scenario by using the input scenario variable USER_NAME in each scenario template. Only a user mapped by JP1/Base can be specified as the execution user of a scenario. You need to map (user mapping) the OpenTP1 system administrator before you execute a scenario. For details about user mapping, see the manual Job Management Partner 1/Base Description, User's Guide and Reference.