AWSDEC - Events file messages
This section lists events file error and warning messages that might be issued.
The message component code is DEC.
AWSDEC001E
File system error !1 on events file.
AWSDEC002E
An internal error has occurred. The following UNIX system error occurred on an events file: "error_number" at line = "line".
See message.
line is the line number of the events file that was being processed when the error occurred.
error_number is the number that identifies the system error; it can supply you for more information about error causes.
This message is generated by a library function that is called by more than one program. The calling program decides how to process the error that this message has revealed. Look in the log for other messages following this one to see how HCL Workload Automation reacts.
Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSDEC004E
IPC error !1 on events file.
AWSDEC005E
DB error !1 on events file.
AWSDEC006E
The program was unable to allocate an internal data structure area (comarea).
This is probably an operating system error returned by the library function 'malloc'.
This message is generated by a library function that is called by more than one program. The calling program decides how to process the error that this message has revealed. Look in the log for other messages following this one to see how HCL Workload Automation reacts.
Check the following:
- Verify if the workstation has enough memory available. Information about the memory requirements of HCL Workload Automation is provided in the Release Notes. If not, you might need to increase the memory of the workstation or make changes in memory management and paging to make more memory available to the program. Rerun the program.
- If the workstation memory is adequate, try closing all the applications that you do not need, and then rerun the program.
- If the problem persists, reboot the workstation, and then rerun the program.
- If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSDEC008E
An event file was created by a newer version of HCL Workload Automation than this version, and is not compatible.
See message.
This message is generated by a library function that is called by more than one program. The calling program decides how to process the error that this message has revealed. Look in the log for other messages following this one to see how HCL Workload Automation reacts.
Take the following steps:
- Remove all existing event files
- Restart HCL Workload Automation. The event files are recreated, but with the current version.
AWSDEC009E
An event file cannot be opened because it has been already opened by another process.
See message.
This message is generated by a library function that is called by more than one program. The calling program decides how to process the error that this message has revealed. Look in the log for other messages following this one to see how HCL Workload Automation reacts.
Use the operating system tools to determine which process is locking the event file. Wait for that process to finish. You might decide to stop that process immediately, but you must ensure that it is safe to do so. Restart the process that was prevented from running. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSDEC010E
An internal error has occurred. The open access mode is not valid: "access_mode".
See message.access_mode is a number that identifies the type of access.
This message is generated by a library function that is called by more than one program. The calling program decides how to process the error that this message has revealed. Look in the log for other messages following this one to see how HCL Workload Automation reacts.
Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSDEC011W
The time-out interval for messages arriving in an event file has elapsed.
This message is generated by a library function that is called by more than one program. The time-out value is passed to the function by the calling program, and can be a positive number of seconds (between 2 and 10, depending on the program), 0 (do not wait), or a negative number (wait until a response is received.
The calling program decides how to process the condition that this message has revealed. Look in the log for other messages following this one to see how HCL Workload Automation reacts.
No action required.
AWSDEC012E
An internal error has occurred. The internal data structure area (comarea) for event file processing could not be initialized.
See message.
This message is generated by a library function that is called by more than one program. The calling program decides how to process the error that this message has revealed. Look in the log for other messages following this one to see how HCL Workload Automation reacts.
Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSDEC014E
The event file or the directory containing the event file does not exist or cannot be found.
See message.
This message is generated by a library function that is called by more than one program. The calling program decides how to process the error that this message has revealed. Look in the log for other messages following this one to see how HCL Workload Automation reacts.
Verify that the HCL Workload Automation user has the correct permissions to access the HCL Workload Automation home directory. If not, add these permissions.
If the permissions are correct, verify that the HCL Workload Automation user has the correct permissions to access the file. If not, add these permissions.
Restart HCL Workload Automation to recreate the event file.
AWSDEC015E
An internal error has occurred. The length ("record_length") of a record read from or written to the event file is not correct.
The program is trying to read or write record_length bytes of an event file but record_length is not a valid integer because it is less than zero. record_length takes the value from sizeof().
This message is generated by a library function that is called by more than one program. The calling program decides how to process the error that this message has revealed. Look in the log for other messages following this one to see how HCL Workload Automation reacts.
Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSDEC018E
An internal error occurred while attempting to compact the file "event_file". The file is unusable.
See message.
event_file is the file being processed that gave an error.
This message is generated by a library function that is called by more than one program. The calling program decides how to process the error that this message has revealed. Look in the log for other messages following this one to see how HCL Workload Automation reacts.
The indicated file is corrupt.
Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSDEC019W
The supplied maximum size of the file "event_file" is "max_size" bytes, which is too small. A higher value will be allocated.
See message.
event_file is the file that will be allocated a larger maximum size than the stored value.
You need take no action, but you might decide to change the maximum size to a value of your choice with the evtsize tool.
AWSDEC020W
The maximum size of the file "event_file" has been changed to "max_size" bytes.
See message.
event_file is the file that has been allocated the indicated maximum size.
You need take no action, but you might decide to change the maximum size to a value of your choice with the evtsize tool.
AWSDEC100E
An internal error has occurred. While processing an event file an error ("error_number") of type ("error_type") occurred.
See message.
error_number is the operating system error number.
error_type is the type of error.
This message is generated by a library function that is called by more than one program. The calling program decides how to process the error that this message has revealed. Look in the log for other messages following this one to see how HCL Workload Automation reacts.
Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.