7.6.1 Investigating failures in screen operations of operating environment and command operations

When a failure occurs, check messages displayed on console or screens of the operating environment and investigate the failure. When the screens of operating environment are not operating, take actions so that the screens are restored to normal status.

Organization of this subsection

(1) Methods for log analysis and classification of failure
(2) Main failures and corresponding actions
(3) How to take actions when screens of the operating environment cannot be operated

(1) Methods for log analysis and classification of failure

The following figure shows the investigation procedure when a failure occurs when you perform command operations or screen operations of the operating environment:

Figure 7‒37: Failure investigation procedure (Failure investigations when performing command operations or screen operations of the operating environment)

The description of the flow of investigation shown in Figure 7-37 is as follows:

When an error occurs in command operations or screen operations of the operating environment, first check messages output to the console as a response to the command.

Also, check if messages are output as the detailed information of messages. The following figure shows output examples:
- For KDEC or KEOS messages (messages related to HCSC - Manager) whose detained information includes a message whose ID begins with KDEC
  
  See the manual uCosminexus Service Platform Messages, and take countermeasures.
- For KEOS messages (messages related to HCSC - Manager) whose detailed information includes a message whose ID does not begin with KDEC
  
  See the manual appropriate for the message. For example, if the detailed information includes a message whose ID begins with KDJE, see the manual uCosminexus Application Server Audit Log Messages.
Reference the acquired message log when the cause cannot be specified. The following message logs are referenced as failure information when executing setup or unsetup. For details, see "7.4.1 Message log".
- HCSC-Manager log
- Integrated message log
- Activity log of J2EE server
The cause for occurrence of a failure might be due to environment settings or system status before command execution. Therefore, check locations where command response messages are output, and confirm that there are no other error messages and take appropriate actions.

Furthermore, the messages output to console are duplicated and output while checking the contents of message log. Therefore, check suitable execution time.

To Page Top

(2) Main failures and corresponding actions

The following table lists and describes the main failures and corresponding actions when executing command operations:

Table 7‒67: Main failures and corresponding actions (Failure investigation when executing command operations and screen operations of the operating environment)
Operation	Main failures	Reason that can be considered	Troubleshooting	Reference
csm command execution when using Type4 driver	If the `csm` command is executed when the HCSC server is not running, the following error occurs: KDEC10410-E (KDEC10044-E) The following detailed information is output in the KDEC10044-E message: `(error` `code` `=` `KDEC05012-E,` `error` `message` `=` `Database` `access` `initialization,` `before` `HCSC` `server` `startup,` `failed` `because` `loading` `of` `the` `JDBC` `driver` `failed.` `(JDBC` `name` `=` `JP.co.Hitachi.soft.HiRDB.JDBC.HiRDBDriver))`	Any one of the following directories is not set up: <Installation directory of Service Platform>`\`CSC`\`config`\`msg`\`cmdconf.bat <Installation directory of Service Platform>/CSC/config/msg/cmdconf <Installation directory of Service Platform>CSC/config/msg/cmdconf	Specify the path of jar file (pdjdbc2.jar) of HiRDB Type4 JDBC Driver in HCSC_ADDCLASSPATH of cmdconf (cmdconf.bat)	"6.5.4 HCSC-Messaging command definition file" in "Service Platform Reference Guide".
csm command execution when using Oracle	If the `csm` command is executed when the HCSC server is not running, the following error occurs: KDEC10410-E (KDEC10044-E) The following detailed information is output in the KDEC10044-E message: `(error` `code` `=` `KDEC05012-E,` `error` `message` `=` `Database` `access` `initialization,` `before` `HCSC` `server` `startup,` `failed` `because` `loading` `of` `the` `JDBC` `driver` `failed.` `(JDBC` `name` `=` `oracle.jdbc.OracleDriver))`		Specify the absolute path of jar file of Oracle JDBC Thin driver in HCSC_ADDCLASSPATH of cmdconf (cmdconf.bat).
csm command execution in a status where HCSC server is not started	If the `csm` command is executed when the HCSC server is not running, the following error occurs: KDEC10410-E (KDEC10044-E) The following detailed information is output in the KDEC10044-E message: `(error` `code` `=` `KDEC05001-E,` `error` `message` `=` `An` `attempt` `to` `open` `a` `connection` `to` `the` `database` `has` `failed.` `(reason` `=` `KFPA11724-E` `Environment` `definition` `error,` `variable=PDUSER,` `reason=NO` `VALUE[PrdbConnection.PrdbConnection],` `SQL` `state` `=` `R0000,` `error` `code` `=` `-724))`	The user name and password of database are not specified in option of the csm command.	Specify the user name and password of database in the option of the csm command. When the HCSC server is offline, specify the user name and password of database without fail.	"5. Commands (Operating and Execution Environments)" in "Service Platform Reference Guide".
csm command execution	The `csm` command fails, and the KFPA11912-E message (lack of work area for locks) is output to the database (HiRDB) log and trace.	Insufficient working area due to mutual exclusion.	Increase the value specified for following operands of HiRDB system definition and restart HiRDB: pd_max_access_tables pd_lck_pool_size pd_fes_lck_pool_size	" HiRDB Version 9 System Definition"

To Page Top

(3) How to take actions when screens of the operating environment cannot be operated

The actions to be taken when screens of the operating environment cannot be operated are as follows:

(a) When screen operations fail and you cannot click the button

Take actions as per the following procedure:

Investigate the cause of error output to the dialog box or screen console and take appropriate actions.
Perform any of the following operations:
- Execute [Update to the latest information] from the HCSC-Manager menu
- Close the editor and re-display
When you are unable to recover the screen with step 1 and 2, execute any of the following operations:
- Execute commands for operations that ended in an error
- Execute commands for operations that failed and operations opposite to the failed operations (Stop when the start procedure fails)

(b) When there is "No response" from the Eclipse screen

Take actions as per the following procedure:

Click the [Close] button of the Eclipse screen, and close the screen forcefully.

When you cannot close the screen with the button, end the tasks of Eclipse from the [Application] tab of the [Task manager].
Investigate the cause of error and take actions.
Start the Eclipse screen, login to HCSC-Manager, and then re-execute the operations that ended with an error.

Important note: On performing the above mentioned actions, the content that is being edited in the Eclipse same as the operating environment is lost. When you operate the screens of the operating environment, you must save or terminate contents that are being edited beforehand in Eclipse.

To Page Top