It includes the following lists of abort codes:

• Table 3-1 ABORT codes PaXXXXX
• Table 3-2 ABORT codes PbXXXXX
• Table 3-3 ABORT codes PdXXXXX
• Table 3-4 ABORT codes PeXXXXX
• Table 3-5 ABORT codes PhXXXXX
• Table 3-6 ABORT codes PkXXXXX
• Table 3-7 ABORT codes PoXXXXX
• Table 3-8 ABORT codes PrXXXXX
• Table 3-9 ABORT codes PsXXXXX
• Table 3-10 ABORT codes PtXXXXX
• Table 3-11 ABORT codes PuXXXXX
• Table 3-12 ABORT codes PwXXXXX
• Table 3-13 ABORT codes PxXXXXX
• Table 3-14 ABORT codes PyXXXXX
• Table 3-15 ABORT codes PiXXXXX
  

  Table 3-1 ABORT codes PaXXXXX

  ABORT Code	Cause	Action
  Pab1001	Allocation of combuf communication field failed for one of the following reasons: Allocation of communication field or header failed. Requested size was invalid.	Back up all files in %PDDIR%\spool and contact a customer engineer.
  Pab1005	Value returned from the dic manager was invalid for because the table ID lock failed.
  Pab1113	Transmission of SQL object transfer request information failed during normal communication.	Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. This error may occur when the workload at the destination (FES, BES, DIC) is high. In such a case, reduce the workload at the destination. This abort code can also be generated by an SQL object buffer shortage, in which case increase the value of the pd_sql_object_cache_size operand of the system definition or server definition. This error can also occur if the execution of the pdcancel command eliminates the transmission destination server process.
  Pab1114	Reception of SQL object transfer request information failed during normal communication.	Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. This error may occur when the workload at the destination (FES) is high. In such a case, reduce the workload at the destination.
  Pab1500	Invalid object was transferred from the front-end server. When HiRDB is operated in a multi-FES environment, this error may occur if the number of FES processes is greater than the number of individual BES processes (value of pd_max_bes_process in server definition).	Back up all files in %PDDIR%\spool and contact a customer engineer.
  Pab1501	SQL object transfer failed. Transaction was terminated at the front-end server due to an error.	Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute.
  Pab1502	A conflict was detected during SQL object transfer processing using the routine.	Back up all files in %PDDIR%\spool and contact a customer engineer.
  Pab2001	Thread suspense lock failed.
  Pab2002	Release of thread suspense lock failed.
  Pab2003	Resource lock failed.	Correct the error that occurred in object creation and object transfer processing and re-execute.
  Pab2004	Release of resource lock failed.	Back up all files in %PDDIR%\spool and contact a customer engineer.
  Pab2010	Lock control on SQL object management information using the routine failed.
  Pab2011	Release of lock control on SQL object management information using the routine failed.
  Pab2012	Lock control on SQL object get management information using the routine failed.	Check the error cause from the error message that was output before the processing was aborted, take corrective action, and then re-execute.
  Pab2013	Release of lock control on SQL object get management information using the routine failed.	Back up all files in %PDDIR%\spool and contact a customer engineer.
  Pab2350	Length of module requested for release is invalid.
  Pab2351	Address of module requested for release is invalid.
  Pab2352	Information returned from dic to sqa is invalid.
  Pab2353	Length of module requested for allocation is invalid.
  Pac1001	A connect request was rejected by the dictionary manager, but rpc chain cannot be disconnected.
  Pac2001	Return code of dbh function call is invalid. (p_f_dbh_drop_list)
  Pac2004	0 was specified for pd_max_access_tables.
  Pac2008	Lock control on user management information failed.	Check the error cause from the error message that was output before processing was aborted, take corrective action, and then re-execute.
  Pac2009	Release of lock control on user management information failed.	Back up all files in %PDDIR%\spool and contact a customer engineer.
  Pac2050	Output outhead length is invalid for RPC from client.
  Pac2051	SQL to be executed without creating an SQL object (definition SQL) has an invalid SQL object.
  Pac2052	Requested static compilation has the same section number as the already compiled dynamic SQL. Or, requested dynamic compilation has the same section number as the already compiled static SQL.
  Pac2053	Number of p_code's obtained from optimization processing (zipsncls) is invalid ( 0).
  Pac2054	Parameter is invalid in a statistics log acquisition request (log address is 0, log size is 0).
  Pac2055	Process private area necessary for SQL execution cannot be allocated.	Reduce the number of resident processes in the server for which this message was output.
  Pac2056	Input data format is invalid for RPC from client (offset count is 0, sqlioa offset is 0).	Back up all files in %PDDIR%\spool and contact a customer engineer.
  Pac2352	Return code of DIC function call is invalid. (p_f_dic_freecache)
  Pac2354	Check the error message that was output before the abort (the error indicated in this message) occurred. If an error message was not output before the abort, the following causes can be suspected: When a UAP under OLTP is the client and the multi-connection facility is used in a HiRDB server that does not support the multi-connection facility: within a single transaction branch under OLTP, an SQL statement was executed using different connection handles on the same HiRDB. The upper limit on the number of transactions that can be executed concurrently was exceeded. It is possible that transactions that cannot be committed or rolled back in the system are waiting for settlement. A temporary memory shortage occurred. The upper limit on the number of files that can be opened concurrently has been reached.	Check the cause of the problem based on the error message that was output before the abort. If an error message was not output before the abort, take one of the following actions: Within a single transaction branch under OLTP, different connection handles cannot be used on the same HiRDB. One of the following actions should be taken: Check to see whether the HiRDB server supports the multi-connection facility. Check the UAP processing method. Execute the pdls -d trn command. If a transaction with a value greater than or equal to pd_max_users is indicated, wait awhile, and then re-execute the command. To provide for the possibility that the error cannot be recovered, prepare to settle the transactions by using either the pdcmt or pdrbk command. Wait awhile, and then re-execute the command. Review the upper limit on the number of files that can be opened in a process. Also review the kernel parameter if necessary. If the problem persists after the above actions are taken, save the information to be acquired in the event of an error, and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Pac2355	Internal conflict occurred in the controller.	Back up all files in %PDDIR%\spool and contact a customer engineer.
  Pac2358	Shared memory size (module pool) to be allocated is invalid.
  Pac2359	Characters type code is invalid.
  Pac2360	Execution with a section number not found in the object was requested during stored procedure execution.
  Pac2361	An operation code that cannot be executed was requested during stored procedure execution.
  Pac2362	A section that cannot be executed was found in a stored procedure object.
  Pac2363	Transaction request is invalid.
  Pac2364	UAP client libraries forming a global transaction have different versions.	Match the versions of the UAP client libraries forming the global transaction.
  Pac2365	A process private area required for SQL execution cannot be allocated, or memory is insufficient.	Check the load on the system and re-execute the UAP. Alternatively, re-estimate memory.
  Pac2366	An error was returned because a system error occurred during reception processing (front-end server) of the trigger execution request.	Check the error cause from the error message that was output before processing was aborted, take corrective action, and then re-execute. This error may also occur when there is a heavy load on the transmission source (back-end server). If this is the case, reduce the load on the transmission source.
  Pac2367	Transmission processing of the trigger execution result returned an error. Possible causes are that either the transmission destination server (back-end server) or the unit is down, or that the system could not respond due to a heavy load.	Check the error cause from the error message that was output before processing was aborted, take corrective action, and then re-execute.
  Pac2368	A trigger execution request failed. An error occurred; then the front-end server terminated the transaction.	Check the error cause from the error message that was output before processing was aborted, take corrective action, and then re-execute.
  Pac2501	Attempt was made to execute Auto Commit in the XA environment.	Back up all files in %PDDIR%\spool and contact a customer engineer
  Pac2502	Invalid prepare request was issued from client.
  Pae2250	Argument in high-order module is invalid during SQL object execution.	Back up all files in %PDDIR%\spool and contact a customer engineer. If HiRDB does not restart automatically, restart it manually.
  Pae2251	System error occurred during SQL object execution (invalid return code).
  Pae2252	SQL object is invalid.
  Pae2253	Return code of a low-order module is invalid during SQL object execution.
  Pae2255	System error occurred during SQL object execution (invalid internal code).
  Pae2257	Memory shortage or system error occurred during SQL object execution (internal conflict).	If a memory shortage occurred, wait a while and then re-execute. Otherwise, contact a customer engineer.
  Pae2258	Internal system contradiction was detected during SQL object execution.	Contact a customer engineer.
  Pae2259	Allocation of system private area failed or a memory shortage occurred.	Check the system load and re-execute the UAP. Or, re-estimate the memory size.
  Pae2354	Return code of SYSM function call is invalid.	Check the error cause from the error message that was output before processing was aborted, take corrective action, and then re-execute. If an error message is output, save the files under %PDDIR%\spool, %PDDIR%\conf, and %PDDIR%\tmp, save the event log (in UNIX, syslogfile), and contact a customer engineer.
  Pae3001	Reply text receive processing resulted in an error.	Contact a customer engineer.
  Pae3002	HiRDB-specified information is missing from reply text.
  Pae3003	Unexpected reply text was received from the server.
  Pae3004	The results of SQL statements executed between HiRDB servers were not received within the specified PDCWAITTIME. A server-to-server communication error may have occurred. HiRDB executes multiple server-to-server communications or database accesses for a single request from a client. Because the client monitors the cumulative processing time using the value of PDCWAITTIME, it is usually the client that first detects a timeout and sends a recovery instruction to the server. If the client is unable to send a recovery instruction due to a communication error between the client and server, the server also detects the error.	Check the error cause from the OS and HiRDB error messages that were displayed prior to the abort, take appropriate action, then re-execute.
  Pae3005	Timeout occurred in a HiRDB/Parallel Server while a back-end server or dictionary server was waiting for an SQL execution request library to be received from a front-end server.	An error, such as a memory shortage, may have occurred in the unit in which the back-end server process or dictionary server process is located, making SQL execution impossible. Determine the cause of the error in the applicable unit, and re-execute after taking appropriate action. Until the action is completed, keep intact the files under %PDDIR%\spool, \conf, and \tmp.
  Pae3010	Retrieval result send processing resulted in an error. The destination server or unit may be shut down or unable to reply due to high workload.	Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute.
  Pae3100	An error occurred during analysis of the following operands: pd_max_list_users pd_max_list_count pd_java_runtimepath pd_java_libpath pd_sql_send_buff_size	Save the files under %PDDIR%\spool, %PDDIR%\conf, and %PDDIR%\tmp, save the event log (in UNIX, syslogfile), and contact a customer engineer.
  Pae3101	Shared memory could not be released while processing an error that had occurred at server startup or while stopping the server.
  Pae3110	An unrecoverable error occurred during thread lock.
  Pae4000	Either of the following possibilities should be investigated: The sending of an abstract data type get request returned an error. Possibly the destination server or unit is down or unable to respond due to high load. An internal conflict occurred in the operation for the abstract data type.	Check the error cause from the error message that was output before processing was aborted, take corrective action, and then re-execute. If the problem is other than a transmission error, contact a customer engineer.
  Pae4001	The information returned from the plug-in implementation function is invalid.	Contact a customer engineer. For the name of the plug-in implementation function in which the error occurred, see the preceding error message.
  Pae5000	An unrecoverable error occurred during a transaction commit or rollback.	Save the files under %PDDIR%\spool, %PDDIR%\conf, and %PDDIR%\tmp, save the event log (in UNIX, syslogfile), and contact a customer engineer.
  Pag1660	Invalid data type was detected during data comparison.	Back up all files in %PDDIR%\spool and contact a customer engineer. If HiRDB does not restart automatically, restart it manually.
  Pag1670	Internal system conflict was detected during regular expression comparison.
  Pag1671	Internal system conflict was detected during regular expression comparison.
  Pag1672	Internal system conflict was detected during regular expression comparison.
  Pag1680	Internal system conflict was detected during data conversion.
  Pao0002	Internal conflict occurred during optimization processing.	Back up all files in %PDDIR%\spool and contact a customer engineer.
  Pao0003	Foreign server information is not configured.	After executing the CREATE SERVER statement, restart the HiRDB system and re-execute SQL. If this error occurs even after restarting the HiRDB system, back up all files in %PDDIR%\spool or %PDDIR%\conf and contact a customer engineer.
  Pao2001	SQL object was invalid.	Back up all files in %PDDIR%\spool and contact a customer engineer.
  Pao2002	Internal conflict occurred during optimization processing at the time of execution.
  Pao3001	An internal conflict occurred while the definition file was being read.	Back up all files in %PDDIR%\spool and %PDDIR%\conf, and contact a customer engineer.
  Pao3002	A memory shortage occurred while the definition file was being read.	Take corrective action as indicated by the memory shortage error message output immediately before this message, and restart the unit that shut down.
  Pap2255	There is not enough stack data area.	Contact a customer engineer.
  Par2400	Attempt was made to create a free chain in an area other than the control block area.	Back up all files in %PDDIR%\spool and contact a customer engineer.
  Par2401	Conflict occurred while creating a free chain for a control block.
  Par2402	Attempt was made to release a control block that was already released.
  Par2410	Terminated abnormally.	Back up all files in %PDDIR%\spool and contact a customer engineer. If HiRDB does not restart automatically, restart it manually.
  Par2412	Detachment of main thread failed in the same section.	Back up all files in %PDDIR%\spool and contact a customer engineer.
  Par2413	Drop list processing terminated abnormally while releasing the SCB control block.
  Par2414	End next processing terminated abnormally while releasing the PCB control block.	Back up all files in %PDDIR%\spool and contact a customer engineer. If HiRDB does not restart automatically, restart it manually.
  Par2415	Attempt was made to allocate an area of 1 GB or more.	Back up all files in %PDDIR%\spool and contact a customer engineer.
  Pas2100	Analysis trigger was invalid during semantic analysis.
  Pas2101	Contradiction was detected during SQL analysis processing.	Back up all files in %PDDIR%\spool and %PDDIR%\tmp and contact a customer engineer.
  Pas2352	Invalid information was returned from dic to sqa.	Contact a customer engineer.

  Table 3-2 ABORT codes (PbXXXXX)

  ABORT Code	Cause	Action
  Pba0101	Internal conflict occurred.	Contact a customer engineer.
  Pba0201	Parameter is invalid.
  Pba0202	Execution sequence of functions is invalid.
  Pba0301	Return code is invalid.
  Pba0401	Contents of input buffer from SQA are invalid.
  Pba0402	Contents of output buffer from SQA are invalid.
  Pba0501	Non-execution of the XA interface function was detected.
  Pba0502	Non-execution of the DF/UX initialization function or DF for Windows NT initialization function was detected.
  Pba0601	SQL statement's execution function was called incorrectly.
  Pbb0200	An input parameter of a memory management function is invalid.
  Pbb0201	An input address of a memory management function is invalid.
  Pbb0204	A status error occurred in a memory management function.
  Pbb0290	A return code for a memory management function is invalid.
  Pbb0300	No base address is set for CMT.
  Pbb0301	No base address is set for PMT.
  Pbb0400	An input parameter of an error reporting function is invalid.
  Pbb0401	An event type of an error reporting function is invalid.
  Pbb0402	An event type of an error reporting function is not supported.
  Pbb0403	An error type of an error reporting function is invalid.
  Pbb0404	An error type of an error reporting function is not supported.
  Pbb0405	No table creation area exists for an error reporting function.
  Pbb0490	An internal conflict occurred in an error reporting function.
  Pbb0500	A conflict occurred in an internal table of an XA request processing function.
  Pbb0590	An internal conflict occurred in an XA request processing function.
  Pbb0600	A conflict occurred in an internal table of an SQLplug function.
  Pbb0601	An SFD/SQL conflict occurred in an SQLplug function.
  Pbb0690	An internal conflict occurred in an SQLplug function.
  Pbb0700	A input parameter of a sequence check function is invalid.
  Pbb0790	A return code of a sequence check function is invalid.
  Pbb1000	A conflict occurred in an internal table of an SQL conversion function.
  Pbb1001	An SFD/SQL conflict occurred in an SQL conversion function.
  Pbb1090	An internal conflict occurred in an SQL conversion function.
  Pbb2090	An SQA return code is invalid.
  Pbc0001	Error occurred during abort code editing.
  Pbc0002	Internal contradiction occurred.
  Pbc0101	Invalid address was specified for memory reallocation or release.
  Pbc0102	Destruction of a memory area was detected.

  Table 3-3 ABORT codes (PdXXXXX)

  ABORT Code	Cause	Action
  Pd00001	Error occurred during lock acquisition processing.	The KFPD00004-E message is output. If this message displays pdi_olk_thdlock as the name of the function resulting in the error and -20023 as the value of errno, the number of FIFOs per process has exceeded the OS's limit; increase the value for the OS. If the message displays pdi_olk_thdlock as the name of the function resulting in the error and -20024 as the value of errno, the number of FIFOs per system has exceeded the OS's limit; increase the value for the OS. If any other information is displayed in the KFPD00004-E message, contact a customer engineer.
  Pd00003	File I/O error occurred.	Refer to the KFPD00003 message to check the cause of the I/O error, and take appropriate action.
  Pd00004	System call error occurred.	Refer to the KFPD00004 message to check the cause of the system call error, and take appropriate action.
  Pd00005	Error occurred during server initialization.	If the KFPD00005-E, KFPD00020-E or KFPD00021-E message was output, take corrective action based on the message that was output. If none of these messages was output, contact a customer engineer.
  Pd00008	Internal system conflict occurred.	During an abort, a KFPD00008-E or KFPD00020-E message is output. Take action according to the message that has been output.
  Pd00030	Internal system conflict occurred.	Contact a customer engineer.
  Pd00777	Dictionary contents are invalid.	Contact a customer engineer.
  Pd10000	Registry thread activation failed.	If the KFPD00021-E message was output, take corrective action based on that message. If this message was not output, contact a customer engineer.
  Pd10001	Registry thread stop failed.	Contact a customer engineer.
  Pd10002	An error occurred during access to the registry.	Check the error cause from the error message that was output before processing was aborted, take the corrective action, and then re-execute.
  Pd17001	An error occurred during object cache control processing.	Contact a customer engineer.

  Table 3-4 List of abort codes (PeXXXXX)

  Abort code	Cause	Action
  Peama01	An internal error occurred after the command received by the HiRDB Assist - Server was executed; the HiRDB Assist - Server process terminated.	UNIX version: Save all files under the setup directory for the HiRDB Assist - Server and also the syslog file, and then notify a customer engineer. Windows version: There may have been a request for multiple commands to be executed consecutively. Provide a one-second interval between command executions, and then re-execute the command. If the Peama01 abort problem still persists after this action is taken, save all files under the HiRDB Assist - Server installation directory and the event log, and notify a customer engineer.

  Table 3-5 ABORT codes (PhXXXXX)

  ABORT Code	Cause	Action
  Phb0001	Message output error occurred.	Back up all files in %PDDIR%\spool and restart HiRDB. Or, notify a customer engineer.
  Phb0002	Semaphore handling error occurred.
  Phb0003	ENQ counter error occurred.
  Phb0004	Invalid put request was issued.
  Phb0005	Function code is invalid.
  Phb0006	Internal function error occurred.
  Phb0007	Internal conflict was detected in the HiRDB file system.
  Phb0008	Invalid free request was issued.
  Phb0009	Log output error occurred.
  Phb0010	Resource shortage occurred while opening a HiRDB file.	Reduce the number of users, and start HiRDB.
  Phb0011	Semaphore initialization error occurred.	Resolve the cause of the error indicated in the KFPH23015-E message, and then restart HiRDB. If the cause of the error cannot be determined, contact a customer engineer.
  Phb0012	Shared memory detachment error occurred.
  Phb0013	In UNIX, an ordinary file close error occurred. In Windows, a file close error occurred.
  Phb0014	Shared memory release error occurred.
  Phb0015	Shared memory allocation error occurred.
  Phb0016	Shared memory attachment error occurred.
  Phb0017	There is no available entry in TCB buffer stack.	Back up all files in %PDDIR%\spool and restart HiRDB. Or, contact a customer engineer.
  Phb0018	Lock error occurred.
  Phb0019	Unlock error occurred.
  Phb0032	An error occurred during allocation of status file records.	Take the action indicated in the immediately preceding KFPH23033-E message, and restart HiRDB.
  Phb0106	A memory shortage occurred.	Take corrective action per the KFPH23003-E message output immediately before this message, and restart HiRDB.
  Phb0107	Mapping of the global buffer failed.	Take corrective action per the KFPH23003-E or KFPH23005-E message output immediately before this message, and restart HiRDB.
  Phb1001	Buffer definition analysis termination error occurred.	Resolve the cause of the error indicated in the KFPH23015-E message, and then restart HiRDB. If the cause of the error cannot be determined, contact a customer engineer.
  Phb1002	Invalid argument was detected while starting buffer definition analysis.
  Phb1003	Invalid argument was detected during buffer definition analysis.
  Phb1004	Invalid option was detected during buffer definition analysis.	Back up all files in %PDDIR%\spool and restart HiRDB. Or, contact a customer engineer.
  Phb1018	Acquisition of RDAREA information for global buffer creation failed.	Determine the cause from the error messages output before the ABORT code, take appropriate action, and then restart the unit. If return code=-310 is output in a KFPH22013-E message, the dictionary server is stopped; restart the dictionary server and then restart the unit. If the cause of the error cannot be determined from the error messages, contact a customer engineer.
  Phb1021	The number of pdbuffers exceeds the limit.	Take action as indicated in the immediately preceding KFPH23029-E message, and restart HiRDB.
  Phb1022	The number of pdbuffers does not match the number when started previously.	Take action as indicated in the immediately preceding KFPH23031-E message, and restart HiRDB.
  Phb1023	The pdbuffer option specification is invalid.	Take action as indicated in the immediately preceding KFPU00218-E message, and restart HiRDB.
  Phb1025	The memory size was exceeded.	Take action as indicated in the immediately preceding KFPH23032-E message, and restart HiRDB.
  Phb1026	The dynamic update of global buffer facility cannot be used.	Take action as indicated in the immediately preceding KFPH23034-E message, and restart HiRDB.
  Phb2001	RDAREA ID or page number is invalid.	Restart HiRDB and recover the corresponding RDAREA. Also, contact a customer engineer.
  Phb2002	Shortage occurred in reserve buffer.	Back up all files in %PDDIR%\spool and restart HiRDB. Or, contact a customer engineer.
  Phb2003	Duplicate GET request was issued.
  Phb2004	Chain error occurred.
  Phb2007	Time stamp mismatch was detected while outputting data to a database.
  Phb2008	Object ID mismatch within a page was detected during data output to the database.
  Phb2009	Invalid parameter or invalid processing sequence was detected while forcibly outputting a log.
  Phb2010	If unitdown is specified in the pd_db_io_error_action operand, an RDAREA I/O error has occurred, causing HiRDB (for HiRDB/Parallel Server, a unit) to terminate abnormally.	Referring to the error message output before the process aborted, determine the cause of the error. Then, either switch over the system again, or restart HiRDB.
  Phb3001	Batch input occurred on index page.	Back up all files in %PDDIR%\spool and restart HiRDB. Alternatively, contact a customer engineer.
  Phb3002	Batch input request is invalid.
  Phb3004	HiRDB file OPEN/CLOSE processing failed.
  Phb3008	A server process terminated abnormally while a local buffer was being used. A page (update page) was detected that, temporarily, recovery processing could not recover.	Restart HiRDB.
  Phb4001	Internal conflict occurred.	Back up all files in %PDDIR%\spool, and restart HiRDB. Alternatively, contact a customer engineer.
  Phb4002	Undefined value was returned.
  Phb4003	Function parameter error occurred.
  Phb4004	rpc open error occurred.
  Phb4005 Phb4006 Phb4007	Internal function error occurred.
  Phb4009	Memory shortage occurred.	Reduce the number of users, and then start HiRDB.
  Phb4010	The message queue ID could not be obtained.	Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact a customer engineer.
  Phb4011	Message receive error occurred.
  Phb4012	Message send error occurred.
  Phb4020	Update flag is invalid.
  Phb4022	Synchronization output flag is invalid.
  Phb4023	Deferred write status is invalid.
  Phb4030	HiRDB file initialization error occurred.
  Phb4031	HiRDB file open error occurred.
  Phb4032	HiRDB file close error occurred.
  Phb4033	HiRDB file write error occurred.
  Phb4034	A HiRDB file close error occurred.	Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact a customer engineer.
  Phb4035	Disk number is invalid.	Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact a customer engineer.
  Phb4041	Repeated attempts to open a HiRDB file failed due to a shortage of open resources.	Take action according to the preceding KFPH23201-W or KFPH23100-E message, and then restart HiRDB.
  Phb4044	A semaphore operation error occurred in the deferred write process.	Check the cause of the error based on the error message (KFPO00107-E) preceding the abort, take appropriate action, and then re-execute the command. If an error message is not output, save the files under %PDDIR%\spool, and then restart HiRDB. Also, notify a customer engineer.
  Phb4109	A memory shortage occurred.	Take one of the following actions to provide additional memory, and then restart HiRDB: Reduce the number of other processes running on the same machine. Increase the swap area. Provide additional real memory.
  Phb4141	When the facility for parallel writes in deferred write processing was being used, a HiRDB file could not be opened due to a shortage of open resources, even when the opening operation was retried in the write process.	Take corrective action according to a previous KFPH23201-W or KFPH23100-E message, and then restart HiRDB.
  Phb4144	When the facility for parallel writes in deferred write processing was being used, a semaphore operation error occurred in the write process.	Check the cause of the error based on the error message (KFPO00107-E) preceding the abort, take appropriate action, and then re-execute the command. If an error message is not output, save the files under %PDDIR%\spool, and then restart HiRDB. Also, notify a customer engineer.
  Phb**** *: Any character string	Internal contradiction was detected during DB buffer processing.	Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact a customer engineer.
  Phc0001	getarea return code is invalid.	Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. If no error message was output, contact a customer engineer.
  Phc0002	Message editing failed.
  Phd0002	RDAREA ID is invalid.	Check to see if there is an operation error on the applicable RDAREA. If there is an error, the RDAREA should be recovered. If the RDAREA has been moved, restart HiRDB. If there is no error, save the files under %PDDIR%\spool, and contact a customer engineer.
  Phd0003	Internal work file access error occurred.	Check the system operation and recover the database if an error was found. If there is no error, save the files under %PDDIR%\spool, and contact a customer engineer.
  Phd0004	Thread lock terminated abnormally.	Save the files under %PDDIR%\spool, and contact a customer engineer.
  Phd0005	File number is invalid.	Check the system operation and recover the database if an error was found. If there is no error, save the files under %PDDIR%\spool, and contact a customer engineer.
  Phd0006	Invalid log was detected during rollback.
  Phd0007	Invalid log was detected during log collection.
  Phd0008	Internal conflict was detected while a server transfer area was being created.	Save the files under %PDDIR%\spool, and contact a customer engineer.
  Phd0009	Internal conflict was detected during communication.
  Phd0010	An internal function error was detected.
  Phi0002	Analysis of a definition file failed.
  Phi0013	A thread lock error occurred.
  Phi0014	A thread unlock error occurred.
  Phi1001	Acquisition of environment definition variable failed.	Check the error message that was output before ABORT for the cause of the error, take appropriate action, then re-execute. If no error message was output, contact a customer engineer.
  Phi1002	Allocation of common control block failed.
  Phi1003	Communication open error occurred.
  Phi1006	Initialization error occurred in the SQL analysis component.
  Phi1007	Initialization error occurred in the dictionary management component.
  Phi1008	Initialization error occurred in the database management component.
  Phi1010	Allocation of log server area failed.
  Phi1011	Message editing failed.
  Phi1012	Acquisition of a HiRDB database environment information file from the running system failed.	If all of the following conditions are satisfied, confirm that the HiRDB running system is active, and then restart the HiRDB standby system: Hitachi HA Toolkit Extension is being used. The rapid system switchover facility is being used. A KFPS01861-E message was output to the event log (in UNIX, syslogfile) of the running system. Otherwise, eliminate the cause of the error output in the KFPH20003-E message, and restart the HiRDB standby system. If you cannot determine the cause of the error, contact a customer engineer.
  Phl0001	Internal logical contradiction occurred.	Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact a customer engineer.
  Phl0002	Buffer allocation error occurred.
  Phl0003	Function code was invalid during Build-List.
  Phl0004	List ID (address) is invalid.
  Phl0005	Return code is invalid.
  Phl0006	read request page number is invalid.
  Phl0007	Number of pages in string is invalid.
  Phl0008	Work table buffer pool's contents are invalid.	Back up all files from %PDDIR%\spool and contact a customer engineer.
  Phl2355	Return code contradiction occurred.	If RPC trace information is being collected, back up the RPC trace information. Next, back up all files in %PDDIR%\spool and restart HiRDB. Also, contact a customer engineer.
  Phl3722 Phl3723	Internal conflict occurred.	Save the files under %PDDIR%\spool, and contact a customer engineer.
  Phl4002 Phl4003	Interface is invalid.
  Phl4018	Return code of a list module is invalid.
  Phl4023	Row address of a list is invalid.
  Phl5301	I/O error occurred.
  Phlb001	Internal contradiction was detected.
  Phm0001	Return code of buffer management is invalid.	Use the database recovery utility to recover the database and restart.
  Phm0002	Return code of directory management is invalid.	Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact a customer engineer.
  Phm0003	A memory shortage occurred when a shared table was being updated without issuing a LOCK TABLE statement in EXCLUSIVE mode.	Take corrective action according to the preceding memory shortage error message. If the unit is down, restart the unit that was shut down.
  Phm0004	Buffer memory corruption was detected when a shared table was being updated without issuing a LOCK TABLE statement in EXCLUSIVE mode.	Save the files under %PDDIR%\spool, restart the abnormally terminated unit, and contact a customer engineer.
  Phm0999	Internal contradiction was detected.	Use the database recovery utility to recover the database and restart.
  Phm1001	Attempt was made to insert a FIX table page that was greater than the defined length.	Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact a customer engineer.
  Phm1002	I/O area or offset list was not found.
  Phm1003	Length of variable-length data is 0.
  Phm1100 Phm1101	Internal conflict occurred during BLOB data I/O processing.	Contact a customer engineer.
  Phm1102	Invalid RDAREA number was specified for BLOB data.	If the RDAREA has been moved, restart HiRDB. If there is no operation error, contact a customer engineer.
  Phm1103	Internal conflict occurred while BLOB data was being updated.	Contact a customer engineer.
  Phm1104	File number was invalid.
  Phm1105	Internal conflict occurred while BLOB data was being retrieved.
  Phm1110	A return code indicating an error was returned from another component function.	Recover the database using the database recovery utility.
  Phm2001	Format of a row to be updated is invalid.	Check the database recovery procedure for an error. If there is a database that has not been recovered, either recover it or re-create it. If there is no error, contact a customer engineer.
  Phm2002	Type of table to be updated is invalid.	Back up the files under %PDDIR%\spool and contact a customer engineer.
  Phm5001	An attempt was made to project a row identifier during row I/F for a non-FIX table.
  Phm5002	Buffer management error occurred.	Use the database recovery utility to recover the database and restart.
  Phm5003	Specified scan type is invalid.	Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact a customer engineer.
  Phm5004	Data projection is not available to specified server machine.
  Phm5011	Page is invalid (branching destination page).	Check the database recovery procedure for an error. If there is a database that has not been recovered, either recover it or re-create it. If there is no error, contact a customer engineer.
  Phm5012	Page is invalid (branching source page).
  Phm5013	Page number is invalid. Table ID in the database does not match the requested table ID during fetch processing.
  Phm5014	Slot value is invalid. A row was deleted or a nonexisting row was fetched.
  Phm5015	Page is invalid (page specified for fetch was not found).
  Phm5016	Slot value is invalid. A row was deleted, or a nonexisting row was specified as the branching destination.
  Phm5017	Row format is invalid. The format of the fetched row is not P/B/ F.
  Phm5018	Row format is invalid. The format of the branching destination row is not B'/F'.
  Phm5019	Invalid row format. The branching destination row is not in the B/B'/A format.	Make sure that no errors were made in the database recovery procedure. If there is an unrecovered database, either recover or recreate it. If there is no error, contact a customer engineer.
  Phm5020	The stored page for BINARY attribute data of the abstract data type is invalid.
  Phm5021	Return value is invalid.	Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact a customer engineer.
  Phm5022	Work area shortage occurred while a suppress table was being retrieved.	Set the number of DECIMAL columns in the conditional expression to no more than 512 and re-execute. Back up all files in %PDDIR%\spool and contact a customer engineer.
  Phm6000	Invalid locking operation, or invalid RDAREA ID.	If the RDAREA has been moved, restart HiRDB. If there is no operation error, save the files under %PDDIR%\spool, and contact a customer engineer.
  Phm6001 Phm6002 Phm6003 Phm6004	Lock processing is invalid.	Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact a customer engineer.
  Phm6005 Phm6007	Codes indicating an error was returned from another component's function.
  Phm6100	The HiRDB restart memory size for the process native area used by all processes on the unit controller is insufficient.	Because recovery by restarting is not complete, complete the recovery using the following procedure: Unload logs following the log displayed in the previous synchronization point completion message KFPS02183-I. Use pdstart -r to start HiRDB. Use the pdrstr command to recover the most recent synchronization point of the RDAREA used by the master directory. Use pdstop to stop. Use pdstart dbdestroy to start HiRDB. Recover RDAREAs other than the RDAREA used by the master directory to the most recent synchronization point. Use pdstop to stop. After completing the recovery, revise the definition parameters or expand the memory, and then perform a normal startup of HiRDB. For details about the recovery procedure, see the section on recovering all RDAREAs to the most recent synchronization point in the manual HiRDB Version 8 System Operation Guide.
  Phm7000	Attempt was made to output an invalid log.	Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact a customer engineer.
  Phm9000	Internal logical contradiction was detected.	Use the database recovery utility to recover the database and restart.
  Phr0100	Contradiction was detected while updating page writing information.	Back up the files under %PDDIR%\spool and contact a customer engineer.
  Phr1110	Internal conflict occurred in the table for managing the RDAREA status.	Restart HiRDB.
  Phr1111	Internal conflict occurred when RDAREA status information was being registered in the table for managing RDAREA status.
  Phr1112	The number of RDAREAs exceeded the maximum system value when RDAREA status information was being registered.
  Phr1113	In the redo log assignment during restart, a log assignment process was not found.	Use the database recovery utility to recover the database and restart.
  Phr1114	The number of redo processes during restart is invalid.
  Phr1115	An attempt was made to start a redo process without acquiring a log buffer during restart.
  Phr1116	During restart, a log with the invalid redo log type was detected.
  Phr1117	The number of RDAREAs contradicts the number of RDAREA status information items in the table for managing RDAREA status.
  Phr1118	Internal conflict occurred in a restart write page information table.	Back up the files under %PDDIR%\spool, and contact a customer engineer.
  Phr1210	Internal conflict occurred in information on the number of log update pages during a restart redo process.	Use the database recovery utility to recover the database and restart.
  Phr1212	During the restart redo process, an attempt was made to improperly update the transaction management table during the analysis of the transaction status.
  Phr1213	During the restart redo process, the index log contains invalid lock recovery information.
  Phr1214	During the restart redo process, the directory log contains invalid lock recovery information.
  Phr1215	During the restart redo process, the log for recovering the lock contains invalid lock recovery information.
  Phr1216	During the restart redo process, the log contains an invalid lock type.
  Phr1217	During the restart redo process, processing instructions for the log contain an error.
  Phr1218	The number of disks is invalid.
  Phr1300	Code indicating an error was returned by another subcomponent function.	Check the error cause from the error message that was output before processing was aborted, take corrective action, and then re-execute. If an error message was not output before processing was aborted, save %PDDIR%\spool and contact a customer engineer.
  Phr1310	During the restart data page redo process, a return code indicating an error was returned.	Use the database recovery utility to recover the database and restart.
  Phr1311	During the restart index page redo process, a return code indicating an error was returned.
  Phr1312	During the restart directory page redo process, a return code indicating an error was returned.
  Phr1320	During the restart redo processing, a return code indicating an error was returned when an attempt was made to recover a directory inconsistency.
  Phr1321	During the restart redo processing, a return code indicating an error was returned when an attempt was made to recover an index inconsistency.
  Phr1400	Code indicating an error was returned from another component function.	If an error message was output before the abort, determine the cause of the problem based on that message, take appropriate corrective action, and then re-execute the command. If there was no error message before the abort, save the files under %PDDIR%\spool, and contact a customer engineer.
  Phr1401	During the restart, acquisition of a log buffer shared memory segment address failed.	Recover the database using the database recovery utility.
  Phr1410	Recovery-related semaphore operation failed.
  Phr1411	Retrieval of recovery-related semaphore value failed.
  Phr1412	Allocation of recovery-related semaphore failed.
  Phr1413	Recovery-related semaphore operation failed.
  Phr1420	Allocation of area used for recovery-related processing (process private area) failed.	Check the number of processes, take appropriate action, and re-execute.
  Phr1421 Phr1422 Phr1423 Phr1424	Allocation of area required for RDAREA status management table (process private area) failed.
  Phr1425 Phr1426 Phr1427 Phr1428	Allocation of an area (process private area) required for management of page write information used in a restart redo failed.
  Phr1430	A return code indicating an error was returned from the pd_lck_notrn_get function during lock recovery at restart.	Save the information to be acquired in the event of an error, and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Phr1431	A return code indicating an error was returned from the pd_lck_notrn_release function during lock release at restart.
  Phr1440	A return code indicating an error was returned from the pdi_log_get_rerun_buff function during log input at restart redo.
  Phr1441	Reception of a message from the pdi_log_get_rerun_buff failed during log input at restart redo.
  Phr1442	Release of the log buffer failed at restart redo.
  Phr1443	Code indicating an error was returned when attempt was made to obtain a log sequence number from the log server.
  Phr1444	A return code indicating an error was returned from the log server in the processing for which the Isn by RDAREA was to be posted to the log server at restart redo.
  Phr1450	Code indicating an error was returned when pdi_trn_sv_tran_ent function was issued to obtain the number of transactions.
  Phr1451	During restart redo processing, the function pdi_tjl_chg_trnid was issued, which acquires a transaction identifier from the second header of log records, but a return code indicating an error was returned.
  Phr1460 Phr1461	Status file read operation failed.	Use the database recovery utility to recover the database. Restart HiRDB.
  Phr1462	Status file write operation failed.	Restart HiRDB.
  Phr1463 Phr1464	Allocation of status file record failed.	Check the estimated status file size for an error. If it is correct, contact a customer engineer.
  Phr1465	Code indicating an error was returned when the pdi_sts_sys_iosize function was issued to obtain the status file record size.	Re-create the status file and restart HiRDB.
  Phr1466	The pdi_sts_sys_iosize function was issued to obtain the status file record size, but the returned record size was outside the permitted range.
  Phr1470	During restart redo processing, the function p_m_dhh_idx_gtngid was issued using multiple update pages as a design from the index log, but a return code indicating an error was returned.	Use the database recovery utility to recover the database.
  Phr1471	During restart redo processing, the function p_m_dhh_idx_gtpgn was issued for acquiring update pages from the index log, but a return code indicating an error was returned.
  Phr2100	Multiple identical transactions were detected during transaction analysis during restart redo processing.
  Phr2200	Attempt was made to register more RDAREAs than the permitted maximum into the table for managing RDAREA status information.	Restart HiRDB.
  Phr2210	A conflict was detected when writing status information for the RDAREA to the status file was attempted.	Back up all files in %PDDIR%\spool and contact a customer engineer.
  Phr2300 Phr2310 Phr2311	Internal conflict occurred in recovery processing.	Use the database recovery utility to recover the database.
  Phr2350	An error occurred during execution of the database recovery utility. This problem can occur in the following cases: The backup that was input does not match the log. When the database was recovered using the log only, the database did not match the log. There was an error in the operation.	If the input backup does not match the log: Use the correct backup and log; re-execute the database recovery utility. If the database does not match the log: Re-execute the database recovery utility based on the backup and all valid log files that have been collected since the backup. Other than the above: Check for errors in the operation of the targeted RDAREA. Recover the RDAREA if you find an error. If you do not find an error, contact a customer engineer.
  Phr2400	Message editing failed.	Restart HiRDB.
  Phr2401	Attachment of buffer shared memory failed.	Refer to the message that was output before this ABORT code.
  Phr2402	First log for which rollback should have been completed cannot be found.	Use the database recovery utility to recover the database, back up all files in %PDDIR%\spool, and contact a customer engineer.
  Phu0001	Text area allocation error occurred.	Check for any unnecessary process.
  Phu0002	Forced page output error occurred.	Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact a customer engineer.
  Phu0003	Status file update error occurred.
  Phu0004	Commit failed.	Resolve the cause of the error based on the KFPH27000-E message, and then restart HiRDB. If the cause of the error cannot be determined, contact a customer engineer.
  Phu0005	Internal contradiction was detected.	Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact a customer engineer.
  Phu0006	System manager's function call failed.	Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. If no error message was output, back up all files in %PDDIR%\spool and contact a customer engineer.
  Phy1001	Invalid parameter.	Back up all files in %PDDIR%\spool and contact a customer engineer.
  Phy2001	Internal conflict occurred in the data directory.	Make sure that the indicated RDAREA is operating correctly. If there is an operation error, recover the RDAREA. If the problem persists even when there is no apparent error, contact a customer engineer.
  Phy2002	An RDAREA status conflict was detected.
  Phy3001	An invalid return code was detected.	Back up all files in %PDDIR%\spool and contact a customer engineer.
  Phy4001	An internal logical conflict was detected.
  Phz3011	Buffer management return code is invalid.	Back up all files in %PDDIR%\spool and restart HiRDB. If the same error recurs, contact a customer engineer.
  Phz3021	Internal contradiction occurred in the data directory.	Make sure that the indicated RDAREA is operating correctly. If there is an operation error, recover the RDAREA. If Real Time SAN Replication with the log-only synchronous method is being used, perform preparation for log application. If the problem persists even when there is no apparent error, contact a customer engineer.
  Phz3033	Invalid code was returned from an internal subroutine.	Check the system operation and recover the database if an error was found. If no error was found, save the files under %PDDIR%\spool, and contact a customer engineer.
  Phz3101	Internal contradiction occurred in the directory.	Make sure that the indicated RDAREA is operating correctly. If there is an operation error, recover the RDAREA. If Real Time SAN Replication with the log-only synchronous method is being used, perform preparation for log application. If the problem persists even when there is no apparent error, contact a customer engineer.
  Phz3510	The buffer management return code is invalid.	Back up all files in %PDDIR%\spool and restart HiRDB. If the same error recurs, contact a customer engineer.
  Phz3712	Error occurred in the master directory RDAREA.	Resolve the error, recover the RDAREA, and then restart HiRDB. If Real Time SAN Replication with the log-only synchronous method is being used, perform preparation for log application, and then restart.
  Phz3714	Buffer request is invalid.	Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact a customer engineer.
  Phz3715	Request contradicts the buffer information.
  Phz3716	Contradiction occurred in a directory macro.
  Phz3717	Requested file ID is invalid.
  Phz3722	Listing work file name cannot be created.	Contact a customer engineer.
  Phz3723	Listing work file I/O failed.
  Phz3730	System RDAREA free request was issued.	Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact a customer engineer.
  Phz3760	Page was damaged (UTL environment).
  Phz3771	Internal conflict occurred in the HiRDB file system.	Resolve the cause of the error based on the KFPH23100-E message, and then restart HiRDB.
  Phz3785	Buffer shutdown request was issued for the master directory RDAREA.	Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact a customer engineer.
  Phz4002	Column ID list is invalid.	Contact a customer engineer.
  Phz4003	Internal logical conflict occurred.
  Phz4018	Address selection failed in a list page.
  Phz4020	Internal logical conflict occurred.
  Phz4023	Database was damaged.	Check the database recovery procedure for an error. If there is a database that has not been recovered, either recover it or recreate it. If there is no error, contact a customer engineer.
  Phz4025	Return code is invalid.	Contact a customer engineer.
  Phz4100	Error was detected during exclusive processing.	Back up all files in %PDDIR%\spool and contact a customer engineer.
  Phz4107	An error was detected during locking processing.	If the RDAREA has been moved, restart HiRDB. If there is no operation error, save the files under %PDDIR%\spool, and contact a customer engineer.
  Phz4113	Index contains the ID of an RDAREA that does not comprise the table.	Use the database recovery utility to recover the database and restart.
  Phz4300	More retrieval conditions were specified than permitted.	Reduce the number of retrieval conditions and re-execute.
  Phz4301	SQL object is invalid.	Contact a customer engineer.
  Phz4302	The number of units or tables exceeds the limit.	Specify an appropriate size based on the database design.
  Phz4303	Return code is invalid.	Back up all files in %PDDIR%\spool and restart HiRDB. Also, contact a customer engineer.
  Phz4304	Data contains the null value.	Use the database recovery utility to recover the database and restart.
  Phz4500 Phz4501 Phz4502 Phz4506	Return code is invalid.	Back up all files in %PDDIR%\spool and contact a customer engineer.
  Phz4508	Area allocation failed.
  Phz4509	Index page information is invalid.	Use the database recovery utility to recover the database and restart.
  Phz4510	Error was detected in an index entry.
  Phz4511	Row information is invalid.
  Phz4512	Upper-level index key value is duplicated.
  Phz4513	Index entry to be deleted was not found.
  Phz4514 Phz4515	Request code is invalid.	Back up all files in %PDDIR%\spool and contact a customer engineer.
  Phz4518	Table type is invalid.
  Phz4520	Data type is invalid.
  Phz4521	ENCODE result is invalid.
  Phz4524	Termination condition code is invalid.	Use the database recovery utility to recover the database and restart.
  Phz4526	Page type retrieved based on a row identifier was invalid.
  Phz4532	Return code is invalid.	Back up all files in %PDDIR%\spool and contact a customer engineer.
  Phz4539	Index definition information is invalid.	Use the database recovery utility to recover the database and restart.
  Phz4545	The current position exceeds the maximum number of duplicate index entries subject to retrieval. Or, the current slot exceeds the maximum number of entries in the index page subject to retrieval.
  Phz4547	Index type is invalid.	Back up all files in %PDDIR%\spool and contact a customer engineer.
  Phz4703	Function code is invalid.
  Phz4704	The current position of the index was dropped during a search in which WITHOUT LOCK NOWAIT was not specified. Or, the return code from a lower module was invalid.	Check if, during a search, another SQL in the same transaction updated or dropped the same table, eliminate the cause of the error, and re-execute. If the same table was not updated or dropped during the same transaction, back up all files under %PDDIR%\spool, and contact a customer engineer.
  Phz4705	Return code from other module is invalid.	Back up all files in %PDDIR%\spool and contact a customer engineer.
  Phz4706	Return code from a subroutine is invalid.
  Phz4707	Table type is invalid.
  Phz4709	Shortage occurred in the area to be allocated.
  Phz4710	Parameter is invalid.
  Phz4750	Table identifier and index identifier are invalid.
  Phz4753	Return code from a low-order module is invalid.
  Phz4754	Return code from other module is invalid.
  Phz4760	RHF-UTL interface is invalid.
  Phz4801	Return code is invalid.
  Phz4802	Call parameter is invalid.
  Phz4804	Column ID is invalid.
  Phz4805	Multicolumn list is invalid.
  Phz4807	Internal conflict occurred during the manipulation of an index information file.
  Phz**** *: Any character string	Allocation of internal area failed.

  Table 3-6 Abort codes (PkXXXXX)

  ABORT Code	Cause	Action
  Pk00001	Received an invalid message.	If a control statement file was specified when executing a file in %PDDIR%\spool or executing a utility, back up the control statement file and contact a customer engineer.
  Pk00002	Internal conflict was detected.
  Pk00003	The RDAREA on which the status was being analyzed using the pddbst function was deleted.	Be careful not to delete the RDAREA when the pddbst command is running. If the RDAREA has not been deleted, save the files under %PDDIR%\spool, and the control statement file if a control statement file was specified during the execution of the utility, and then contact a customer engineer.
  Pk00004	The contents of the work file are invalid.	When a utility is executing, do not execute the following files in HiRDB-installation-drive\tmp (in UNIX, /tmp) or in the directory specified in the workdir statement: Process ID.dbst.data Process ID.bst.msg Process ID.dbst.glaf Process ID.dbst.stor If operations such as file deletion have not been performed, collect the files under %PDDIR%\spool, as well as the above files, and then contact a customer engineer.
  Pk00005	Inter-process communications cannot be continued.	Refer to the error messages output to the event log (in UNIX, syslogfile) or to the message log file, and eliminate the cause of the communication error. If an unresolvable error occurred, collect the files under %PDDIR%\spool, and the control statement file if a control statement file was specified during the execution of the utility, and then contact a customer engineer.
  Pk00006	The database state analyzed table and database management table obtained before and after the database condition analysis do not match.	When executing the facility for accumulating condition analysis results, do not execute multiple pddbst commands against the same RDAREA. If these commands have not been executed simultaneously, save the data under %PDDIR%\spool and, if a control statement file is specified when a utility is executing, save the information (obtained by the pdfbkup command) on the RDAREA used by the data dictionary that stores the control statement file, database state analyzed table, and database management table, and contact a customer engineer.
  Pk00007	Due to a system call error, interval analysis could not be executed.	Save the data under %PDDIR%\spool and, if a control statement file is specified when a utility is executing, save that control file, and contact a customer engineer. This error can be temporarily avoided by executing pddbst without specifying the -w option.
  Pk00008	The table analyzed by pddbst does not match the index dictionary information.	During execution of pddbst, do not change tables or indexes. If the definitions have not been changed, acquire the data under %PDDIR%\spool and, if a control statement file is specified when a utility is executing, save the information (obtained by the pdfbkup command) on the RDAREA used by the data dictionary that stores the control statement file, database state analyzed table, and database management table, and contact a customer engineer.

  Table 3-7 Abort codes (PoXXXXX)

  ABORT Code	Cause	Action
  Po***** *: Any character string	An error occurred in the OS library service function.	UNIX version: If the HiRDB directory was removed without the pdcspool command being used, enter the pdsetup -d command to cancel setup, and then enter the pdsetup command to begin set up again. Otherwise, determine the cause of the error based on the error message output before the process aborted, take corrective action, and re-execute. If no error message was output, back up the error-related information, and contact a customer engineer. Windows version: Determine the cause from the error messages output before the ABORT code, take appropriate action, and restart. If no error messages are output, save the information acquired when the error occurred, and contact a customer engineer. The information acquired in the event of an error includes the files under %PDDIR%\spool, the event log (in UNIX, syslogfile), and standard error output.
  Polkcrt	A process was forcibly terminated while shared memory was being updated, meaning that operation can no longer be guaranteed. HiRDB (unit if HiRDB/Parallel Server) terminated abnormally. This abort code may appear in the following cases: A pdstop -f command was executed. A pdstop -z command was executed. A system was switched over. An executing HiRDB process (any process, including server processes, command processes, and utility processes) was forcibly terminated using the Ctrl+C key, the UNIX OS kill command, or the Windows pdkill command. Real Time SAN Replication with the log-only synchronous method is being used, and the pdrisedbto command was executed	If 1-4, there is no problem; recovery processing will be performed upon restart (including restart of the system switchover target). If 5, see the manual HiRDB Version 8 Disaster Recovery System Configuration and Operation Guide, and take action on the basis of the database inheritance procedure for each site switchover format. Otherwise, back up the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool, the event log (in UNIX, syslogfile), and standard error output.

  Table 3-8 ABORT codes (PrXXXXX)

  ABORT Code	Cause	Action
  Pr00001	Internal contradiction was detected in a common function.	Back up the error-related information, and contact a customer engineer. The error information includes the files under %PDDIR%\spool and the standard error output.
  Pr00002	Invalid interface to JP1/OmniBack II was detected.
  Pr10001	Internal contradiction was detected in 0bcpy.
  Pr20001	Internal contradiction was detected in 0rcopy.
  Pr30001	Internal contradiction was detected in 0brstr.
  Pr40001	Internal contradiction was detected in 0rrstr.
  Pr50001	Internal contradiction was detected in 0lrstr.
  Pr60001	Internal contradiction was detected in 0mrstr.
  Pr70001	Internal contradiction was detected in 0wrstr.
  Pr80001	Internal contradiction was detected in pdcopy.
  Pr90001	Internal contradiction was detected in pdrstr.

  Table 3-9 ABORT codes (PsXXXXX)

  ABORT Code	Cause	Action
  Psad*** *: Any character string other than those in the Psad codes that follow.	Error occurred during system or server startup or termination processing.	Determine the cause of the error based on the error message output before the process aborted, take corrective action, and re-execute. If no error message was output, save the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Psadc22	HiRDB has not been installed or set up correctly.	Check for the following possible reasons: The setup was for the HiRDB installed at a remote host. The HiRDB directory was created on an NFS-connected disk. The disk containing the HiRDB directory was not mounted during OS initialization.
  Psadci5	Acquisition of a network, host, or entry failed. Consider one of the following causes: The host name specified in the system common definition is not in the hosts file. The system does not have reference privileges to the hosts file. If you are using DNS or WINS, the host name or IP address is not in the search database. If you are using DNS or WINS, the system does not have reference privileges to the search database, or the setting is incorrect.	Eliminate the error and re-execute.
  Psadh11	Error occurred in the file for HiRDB Datareplicator data linkage.	Correct the operating environment on the basis of the reason code displayed in the KFPS01801-E message that was output immediately previously, then re-execute.
  Psadh71 Psadh73 Psadh75 Psadh78 Psadh82 Psadh85 Psadh88 Psadh8c Psadh8q Psadha3	Either the HA monitor or Hitachi HA Toolkit Extension has not been started. Or, a connection cannot be established to either the HA monitor or Hitachi HA Toolkit Extension. Therefore, HiRDB cannot be started in the server mode.	Either a KFPS01873-E message or KFPS01874-E message was generated before this abort code. Take corrective action according to these messages. If an HA monitor, Hitachi HA Toolkit Extension, or cluster software message is output, also take corrective action in reference to those messages.
  Psadh79 Psadh7a	When the server was being started, it was aborted by the forced termination of the server (pdstop -s -z command). This message is output in some cases when the server being started is aborted by the forced termination command when the standby-less system switchover (effects distributed) facility is in effect.	This is not a problem if the server was aborted. If the server was not aborted, contact a customer engineer. If an HA monitor, Hitachi HA Toolkit Extension, or cluster software message is output, also take appropriate corrective action by referring to the message.
  Psadhf0	Consider the following causes: When a system switchover facility is being used, after a normal termination or a planned termination was determined during termination processing in the running system HiRDB, a CPU error or a machine slowdown call used a system switchover. User server hot standby is applied, and Hitachi HA Toolkit Extension is being used. (a) Before the Hitachi HA Toolkit Extension service process was activated (using the hateserve command), HiRDB was started using the pdstart command. If HiRDB is started before the Hitachi HA Toolkit Extension service process is activated, HiRDB will start in standby status, and activation of the Hitachi HA Toolkit Extension service process performs standby release processing. (b) After starting the standby system HiRDB, start the running system HiRDB normally. At this time, startup of the running system HiRDB will fail, and a system switchover will occur. The unit used for system switchover is a recovery-unnecessary front-end server unit.	If the running HiRDB system is in normal or planned termination status, stop the standby HiRDB system along with the running system. However, if a switchover occurred after normal or planned termination had been confirmed on the running system, the standby system aborts HiRDB and terminates because termination linkage has not been performed for the HA monitor or Hitachi HA Toolkit Extension. If HiRDB is to be started after it was terminated by this abort code, it is sometimes difficult to determine whether HiRDB is the running system or the standby system if either the HA monitor or Hitachi HA Toolkit Extension is down, in which case the startup processing can stall. In this case, the following HA monitor or Hitachi HA Toolkit Extension command should be executed to make the local system a running system: 1. Use the monshow command to verify that the status of the executing server is "*SBY*" (startup of the executing server is in standby). 2. Use the monact command to notify the HA monitor or Hitachi HA Toolkit Extension that the local server is the executing server. (a) If the pdstart command is executed before the Hitachi HA Toolkit Extension service process is activated, execute it after the Hitachi HA Toolkit Extension server process is activated, or specify the HiRDB activation command in the actcommand operand of the Hitachi HA Toolkit Extension server definition statement. If the pdstart command is executed from a shell, have the shell execute the pdstart command after the Hitachi HA Toolkit Extension service process is activated. (b) Take action based on the cause of the error in starting the running system HiRDB, and then start the running system HiRDB. Units that use system switchover cannot use recovery-unnecessary front-end servers. Change the system definition to use either the system switchover facility or recovery-unnecessary front-end servers. If the cause at left is not applicable, contact a customer engineer.
  Psadhfe	Startup processing was suspended because both systems started up as standby systems while Hitachi HA Toolkit Extension was being used. The Hitachi HA Toolkit Extension service process may not be active.	To set up the primary system as the running system, start over with the following procedure: On the primary system, start the Hitachi HA Toolkit Extension service process. Start the primary system unit as the running system. If the secondary system terminates abnormally, use the pdls command to check if startup of the running system unit is complete, and then start the secondary system unit as the standby system. To set up the secondary system as the running system, start over with the following procedure: Use the pdstop -z command (pdstop -f for HiRDB/Single Server) to forcibly terminate the secondary system unit. Start the Hitachi HA Toolkit Extension service process on the secondary system unit. Start the secondary system unit as the running system. Use the pdls command to check if startup of the secondary system unit is complete, and then start the running system unit as the standby system.
  Psadhff Psadhfg	The HiRDB system could not be placed on wait status.	If memory is insufficient, determine the reason why memory is insufficient, take corrective action, and restart. If an error message was output before the process aborted, determine the cause of the error based on the error message, take corrective action, and restart. If no error message was output, save the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, and the event log (in UNIX, syslogfile).
  Psadhfh	System switchover occurred after normal or planned termination of HiRDB was confirmed.	If this abort code was output during system switchover, restart HiRDB on the switchover target.
  Psadma2 Psadmaa Psadmam Psadman Psadmaq Psadmat PsadmaC PsadmaK PsadmaL PsadmaN PsadmaO PsadmbF Psadmcr Psadmmk Psadmmm	The HA monitor, Hitachi HA Toolkit Extension, or the cluster software has not been started or is unavailable for connection. Therefore, HiRDB cannot be started in server mode.	Either a KFPS01873-E message or KFPS01874-E message was generated before this abort code. Take corrective action according to these messages. If an HA monitor, Hitachi HA Toolkit Extension, or cluster software message is output, also take corrective action in reference to those messages.
  Psadnt1	The user authorization is invalid.	Confirm that the user executing an operating command has administrator privilege (other than a HiRDB administrator).
  Psadp20	The host name specified in the system definition is not in the hosts file. The hosts file cannot be referenced with the HiRDB administrator ID. UNIX version: If HiRDB is running on a server machine on which DNS or NIS is configured, operation is discontinued if the host name is not registered to the DNS or NIS in the host reference rules file (/etc/nsswitch.conf).	Register the host name specified in the system definition to the hosts file. Set the hosts file reference privileges such that the hosts file can be referenced with the HiRDB administrator ID. UNIX version: If DNS or NIS is configured on the server machine, change the definitions in the /etc/nsswitch.conf file as follows: hosts:dns [NOTFOUND=continue TRYAGAIN=continue] nis [NOTFOUND=continue TRYAGAIN=continue] files Restart HiRDB after employing one of the preceding to correct the problem. If none of these is applicable, contact a customer engineer.
  Psadp40	The PDDIR environment variable cannot be referenced.	If this error occurs in a command process, check whether the PDDIR environment variable is correctly set up. If this error occurs in a HiRDB server process, memory shortage is a possible cause. In this case, take the following actions: Close any processes or windows that are not needed. Add a system swap area.
  Psadp43	An error occurred while the HiRDB External Data Access management file was being accessed.	Back up the error-related information, and contact a customer engineer. The information to back up is as follows: All files under %PDDIR% Event log (in UNIX, syslogfile) Output of standard error
  Psadp44	An error occurred while the HiRDB Staticizer Option management file was being accessed.	Back up the error-related information, and contact a customer engineer. The information to back up is as follows: All files under %PDDIR% Event log (in UNIX, syslogfile) Output of standard error
  Psadp45	The definition analysis file set in the HiRDB system definitions cannot be opened.	Check if revocations or privileges for files under %PDDIR%\lib\sysconf and %PDDIR%\lib\sysdef have been changed. If revocations or privileges have been changed: In UNIX, specify y in the response message when the pdsetup -d command is executed. Then, re-execute the pdsetup command. In Windows, re-install HiRDB. If other than the preceding: Back up the error-related information and contact a customer engineer. The information to back up is as follows: Files under %PDDIR%\spool Files under %PDDIR%\tmp Event log (in UNIX, syslogfile) Output of standard error
  Psadp47	An error occurred while the HiRDB Advanced High Availability management file was being accessed.	Back up the error-related information, and contact a customer engineer. The information to back up is as follows: All files under %PDDIR% Event log (in UNIX, syslogfile) Output of standard error
  Psadp48	An error occurred while the HiRDB Advanced Partitioning Option management file was being accessed.
  Psadp49	An error occurred during access to the HiRDB Non Recover FES management file.
  Psadp64	An error occurred while the HiRDB LDAP Option management file was being accessed.
  Psadp50	An error occurred while accessing the management file of the HiRDB Disaster Recovery Light Edition option program product.	Save the information acquired during the error, and contact a customer engineer. The information to be acquired in the event of an error includes all files under %PDDIR%, the event log (in UNIX, syslogfile), and standard error output.
  Psadr3C Psadr3E	The HA monitor, Hitachi HA Toolkit Extension, or the cluster software has not been started or is unavailable for connection. Therefore, HiRDB cannot be started in server mode.	Either a KFPS01873-E message or KFPS01874-E message was generated before this abort code. Take corrective action according to these messages. If an HA monitor, Hitachi HA Toolkit Extension, or cluster software message is output, also take corrective action in reference to those messages.
  Psadr5w	System server startup processing failed.	If there is a memory shortage, check the cause of the memory shortage, and restart HiRDB after taking corrective action. If there was an error message preceding the abort, check the cause of the problem based on the error message, and restart HiRDB after taking corrective action. If there is no error message, save the information to be saved in the event of an error, and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, and the event log (in UNIX, syslogfile).
  Psadr62	Error was detected in the system manager's status information while restarting HiRDB.	If the HiRDB version had been changed before HiRDB was restarted, restore the previous version. Terminate HiRDB normally, and then restore the previous version. If that is not the case, save the event log (in UNIX, syslogfile) and all files under %PDDIR%\spool, and contact a customer engineer.
  Psads01	The pdstart command was executed during OS initialization	Wait for OS initialization to complete, and then re-execute the command. If this same error recurs even after OS initialization, contact a customer engineer. Note that this error also occurs when the pdstart command is specified in the OS environment file (/etc/localrc). HiRDB commands cannot be specified in the /etc/localrc or /etc/localshutrc files. To start the OS and HiRDB at the same time, specify AUTO in the pd_mode_cont operand of the system common definition.
  Psads3m Psadsb2	An error occurred while obtaining shared memory.	Determine the cause from the error messages output before the ABORT code, take appropriate action, and then re-execute.
  Psads3y	The number of servers in the unit exceeds the limit.	Reduce the number of servers defined for the unit, and then re-execute.
  Psads73 Psads78	The HA monitor, Hitachi HA Toolkit Extension, or the cluster software has not been started or is unavailable for connection. Therefore, HiRDB cannot be started in server mode.	Either a KFPS01873-E message or KFPS01874-E message was generated before this abort code. Take corrective action according to these messages. If an HA monitor, Hitachi HA Toolkit Extension, or cluster software message is output, also take corrective action in reference to those messages.
  Psads7e	The system server could not be placed on wait status.	If memory is insufficient, determine the reason why memory is insufficient, take corrective action, and restart. If an error message was output before the process aborted, determine the cause of the error based on the error message, take corrective action, and restart. If no error message was output, save the error-related information, and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, and the event log (in UNIX, syslogfile).
  Psads8b	System server start processing failed.
  Psads9v	Start the preparation for log application before initializing the database.	After initializing the database from the transaction execution site and then terminating normally, perform preparation for log application. For details about preparation for log application, see the manual HiRDB Version 8 Disaster Recovery System Configuration and Operation Guide. After performing preparation for log application, start the log application site.
  Psads9w	The HiRDB addressing mode of the log application site does not match the database.	Set the HiRDB addressing mode of the transaction execution site to match that of the log application site, and then perform preparation for log application. If migrating from 32-bit mode to 64-bit mode, perform migration following the version upgrade procedure. For details about preparation for log application and the version upgrade procedure, see the manual HiRDB Version 8 Disaster Recovery System Configuration and Operation Guide.
  PsadsA8	If the KFPH20012-E message was output immediately prior to this error, the version of HiRDB is invalid. The version of HiRDB that created the database is newer than the version of HiRDB that is using the database; therefore, the database cannot be accessed. Or, the database cannot be transferred from the version of HiRDB that created it to the version of HiRDB that is using it. If the KFPH20005-E message was output immediately prior to this error, access failed to the HiRDB master directory RDAREA. If a HiRDB/Parallel Server is composed of multiple units, all units that lack a dictionary are terminated.	Take corrective action based on the information provided in the KFPH20012-E message or the KFPH20005-E message.
  PsadsAp	This message is generated in some cases during server startup processing if the server being started was aborted by an HA monitor, Hitachi HA Toolkit Extension, or server abort command (pdstop -s -z or pdstop -s -f).	A KFPS05617-I message is generated before stopping. The stoppage, which occurred due to a stop request, is not a problem.
  PsadsaB Psadshy	Referencing of HiRDB External Data Access failed. HiRDB External Data Access may not be configured correctly.	Check the message output before the process aborted, and take corrective action as indicated by that message. If no message was output, contact a customer engineer.
  PsadsBa PsadsBb	The HiRDB version of the log application site does not match the database version.	Perform preparation for log application. For details about preparation for log application, see the manual HiRDB Version 8 Disaster Recovery System Configuration and Operation Guide. If the HiRDB versions of the transaction execution site and the log application site do not match, make them the same, and then perform preparation for log application. After performing preparation for log application, start the log application site.
  Psadshz	The value specified in the pd_routine_def_cache_size operand is invalid.	Specify the correct value in the pd_routine_def_cache_size operand.
  Psadsr8	An attempt was made to start a process that would result in the maximum number of active processes per user being exceeded, or the maximum number of processes on the entire system being exceeded.	Check the value of the OS parameter.
  Psadtlf Psadt7h	Error occurred during server stop processing.	The server termination command was aborted because the server process terminated abnormally (including pdcancel) during server termination processing. This prevents the HiRDB system from being placed on an invalid status. Restart the HiRDB system and terminate it normally. If the above event does not apply, check the error cause from the error message that was output before processing was aborted and take appropriate action.
  Psadt1u Psadt7G	The HA monitor, Hitachi HA Toolkit Extension, or the cluster software has not been started or is unavailable for connection. Therefore, HiRDB cannot be started in server mode.	Either a KFPS01873-E message or KFPS01874-E message was generated before this abort code. Take corrective action according to these messages. If an HA monitor, Hitachi HA Toolkit Extension, or cluster software message is output, also take corrective action in reference to those messages.
  Psadv01 Psadv02 Psadv03 Psadv04 Psadv05 Psadv06 Psadv07 Psadv08	The gethostbyname system command cannot be used to convert a host name to the corresponding IP address.	Check the following items, and correct any errors: Setting error in the hosts Invalid privilege to the hosts file Setting error in the DNS or NIS setting files (such as nsswitch.conf or resolv.conf) Invalid privilege to DNS or NIS setting files (such as nsswitch.conf or resolv.conf) Also, if using DNS or NIS, errors can occur during communication with the DNS or NIS server.
  Psau*** *: Any character string other than those in the Psau codes that follow.	An error occurred in the security audit facility.	Check the error message that was output before ABORT for the cause of the error, take appropriate action, and then re-execute. If no error message was output, back up the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Psau001	Writing of the status file failed.	Save the files under %PDDIR%\spool, and the event log (in UNIX, syslogfile), and contact a customer engineer.
  Psaud0V Psaud0w	Allocation of shared memory failed. This problem can occur when the following operations are performed successively in a standby-less system switchover configuration: An alternate BES unit is started, and the accepting and the alternate portion are put in a standby status. The alternate portion is terminated using the pdstop -q -c command without stopping the accepting unit. After the following specification values for definitions of security audit on the unit control information definition (pdutsys) about the alternate portion are added or modified, the alternate portion is started using the pdstart -q -c command: pd_aud_file_name pd_aud_async_buff_size pd_aud_async_buff_cnt	When the pd_aud_file_name definition specification is to be added to the alternate portion of the alternate BES unit in a standby-less system switchover configuration, stop the accepting unit as well as the alternate portion, and restart HiRDB. For a configuration other than a standby-less system switchover configuration, save the information to be saved in the event of an error, and contact a customer engineer. Save the files under %PDDIR%\spool, and the event log (in UNIX, syslogfile).
  Psaud11	Acquisition of a status file record failed.	Check the size of the status file. If the estimated size is correct, save the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Psaud13 Psaud14 Psaud15	Writing of the status file failed.	Save the files under %PDDIR%\spool, and the event log (in UNIX, syslogfile), and contact a customer engineer.
  Pscm*** *: Any character string other than those in the Pscm codes that follow.	Error occurred during operation command control processing.	Check the error message that was output before ABORT for the cause of the error, take appropriate action, then re-execute. If no error message was output, save the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Pscm052	Possible causes of the problem are as follows: Among the units that make up the HiRDB/Parallel Server, the HiRDB version does not match the version of a HiRDB option program product. Either a unit with a system manager is not running or a unit non-system manager unit that has not been reduced-activated is not running. In a configuration where Real Time SAN Replication with the log-only synchronous method is applied, the startup of transaction execution sites and log application sites was mixed. In a standby-less system switchover configuration, HiRDB Datareplicator operation directories do not match. In a standby-less system switchover configuration, the contents of the system common definition do not match.	If versions do not match, take action appropriate to the KFPS05207-E or KFPS05208-E message and the KFPS05209-I message. If versions do match and there is a unit that is not running, use the pdstart command to start the HiRDB system. If the startup mode was mixed, refer to the KFPS05247-E message, decide whether to start from the transaction execution sites of the entire HiRDB system or from the log application sites, and then restart the entire HiRDB system. If the contents of the system common definition do not match, take action according to the KFPS05248-E and KFPS05249-E messages.
  Pscm05c	Input/output processing on a status file failed.	Investigate the cause of the problem and take corrective action with reference to the preceding status file error message. After taking corrective action, restart the abnormally terminated unit. If there is a KFPS05190-E message, restart the abnormally terminated unit. If there is no error message, it is possible that either a memory shortage or a network error has occurred. Check to see if a memory shortage or a network error has occurred, take appropriate action, and then restart the abnormally terminated unit. If these possibilities do not apply, contact a customer engineer.
  Pscm05d Pscm05f Pscm05g Pscm05h	Due to a disk error, uninstallation of the option program product using the pdopsetup -d command failed.	Determine the cause from the immediately preceding KFPO00107-E message, and take appropriate action. Then, re-execute the pdopsetup -d command, and uninstall the option program product.
  Psit***	An error occurred during interval timer processing.	Check the error message that was output before ABORT for the cause of the error, take appropriate action, then re-execute. If no error message was output, save the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Psji*** Psjj*** Psjk*** Psjl*** Psjm*** Psjn*** *: Any character string other than applicable codes that follow.	An error occurred during interval timer processing. Error occurred during log processing.
  Psjie42	A failure occurred during startup of the log service process. Consider the following causes: No swap target existed. Memory was insufficient.	If there is no swap target, either add a system log file, or unload a system log file and create a file that can be a swap target, and then restart. If memory is insufficient, determine the reason why memory is insufficient, take corrective action, and restart. If an error message was output before the process aborted, determine the cause of the error based on that error message, take corrective action, and restart. If no error message was output, save the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Psjih18 Psjih24 Psjns08	Shortage occurred in message resources.	Reconfigure the kernel (increase the values of msgtql and msgmnb).
  Psjiz09	Consider the following causes: An error preventing access to the HiRDB Datareplicator installation directory occurred, such as an error on the disk on which HiRDB Datareplicator is installed. The addressing modes of HiRDB and HiRDB Datareplicator differ. HiRDB Datareplicator is not installed.	Take corrective action based on the results of the following checks: Check whether an error has occurred that prevents access to the HiRDB Datareplicator installation directory, such as an error on the HiRDB Datareplicator installation disk in the server machine with the unit that output the message. If so, eliminate the error and re-execute. Check if the addressing mode used by the unit that output the message is the same as the addressing mode used by HiRDB Datareplicator. If the HiRDB addressing mode differs from that of HiRDB Datareplicator, replace the addressing mode of HiRDB Datareplicator with that of HiRDB, and re-execute. Check if HiRDB Datareplicator is installed on the server machine with the unit that output the message. If it is not installed, install HiRDB Datareplicator and re-execute. If none of the preceding reasons is applicable, contact a customer engineer.
  Psjjd0c	The acquisition of a synchronization point dump file could not be continued due to a network problem; the system terminated abnormally.	Eliminate the cause of the error, and then restart HiRDB.
  Psjjt36	Memory is insufficient.	The process private area is insufficient. Set the memory allocation to the estimated value. Alternatively, quit unneeded processes.
  Psjke01	A temporary memory shortage occurred.	Check the cause of the memory shortage, take corrective action, and then restart HiRDB.
  Psjmg01	Shortage occurred in memory or system file table.	Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. If no error message was output, back up the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Psjmg60	The AIO kernel extension is not installed in an environment in which the facility for parallel output of system logs is used.	Check to see if the AIO kernel extension is installed. Check the specification value for the pd_log_dual_write_method for server definitions.
  Psjmg62	Not enough memory.	There is not enough memory for the process-private area. The memory requirements should be reviewed.
  Psjn022 Psjn031 Psjn039	Error occurred while starting the synchronization point dump service process.	Based on the error message preceding the abort, take corrective action, and then re-execute the command. If there is no error message, save the information to be saved in the event of an error, and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Psjn051	Error occurred while terminating the log service process.
  Psjn052 Psjn053	Error occurred while terminating the synchronization point dump service process.
  Psjn060	System file required for log output cannot be opened.	Files in %PDDIR%\lib\sysconf or in %PDDIR%\lib\sysdef cannot be opened successfully. Check if HiRDB has been installed correctly.
  Psjn094	Memory is insufficient.	Shortage occurred in the process private area. Re-estimate the memory.
  Psjn0g5	A failure occurred on startup of the log service process. There may be insufficient memory.	If memory is insufficient, determine the reason why memory is insufficient, take corrective action, and restart. If an error message was output before the process aborted, determine the cause of the error based on that error message, take corrective action, and restart. If no error message was output, save the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Psjn0g6	Error occurred while starting the status service process.	Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. If no error message was output, back up the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Psjn0gf	Error occurred while terminating the status service process.
  Psjn140	Error occurred while terminating the log service process.
  Psjn189	Memory is insufficient.	Shortage occurred in the process private area. Re-estimate the memory.
  Psjn308	There is no swappable file.	Provide an available file by either adding or unloading a file.
  Psjn320	Processing cannot be continued due to an error such as a communication error.	Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. If no error message was output, back up the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Psjn321	Processing cannot be placed on wait status, because all management blocks have been used. Or, an error occurred while processing was on wait status.
  Psjn327	Memory shortage, network error, or timeout occurred.	Refer to the reason code in the message log to check the cause of the error, take appropriate action, then re-execute.
  Psjn329	Memory shortage or network error occurred.	Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. If no error message was output, back up the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Psjn335 Psjn336 Psjn338 Psjn341 Psjn345 Psjn347 Psjn349 Psjn352 Psjn354 Psjn355 Psjn357 Psjn359	Lock release wait status occurred, but processing cannot be placed on wait status because all management blocks have been used. A process area to be managed by the OS library cannot be allocated.	Re-estimate the memory.
  Psjn381	There is no swappable file.	Provide an available file by either adding or unloading a file.
  Psjn625	System file required for log output cannot be opened.	Files in %PDDIR%\lib\sysconf or in %PDDIR%\lib\sysdef cannot be opened. Check if HiRDB has been installed correctly.
  Psjnc20 Psjnd20 Psjne06 Psjne15 Psjnf04	Lock release wait status occurred, but processing cannot be placed on wait status because all management blocks have been used. A process area to be managed by the OS library cannot be allocated.	Re-estimate the memory.
  Psjnf07	There is no swappable file.	Provide an available file by either adding or unloading a file.
  Psjnf16	Processing cannot be continued due to an error such as a communication error.	Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. If no error message was output, back up the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Psjng02 Psjng04	Lock release wait status occurred, but processing cannot be placed on wait status because all management blocks have been used. A process area to be managed by the OS library cannot be allocated.	Re-estimate the memory.
  Psjng05	Memory shortage or network error occurred.	Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. If no error message was output, back up the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Psjng10	Memory shortage, network error, or timeout occurred.
  Psjnh51	Error was detected in the log server's status information while starting HiRDB.	If the HiRDB version had been changed before HiRDB was restarted, restore the previous version. Terminate HiRDB normally and then restore the previous version. If that is not the case, save the event log (in UNIX, syslogfile) and the files under %PDDIR%\spool, and contact a customer engineer.
  Psjnk03	Network error occurred.	Check the cause of the network error, take appropriate action, then restart HiRDB.
  Psjnk04 Psjnk05	Memory is insufficient.	Shortage occurred in the process private area. Re-estimate the memory.
  Psjnk11	Network error occurred.	Check the cause of the network error, take appropriate action, then restart HiRDB.
  Psjlm25	System file required for log output cannot be opened.	Check if HiRDB has been installed correctly.
  Psjlm52	Memory is insufficient.	Re-estimate the memory.
  Psjnm27 Psjnm28 Psjnm29 Psjnm30	Memory shortage or network error occurred.	Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. If no error message was output, back up the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Psjnr31	Database recovery processing was invalid during restart.	Check the reason code in the KFPS01267-E message that was output immediately previously, and re-execute.
  Psjnr38	Invalid data was detected in the event log file.	Save the files under %PDDIR%\spool as well as the system log file, and then take one of the following actions: When the HiRDB version was changed even though HiRDB had not terminated normally during the previous operation: Restore the previous HiRDB version. When the contents of the previous version or the contents of other systems were changed inadvertently because the entire disk or the HiRDB file system area for the event log file was restored accidentally: Restore the event log file. If this is not possible, first terminate HiRDB forcibly, then restore the database to the backup acquisition point (or to the last unload log acquisition point if an unload log file is available). Then, recover the database by re-executing the jobs that were entered after the backup was made. When the event log was not loaded after synchronization point dumps had been enabled: The contents of the status file or synchronization point dump file may be corrupt. First, terminate HiRDB forcibly, then restore the database to the backup acquisition point. Then, recover the database by re-executing the jobs that were entered after the backup was made. When a log application site was running, paircreate or pairresync was executed against the pair volume that stores the system log file, and a form copy was executed Restart the log application site HiRDB, and restart the log application. If the log application cannot be restarted, perform preparation for log application, and then restart the log application. If a site takeover for disasters was performed, see the manual HiRDB Version 8 Disaster Recovery System Configuration and Operation Guide, and take any required actions. In all other cases: Contact a customer engineer.
  Psjnr46	An error occurred in the creation of the transaction information file. The primary causes are as follows: Insufficient process native area Access to the %PDDIR%\spool\pdtrninf directory failed Insufficient volume on the disk where the %PDDIR%\spool\pdtrninf directory resides	The actions for items 1-3 to the left are as follows: Take action based on the instructions given in the KFPO00106-E message. Determine the cause of the failure to access the %PDDIR%\spool\pdtrninf directory, and take measures to enable the HiRDB administrator to read and write files in the %PDDIR%\spool\pdtrninf directory. If there is no %PDDIR%\spool\pdtrninf directory, set up HiRDB again. Remove any unnecessary files to increase the free space on the disk. If the error cannot be resolved, save the information acquired during the error, and contact a customer engineer. The information to be saved includes the following: All files under %PDDIR%\spool Event log (in UNIX, syslogfile)
  Psjnt04	Lock release wait status occurred, but processing cannot be placed on wait status because all management blocks have been used. A process area to be managed by the OS library cannot be allocated.	Re-estimate the memory.
  Psjnu07	Processing cannot be placed on wait status, because all management blocks have been used. Or, an error occurred while processing was on wait status.	Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. If no error message was output, back up the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Psjnu08 Psjnu12 Psjnu17	Lock release wait status occurred, but processing cannot be placed on wait status because all management blocks have been used. A process area to be managed by the OS library cannot be allocated.	Re-estimate the memory.
  Pslg*** *: Any character string	Error occurred during message log output processing.	Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. If no error message was output, back up the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Pslk*** *: Any character string	Error occurred during lock control processing.
  Psna*** *: Any character string other than the Psna code that follows.	Error occurred during name service processing.	If no error message was output, back up the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Psna005	The port number allocated to HiRDB is being used by another program; or a previously activated HiRDB process (in UNIX, a zombie process) remains.	If a bind system call error occurred, take one of the following actions, as appropriate to the cause: If the port is being used by another program Check the value of the pd_name_port operand in the system common definition and assign a unique port number If a zombie process remains in UNIX, remove the zombie process using the OS's kill command. If a process remains in Windows, remove the process using the pdkill command.
  Psnd*** *: Any character string other than those in the Psnd codes that follow.	Error occurred during system operation control processing.	If no error message was output, back up the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Psnd530 Psnd537 Psnd538 Psnd53a	Shortage occurred in the area that is used to store the identifiers of the users accessing this server.	Re-execute when there are fewer users accessing this server. Terminate any remaining transactions. If this error occurs frequently, terminate HiRDB normally and increase the following server-related definition values: HiRDB/Single Server pd_max_users HiRDB/Parallel Server If the error occurred at a front-end server: pd_max_users If the error occurred at the back-end server: pd_max_bes_process If the error occurred at the dictionary server: pd_max_dic_process
  Psnd678 Psnd679	Because status information on a recovery unnecessary front-end server unit is STOP(A); even though an attempt was made to abort that unit and restart, the attempt failed, and the system terminated abnormally.	Restart the unit that terminated abnormally.
  Psnda09	Process private area shortage occurred.	Re-estimate the memory requirement for the process private area.
  Psndb22	The number of utilities executed concurrently has reached the upper limit.	Specify 1 in the pd_utl_exec_mode operand. If 1 is specified in the pd_utl_exec_mode operand, check to see if utilities are executed concurrently in excess of the value of the pd_max_users operand. If utilities are executed concurrently in excess of the value of the pd_max_users operand, reduce the number of concurrently running utilities. If the value is not exceeded, save the information to be acquired in the event of an error, and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and the event log (in UNIX, syslogfile) on the system manager and the unit that output this ABORT code.
  Psndc04 Psndc05 Psndc06 Psndc07 Psndc08 Psndh1a Psndh2c Psndh2e Psndh2h	The unit with a system manager stopped or a network fault occurred, causing communications failure with the system manager. The affected unit is terminated.	If the unit with a system manager is stopped, check the cause of the stoppage of the system manager unit, based on the error message preceding the abort code, and resolve the error. After that, restart HiRDB. If the error occurred even when the system manager unit was running, a network fault must be suspected. Investigate the problem by seeing 4.1 Detail codes for RPC-related errors. If the cause of the problem cannot be identified, save the files under %PDDIR%\spool and the system log files for the system manager unit and the unit that generated the abort code, and contact a customer engineer.
  Psndc24 Psnds53	There is insufficient process native area.	Determine the cause of the insufficient process native area, take appropriate action, and then restart HiRDB. If the error cannot be resolved, save the information acquired during the error, and contact a customer engineer. UNIX version: The information to be acquired in the event of an error includes the files under %PDDIR%\spool and syslogfile on the system manager and the unit that output this ABORT code. Windows version: The information to be acquired in the event of an error includes the files under %PDDIR%\spool and the event log on the system manager and the unit that output this ABORT code.
  Psndd02	During transaction commit processing, either an error occurred in a unit with a transaction branch, or a transaction could not be determined because a network error occurred. The transaction can be determined by forcibly terminating and restarting the applicable unit.	If a unit with a transaction branch is not running, start the unit. If a network error occurred, eliminate the cause of the network error. If the cause is none of the preceding, eliminate the cause of the error based on the message output immediately before this abort code. If no message was output, contact a customer engineer.
  Psndd04 Psndd05	Transaction, command, or utility recovery could not be communicated because the system manager unit had stopped or a network error occurred. Consequently, the unit was stopped.	If the system manager unit had stopped, determine the reason from the error message that was output before processing was aborted, correct the error, and restart HiRDB. If a network error occurred, recover the network and then stop the HiRDB system forcibly with the pdstop -f command, and then restart the HiRDB system. Restart the system, not the unit. If the cause cannot be determined, save the files under %PDDIR%\spool and the system log files in both the system manager unit and the unit where this abort code was output, and contact a customer engineer.
  Psndd18 Psnds42	An error occurred when a unit was being started.	Resolve the cause of the error based on the preceding message. If there is no message output, contact a customer engineer.
  Psndm05	Consider the following causes: From within units making up HiRDB, either versions of HiRDB or versions of option program products do not match. Either a unit with a system manager has not started, or a unit has not started due to reduced activation. A communication error occurred between units configuring HiRDB.	If the versions do not match, take corrective action based on the KFPS05207-E, KFPS05208-E, and KFPS05209-E messages. If a unit with a system manager has not started, or if a unit has not started due to reduced activation, start the inactive unit. If a communication error occurred, eliminate its cause, and then start HiRDB. If none of the preceding is applicable, save the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Psndm19	Master directory is being used by another HiRDB system.	Two HiRDB systems cannot be started concurrently if the first HiRDB file name in the master directory RDAREA is the same in both system common definitions. Recheck the system common definitions and restart.
  Psndm20	A unit uses character codes that are not compatible with the character codes of the system manager.	The character code type for the unit and the character code type for system manager do not match; the HiRDB system cannot be started. Refer to the information in the KFPS05206-E message, and set the same character codes type. UNIX version: To change the codes type, execute pdsetup -d, enter y in response to the response message, then specify the correct character codes type with pdsetup -c. Windows version: Refer to the related messages, eliminate the cause of the error, and then restart HiRDB.
  Psndm80	The character codes used by the HiRDB that was started are not compatible with the character codes used by HiRDB when the database was initialized.	Take action appropriate to the KFPH20011-E message.
  Psnd098 Psnd234 Psnde70 Psnde80 Psndsp0 Psndsp1 Psndsp2 Psndsp3	Error occurred during HiRDB unit termination processing. If the termination processing is planned termination, all units are terminated forcibly.	Referring to the KFPS05111-E message output immediately before the abort code, determine the cause and eliminate the error. Then, restart HiRDB. If the process aborted during planned termination processing, make sure that all units are stopped before restarting HiRDB. If there are any active units, stop all units by either executing the pdstop -f command from a server machine that has the system manager, or by executing the pdstop -z command from a server machine with an active unit. Then, restart HiRDB. Use the following procedure to check if the units are stopped: Check the event log (in UNIX, syslogfile) of each unit for KFPS01821-E messages or KFPS01841-I messages (termination mode of FORCE) Refer to KFPS01850-I messages (termination mode of FORCE) output to the event log (in UNIX, syslogfile) of the unit where the system manager resides If the cause cannot be determined even after referring to the KFPS05111-E message, save the files under %PDDIR%\spool, and the event log (in UNIX, syslogfile) for the unit, and contact a customer engineer.
  Psndv03	Communication with the system manager failed when upgrading a dictionary or when migrating an SQL object. To avoid malfunctioning due to communication failures, unit activation was suspended.	If the system manager unit is stopped: Determine the reason why the unit stopped based on the error message output before the process aborted, and eliminate the error. Then, restart the HiRDB system. To restart, execute the pdstart command without any options. If a unit without the system manager is stopped: Determine the reason why the unit stopped based on the error message output before the process aborted, and eliminate the error. Then, forcibly terminate the HiRDB system with the pdstop -f command, and restart it. To restart, execute the pdstart command without any options. If a network error occurred: After recovering the network, forcibly terminate the HiRDB system with the pdstop -f command, and restart it. To restart, execute the pdstart command without any options. Other than the above: Restart the HiRDB system. If this error continues to occur, save the files under %PDDIR%\spool and the system log files on the system manager unit and on the unit that output this abort code, and then contact a customer engineer.
  Psp**** *: Any character string other than those in the Psp codes that follow.	Error occurred during process control processing.	Check the error message that was output before ABORT for the cause of the error, take appropriate action, then re-execute. If no error message was output, save the error-related information and contact a customer engineer. The error-related information includes the files under %PDDIR%\spool and the standard error output.
  Psp0766 Psp0767 Psp5008 Psp5011 Pspk001 Pspk002	The HA monitor, Hitachi HA Toolkit Extension, or the cluster software has not been started or is unavailable for connection. Therefore, HiRDB cannot be started in server mode.	Either a KFPS00727-E message or KFPS00728-E message was generated before this abort code. Take corrective action according to these messages. If an HA monitor, Hitachi HA Toolkit Extension, or cluster software message is output, also take corrective action in reference to those messages.
  Psp4017	If -prc terminated abnormally with this ABORT code during HiRDB startup, possible reasons are as follows: Contents of the hosts file are invalid. Default host was not set up correctly. Network has not been started.	Correct the hosts file, default host, or network setup, then re-execute HiRDB.
  	The following causes are possible in UNIX: There is no access privilege to the /dev/HiRDB/pth directory, or it does not exist A device is mounted under the name /dev/HiRDB	Check the access privilege to /dev/HiRDB/pth. If a device is mounted to /dev/HiRDB, unmount /dev/HiRDB, and then use the pdsetup command to perform setup again.
  Psp7013	The post-processing process of HiRDB aborted. The following are possible causes: The disk holding the HiRDB operation directory is too small, or there are insufficient i-nodes. The HiRDB administrator user ID cannot log in. A failure occurred during acquisition of a network, host, or entry.	Check the error cause from the error message that was output before processing was aborted, and then re-execute. If an error message is not output and none of the causes listed on the left is applicable, save the information collected at error time and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool, the event log (in UNIX, syslogfile), and standard error output.
  Psp7019	Because the number of times that the server process terminated abnormally while the abnormal termination monitoring facility was monitoring exceeded the value specified in the pd_down_watch_proc operand, HiRDB (or the applicable unit for HiRDB/Parallel Server) terminated abnormally.	To prevent HiRDB from terminating abnormally due to the server process terminating abnormally, either omit the pd_down_watch_proc operand, or specify 0. For details about the abnormal termination monitoring facility, see the HiRDB Version 8 System Operation Guide.
  Psp8001	Request for forced termination of a server process was accepted, but the forced termination request was aborted after the process was released because it was a critical process.	Determine the reason why the request for forced termination of the process was accepted, based on the status of the executed transaction or on other messages that were output, and take corrective action as needed. If you intentionally used the pdcancel or other command to forcibly terminate the process, you need not take any corrective action for this abort code. On HiRDB/Parallel Server, if rollback processing on a back-end server requires 5 minutes or more to complete in response to a rollback request from a front-end server, the back-end server process may abort with this code (to speed up transaction commitment, the back-end server process is cancelled internally). You need not take any particular action when a large update for which rollback is expected to take a long time is being executed. However, if the rollback is not intentional, determine the cause of the rollback and take corrective action.
  Pspc013	Timeout occurred during communication for the process server.	If a command was entered during HiRDB termination processing, re-execute the command after termination processing is completed. If timeout recurs, contact a customer engineer.
  Psph052	A user request other than HiRDB caused the HiRDB process server demon to stop. The following user request other than HiRDB is possible: The kill command of the OS (pdkill command for Windows) was executed. This abort, however, only affects the SIGTERM signal.	Restart either HiRDB or the unit. Check to see if the kill command of the OS (or the pdkill command for Windows) has been executed. If the kill command of the OS (or the pdkill command for Windows) has not been executed, contact a customer engineer.
  Psrc*** Psrf*** Psrm*** Psrp*** Psrq*** Psrr*** *: Any character string other than applicable codes that follow.	Error occurred during communication processing.	Check the error cause from the error message that was output before processing was aborted, take appropriate action, then re-execute. If no error message was output, back up the error-related information and contact a customer engineer. Error-related information is in files under %PDDIR%\spool and in the output from standard error.
  Psrc039	Timeout occurred while waiting for a response from the server during transaction startup processing.	The requested service is invalidated. Review the value of the pd_watch_time operand, and re-execute the command.
  Psrc191	Communication workload is high and data cannot be sent even when retry is executed. Or, the destination process is on a status that does not permit it to receive data for a long time. If this does not apply, see 4.1 Detail codes for RPC-related errors.	The communication (LAN) load may be too high. Therefore, either reduce the load and re-execute the processing, or examine the SQL that was executing when the abort occurred, and consider using an SQL with a reduced processing time. If this does not apply, see 4.1 Detail codes for RPC-related errors. If the problem recurs after you have taken the above actions, save the information acquired during the error, and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Psrc304	Transaction did not terminate even though the fixed time from the previous chain RPC call elapsed. Although the PDSWAITTIME specification time elapsed, the UAP did not issue a new SQL to the front-end server or single server being used by the UAP.	Re-execute the target service request because the request has been invalidated. Increase the time specified in PDSWAITTIME of the client environment definition and re-execute.
  Psrc323 Psrc324	Attempt was made to report completion of a service to the service request source, but the service request source was not found. Or, reply cannot be sent due to a communication error.	Re-execute, because the corresponding service will be invalidated.
  Psrc341 Psrc345 Psrc360	An SQL not supported by the HiRDB server was executed (this occurs when the HiRDB client version is newer than the HiRDB server version).	Identify the SQL that caused the error from the HiRDB client's error log. That SQL cannot be executed. For details on the HiRDB client's error log, see the HiRDB Version 8 UAP Development Guide.
  Psrc361	When executing a UAP, operation command, or utility, a failure occurred when receiving a communication message. Insufficient memory is the likely cause.	To release memory, stop all processes that can be stopped. Alternatively, set memory to the estimated value. If plenty of memory exists, consider another cause. If this is the case, save the error-related information, and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Psrc362 Psrc363	A failure occurred responding to an SQL query. Insufficient memory is the likely cause.
  Psrc397	Too much time elapsed between service completion and the next service request. Data will be recovered by terminating the process forcibly. (Some type of error may have occurred in the service-requesting process or in the network, preventing the next service request from being sent.)	Eliminate the error cause and re-execute the utility.
  Psrc398 Psrc399	Requested service response cannot be returned to the requesting source. Data will be recovered by terminating the process forcibly. (An error may have occurred in the network or there was no requesting process, preventing the response from being returned.)
  Psrc661	Allocation of process private memory for storing information received from the UAP (for example, INSERT data) failed.	Either reduce the number of processes in the system or review the memory requirements.
  Psrc712	When a UAP was being processed in a server selected by a chained RPC, the system detected a failure at the host executing the UAP or a network disconnection while waiting for a service request from the UAP.	Re-execute the target service request because the request has been invalidated.
  Psrc752	When a UAP was being processed in a server selected by a chain RPC, the system detected cancellation of UAP execution while waiting for a service request from the UAP.
  Psrc780	An unexpected error occurred during a communications system call.	Take corrective action by seeing the preceding KFPS00353-E message.
  Psrd*** *: Any character string other than those in the Psrd codes that follow.	Error occurred during system operation control processing.	Check the error message that was output before ABORT for the cause of the error, take appropriate action, then re-execute. If no error message was output, back up the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool, the event log (in UNIX, syslogfile), and standard error output.
  Psrd111 Psrd112 Psrd121	An error occurred during unit termination processing. If the error occurs during log application site termination or during a planned termination, all units are terminated forcibly.	Referring to the KFPS05111-E message output immediately before the abort code, determine the cause and eliminate the error. Then, restart HiRDB. If the error occurred during a planned termination or during log application site termination, confirm that all units were terminated, and then restart HiRDB. If some units were not terminated, execute the pdstop -z command on the servers where all units were to be terminated, and then restart HiRDB. Check the following to make sure the units are stopped: Check the event log (in UNIX, syslogfile) of each unit for KFPS01821-E messages or KFPS01841-I messages Refer to KFPS01850-I messages (termination mode of FORCE) output to the event log (in UNIX, syslogfile) of the unit where the system manager resides If the cause cannot be determined even after referring to the KFPS05111-E message, save the files under %PDDIR%\spool, and the event log (in UNIX, syslogfile) for the unit, and contact a customer engineer.
  Psrda31	Memory allocation failed when starting the process that monitors activation status of the other host (server machine).	Re-estimate memory. Alternatively, reduce the number of processes running on the system and re-execute.
  Psrda58 Psrdp11 Psrdp12 Psrdp15 Psrdp16 Psrdp17 Psrdp18 Psrdp19	An error occurred during HiRDB system termination processing. If termination was planned, all units other than the system manager unit are forcibly terminated. Possible causes include a termination processing error occurring on a non-system manager unit, or a communication error.	Check the message output before the KFPS05221 message, eliminate the error, and restart HiRDB. If the process aborted during planned termination processing, make sure that all units are stopped before restarting HiRDB. If there are any active units, stop all units by either executing the pdstop -f command from a server machine that has the system manager, or by executing the pdstop -z command from a server machine with an active unit. Then, restart HiRDB. Check the following to make sure the units are stopped: Check the event log (in UNIX, syslogfile) of each unit for KFPS01821-E messages or KFPS01841-I messages (termination mode of FORCE) If the cause cannot be determined, save the files under %PDDIR%\spool, and the event log (in UNIX, syslogfile) for the unit, and contact a customer engineer.
  Psrda65 Psrdi54 Psrdi55 Psrdi56	Input/output processing on a status file failed.	Investigate the cause of the problem and take corrective action by seeing the preceding status file error message. After taking corrective action, restart the abnormally terminated unit. If the cause of the problem cannot be identified, contact a customer engineer.
  Psrdas1	The unit with a system manager stopped or a network fault occurred, causing communications failure with the system manager. The affected unit is terminated.	If the unit with a system manager is stopped, check the cause of the stoppage of the system manager unit, based on the error message preceding the abort code, and resolve the error. After that, restart HiRDB. If the error occurred even when the system manager unit was running, a network fault must be suspected. Investigate the problem by seeing 4.1 Detail codes for RPC-related errors. If the cause of the problem cannot be identified, save the files under %PDDIR%\spool and the system log files for the system manager unit and the unit that generated the abort code, and contact a customer engineer.
  Psrdg04 Psrdt81 Psrdt83 Psrdu31 Psrdu33 Psrdu35 Psrdu39	There is insufficient process native area.	Determine the cause of the insufficient process native area, take appropriate action, and then restart HiRDB. If the error cannot be resolved, save the information acquired during the error, and contact a customer engineer. UNIX version: The information to be acquired in the event of an error includes the files under %PDDIR%\spool and the syslogfile of the system manager and the unit that output this ABORT code. Windows version: The information to be acquired in the event of an error includes the files under %PDDIR%\spool and the event log of the system manager and the unit that output this ABORT code.
  Psrf203	Allocation failed for process private memory to be used to store information received from UAPs (SQL information such as INSERT data).	Either reduce the number of processes in the system or re-estimate the memory size.
  Psrf301	The allocation of a received message area failed during the reception of a message. To prevent the occurrence of a no-response status due to the inability to receive messages, the system is aborted.	Free memory by terminating any processes that are running in the system that can be terminated. Or, re-estimate memory requirements.
  Psrf302	The allocation of an internal communication logging information area failed. This problem is detected at process startup time. To prevent the continued execution of a process under insufficient memory conditions, the system is aborted.
  Psrp491	Data transmission failed due to the following possible reasons: Not enough socket descriptors Invalid contents of the hosts file If these reasons do not apply, see 4.1 Detail codes for RPC-related errors.	The indicated service is invalidated. Either execute the command when the load is light, or take action by referring to 4.1 Detail codes for RPC-related errors.
  Psrp506	Not enough internal tables	If this error occurred frequently when HiRDB was running and at the same time utilities were executed successively or executed on a multiple basis, either increase the execution interval or reduce the level of multiplicity, or increase the value of the pd_max_server_process operand. If the error occurred while HiRDB was down, start HiRDB, and then re-execute the command. If the problem persists after these measures are taken, contact a customer engineer.
  Psrp507	Insufficient memory	There is not enough process-private area. Review the memory requirements. Also, terminate any unneeded processes.
  Psrp616	The allocation of a received message area for inter-thread communications failed. To prevent the occurrence of malfunction due to the inability to receive messages, the system is aborted.	Free memory by terminating any processes that are running in the system that can be terminated. Or, re-estimate memory requirements.
  Psrq016 Psrq017	Attempt was made to report completion of a service to the service request source, but the service request source was not found. Or, reply cannot be sent due to a communication error.	Re-execute, because the corresponding service will be invalidated.
  Psrq801	A failure occurred when referencing the host name used by HiRDB, or when acquiring an address. Consider the following causes: There is no host name or IP address in the hosts file. The system does not have reference privileges to the hosts file. The standard host name has been changed to an incorrect one not specified in the hosts file. If you are using DNS or WINS, the host name or IP address is not in the search database. If you are using DNS or WINS, the system does not have reference privileges to the search database.	HiRDB uses the host name that is specified in the pdunit operand of the system common definition (%PDCONFPATH%\pdsys), which is the standard host name of the applicable server machine. Eliminate the cause of the error and re-execute.
  Psrq809	UNIX version: The value set in the OS parameter (kernel parameter) maxfiles_lim is too small; HiRDB cannot be started. Windows version: Due to insufficient capacity on the installation drive, shared memory work files cannot be allocated.	UNIX version: Reset the value of maxfiles_lim to 1024 or more. Windows version: On the HiRDB installation drive, allocate at least as much free space as is required for the shared memory size.
  Psrq810	The maximum number of HiRDB processes defined for the unit has been exceeded.	Either re-execute the operation or check the value specified in the pd_max_server_process operand. The specified value may be too small.
  Pssc*** *: Any character string other than those in the Pssc codes that follow.	Error occurred during schedule processing.	Refer to the error message that was output before ABORT to check the cause of the error, take appropriate action, then re-execute. If no error message has been output, save the error-related information and contact a customer engineer. Error-related information is in files under %PDDIR%\spool and in the output from standard error.
  Pssc412	A shortage of process-private memory occurred during back-end server processing when the standby-less system switchover (effects distributed) facility was being used.	Reduce the number of processes in the system and then re-execute the command. Or, review the amount of available process-private memory.
  Pssc60b	Process private memory shortage occurred while initializing the message queue.	Reduce the number of processes within the system and re-execute, or re-estimate the process private memory size.
  PsscZ01	Even though the message queue monitoring duration (value of pd_queue_watch_time operand) of the message queue monitoring facility was exceeded, messages are not being flushed from the message queue. For details about the message queue monitoring facility, see the HiRDB Version 8 System Operation Guide.	For causes of message queue hold-up and corrective actions that can be taken, see the HiRDB Version 8 System Operation Guide. If these possibilities do not apply, contact a customer engineer.
  PsscZ70	An internal error occurred.	If there is a preceding error message, take corrective action according to that message. If there is no message output, save the information to be acquired in the event of an error, and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and the event log (in UNIX, syslogfile) of the system manager and the unit that output this ABORT code.
  Pssp*** *: Any character string other than applicable codes that follow.	An error occurred during synchronization point dump processing.	Determine the cause based on the error message output before the process aborted, take corrective action, and re-execute. If no error message was output, back up the error-related information, and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Psspc01	An error occurred during automatic computing of the pd_spd_syncpoint_skip_limit operand.	Quit using automatic computing, and estimate a value for this operand. For details about how to estimate system resources, see the description of the skipped effective synchronization point dump monitoring facility in the HiRDB Version 8 System Operation Guide.
  Psss*** *: Any character string	Error occurred during status file processing.	Refer to the error message that was output before ABORT to check the cause of the error, take appropriate action, then re-execute. If no error message has been output, save the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Psss372	See Psss***.	For a HiRDB/Parallel Server, check to see if the system manager is running normally or if there has been an error on the network. If the system manager is not running normally or there has been an error on the network, check the cause of the error, resolve the error, and restart HiRDB. If the above possibilities do not apply, see the action under Psss***.
  Psst*** *: Any character string	Error occurred during statistics log processing.	Check the cause of the error based on error messages preceding the abort, take corrective action, and then re-execute the command. If there is no error message, save the information to be acquired in the event of an error, and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Pst*** Pstd*** Psth0r* Psti0r* Pstj*** Pstm0r* Pst**** *: Any character string other than applicable codes that follow.	Error occurred during transaction processing.	Refer to the error message that was output before ABORT to check the cause of the error, take appropriate action, then re-execute. If no error message has been output, save the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Pst80rq	The system server could not be placed on wait status.	If memory is insufficient, determine the reason why memory is insufficient, take corrective action, and restart. If an error message was output before the process aborted, determine the cause of the error based on the error message, take corrective action, and restart. If no error message was output, save the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Pst87r2	A synchronization point was not acquired during normal startup processing; the startup process is cancelled. A synchronization point was not acquired during normal termination or planned shutdown; the termination process is cancelled.	Check the cause of the error based on the reason code indicated in the preceding KFPS02178-E message, and take corrective action. If the system aborted during normal startup processing, resolve the error, and then restart HiRDB. If the system aborted during normal termination or planned shutdown, it is an indication that the normal termination or planned shutdown of HiRDB failed. In this case, take corrective action, restart HiRDB as necessary, and execute the normal termination or planned shutdown of HiRDB again.
  Pst8br0	A receive timeout occurred when information for recovering related transactions was being transmitted during transaction recovery processing. In UNIX, the files under /dev/HiRDB/pth were deleted while HiRDB was running.	If there is a machine for which the power is off (or the network is down), turn on the power (or bring up the network). In addition, reduce the level of multiple access to HiRDB.
  PstA0m0 PstAlm7 Pst80r7 Pstf0r0 Pstclrd Pstclr2 Pstclr3 Pstclrf	Memory allocation failed.	Re-estimate the memory. Or, reduce the number of processes in the system and re-execute. If this error recurs, contact a customer engineer.
  Pstb0r6 Pstb0rB	The buffer size is too small; the transaction processing is terminated.	Change the value specified in the pd_log_max_data_size operand of the server common definition for each server to the target specification value.
  Pstc2r1	Unable to continue transaction recovery due to a network error; the system is abnormally terminated.	Resolve the error, and then restart HiRDB.
  PstD2m1	Unrecoverable error, such as a communication error, occurred during transaction processing.	If the KFPS00992-I message was output after the process was aborted, take action based on that message. If the KFPS00990-I message was output, check its message completion type. If no message has been output, the transaction was committed in accordance with the requested commit type.
  PstD2m9	A communication error occurred during commit processing.	Check the status of the system and the network. If the transaction is not settled, use the pdcmt or pdrbk command to settle it.
  Pstf0r1	An attempt was made to modify a system definition that cannot be changed during restarting.	Restart the system by resetting the values of pd_max_users, pd_max_bes_process, and pd_max_dic_process.
  Pstf0ra	An attempt was made to input a record exceeding the record length stored in the status file and recorded during the last system operation. It is possible that a specification value in one of the following parameters was significantly changed: pd_max_users, pd_max_bes_process, and pd_max_dic_process.
  Pstf0rc	Operation directory environment is invalid.	Check that the operation directory is set up correctly and that no change has been made to the file privilege or file contents after setup. If the error recurs after setting up the environment again, contact a customer engineer.
  Psth0ra	Different OLTP identifiers were set in an OLTP. For OpenTP1, the OLTP identifier specified in the user service or user service default definition differs from the OLTP identifier specified in the transaction service definition.	Use the same OLTP identifier in both the transaction service definition and the user service default definition or user service definition.
  Psth0r1 Psth0rb Psth0rd Psth1r0 PstD5m3 PstD6m5 PstD6mg PstD7m4 Pst93m3	A timeout occurred due to processes contending for system resources. If transaction recovery processing is being performed, you can release the resource contention and continue transaction recovery by forcibly terminating and then restarting the applicable unit.	Reduce the number of concurrent accesses to HiRDB and re-execute. If the unit is stopped, restart it. If this error occurs frequently, contact a customer engineer.
  Psti*** *: Any character string other than the Psti code that follows.	Error occurred during timer processing.	Check the error message that was output before ABORT for the cause of the error, take appropriate action, then re-execute. If no error message was output, save the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and %PDDIR%\tmp, the event log (in UNIX, syslogfile), and standard error output.
  Psti0rf	Transaction service function cannot be used because the PDUSER environment variable is defined incorrectly in the OpenTP1 definition.	Check if putenv PDUSER authorization identifier/password is specified in a definition other than OpenTP1's user service definition or user service default definition, take appropriate action (delete PDUSER from OpenTP1's transaction definition), then restart OpenTP1 and HiRDB.
  Pstj14j	A synchronization point was not acquired during normal startup processing; the startup process is cancelled.	Check the cause of the problem and take corrective action based on the reason code indicated in the preceding KFPS02178-E message. After corrective action is taken, restart HiRDB.
  Pstj14k	A synchronization point was not acquired during normal termination or planned shutdown; the termination process is cancelled.	Check the cause of the problem and take corrective action based on the reason code indicated in the preceding KFPS02178-E message. Also, because the normal termination or planned shutdown of HiRDB failed, take corrective action, and if necessary, restart HiRDB, and execute the normal termination or planned shutdown of HiRDB.
  Pstj14m Pstj14n	A temporary memory shortage occurred.	Check the cause of the memory shortage, take corrective action, and then restart HiRDB.
  Pstjf97	There is insufficient process native area.	Take action based on the instructions given in the KFPO00106-E message.
  Pstmex1	Error occurred during transaction processing.	Save the files in %PDDIR%\spool, and the event log (in UNIX, syslogfile) of the unit where the error occurred, and contact a customer engineer.
  Pstmex2	Request for forced termination of a server process was accepted, but forced termination was aborted after the process was released because it was a critical process.	Determine the reason why the request for forced termination of the process was accepted, based on the status of the executed transaction or on other messages that were output, and take corrective action as needed. If you intentionally used the pdcancel or other command to forcibly terminate the process, you need not take any corrective action for this abort code. On HiRDB/Parallel Server, if rollback processing on a back-end server requires 5 minutes or more to complete in response to a rollback request from a front-end server, the back-end server process may abort with this code (to speed up transaction commitment, the back-end server process is cancelled internally). You need not take any particular action when a large update for which rollback is expected to take a long time is being executed. However, if the rollback is not intentional, determine the cause of the rollback, and take corrective action.

  Table 3-10 Abort codes (PtXXXXX)

  ABORT Code	Cause	Action
  Pt00000	An invalid data code was detected (self-contradictory).	If an error message was output immediately before the process aborted, take corrective action based on that message. If no message was output, save the files under %PDDIR%\spool and %PDDIR%\conf, and the event log (in UNIX, syslogfile), and contact a customer engineer.
  Pt00001	A transmission error occurred (send).
  Pt00002	A reception error occurred. (recv).
  Pt00003	Sent text is invalid (process start).
  Pt00004	Reply text is invalid (process start).
  Pt00005	Sent text is invalid (SQL execution).
  Pt00006	Reply text is invalid (SQL execution).
  Pt00007	A communication sequence is invalid.
  Pt00008	A log block is invalid.
  Pt00009	A log record is invalid.
  Pt00010	A service start error occurred (pd_com_call).
  Pt00011	A service stop error occurred (pd_com_poll_any_replies).
  Pt00012	Branch registration failed.
  Pt00013	Branch deletion failed.
  Pt00014	An attempt to acquire the host name of the primary system failed.
  Pt00015	Assertion failed.
  Pt00016	An attempt to build table definition information failed.
  Pt00017	An attempt to deserialize table definition information failed.
  Pt00018	An attempt to start service (connect) failed.
  Pt00019	An attempt to stop service (disconnect) failed.
  Pt00020	An abnormal termination was detected on the communication target.

  Table 3-11 ABORT codes (PuXXXXX)

  ABORT Code	Cause	Action
  Pu**** *: Any character string	Error occurred in the common system service function.	Check the error message that was output before ABORT for the cause of the error, take appropriate action, then re-execute. If no error message was output, save the error-related information and contact a customer engineer. The information to be acquired in the event of an error includes the files under %PDDIR%\spool and standard error output.
  Pu00000	Invalid data code was detected.	Contact a customer engineer.
  Pu00001	Transmission error occurred.
  Pu00002	Management table is invalid (send).
  Pu00003	Management table is invalid (receive).
  Pu00004	Transmission error occurred.
  Pu00100	Invalid reply text was received.
  Pu00200	An internal conflict was detected during input data edit processing.	Save the files under %PDDIR%\spool, and the contents of the control information file that was specified when the utility was executed, as data, and contact a customer engineer.
  Pu01000	Request code is invalid (input data receive processing).
  Pu01001	Request code is invalid (error message send processing).
  Pu01002	Request code is invalid (index information send processing).
  Pu02000	Receive error occurred (pdi_com_recv).	In the case of server termination, there is no need to contact a customer engineer.
  Pu02001	Preparations for communication cannot be performed.	Take action appropriate to the error message.
  Pu02002	Transmission is not available due to the status.
  Pu02003	Index information cannot be received.
  Pu02004	Timeout occurred while waiting for a message from the server.
  Pu02100	COMMIT cannot be issued due to the status.
  Pu03000	RDAREA ID is invalid.
  Pu04000	An invalid server activation request was received.	Save the files under %PDDIR%\spool, and the contents of the control information file that was specified when the utility was executed, as data, and contact a customer engineer.
  Pu04010	An interface conflict was detected.
  Pu04100	An area was destroyed by the UOC.	Correct the UOC error.
  Pu04500	The status of the audit trail file is unknown.	Save the files under %PDDIR%\spool, and contact a customer engineer.
  Pu04600	An error occurred that prevents processing from continuing when outputting to the audit trail file.
  Pu05000	An invalid plug-in function was detected.	Save the files under %PDDIR%\spool, and the contents of the control information file that was specified when the utility was executed, as data, and contact a customer engineer.
  Pu05100	An error was detected in the plug-in function that prevented the continuation of processing.	Correct the cause of the error by referring to the KFPY99999-E message that was output before the abnormal termination. If there is no message output, or if an error that cannot be resolved at the user level occurs, save the files under %PDDIR%\spool, and contact a customer engineer.
  Pu06000	An invalid utility work file was created.	Take the following actions by referring to the KFPL00703-I message: If the number of data items stored is equal to the number of data items in the input data file, data need not be recovered. If the number of data items stored is less than the number of data items in the input data file or no messages are output, it is impossible to determine which data items failed to be stored. In this case, reset the utility to the condition that existed before it was executed and re-execute. This error occurs when the work file under the temporary directory (in UNIX, $PDDIR/tmp and /usr/tmp; in Windows, %PDDIR%\tmp) created by the utility is destroyed. During the execution of the utility, do not operate on any of the files belonging to the HiRDB administrator that are stored under this directory.
  Pu07000	A reception error occurred (pdi_com_recv).	Take corrective action based on the KFPL20005-E and KFPL20100-E messages output immediately before the system terminated abnormally.
  Pu07001	A communication message could not be sent.	Take corrective action based on the KFPL20100-E message output immediately before the system terminated abnormally.
  Pu07002	An internal conflict occurred.	Save the files under %PDDIR%\spool, and the contents of the control information file that was specified when the utility was executed, as data, and contact a customer engineer.
  Pu07003	An internal conflict occurred (invalid line ID).
  Pu07004	An error occurred during transaction processing (start, terminate, commit, or rollback).	Take corrective action based on the KFPL20020-E message output immediately before the system terminated abnormally.
  Pu07005	A process cannot be started.	Eliminate the cause of the error based on the message output immediately before the system terminated abnormally. If an error that cannot be resolved occurs, save the files under %PDDIR%\spool, and contact a customer engineer.
  Pu10000	Requested code is invalid (startup information receive processing).	Contact a customer engineer.
  Pu10001	Requested code is invalid (parameter information receive processing).
  Pu10002	Contradiction was detected during row data retrieval processing.
  Pu10003	Requested code is invalid (parameter information send processing).
  Pu10004	Message log cannot be output.
  Pu10005	Invalid data was detected in the table to be unloaded.	The database is damaged. Check whether there is any conflict in the operation of the database. If the cause of damage cannot be found in the operating method, save the RDAREA in which the table is stored and the log for the affected server, and then contact a customer engineer. Recover the database from its backup, and then unload the table.
  Pu10006	An internal conflict occurred (invalid content in DAT format data conversion buffer).	Save the files under %PDDIR%\spool, and the contents of the control information file that was specified when the utility was executed, as data, and contact a customer engineer.
  Pu11000	An internal error occurred on reception of an unexpected request code.	Contact a customer engineer.
  Pu11111	A commit cannot be performed.	Eliminate the cause of the error based on the KFPL20020-E message output immediately before the system terminated abnormally. If an error that cannot be resolved occurs, save the files under %PDDIR%\spool, and contact a customer engineer.
  Pu12002	Processing results cannot be reported due to a communication error.	The system terminated abnormally because processing results could not be reported. However, free pages have been released, and the database can be accessed. If any unreleased free pages remain when you execute the pddbst command, eliminate the cause of the error by referring to any communication-related error message output immediately before the system terminated abnormally. Then, re-execute the command. If an error that cannot be resolved occurs, save the files under %PDDIR%\spool, and contact a customer engineer. The server can also terminate abnormally on this abort code if a system switchover occurs during the execution of the utility and the utility process that outputs result lists terminates abnormally.
  Pu13000	There is a mistake in the startup parameter of the pdreclaim command.	If you are currently doing so, do not specify a table or an index with the -k option of the pdrorg command. In other cases, save the files under %PDDIR%\spool, and contact a customer engineer.
  Pu15100	Error was detected in the plug-in function that prevented the further continuation of processing.	Correct the cause of the error by referring to the KFPY99999-E message that was output before the abnormal termination. If there is no message output or if an error that cannot be resolved at the user level occurs, save the files under %PDDIR%\spool, and contact a customer engineer.
  Pu20000	Open processing was attempted on a file with an invalid path name.	Determine whether the path name of the file is a null value. If the specification of the path name is correct, save the files under %PDDIR%\spool, and contact a customer engineer.
  Pu20001	An error occurred during transaction processing (startup, termination, commit, or rollback).	Save the files under %PDDIR%\spool, and contact a customer engineer.

  Table 3-12 Abort codes (PwXXXXX)

  ABORT Code	Cause	Action
  Pw05000	An internal conflict occurred during HiRDB startup.	Save the files under %PDDIR%\spool, %PDDIR%\conf, and %PDDIR%\tmp, and the event log (in UNIX, syslogfile), and contact a customer engineer.
  Pw05001	An error occurred during analyses of foreign server information definitions.	Eliminate the cause of the error based on the KFPW05001-E message output immediately before the system terminated abnormally. If no error message was output, save the files under %PDDIR%\spool, %PDDIR%\conf, and %PDDIR%\tmp, and the event log (in UNIX, syslogfile), and contact a customer engineer.
  Pw05002	An internal conflict occurred during reading of a HiRDB internal file.	Save the files under %PDDIR%\spool, %PDDIR%\conf, and %PDDIR%\tmp, and the event log (in UNIX, syslogfile), and contact a customer engineer.
  Pw05003	An internal conflict occurred during acquisition of HiRDB External Data Access Adapter information.	Save the files under %PDDIR%\spool, and contact a customer engineer.
  Pw05021	An internal conflict occurred during shared memory computation processing.
  Pw05030	An internal conflict occurred during dictionary search processing.	Save the files under %PDDIR%\spool, %PDDIR%\conf, and %PDDIR%\tmp, and the event log (in UNIX, syslogfile), and contact a customer engineer.
  Pw05031	An internal conflict occurred during creation of a HiRDB internal file.
  Pw05032	An internal conflict occurred during creation of a HiRDB internal file.	Save the files under %PDDIR%\spool and contact a customer engineer.
  Pw06000	An error occurred during process startup.	Take corrective action based on the message output immediately before the process aborted. Then, re-execute. If no error message was output, save the files under %PDDIR%\spool, %PDDIR%\conf, and %PDDIR%\tmp, and the event log (in UNIX, syslogfile), and contact a customer engineer.
  Pw06011	An internal conflict occurred during process termination.	If no error message was output, save the files under %PDDIR%\spool, %PDDIR%\conf, and %PDDIR%\tmp, and the event log (in UNIX, syslogfile), and contact a customer engineer.
  Pw06016	An internal conflict occurred.
  Pw06017	An internal conflict occurred.
  Pw07001	An internal conflict occurred during transaction start processing.
  Pw07002	An internal conflict occurred during transaction end processing.
  Pw07016	An internal conflict occurred.
  Pw08001	An internal conflict occurred on the thread start trigger.
  Pw08002	An internal conflict occurred on the thread end trigger.
  Pw09001	A failure occurred during message output processing.
  Pw09003	An internal conflict was detected during statistics log output processing.
  Pw09004	An internal conflict was detected during statistics log editing.
  Pw10000	An internal conflict was detected during connection information assignment processing.	Eliminate the cause of the error based on the KFPW02501-E message output immediately before the system terminated abnormally. If no error message was output, save the files under %PDDIR%\spool, %PDDIR%\conf, and %PDDIR%\tmp, and the event log (in UNIX, syslogfile), and contact a customer engineer.
  Pw10001	An internal conflict was detected during connection to a foreign server.	Save the files under %PDDIR%\spool, %PDDIR%\conf, and %PDDIR%\tmp, and the event log (in UNIX, syslogfile), and contact a customer engineer.
  Pw10002	An internal conflict was detected during disconnection from a foreign server.
  Pw10003	An internal conflict was detected during release of connection information.
  Pw10010	SQL was executed for an external table without HiRDB External Data Access installed.
  Pw10011	An internal conflict was detected when SQL was executed.
  Pw10012	An internal conflict was detected when SQL was executed.
  Pw10013	The foreign server definition for executing the SQL to be processed does not exist.	Define the foreign server with CREATE SERVER, and restart HiRDB.
  Pw10014	An internal conflict was detected when SQL was executed.	Save the files under %PDDIR%\spool, %PDDIR%\conf, and %PDDIR%\tmp, and the event log (in UNIX, syslogfile), and contact a customer engineer.
  Pw10015	An internal conflict was detected when SQL was executed.
  Pw10016	An internal conflict was detected when loading HiRDB External Data Access Adapter.
  Pw15000	An internal conflict was detected.
  Pw20001	An unexpected return value was returned from HiRDB External Data Access Adapter.
  Pw20003	An internal conflict was detected when SQL was executed.

  Table 3-13 ABORT codes (PxXXXXX)

  ABORT Code	Cause	Action
  Pxe7500	Error that prevents continued processing was detected during execution of the dictionary export/import utility.	The error cause is output in the KFPX18430-E message. Contact a customer engineer.
  Pxi0002	HiRDB file write error occurred.	Save the files under %PDDIR%\spool and contact a customer engineer.
  Pxi0007	RPC communication ID is invalid.
  Pxj0001	JAR file transfer between hosts failed.	Re-execute the command. If the error occurs again after re-execution, contact a customer engineer.
  Pxj0002	Invalid interface was detected while analyzing the definition file.	Contact a customer engineer.
  Pxj0003	Contradiction was detected while analyzing pd_java_archive_directory.
  Pxj0004	Contradiction was detected while analyzing the pdstart command parameters.
  Pxm0001	Allocation of text area failed.	Communication area cannot be allocated. Take action appropriate to the KFPX24201-E message.
  Pxm0002	HiRDB file write error occurred.	Save the files under %PDDIR%\spool and contact a customer engineer.
  Pxm0003	Internal conflict occurred in the dictionary.	Ensure that the dictionary table recovery and reorganization procedures are correct. If the procedures are correct, save the files under %PDDIR%\spool, back up the data dictionary RDAREA by specifying -Mr in pdcopy, and contact a customer engineer.
  Pxm0004	Error occurred during global buffer allocation.	Save the files under %PDDIR%\spool and contact a customer engineer.
  Pxm0005	Internal conflict occurred in the directory.	Ensure that the master directory RDAREA recovery procedure and the data dictionary RDAREA recovery and reorganization procedures are correct. If the procedures are correct, save the files under %PDDIR%\spool and \dbenv, back up the master directory RDAREA and data dictionary RDAREA by specifying -Mr for pdcopy, and contact a customer engineer.
  Pxm0006	Internal conflict occurred in the global buffer.	Save the files under %PDDIR%\spool and \dbrv and contact a customer engineer.
  Pxm0009	Transaction commit or rollback failed.	Eliminate the cause of the error based on the KFPX24214-E message output immediately before the system terminated abnormally. If an error that cannot be resolved occurs, save the files under %PDDIR%\spool, and contact a customer engineer.
  Pxv0001	Transaction commit or rollback processing failed.	Eliminate the cause of the error based on the KFPX24400-E message output immediately before the system terminated abnormally. If an error that cannot be resolved occurs, save the files under %PDDIR%\spool, and contact a customer engineer.
  Pxv0002	Internal conflict occurred in the dictionary.	Ensure that the dictionary table recovery and reorganization procedures are correct. If the procedures are correct, save the files under %PDDIR%\spool and the backup of the data dictionary RDAREA obtained before the version upgrade, and contact a customer engineer.

  Table 3-14 ABORT codes (PyXXXXX)

  ABORT Code	Cause	Action
  Pyp1101	A plug-in requested abnormal termination.	Take action based on the KFPY03001-E message.
  Pysf001	Internal conflict was detected.	Contact a customer engineer.
  Pysf002
  Pysf007	An error occurred in a plug-in call during transaction processing.	If the KFPY99999-I message is output, take action according to this message. If HiRDB is terminated after an action was taken, restart HiRDB. If no KFPY99999-I message was output, save the files under %PDDIR%\spool, %PDDIR%\tmp, and %PDDIR%\plugin, and the event log (in UNIX, syslogfile), and contact a customer engineer.
  Pysf008	An error occurred in a plug-in call at the transaction recovery process termination timing.
  Pysf009	An error occurred in a plug-in call at the database recovery utility process startup timing and user process startup timing.
  Pysf00a	An error occurred in a plug-in call at the database recovery utility process termination timing and user process termination timing.
  Pysf00b	An error occurred in a plug-in call at the roll forward processing process startup timing.
  Pysf00c	Internal conflict was detected.	Contact a customer engineer.
  Pysf00d	An error occurred in a plug-in call at the roll forward processing process termination timing.	If the KFPY99999-I message is output, take action according to this message. If HiRDB is terminated after an action was taken, restart HiRDB. If no KFPY99999-I message was output, save the files under %PDDIR%\spool, %PDDIR%\tmp, and %PDDIR%\plugin, and the event log (in UNIX, syslogfile), and contact a customer engineer.
  Pysf00e	Internal conflict was detected.	Contact a customer engineer.
  Pysf00f	An error occurred in a plug-in call at the transaction recovery processing process termination timing.	If the KFPY99999-I message is output, take action according to this message. If HiRDB is terminated after an action was taken, restart HiRDB. If no KFPY99999-I message was output, save the files under %PDDIR%\spool, %PDDIR%\tmp, and %PDDIR%\plugin, and the event log (in UNIX, syslogfile), and contact a customer engineer.
  Pysf010	Internal conflict was detected.	Contact a customer engineer.
  Pysf012	An error occurred in a plug-in call at the thread startup timing.	If the KFPY99999-I message is output, take action according to this message. If HiRDB is terminated after an action was taken, restart HiRDB. If no KFPY99999-I message was output, save the files under %PDDIR%\spool, %PDDIR%\tmp, and %PDDIR%\plugin, and the event log (in UNIX, syslogfile), and contact a customer engineer.
  Pysf013	An error occurred in a plug-in call at the thread termination timing.
  Pysf015	An error occurred in a plug-in call at the transaction startup timing for the transaction recovery processing process.
  Pysf016	An error occurred in a plug-in call at the transaction prepare processing timing.
  Pysf017	An error occurred in a plug-in call at the transaction commitment processing timing.
  Pysf018	An error occurred in a plug-in call at the transaction commitment processing timing.
  Pysf019	An error occurred in a plug-in call at the thread startup timing for a database recovery utility process.
  Pysf01a	An error occurred in a plug-in call at the thread ending timing for a Database Recovery Utility process.
  Pysf01b	An error occurred when the front-end server was being started.	If the message KFPY01001-E, KFPY01002-W, KFPY01003-E, KFPY01004-E, KFPY01005-E, or KFPY01012-E is output, take action according to the message. If a unit is already started, normally terminate it and then restart HiRDB. If the above messages were not output, save the files under %PDDIR%\spool, %PDDIR%\tmp, and %PDDIR%\plugin, and the event log (in UNIX, syslogfile), and contact a customer engineer.
  Pysf01c	An error occurred when the back-end server was being started.
  Pysf01d	An error occurred when the dictionary server was being started.	If the message KFPY01002-W, KFPY01005-E, or KFPY01007-E is output, take action according to the message. After that, restart HiRDB if it has been terminated. If a unit is already started, normally terminate it and then restart HiRDB. If the above messages were not output, save the files under %PDDIR%\spool, %PDDIR%\tmp, and %PDDIR%\plugin, and the event log (in UNIX, syslogfile), and contact a customer engineer.
  Pysf01e	An error occurred in a plug-in call at the rollback process startup timing or termination timing for the database recovery utility.	If the KFPY99999-I message is output, take action according to this message. If HiRDB is terminated after an action was taken, restart HiRDB. If no KFPY99999-I message was output, save the files under %PDDIR%\spool, %PDDIR%\tmp, and %PDDIR%\plugin, and the event log (in UNIX, syslogfile), and contact a customer engineer.
  Pysf01f	Error occurred while calling a server startup process plug-in.
  Pysf020	Internal conflict was detected.	Contact a customer engineer.
  Pys0001	An internal conflict was detected	Save the files under %PDDIR%\spool, %PDDIR%\tmp, and %PDDIR%\plugin, and the event log (in UNIX, syslogfile), and contact a customer engineer.
  Pys0002
  Pys0003
  Pys0004
  Pys0005
  Pys0006
  Pys0007
  Pys0008
  Pys000b
  Pys000c
  Pys000d
  Pys000e
  Pys000f
  Pys0010
  Pys0011
  Pys0012
  Pys0013
  Pys0014
  Pys0015
  Pys0016
  Pys0017
  Pys0018
  Pys0019
  Pys001a
  Pys001b
  Pys001c
  Pys001d
  Pys001e
  Pys001f
  Pys0020
  Pys0021
  Pys0022

  Table 3-15 ABORT codes (PiXXXXX)

  ABORT Code	Cause	Action
  Pia4010	An attempt was made to create a message queue identifier, but the system-determined number of message queue identifiers for the entire system has exceeded the limit.	Revise the message queue estimation formula to increase the number of message queue identifiers, and restart HiRDB.
  Pia4011	A message send/receive error has occurred.	If message queue identifiers for users have been removed from the system, restart HiRDB. If that is not the case, save the files under %PDDIR%\spool, and then restart HiRDB. Also, contact a customer engineer.
  Pia***** *: Any character string	An internal conflict was detected.	Save the files under %PDDIR%\spool, and restart HiRDB. Also, contact a customer engineer.