|
> From: Joep Beckeringh > > How does %open behave strangely? I just did a little test (added two > procedures to a mainline program; one for opening and one for closing; > called the opening one in case of page up and the closing one in case of > page down; opened the file in the mainline when it was not open; stepped > through the whole thing in debug mode) and did not find anything strange. In V5R1, if you open the file using the mainline (NOT with USROPN), and then access the module through a procedure and test the %open BIF, it won't show as open. But if you subsequently try to open the file, it fails. I ran into this problem when I was moving from CALLB to CALLP. I haven't tested it lately, so I'm not sure if it hasn't been fixed somewhere along the line. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.