Data Conversion Errors

Robert J.M. Edis robert.edis@creatcomp.com
Fri, 7 Jul 2000 10:51:02 -0400


G'day Stewart

I agree with Ole, we need to see ALL the data in your set to identify the
source of the DCEs.  The most common cause of DCEs in a situation like this
is the data itself, not the program or the software.

Regards,

Blue 

-----Original Message-----
From: Stuart J. Rosenboom
To: powerh-l@sphere.swau.edu
Cc: JimKnapp@parker.com
Sent: 7/7/00 3:01 AM
Subject: Data Conversion Errors 

Hello All,

Background:  I have been working on a project using PowerHouse version
8.19.C3 in MPE/ix Version C.55.06 environment.  In my programs a take a
6 digit date (YYMMDD) from a Zoned Numeric field, Convert it to a
character string, add the century then convert the resulting 8 character
date to numeric and store it in a DATE type variable.  This works fine
for record selection purposes when compares to other DATE Type variables
containing parameters received from user prompts.

I am now trying to use the same calculated date for record selections
based on the System date using the SYSDATE function.  When I do this I
get Data Conversion errors on the calculated dates.  The program
functions correctly (i.e.: the calculated date is correct) but, because
of the Data Conversion Errors, the program aborts my batch jobs when I
run it in a Batch job (I check for JCW <> 0 in my stream jobs for error
trapping purposes).

Here is a brief excerpt of the code I am having problems with:

ACCESS *H850SUB0  LINK PO TO EOU-REFERNO OF *EDI85HDI OPTIONAL &
    LINK EOU-REFERNO TO EOU-REFERNO OF *EDI85DTI OPTIONAL
;
DEFINE PO_DATE CHAR*6 = ASCII(HDR_PO_DATE OF EDI85HDI,6)
DEFINE CHR_PO_DATE CHAR*8 = PACK("20" +       &     ; Y3K Bug, Job
security!
    ASCII(HDR_PO_DATE OF EDI85HDI,6))
DEFINE TRANS_DATE DATE = NCONVERT(CHR_PO_DATE)
DEFINE CHR_PO_LINE CHAR*3 = ASCII(INTENTNO,3)
;
SELECT EDI85HDI IF TRANS_DATE = SYSDATE
SELECT EDI85DTI IF CHR_PO_LINE = EOU-DETAILSEQB
;
SELECT IF NOT(RECORD EDI85DTI EXISTS)
;
SORTED ON VNCODE ON PO ON POLINE

Here are the actual values being processed in the code segment above:

> FINAL FOOTING  SKIP 03   HDR_PO_DATE PO_DATE CHR_PO_DATE TRANS_DATE
SYSDATE
> GO

?

     706  000706  20000706  07/06/2000  07/06/2000



?

Records selected:  12
Lines printed:     16
Pages printed:     2

** Data conversion errors: 6

>

Has anyone seen this type of problem before?  Is there a possible Y2K
bug in PowerHouse?

Thanks in advance,
Stuart J. Rosenboom
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
This list is closed, thus to post to the list, you must be a subscriber.