RE: CICS VSAM File Access Techniques

New Message Reply Date view Thread view Subject view Author view Other groups

Subject: RE: CICS VSAM File Access Techniques
From: Dodds, Jim (jim.dodds@kysu.edu)
Date: Wed Nov 11 2009 - 12:16:24 EST


That is the way I have had to do it in the past also. 

 

Jim Dodds

Systems Programmer

Kentucky State University

400 East Main Street

Frankfort, Ky 40601

502 597 6114

 

From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf
Of industrynews@winwholesale.com
Sent: Wednesday, November 11, 2009 12:07 PM
To: VSE Discussion List
Subject: CICS VSAM File Access Techniques

 

        When you have a multi-part key, where the last part of the key
is some kind of sequence field, I've found that I can easily go directly
to the last record in the file but I cannot (so easily) go directly to
the last record in a given sequence of records.  Is this at all
possible?  Meaning... 

        To go directly to the last record in the file requires a
completely high-value key and a STARTBR EQUAL (which results in
EIBRESP=0) followed by a READPREV which succeeds in retrieving the last
record in the file. 

        To go directly to the last record in a given sequence of
records, I tried setting the first part of the key to the value for the
desired group of records and setting the sequence field to high-values.
However, in this case, the STARTBR EQUAL results in NOTFND (EIBRESP=13)
and the READPREV, of course, then results in INVREQ (EIBRESP=16). 

        Am I forced, in this case, to set the first part of the key to
the value for the desired group of records, set the sequence field to
all 9's, and then use STARTBR GTEQ followed by READNEXT and two
READPREV?  ...and, then, have to have a special case if I hit the end of
file on the READNEXT? 

        Anybody follow all that? 

Sincerely,

Dave Clark

WinWholesale Group Services
3110 Kettering Boulevard
Dayton, Ohio  45439  USA
(937) 294-5331


This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary
information. If you have received this message in error, please
immediately notify the sender and delete and destroy the message and all
copies. All unauthorized direct or indirect use or disclosure of this
message is strictly prohibited. No right to confidentiality or privilege
is waived or lost by any error in transmission. 


New Message Reply Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b25 : Tue Nov 24 2009 - 16:05:07 EST