AWSBDX - Jobtable access messages
This section lists jobtable access error and warning messages that might be issued.
The message component code is BDX.
AWSBDX001E Jobman has found a problem with its internal job table. See the message help for details.
Explanation
This message can be provoked by two different situations:
- Jobman expected to find an entry for a running job in its internal job table, but there are no more entries to be read (end-of-table encountered). This is an internal error.
- Jobman tried to add a new job to the job table, but the table is full. There are too many jobs running, The maximum is determined by the jm job table size parameter in the localopts file.
System action
Jobman continues, but the job that it is trying to manage is ignored (it might be run later when the number of running jobs has reduced).
Operator response
Check how many jobs are running using the operating system tools. If you have reached the maximum indicated in the localopts file, you must either explicitly stop an existing job, or wait for jobs to finish as normal, before you can run any new jobs. If you believe that the maximum number of jobs is likely to be exceeded on other occasions, you might want to consider increasing the value of the jm job table size parameter (if you make any changes, you have to stop and restart jobman for them to take effect).
If you have not reached the maximum number of jobs, this is an internal error; search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDX002E You or jobman tried to perform an action on a job that is either not running or is not within jobman's internal job table. Probably the job has terminated. If it is still running, an internal error has occurred. The action that cannot be performed is the following: "action_number".
Explanation
action_number is a number indicating the action that was being performed when the error occurred:
- 1 = open
- 2 = read
- 3 = add
- 4 = update
- 5 = delete
- 6 = lock
- 7 = unlock
- 8 = write
System action
Jobman continues, but the action that you or jobman were trying to perform is ignored.
Operator response
Verify if the job in question is running, using the operating system tools. If it is, try to perform your action manually, for example using a shell command.
If it is not running, and you expected it to be, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDX003E Jobtable - Attempt to add duplicate entry !1.
AWSBDX004E Jobman could not open the jobtable file. The operating system error is: "error_message".
Explanation
The following are the two most commonly occurring possibilities:
- The maximum size of the jobtable (maximum number of entries, as defined in the option jm job table size in the localopts file), is set to 0.
- Jobman could not find an existing jobtable file.
error_message is a system error message, giving more details about the cause of the error.
System action
Jobman stops.
Operator response
Verify if the option jm job table size in the localopts file is equal to 0. If it is 0, change the value to a positive integer value, for example 1024.
If the jm job table size option is already a positive integer, an existing jobtable file was not found. Use the error_message to determine why the file could not be opened. Also search in the log file for entries that indicate that Jobman failed to create the file or had some other problem with the file. When you have identified the cause of the problem, rerun jobman by running the start command for the workstation.
AWSBDX005E Jobman received the following operating system error while handling the jobtable file: "error_number".
Explanation
The system calls that can fail are: lock, fcntl, open, write, lseek, and read. error_number is the operating system error number, which indicates what problem was encountered.
System action
Jobman stops.
Operator response
Resolve the problem indicated in the operating system error message.
Check the file system of <TWS_home> to ensure that there is sufficient space, and that the user has write permission. If jobman has stopped, when you have resolved the problem, rerun jobman.
If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDX006E Jobtable - MPE system error !1.
AWSBDX007E Jobman cannot add a new entry to the job table because the job does not have a valid job number.
Explanation
This is an internal error.
System action
Jobman continues, but the job in question is not run.
Operator response
Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDX008E Jobman tried to perform the action "action_number" but the job table is not locked. This is an internal error.
Explanation
action_number is a number indicating the action that was being performed when the error occurred:
- 1 = open
- 2 = read
- 3 = add
- 4 = update
- 5 = delete
- 6 = lock
- 7 = unlock
- 8 = write
System action
The action is not performed. Jobmon could not be correctly initialized. Jobman might stop.
Operator response
This is an internal error. Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.