|
We had the same problem but it went away after we applied the latest cum package. On 20 Nov 2001 12:33 CST you wrote: > I recently upgraded to V5R1 and after a week of running under V5R1 we are > experiencing problems with open query. According to IBM I have the latest > PTFs for any area that might have an affect on open query. > Listed below is the job log of the error message. Can someone determine > what is wrong or have you had the same problem? > > *NONE Command 11/20/01 08:01:24 QCADRV > QSYS 0390 GLCQTBEX GGLEXEC 011F > Message . . . . : 13700 - OPNQRYF > FILE((GLLAMCUR)) FORMAT(*LIBL/GLFAMCUR > GLFAMCU2) QRYSLT('((AMSSG1 *GE > ''010'') *AND (AMSSG1 *LE ''010''))') > KEYFLD((1/AMBCUR) (1/AMPSEG) > (1/AMTBOR *ASCEND) (1/AMACNO)) MAPFLD((AMSSG1 > '%SST(AMACNO 01 03)') (AMSSG2 > '%SST(AMACNO 04 03)') (AMSSG3 '%SST(AMACNO 07 > 04)') (AMSSG4 '%SST(AMACNO 11 > 02)')) OPTIMIZE(*MINWAIT) > CPF9898 Escape 40 11/20/01 08:01:25 QQQSRVI1 > QSYS *STMT QQQOPTIM QSYS *STMT > From module . . . . . . . . : > QQQFNCHK > From procedure . . . . . . : > QQFUNCTIONCHECK > Statement . . . . . . . . . : 1210 > To module . . . . . . . . . : > QQQOPTIM > To procedure . . . . . . . : > QQQCTINK_LIST > Statement . . . . . . . . . : 29829 > Message . . . . : CTINK_List - > Invalid Parameters.. > Cause . . . . . : This message is > used by application programs as a general > escape message. > CPF4204 Escape 50 11/20/01 08:01:25 QQQQUERY > QSYS *STMT QQQQUERY QSYS *STMT > From module . . . . . . . . : > QQQQUERY > From procedure . . . . . . : STARFC > Statement . . . . . . . . . : 18746 > To module . . . . . . . . . : > QQQQUERY > To procedure . . . . . . . : > QQQQUERY > Statement . . . . . . . . . : 11349 > Message . . . . : Internal failure > occurred in query processor. > Cause . . . . . : A system failure > has occurred in the query processor > program. The query definition > template number is 1. Recovery . . . : See > the low-level messages. Correct > any errors and try your request again. If > the problem continues, report the > problem (ANZPRB command). > CPF3698 Information 00 11/20/01 08:01:25 QSCPUTR > QSYS 0045 QMHAPD QSYS 04E0 > Message . . . . : Dump output > directed to spooled file 1. > Cause . . . . . : Dump output is > being directed to a spooled file. > CEE9901 Escape 30 11/20/01 08:01:30 QLEAWI > QSYS *STMT QQQOPNQF QSYS 00A4 > From module . . . . . . . . : QLEDEH > From procedure . . . . . . : Q LE > leDefaultEh > Statement . . . . . . . . . : 234 > Message . . . . : Application > error. CPF4204 unmonitored by QQQQUERY at > statement 0000011349, instruction > X'0000'. > Cause . . . . . : The application > ended abnormally because an exception > occurred and was not handled. The > name of the program to which the > unhandled exception is sent is > QQQQUERY QQQQUERY QQQQUERY. The program was > stopped at the high-level language > statement number(s) 0000011349 at the > time the message was sent. If more > than one statement number is shown, the > program is an optimized ILE > program. Optimization does not allow a single > 5722SS1 V5R1M0 010525 Job Log > JCR 11/20/01 08:02:07 Page 4 > Job name . . . . . . . . . . : GLCQTBEX User . . . . . . : > THOLLING Number . . . . . . . . . . . : 423651 > Job description . . . . . . : GSJOBD Library . . . . . : > GXAEXEC > MSGID TYPE SEV DATE TIME FROM PGM > LIBRARY INST TO PGM LIBRARY INST > statement number to be determined. > If *N is shown as a value, it means the > real value was not available. > Recovery . . . : See the low level messages > previously listed to locate the > cause of the exception. Correct any errors, > and then try the request again. > CPA0701 Sender copy 99 11/20/01 08:01:30 QCLXERR > QSYS 00DA QCLXERR QSYS 00DA > Message . . . . : CPF9999 received > by GLCQTBEX at 13700. (C D I R) > Cause . . . . . : Control language > (CL) program GLCQTBEX in library GGLEXEC > detected an error at statement > number 13700. Message text for CPF9999 is: > Function check. CEE9901 unmonitored > by QQQOPNQF at statement *N, instruction > X'00A4'. Recovery . . . : This > inquiry message can be avoided by changing > the program. Monitor for the error > (MONMSG command) and perform error > recovery within the program. To > continue, choose a reply value. Possible > choices for replying to message . . > . . . . . . . . . . . . . : C -- > Cancel the CL program. D -- Dump > the CL program variables and cancel the CL > program. I -- Ignore the failing > command. R -- Try the failing command > again. > *NONE Reply 11/20/01 08:02:04 QMHSCLVL > QSYS 05C8 QCLXERR QSYS 00E7 > Message . . . . : C > CPF9999 Escape 40 11/20/01 08:01:30 QMHUNMSG > *N XARAJMGR GXAEXEC 01FE > Message . . . . : Function check. > CEE9901 unmonitored by QQQOPNQF at > statement *N, instruction X'00A4'. > Cause . . . . . : An escape > exception message was sent to a program which > did not monitor for that message. > The full name of the program to which the > unmonitored message was sent is > QQQOPNQF . At the time the message was sent > the program was stopped at higher > level language statement number(s) *N. If > more than one statement number is > shown, the program was a bound program. > Optimization does not allow a > single statement number to be determined. If > *N is shown as a value, it means > the actual value was not available. > Recovery . . . : See the low > level messages previously listed to locate > the cause of the function check. > Correct any errors, and then try the > request again. > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > 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.