I'll try to make changes to have only one active STARTBR, but keep in mind that ENDBR has no parameter that ties itself to a particular STARBR. This means that if you follow the logic, then an ENDBR would release (potentially) hundreds of strings, of which only one is immediately available to the impending READNEXT/READPREV, which also has no parameter that ties itself to a particular STARTBR.
The logic doesn't really make sense. What would the underlying strings be doing other than "being unreachable/being unusable"? David Logan -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Chase, John Sent: Tuesday, February 05, 2008 9:37 AM To: [email protected] Subject: Re: Technical questions about CICS STARTBR and ENDBR > -----Original Message----- > From: IBM Mainframe Discussion List On Behalf Of David Logan > > <...snip...> > Doesn't each STARTBR tie up a VSAM string on the file? > > Probably, but wouldn't it only be one string per *FILE*? So I > would only tie up seven or so, even if I did issue hundreds > of STARTBR? No, it's one string per STARTBR. VSAM has to maintain a "current record pointer" for each browse, in anticipation of a READNEXT or READPREV, so the string is "occupied" until the browse is ended. -jc- ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
