This scenario template sets up a multiOpenTP1 in a specified OpenTP1 folder. If the specified OpenTP1 folder is the original OpenTP1, this scenario template does not execute.

Input scenario variables

DCDIR ~<string of 1 to 50 characters>

Specifies the OpenTP1 folder name to be set up.

This value must be unique within the OpenTP1 system.

HOST_NAME

Specifies the host name of the OpenTP1 node that is to execute the scenario job.

You can omit this input scenario variable. If it is omitted, the scenario job is executed on the target host of the scenario.

USER_NAME

Specifies the user name of the OpenTP1 administrator that is to execute the scenario job.

You can omit this input scenario variable. If it is omitted, the primary user in the user mapping defined in JP1/Base executes the scenario job.

MULTI_ID ~<string of 1 to 4 characters>

Specifies the identifier of a multiOpenTP1.

You can omit this input scenario variable if the OpenTP1 folder specified in the DCDIR input scenario variable is the original OpenTP1.

Executing user

OpenTP1 administrator specified in the USER_NAME input scenario variable

This scenario template deletes a multiOpenTP1 when the specified OpenTP1 folder is a multiOpenTP1. If the specified OpenTP1 folder is the original OpenTP1, this scenario template does not execute.

Input scenario variables

DCDIR ~<string of 1 to 50 characters>

Specifies the name of the OpenTP1 folder to be deleted.

HOST_NAME

Specifies the host name of the OpenTP1 node that is to execute the scenario job.

You can omit this input scenario variable. If it is omitted, the scenario job is executed on the target host of the scenario.

USER_NAME

Specifies the user name of the OpenTP1 administrator that is to execute the scenario job.

You can omit this input scenario variable. If it is omitted, the primary user in the user mapping defined in JP1/Base executes the scenario job.

Executing user

OpenTP1 administrator specified in the USER_NAME input scenario variable

This scenario template sets up an OpenTP1 environment and then starts OpenTP1 and the sample SPP.

Input scenario variables

DCDIR ~<string of 1 to 50 characters>

Specifies a name for the OpenTP1 folder to be set up.

This value must be unique within the OpenTP1 system.

DCCONFPATH

Specifies the folder that stores the OpenTP1 definition files.

HOST_NAME

Specifies the host name of the OpenTP1 node that is to execute the scenario job.

You can omit this input scenario variable. If it is omitted, the scenario job is executed on the target host of the scenario.

USER_NAME

Specifies the user name of the OpenTP1 administrator that is to execute the scenario job.

You can omit this input scenario variable. If it is omitted, the primary user in user mapping defined in JP1/Base executes the scenario job.

BETRAN_FILE1

Specifies the path of the OpenTP1 file system for the primary system.

If you specify a character special file, you must allocate a partition before you execute the scenario template.

BETRAN_FILE2

Specifies the path of the OpenTP1 file system for the secondary system.

If you specify a character special file, you must allocate a partition before you execute the scenario template.

USER_SERVER_NAME ~<string of 1 to 8 characters>

Specifies the name of the user server to be started.

If you use sample scenario templates, specify basespp.

NODE_ID ~<string of 4 characters>

Specifies the node ID of the OpenTP1 to be set up.

This value must be unique within the OpenTP1 system.

PORT_NUMBER ~((5001 to 65535))

Specifies the port number to be used by the name server at the new OpenTP1 node being added to the OpenTP1 system.

MULTI_ID ~<string of 1 to 4 characters>

Specifies the identifier of a multiOpenTP1.

You can omit this input scenario variable if the OpenTP1 folder specified in the DCDIR input scenario variable is the original OpenTP1.

Executing user

OpenTP1 administrator specified in the USER_NAME input scenario variable