× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



The message seems to point directly to an invalid date, time, or timestamp value in table QTEMP.OOBSPN record number 1537. Have you looked at that row? I imagine it should be a simple matter of finding how the bogus value got there and either fixing it or trapping for it.

HTH



-----Original Message-----
From: doreen.boyle@xxxxxxx [mailto:doreen.boyle@xxxxxxx]
Sent: Tuesday, May 12, 2020 12:48 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Query Error

There is a CL job that runs on the Power 8 V7R3. It calls a query that produces a report. The job blows up when it tries to run the query with the errors below. Value in date, time or timestamp not valid. I'm not
sure how to resolve. The CL and query are kind of lengthy so I didn't
post. I can if required.


Message ID . . . . . . : CPA0701 Severity . . . . . . . : 99
Message type . . . . . : Inquiry
Date sent . . . . . . : 05/12/20 Time sent . . . . . . : 02:11:52


Message . . . . : QWM2701 received by OOBS at 380. (C D I R) This
calls a query
Cause . . . . . : Control language (CL) program OOBS in library QGPL
detected an error at statement number 380. Message text for QWM2701 is:

STRQMQRY command failed.

To procedure . . . . . . . : SEND_MESSAGE
Statement . . . . . . . . . : 4311
Message . . . . : Select/omit error on member OOBSPN.
Cause . . . . . : A select/omit error occurred on member OOBSPN file
OOBSPN
in library QTEMP because the fields in record number 1537, record format

*FIRST, member number 1 have one of the following problems: -- A field

contains decimal data that is not valid. -- A field contains floating point
data that is not valid. -- A field contains DBCS data that is not valid.
--
A field contains date, time, or timestamp data that is not valid.

Statement . . . . . . . . . : 28
Message . . . . : RUN QUERY command failed with SQLCODE -181.
Cause . . . . . : The SQLCODE is -181. The SQLSTATE is 22007. The DB2
for
IBM i SQL message text for this error is: Value in date, time, or timestamp
string not valid. Recovery . . . : Check the job log for more
information, correct the error and try the request again.



Doreen Boyle - I.T. Systems Specialist
Ohio Valley Flooring
Office: 513 527-9593
Cell: 513 356-6802
doreen.boyle@xxxxxxx
******************************************



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.