18.2 When a UAP does not execute correctly

Executor: HiRDB administrator

This section explains the actions to be taken when a UAP does not execute correctly.

Organization of this section
(1) Actions to be taken when a UAP will not execute
(2) Actions to be taken when a UAP does not terminate itself
(3) Actions to be taken when a UAP terminates abnormally

(1) Actions to be taken when a UAP will not execute

Table 18-7 lists the possible reasons for UAP execution errors.

Table 18-7 Causes of UAP execution errors and actions to be taken

Possible causeAction to be taken
An HiRDB system definition is invalidA message is displayed indicating the HiRDB system definition that is invalid. Correct the definition on the basis of this message.
Memory is insufficientA message is issued indicating the memory where the shortage occurred. For shared memory, reevaluate the HiRDB system definitions. For process private memory, terminate any unneeded processes.
Too many users are executing concurrently
  • Increase the value of the pd_max_users operand.
  • If the maximum number of server processes for front-end server or single server has been changed with the pdchprc command, increase the maximum value.
An environment variable is invalid in the client environment definitionSee the manual HiRDB Version 8 UAP Development Guide and correct the environment variable.
HiRDB has not been startedStart HiRDB.
For a HiRDB/Parallel Server, a specific unit or server may be shut down; in such a case, start the unit or server.

(2) Actions to be taken when a UAP does not terminate itself

Check the UAP's execution status (for the procedure, see 8.2 When a UAP or utility execution takes too long). If necessary, use the pdcancel command to terminate the UAP forcibly.

It is recommended that after the command has executed you check whether or not the execution results are correct. For details on how to check command execution results, see the manual HiRDB Version 8 Command Reference.

(3) Actions to be taken when a UAP terminates abnormally

If a UAP terminates abnormally, use the pdls -d prc command to check for any remaining UAP processes. If there are any remaining UAP processes, terminate them with the pdcancel command.

It is recommended that after the command has executed you check whether or not the execution results are correct. For details on how to check command execution results, see the manual HiRDB Version 8 Command Reference.