|
View previous topic :: View next topic
|
| Author |
Message |
blayek
New User
Joined: 04 Nov 2016
Posts: 5
Location: USA
|
|
|
|
Hi, I am working on a project where we need to replace all the VSAM and IAM files to VSAM RLS for better higher availability. But while converting the IAMRLS files to VSAM RLS, we are not getting the performance we are expecting. While triggering a transaction to delete all old records from a file it's taking way longer than IAM RLS. While analyzing the Omegamon report I can see below are taking more time :
Journal(MVS Logger) I/O wait Time --- 54%
RLS Wait Time ---- 45%
These two are consuming almost 90% of total execution time. Any guidance on how to reduce this time would be highly appreciated. Thank you very much. |
|
| Back to top |
|
 |
John Gay
New User
Joined: 10 Apr 2017
Posts: 1
Location: United States
|
|
|
|
Maybe due to IAM not being a true VSAM file?
Check out the IAM manual, I believe IAM has it's own RLS.
G/L
John |
|
| Back to top |
|
|
Nic Clouston
Global Moderator
Joined: 10 May 2007
Posts: 2455
Location: Hampshire, UK
|
|
|
|
| No reference to CICS - moving to JCL & VSAM |
|
| Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009
Posts: 582
Location: London
|
|
|
|
| Maybe your Coupling Facility Structure isn't large enough if it wasn't resized to cater for all the extra RLS datasets |
|
| Back to top |
|
|
|
|
