Corrective actions to take in response to errors that occur when commands are executed

The following table shows corrective actions to take in response to errors that occur when commands are executed.

Table 9-9 Corrective actions to take in response to errors that occur when commands are executed

Executed command	Type of error and its corrective action
pdchgconf	The pdchgconf command cannot be executed when the number of ports that the remote shell can use exceeds its limit. If this occurs, terminate HiRDB normally using the pdstop command, and then modify the configuration.
pdtrndec	The pdtrndec command cannot be executed when the number of ports that the remote shell can use exceeds its limit. If this occurs, manually resolve uncompleted transactions. For details about how to manually resolve uncompleted transactions, see Actions when there is an undetermined transaction in the HiRDB Version 9 System Operation Guide.
pdprgcopy or pdprgrenew	The pdprgcopy and pdprgrenew commands cannot be executed when the number of ports that the remote shell can use exceeds its limit. If this occurs, install updates to replace HiRDB on the server machines on which it is installed.
pdstart	The pdstart command cannot be executed when the number of ports that the remote shell can use exceeds its limit. If this occurs, execute the pdstart -q command to start HiRDB on each of the server machines that comprise a HiRDB parallel server configuration.
pdorend	When you reflect online reorganization with the pdorend command, the communications load can become large if there are many servers, and an error can result if the maximum wait time for reflection processing specified in the -w option is exceeded. If this happens, take the following corrective actions. Specify a larger value in the -w option. Make sure the number of online job transactions is low while the pdorend command is executing.

9.5.3 Corrective actions to take in response to errors that occur when commands are executed