Job Management Partner 1/Software Distribution Client Description and User's Guide
This section lists the messages for generator tools.
Processing of generator tools has started [xxx].
- Cause
- Processing of generator tools has started. xxx indicates the startup program name.
Completed the processing of generator tools [nn].
- Cause
- Processing of generator tools is completed. nn indicates the return code.
Starting installation (Standard:rrr).
- Cause
- The standard installation starts. rrr indicates the full package ID.
Starting installation (Linkage:rrr).
- Cause
- The installation that requires linkage processing starts. rrr indicates the full package ID.
Starting installation (UAP:rrr).
- Cause
- UAP-based installation starts. rrr indicates the full package ID.
Completed installation (nn).
- Cause
- Installation is completed. nn indicates the return code.
Starting the end-linked file (ccc).
- Cause
- The end-linked UAP starts. ccc indicates the end-linked UAP name.
Closed the end-linked file (nn).
- Cause
- The end-linked UAP is completed. nn indicates the return code.
The -d option is specified incorrectly.
- Cause
- The date specified in the startup option of the installation command for the specified date (rdsupt) is incorrect.
- Action
- Specify a correct date and then reactivate the command.
The -t option is specified incorrectly.
- Cause
- The time specified in the startup option of the installation command for the specified date (rdsupt) is incorrect.
- Action
- Specify a correct time and then reactivate the command.
The option is specified incorrectly.
- Cause
- The specified command option is incorrect.
- Action
- Specify a correct option and then reactivate the command.
A command for generator tools has already started.
- Cause
- A command for the generator tools has already started.
- This message is output if the command for installation on a specified date (rdsupt) is started or has been started while installing packages by distribution.
- Action
- Wait for the processing of the generator tools being started to complete, then retry.
This is an invalid generator method (fff/mm).
- Cause
- The installation method specified at distribution is incorrect.
- fff: Function name
- mm: Sub-return code
- Action
- Specify a correct installation method when creating the distribution job and then retry distribution.
An error occurred in the cccc command (fff/nn/sss/mm).
- Cause
- An error occurred in the cccc command.
- fff: Function name
- nn: Return code
- sss: Sub-function name
- mm: Sub-return code
- Action
- Retry distribution. If the problem recurs, check the log to determine the cause of the error. If you cannot determine the cause of the error, contact the system administrator.
Accessing a job file generated an error (sss/nn).
- Cause
- A job file access error occurred.
- sss: Sub-function name
- nn: Return code
- Action
- Check if the disk with the directory for installation-scheduled packages failed and then retry distribution. If the problem recurs, check the log to determine the cause of the error. If you cannot determine the cause of the error, contact the system administrator.
Accessing an event log file generated an I/O error (ccc/ee).
- Cause
- An event log file access error occurred.
- ccc: Function code
- ee: Event log error code
- Action
- Check whether the event server of JP1/Base is running, and whether the environment settings are correct.
- If there is no need to output log information for the generator tools to the event log, change the value of EvntlogLevel in the environment settings file to 0, to prevent the event log from being output. For details, see 6.5 Creating the settings file (environment settings file) for the generator tools in PART 2.
Accessing a syslog file generated an I/O error (nn).
- Cause
- A syslog file access error has occurred.
- nn: Return code
- Action
- Check whether the syslogd is running. If there is no need to output log information for the generator tools to the system log, change the environment settings of generator tools (set the environment variable SystemLogOutputLevel to 0) to prevent the system log from being output. For details, see 6.5 Creating the settings file (environment settings file) for the generator tools in PART 2.
Accessing a log file generated an I/O error (sss/nn).
- Cause
- A log file access error occurred.
- sss: Sub-function name
- nn: Return code
- Action
- Check that you have the output privilege to the destination directory of the log file and that the destination disk is normal. Then retry distribution. If the problem recurs, check the log to determine the cause of the error. If you cannot determine the cause of the error, contact the system administrator.
A log file parameter error occurred (ppp).
- Cause
- A log file parameter error occurred.
- ppp: Log file output parameter
- Action
- Retry distribution. If the problem recurs, check the log to determine the cause of the error. If you cannot determine the cause of the error, contact the system administrator.
Waiting time for exclusive conflict is over. Another generator tools process is executing.
- Cause
- A command lock error occurred.
- Action
- If the status of distribution jobs displays Installation Failed, retry distribution. To change the wait time to prevent a command lock conflict, change the environment settings of the generator tools. (Use the CommandWait environment variable to set the wait time to prevent a command lock conflict. For details, see 6.5 Creating the settings file (environment settings file) for the generator tools in PART 2.
Starting a linkage file (ccc).
- Cause
- A linkage file starts. ccc indicates the linkage file name.
Starting a UAP process (ccc) used for installation.
- Cause
- A UAP used for installation starts. ccc indicates the name of a UAP for installation.
Completed the processing of a linkage file (nn).
- Cause
- Processing of a linkage file is completed. nn indicates the return code.
Completed the processing of a UAP used for installation (nn).
- Cause
- Processing of a UAP used for installation is completed. nn indicates the return code.
The specified command was stopped (time over) (nn:ccc).
- Cause
- The ccc command (a linkage file, a UAP used for installation or an end-linked UAP) did not terminate when the monitoring time elapsed.
- nn: Monitoring time
- Action
- Determine the cause of the error and take action against the error. Then retry distribution. Alternatively, set the value larger for the monitoring time, re-package the resources and then re-distribute them. Otherwise, set the GF_WatchTimer environment variable of the generator tools to OFF (monitoring the UAP run time is not done) and then retry distribution.
The specified command does not exist (ccc).
- Cause
- There is no ccc command (a linkage file, a UAP used for installation or an end-linked UAP).
- Action
- Check if the command exists or if its name is correct and take action against it. Then retry distribution.
Could not start the specified command (fff/nn)
- Cause
- An error occurred in the specified command (a linkage file, a UAP used for installation or an end-linked UAP) startup process.
- fff: Function name
- nn: Return code
- Action
- Check the error contents and check if the contents of the command are correct. Take action to fix the trouble and then retry distribution. If the error recurs or if you cannot determine the cause of the error, contact the system administrator.
Starting to delete package of installation-date-installation (rrr/yyy).
- Cause
- Deletion of an installation-date-installation package starts.
- rrr: Package ID
- yyy: Job number
Completed the delete process (nn).
- Cause
- Completed the deletion. nn indicates the return code.
The environmental variable vvv is invalid (ccc).
- Cause
- The value of the environment variable is incorrect.
- vvv: Environmental variable
- ccc: Function code
- Action
- Correct the cause of the error and then retry distribution. The causes may be either:
- The directory that does not exist is specified.
- A file exists in the specified directory.
The disk capacity became insufficient.
- Cause
- The disk does not have enough free space for installation.
- Action
- Obtain enough free space for the installation, then retry.
Failed in copy of resource (fff)
- Cause
- Failed to copy the package.
- fff: Path name of the resource file (User resource path shown in a relative path format)
- Action
- Correct the causes of the error and then retry distribution. The probable cause is:
- The software name, file name, or directory name registered as a package contains a blank.
All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.