Got a really weird one here.

Given a rather complex SQL view, with three sub-views UNION ALL'd together, which was created on a V6 box, and then restored from a save file on a V7 box.

If we use our QuestView utility (native Record Level Access, called from OPM MI) to look at this view, on a V6 box, it works just fine, I can step through the file at will, and these messages appear in the joblog:

Arrival sequence ignored for member FOO. Open of member FOO changed to SEQONLY(*YES). Open of member FOO changed to SEQONLY(*YES). Buffer length longer than record for member FOO.
Open of member FOO changed to SEQONLY(*YES).

All well and good. But on the V7 box (and remember, this view was created under V6, and retrieved from a save file), QuestView craps out, and I get this in the joblog:

Arrival sequence ignored for member FOO. Operation for program device or member FOO, file FOO in library FROBOZZ is not valid. I/O is not allowed because the program device or member FOO file FOO in library FROBOZZ is in error. Error message received by QuestView. See messages in job log for details

I immediately noticed the "SEQONLY" message is absent (I tried an OVRDBF with SDQONLY(*YES), and there was no change in the result).

The "Operation . . . is not valid" message is a CPF5149, sent from QDBSIGEX to QuestView's master MI program, at an instruction that calls the RLA runtime to do the equivalent of an RPG SETLL (by RRN).

The "I/O is not allowed . . . " message is a CPF5129, sent from QDMIFERR to the master MI program, at an instruction that calls the RLA runtime to do the equivalent of an RPG READ (again, by RRN).

Can anybody here shed any light on this?

--
James H. H. Lampert

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].