Hi Doreen
You don't supply the query - so its not easy to determine the cause
Any way - this is strictly a guess - however you are calculating the dates, look at downloading idate and use that instead
Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
'If you're going through hell, keep going.'
Winston Churchill
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of doreen.boyle@xxxxxxx
Sent: Tuesday, May 12, 2020 1:48 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: [EXTERNAL] 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
  ******************************************
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: 
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at 
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: 
https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.