View previous topic :: View next topic
|
Author |
Message |
tjk3030
New User
Joined: 18 Mar 2006 Posts: 22
|
|
|
|
Hello All
I wrote an easytrieve routine to update a VSAM file. Its just one step in a multi step job & only updates one record, the record is small approx 100 characters. The problem is that it appears easytrieve is 'hanging' on to the file during the entire run of the job, not releasing it for other jobs that use the exact same routine to update the same vsam file. It wasn't a problem when only a couple of quick running jobs updated the file but now I have hundreds, some of the jobs run for hours, and having contention problems all the time.
I stumped as to what to do. Is this an easytrieve thing? Should I rewrite the routine in COBOL?
Thanks |
|
Back to top |
|
|
murmohk1
Senior Member
Joined: 29 Jun 2006 Posts: 1436 Location: Bangalore,India
|
|
|
|
tjk3030,
Quote: |
The problem is that it appears easytrieve is 'hanging' on to the file during the entire run of the job, not releasing it for other jobs that use the exact same routine to update the same vsam file |
What is DISP used for VSAM? |
|
Back to top |
|
|
socker_dad
Active User
Joined: 05 Dec 2006 Posts: 177 Location: Seattle, WA
|
|
|
|
Yes. Rewrite in COBOL.
Easytrieve CAN update VSAM files, it is extremely inefficient to use it thus (as you have seen). |
|
Back to top |
|
|
|