IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

What is EXCP in VSAM


IBM Mainframe Forums -> DFSORT/ICETOOL
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
muthuvel

Active User


Joined: 29 Nov 2005
Posts: 217
Location: Canada

PostPosted: Wed Mar 01, 2006 2:57 pm
Reply with quote

What is an EXCP?in what way it is related to the performance of a VSAM file?
Back to top
View user's profile Send private message
DavidatK

Active Member


Joined: 22 Nov 2005
Posts: 700
Location: Troy, Michigan USA

PostPosted: Wed Mar 01, 2006 8:46 pm
Reply with quote

muthuvel,

EXCP is 'EXecute Channel Program' and gives an indication of the number of I/Os that are happening.

The lower the EXCP count, the lower the number of I/Os and the faster the program will run. For the same amount of data being processed a lower EXCP count means that larger buffers arer being read/written, and for VSAM, maybe the fewer times the program is having to go to DASD to access indexes, The more index space the fewer I/Os.

Dave
Back to top
View user's profile Send private message
muthuvel

Active User


Joined: 29 Nov 2005
Posts: 217
Location: Canada

PostPosted: Thu Mar 02, 2006 3:07 pm
Reply with quote

Hi,

Thanks for the information.

And may i know how to write an effective code so that the EXCP's are minimal in an VSAM operation.
Back to top
View user's profile Send private message
DavidatK

Active Member


Joined: 22 Nov 2005
Posts: 700
Location: Troy, Michigan USA

PostPosted: Fri Mar 03, 2006 1:10 am
Reply with quote

There are a couple of programming considerations when accessing VSAM files depending upon how large the VSAM file is and how many accesses are anticipated.

First, you should random access the VSAM file in Key Order, if possible. This means that you should sort, say, an input file in the Key Order of the VSAM file. This means, that when you read a record from the VSAM file, chances are better that the Key you?re accessing will still be in the index stored in memory.

Second, if you?re accessing a large % of the VSAM file, you may find it more effective to sequentially access the file.

This is about the only things I can think of right off that you can do inside the program.

There are a couple of things you can do about the environment your running in.

In the JCL, you can use:

Code:

//FDNAME DD  SUBSYS=(BLSR,'DDNAME=BLSRXX','MSG=I') 
//BLSRXX DD  DSN=YOUR.VSAM.FILE,                 
//             DISP=SHR                                 


Using the BLSR subsystem, effectively copies the entire VSAM file into memory, so that after the initial load, there will be minimal I/Os. This should only be used when you anticipate a large number of accesses.

Also having your Systems Programmer do some tuning will also help.


Dave
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> DFSORT/ICETOOL

 


Similar Topics
Topic Forum Replies
No new posts Access to non cataloged VSAM file JCL & VSAM 18
No new posts Merge two VSAM KSDS files into third ... JCL & VSAM 6
No new posts CVDA value for RRDS VSAM dataset. CICS 2
No new posts VSAM return code 23 - for a Random read COBOL Programming 4
No new posts Open VSAM File in IMS DC Region - DFS... IMS DB/DC 0
Search our Forums:

Back to Top