MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » June 1999

Re: Hex '00' to Hex '40'?



fixed


Bradley

        Three ideas here, first can you use a *LF as the SQL target so that
the fields they are specifying are the only ones in the view, and there by
take advantage of the "default values" in your *PF.   (While SQL and/or Data
Mirror allow you to use an *LF)

        Second, Can you put a Trigger on each *PF so that anyone doing Adds
gets checked for Validity not just the stuff coming over.

        Lastly, Make the Vendor fix their code !!  If you specified a file
format for them to write to then they should be populating the record based
on the files rules, enforced by a Trigger before,  an checked with a
Journal.

        JMS..

-----Original Message-----
From: Stone, Brad V (TC OASIS) <bvstone@taylorcorp.com>
To: 'MIDRANGE-L@midrange.com' <MIDRANGE-L@midrange.com>
Date: Tuesday, June 29, 1999 3:27 PM
Subject: RE: Hex '00' to Hex '40'?


>I wish it were this easy.  The fields are not nulls coming from the SQL
>server database when we are mirroring.. I dont know what they are.  The
>fields that they specify null in come across fine as x'40'.  The ones they
>don't come to us as hex'00'.
>
>Here's why I don't want to do this in my program.
>
>One the web page they made, you can select one of about 20 different item
>types.  For each item type, they set up a table (file).  For each file,
>there is one record for each order, including other type of information.
So
>a file looks like this.
>
>Item number
>Price
>Text1
>Text2
>Text3...
>Text20
>...
>
>So, not only do I have to check 20 files, but I have to check 30 or so
>fields in each file.  That's a lot of checking.
>
>Again, when they do specify null as a value in their SQL database, things
>work fine.  When they leave it blank, it comes across as x'00'.  I didn't
>set up the datamirror stuff, but it looks like I'll have to try and figure
>out what is going on.
>
>Thanks for all the suggestions.
>
>Bradley V. Stone
>Taylor Corporation - OASIS Programmer/Analyst
>bvstone@taylorcorp.com
>
>
>
>-----Original Message-----
>From: Howard Weatherly [mailto:hweatherly@dlis.dla.mil]
>Sent: Tuesday, June 29, 1999 11:04 AM
>To: MIDRANGE-L@midrange.com
>Subject: Re: Hex '00' to Hex '40'?
>
>
>Brad, Sorry about that last post, a Microsoft moment occured!
>
>Anyway to continue the x'00' is a null and you need to account for nulls in
>you
>programs:
>
> 2 WS-LAST-DIFF-SEQ-IND      PIC S9(04) BINARY VALUE ZERO.
>
>    EXEC SQL FETCH C1 INTO
>       :COPY-TABLE,
>       :LAST-DIFF-SEQUENCE   :WS-LAST-DIFF-SEQ-IND,
>        .
>        .
>In the code you check the indicator variable for a negative to know if the
>field
>is null.
>
>
>
>
>
>Stone, Brad V (TC OASIS) wrote:
>
>> This one is odd, but here we go.
>>
>> Our web guys developed a page to receive orders on the web.  We then use
>> Datamirror to mirror the data to an AS/400 DB and the process the orders.
>>
>> Here's the problem.  On fields where they didn't specifically fill with a
>> [null] value (using cold fusion I believe), the value is mirrored to the
>> As/400 as X'00'.
>>
>> Now, we don't want to have to translate all the data on the as/400 simply
>> because there are quite a few files and quite few fields that this
>affects.
>> (Hey, I didn't design the DB, they did..heheh..)  They claim that fixing
>the
>> program to fill in null values will take longer than rewriting the
program
>> on their end.
>>
>> Has anyone had this problem with mirroring of any type?  It's really
>> frustrating.  Or, is there a way to fix it on our end without reading
>> through all the files and checking each field?
>>
>> Bradley V. Stone
>> Taylor Corporation - OASIS Programmer/Analyst
>> bvstone@taylorcorp.com
>>
>> +---
>> | This is the Midrange System Mailing List!
>> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
>> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
>> | To unsubscribe from this list send email to
>MIDRANGE-L-UNSUB@midrange.com.
>> | Questions should be directed to the list owner/operator:
>david@midrange.com
>> +---
>
>
>
>+---
>| This is the Midrange System Mailing List!
>| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
>| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
>| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
>| Questions should be directed to the list owner/operator:
>david@midrange.com
>+---
>+---
>| This is the Midrange System Mailing List!
>| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
>| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
>| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
>| Questions should be directed to the list owner/operator:
david@midrange.com
>+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact