Hi,
I am having a problem with a sequence job that is controlling another 8 sequence jobs.
If we run the individual sequence job,we didn't receive any error.
But when we run the main sequence job,some child sequence jobs got aborted and received the error message
saying:
(DSGetJobInfo) Failed to open RT_STATUS538 file.
Could anyone explain what the cause of this error may be and whether there is any way to avoid it.
Thanks,
MK
Failed to open RT_STATUS538 file
Moderators: chulett, rschirm, roy
Another guess.
There's more to the error message, perhaps even an error -14 buried somewhere. Things run fine individually because you are not taxing your system. All at once, there is too much going on and there aren't enough resources available to support them running at the same time.
You may also need to adjust some configurables like T30FILE or MFILE and the like.
Post complete error messages.
![Wink :wink:](./images/smilies/icon_wink.gif)
There's more to the error message, perhaps even an error -14 buried somewhere. Things run fine individually because you are not taxing your system. All at once, there is too much going on and there aren't enough resources available to support them running at the same time.
You may also need to adjust some configurables like T30FILE or MFILE and the like.
Post complete error messages.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Another possibility is that the job was created and compiled by someone else whose umask setting and group membership was such that you don't have permission to open the RT_STATUS538 file.
This is less likely, but may need to be considered as a possibility.
This is less likely, but may need to be considered as a possibility.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.