Comments on: OVRDBF SHARE(*YES) http://itknowledgeexchange.techtarget.com/itanswers/ovrdbf-shareyes/ Wed, 19 Jun 2013 19:19:38 +0000 hourly 1 By: beanbaggs http://itknowledgeexchange.techtarget.com/itanswers/ovrdbf-shareyes/#comment-86766 beanbaggs Wed, 19 Jan 2011 13:06:54 +0000 #comment-86766 Yes talking about the FD level both programs have the program defined. So it did switch in the “PROGRAMA” which makes sense. Thanks for input.

]]> By: tomliotta http://itknowledgeexchange.techtarget.com/itanswers/ovrdbf-shareyes/#comment-86654 tomliotta Tue, 18 Jan 2011 00:30:08 +0000 #comment-86654 …because of the READ NEXT…

COBOL provides a kind of access to the file buffers. If you aren’t using the READ {NEXT} INTO format, you could be seeing buffer values.

READ … INTO copies into WORKING STORAGE. A READ without the INTO clause should simply increment the pointer to the buffer to access the next record. (There may be no data movement at all.)

I haven’t actually tried what you’re asking, but it might make sense for COBOL. A shared ODP will share the file pointer. That is, OVRDBF SHARE(*YES) allows multiple programs to use the same file pointer.

If access is through the FD record entry rather than through a WORKING STORAGE copy, I wouldn’t be surprised if field values seemed to change. What actually changed would be the address that the field pointed to.

Tom

]]> By: beanbaggs http://itknowledgeexchange.techtarget.com/itanswers/ovrdbf-shareyes/#comment-86633 beanbaggs Mon, 17 Jan 2011 15:28:16 +0000 #comment-86633 I think I have answered my own question as in both “PROGRAMA” and “PROGRAMB” the “FIELDA” of “FILEA” would be setting at “Y” now because of the READ NEXT in “PROGRAMB”.

]]>