Specifications

(S)
Checks again whether there is a process that has opened the file at the next execution interval. Establishment of the
file monitoring event job is delayed until the check finishes.
(O)
If this message appears repeatedly, check whether there is sufficient memory for executing the program, and then
try again to change the status of the file indicated in file-name.
KAVT2023-E
Memory became insufficient. (maintenance-information)
Memory became insufficient.
(S)
Checks whether the file status was updated again at the next execution interval. Alternatively, abnormally terminates
the job.
(O)
Check whether there is sufficient memory for execution.
Use JP1/AJS3 - View to check for a Monitoring Files job that terminated abnormally. If you find a Monitoring Files
job that terminated abnormally, re-register it.
KAVT2024-W
The file information could not be obtained. The file monitoring event may not have occurred. (file-name,
maintenance-information)
An attempt to acquire the status of the file to be monitored has failed.
(S)
The current status of the file to be monitored was unknown. The system checks the status again at the next execution
interval. Any change in the file status that is made before the next execution interval will not be detected.
(O)
Check the following:
• Check whether there are sufficient resources.
• Check whether the size of the file to be monitored is smaller than 2 gigabytes.
To monitor a file equal to or greater than 2 gigabytes, specify the large file support option.
• Make sure that the file to be monitored is not being updated.
If a change in the file status could not be detected, check the file status and then try again to change the status of the
file indicated in file-name.
KAVT2025-E
You cannot specify 10 for the file monitoring interval.
2. Messages
Job Management Partner 1/Automatic Job Management System 3 Messages 1
583