The following table lists and describes the sample scenario templates.

Table 6-4 Names and processing of sample scenario templates

No.	Name of sample scenario template	Processing	Input scenario variables to be referenced
1	OpenTP1_GetInstDir	Acquires the OpenTP1 installation folder	HOST_NAME USER_NAME
2	OpenTP1_MakeTP1Dir	Creates an OpenTP1 folder	DCDIR DCCONFPATH HOST_NAME USER_NAME MULTI_ID INST_DIR#
3	OpenTP1_SetConfig	Specifies OpenTP1 definition settings	DCDIR DCCONFPATH HOST_NAME USER_NAME BETRAN_FILE1 BETRAN_FILE2 PORT_NUMBER INST_DIR#
4	OpenTP1_ChangeNodeID	Sets a node ID	DCDIR DCCONFPATH HOST_NAME USER_NAME NODE_ID INST_DIR#
5	OpenTP1_Deploy	Registers OpenTP1	DCDIR HOST_NAME USER_NAME MULTI_ID
6	OpenTP1_MakeFileSystem	Creates an OpenTP1 file system	DCDIR DCCONFPATH HOST_NAME USER_NAME BETRAN_FILE1 BETRAN_FILE2
7	OpenTP1_Start	Starts OpenTP1	DCDIR DCCONFPATH HOST_NAME USER_NAME
8	OpenTP1_StartUAP	Starts a UAP (sample program)	DCDIR DCCONFPATH HOST_NAME USER_NAME USER_SERVER_NAME

#

There is no need for the user to enter the INST_DIR input scenario variable because it is acquired by OpenTP1_GetInstDir and passed to the scenario templates used in the subsequent processing.

The details of the sample scenario templates are provided below, where the numbers correspond to the numbers in the table.

1. OpenTP1_GetInstDir (acquires the OpenTP1 installation folder)
   This sample scenario template acquires the DCDIR environment variable as the OpenTP1 installation folder. The acquired OpenTP1 installation folder is passed to the OUT_INST_DIR output scenario variable.
   
2. OpenTP1_MakeTP1Dir (creates an OpenTP1 folder)
   This sample scenario template creates the OpenTP1 folder specified in the DCDIR input scenario variable by using an OpenTP1 folder creation batch file (OpenTP1-installation-folder\jp1_template\examples\tools\dcjmk_dcdir.bat). This batch file processing is not performed for the original OpenTP1 because its folder will have already been created.
   In OpenTP1 for Windows, user, group, and mode settings are not specified.
   
3. OpenTP1_SetConfig (specifies OpenTP1 definition settings)
   This sample scenario template uses an OpenTP1 environment setup batch file (OpenTP1-installation-folder\jp1_template\examples\tools\dcjset_conf.bat) to configure the OpenTP1 system definitions and the load modules in the following order:
   
   • Creates the following folders:
     For a multiOpenTP1: %DCDIR%\aplib, %DCDIR%\jp1_template\tools, and %DCCONFPATH%
     For the original OpenTP1: %DCDIR%\jp1_template\tools
     
   • Copies aplib, conf, and tools from the OpenTP1-installation-folder\jp1_template\examples folder to the created folder.
   • Specifies the node-specific information (such as the file system path name) in the system definitions.
4. OpenTP1_ChangeNodeID (sets a node ID)
   This sample scenario template sets the node ID of OpenTP1 by using the value of the NODE_ID input scenario variable.
   
5. OpenTP1_Deploy (registers OpenTP1)
   For a multiOpenTP1, this sample scenario template executes the dcsetupml command to set up the multiOpenTP1.
   This processing is not performed for the original OpenTP1, because OpenTP1 will have already been registered.
   
6. OpenTP1_MakeFileSystem (creates an OpenTP1 file system)
   This sample scenario template uses an OpenTP1 file creation batch file (%DCDIR%\jp1_template\examples\tools\dcj_mkfs.bat) to create an OpenTP1 file system and OpenTP1 files. The name of the OpenTP1file system is the values of the BETRAN_FILE1 and BETRAN_FILE2 input scenario variables.
   
7. OpenTP1_Start (starts OpenTP1)
   This sample scenario template starts OpenTP1.
   
8. OpenTP1_StartUAP (starts a UAP (sample program))
   This sample scenario template starts a UAP of the user server set in the USER_SERVER_NAME input scenario variable.
   

Before you can execute the sample scenario templates, you must use JP1/AJS2 - Scenario Operation View to register them into JP1/AJS2 - Manager.

The sample scenario templates are stored at the following location:

/ScenarioLibrary/OpenTP1/TP1_ServerBase/OpenTP1_ScenarioScaleout

In order to register the sample scenario templates, you must set the input scenario variables. The following table lists and describes the information to be set in the sample scenario templates.

Table 6-5 Information to be set in the sample scenario templates

Input scenario variable	Description
DCDIR	Home folder of OpenTP1
DCCONFPATH	Folder that stores the OpenTP1 definition files
HOST_NAME#1	Host name of the OpenTP1 node that is to execute the scenario job
USER_NAME#1	OpenTP1 user name
BETRAN_FILE1#2	Path of the OpenTP1 file system
BETRAN_FILE2#2	Path of the OpenTP1 file system
USER_SERVER_NAME	User server name
NODE_ID	OpenTP1 node identifier (unique string of 4 characters assigned to each node)
PORT_NUMBER	OpenTP1's name port number
MULTI_ID#3	MultiOpenTP1 identifier (string of 4 characters that is unique within the node)

#1

This setting can be omitted.

#2

If you define a character special file, you must allocate a partition before you execute a scenario.

#3

Omit this setting for the original OpenTP1.