|
Hi, Krish
HTH Vern
Thanks, we were able to get around this by creating a file with a format that includes only the field definitions that we plan to access from the given query
I will need to try your suggestion of converting the query . Is there an easy technique of converting programs using queries to SQL ?
On Wed, 8 Dec 2004 11:27:01 -0600, Elvis Budimlic <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > Looks like field MQT_DEFINITION is a DBCLOB that is rather large in size. > Perhaps your V4R4 can't handle DBCLOB's? > I recommend a rewrite using SQL, as SQL can handle DBCLOBs for sure. > > > > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Krish Thirumalai > Sent: Wednesday, December 08, 2004 11:02 AM > To: Midrange Systems Technical Discussion > Subject: Issue with SYSTABLES in V5R3 and OPNQRYF > > We are having a strange error, during a test on V5R3 with the > SYSTABLES file. Any suggestions are welcome,. > > We are using old code that worked fine on V4R4. The client is testing on > V5R3 > > Message . . . . : Shared open of member SYSTABLES failed. > Cause . . . . . : The shared open of member SYSTABLES file SYSTABLES in > library QSYS2 failed because of error code 6. > 6 -- The process large object fields specified in the program is not > consistent with > the value specified for the original open. > > The code looks like this: > > CHGVAR VAR(&QRYSLT) VALUE('TYPE="P" *AND WKFCHR="W" + > *AND SYS_DNAME="' *TCAT &DTALIB *CAT '"') > OVRDBF FILE(SYSTABLES) LVLCHK(*NO) SHARE(*YES) > OPNQRYF FILE((SYSTABLES)) QRYSLT(&QRYSLT) + > MAPFLD((WKFCHR '%SST(SYS_TNAME 6 1)')) > > * READ THRU OUTFILE & RMV ALL MBRS FOR WORK FILES */ > > READ: RCVF > > The RCVF is where the error occurs. > > Thanks > > Krish > -- > > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.