|
View previous topic :: View next topic
|
| Author |
Message |
iliganon
New User
Joined: 09 Jun 2010
Posts: 4
Location: Philippines
|
|
|
|
Hi!
I have this problem when doing a browse on a VSAM KSDS.
In STARTBR and READNEXT, the same RIDFLD and KEYLENGTH are used (obviously). I used the GENERIC and EQUAL options in STARTBR. When all the records containing the RIDFLD are read in READNEXT, the RIDFLD value changes, and the file is read until EOF.
I was assuming that if all the records containing the RIDFLD are browsed/read, a NOTFND condition will occur. Instead, it continues to read the next record in the file until the ENDFILE condition occurs. I saw this using CEDF and noticed that the RIDFLD value changed.
Is this normal during READNEXT? |
|
| Back to top |
|
 |
Binop B
Active User
Joined: 18 Jun 2009
Posts: 407
Location: Nashville, TN
|
|
|
|
Hi iliganon,
Welcoming you the forum ...
Giving below a snapshot of the Manuals ... Hope this clears your doubt ...
| Quote: |
RIDFLD(data-area)
....
Even if the browse is generic, this field should always be large enough to accommodate the complete record identifier. This is because, on completion of the READNEXT command, the field is updated by CICS with the complete identification of the record retrieved. |
|
|
| Back to top |
|
|
CICS Guy
Senior Member
Joined: 18 Jul 2007
Posts: 2146
Location: At my coffee table
|
|
|
|
| iliganon wrote: |
I was assuming that if all the records containing the RIDFLD are browsed/read, a NOTFND condition will occur. Instead, it continues to read the next record in the file until the ENDFILE condition occurs. I saw this using CEDF and noticed that the RIDFLD value changed.
Is this normal during READNEXT? |
Yes, it is normal.
The STARTBR only establishes a starting point for the READNEXT, it does not limit the range of the READNEXT. |
|
| Back to top |
|
|
iliganon
New User
Joined: 09 Jun 2010
Posts: 4
Location: Philippines
|
|
|
|
Thanks guys!  |
|
| Back to top |
|
|
|
|
