Generic ARK for HULFT Script Specification

The specifications of the script (hulft_generic_ark.pl) are described below. When creating a Generic resource, register this script with restore, remove, quickCheck, and recover so that each operation will run based on each script behaviour.
Examples of the execution command line and related filenames/paths are provided throughout the descriptions.
Please refer to the actual script for specifics.

Bringing a Resource In Service (restore)

Attempt to start the HULFT resource using the following steps.

1. Retrieves the tag name of its own resource from command-line options.
2. Retrieves the HULFT service name from the tag name of the self-resource. If it fails, subsequent processing is skipped and the process terminates with exit 0. (*) Unless otherwise specified below, if the process terminates abnormally, it terminates with exit 1.
3. When the full path of a script placed during resource creation contains /!restore/ or /!recover/, it operates in restore or recover mode. (*) The same behavior occurs in both restore and recover modes.
4. Check the status of the HULFT service. If it is already running, the process will terminate.
5. Execute the startup process for the HULFT service. If startup fails, the process will terminate abnormally. utlsvcctl.exe -c start
6. Check the status of the HULFT service. If it is not running, the process will terminate abnormally.
7. The configuration file is read to obtain the port numbers for rcvport, obsport, sddport, srvcprocport, and schport used by HULFT. If the configuration file cannot be read, the process terminates abnormally.
8. Verifes that it is possible to connect to the acquired port. If no port is configured, verification will not be performed. If the port cannot be confirmed, the process will terminate abnormally. utlalivecheck.exe -p $port -w 10
9. Exit normally.
   

Taking a Resource Out of Service (remove)

Attempt to stop HULFT resources using the following steps.
(*) Forced termination is converted to normal termination based on the LKHULFT_FORCE_REMOVE parameter. For details, refer to “Generic ARK for HULFT Parameter List”.

1. Retrieves the tag name of its own resource from command-line options.
2. Retrieves the HULFT service name from the tag name of the self-resource. If it fails, subsequent processing is skipped and the process terminates with exit 0. (*) Unless otherwise specified below,if the process terminates abnormally, it terminates with exit 1.
3. When the full path of a script placed during resource creation contains /!remove/, it operates in removemode.
4. Confirm the startup type for the HULFT service. If the startup type is not manual, change it to manual.
   sc qc $service_name | findstr START_TYPE | findstr DEMAND_START sc config $service_name start=demand
5. Check the status of the HULFT service. If it is already stopped, the process will terminate.
6. Performing HULFT service stop processing. If the stop fails, the process will terminate abnormally. utlsvcctl.exe -c stop
7. Check the status of the HULFT service. If it is not stopped, it will terminate abnormally.
8. Exit normally.
   

Monitoring (quickCheck)

Monitoring will be performed with the following content.

1. Perform the same procedures as steps (6) to (9) in the startup process (restore) to monitor HULFT resources. For details, refer to “Bringing a Resource In Service (restore)”.
   

Recovery (recover)

After executing the stop process for the HULFT resource, execute the start process to recover the HULFT resource.

1. After performing the same processing as the Taking a Resource Out of Service (remove), perform the same processing as the Bringing a Resource In Service (restore). For details, refer to “Bringing a Resource In Service (restore)” and “Taking a Resource Out of Service (remove)”.