View previous topic :: View next topic |
Author |
Message |
sasubashri Beginner
Joined: 20 May 2003 Posts: 15 Topics: 7
|
Posted: Tue Aug 12, 2003 11:32 pm Post subject: File Status 93 |
|
|
A job abended in production because of open error on a VSAM file(File Status 93). The explanation says resource unavailable.
1) Is there a way to find out, to which JOB was this file allocated at that point of time?
2) If the file was not properly closed by some previous job/program is there a way to close it and then reopen it using a COBOL program. _________________ Thanks,
Subashri. |
|
Back to top |
|
|
Brian Beginner
Joined: 12 Aug 2003 Posts: 95 Topics: 6
|
Posted: Wed Aug 13, 2003 1:16 am Post subject: |
|
|
Try with a REGION=5M |
|
Back to top |
|
|
sasubashri Beginner
Joined: 20 May 2003 Posts: 15 Topics: 7
|
Posted: Wed Aug 13, 2003 1:28 am Post subject: |
|
|
Brian,
Thanx for ur reply.
This problem occured in production and it was solved by giving a temporary fix. The temporary fix included closing the VSAM file explicitly
and then rerunning the job. Now I am expected to find out the cause of the problem.
Can you please tell me why you are suggesting that it should be run with REGION=5M _________________ Thanks,
Subashri. |
|
Back to top |
|
|
Brian Beginner
Joined: 12 Aug 2003 Posts: 95 Topics: 6
|
Posted: Wed Aug 13, 2003 1:51 am Post subject: |
|
|
Sasu
Quote: | File Status 93 - NOT ENOUGH VIRTUAL STORAGE FOR VSAM TASK |
A region of 5M for that step might just fix this problem. If your VSAM file is really huge you can opt for additional buffer space.
//VSAM DD DSN=VSAM,DISP=SHR,AMP='BUFND=10,BUFNI=10' |
|
Back to top |
|
|
|
|