Re: SQL Misbehaving

Hi guys,

This morning, I went through the file field by field trying to recreate the
error and I found the culprit FIELD.  It is the attribute field, when I
eliminate this field the file works fine and when I select the field when it
is blank.  Now, I went to DBU and display the HEX values in this field for
all 512 records.  These are my values:  Most of the records are like record
#1.

Record#      Object                 Object type     Object attribute
Storage freed: 0-not free
         1        ACCGSODTA    *USRPRF                                   0
                   CCCCEDCEC4  5EEDDDC4    4444444444        F
                   1337264310        C4297960      0000000000         0

         9        AKERS_MA       *USRPRF        QSECOFR           0
                   CDCDE6D444   5EEDDDC4     DECCDCD444    F
                   12592D4000      C4297960        8253669000         0

       20        AM2000            *USRPRF        QSECQSPO         0
                   CDFFFF4444    5EEDDDC4     DECC00DEDD     F
                   1420000000      C4297960        8253218276          0

      329       QDBSHR           *USRPRF       *IBMQRJE            0
                   DCCECD4444   5EEDDDC4    5CCD00DDDC     F
                   8422890000       C4297960      C924818915          0


----- Original Message -----
From: "Buck Calabro" <Buck.Calabro@commsoft.net>
To: <midrange-l@midrange.com>
Sent: Wednesday, March 20, 2002 12:07 PM
Subject: RE: SQL Misbehaving


> >Explain "Are there characters below x'40' "
>
> Characters below x'40' are reserved as special workstation control
> characters.
>
> Here's a snippet from a customer master file using CPYF master *print
> outfmt(*hex):
>
> *...+... 1 ...+... 2 ...+... 3 ...+... 4
> 0000000000000 0030}00000000Changed by tr
> FFFFFFFFFFFFF4FFFFDFFFFFFFFC88988848A4A9
> 0000000000000000300000000003815754028039
>
> The first 13 characters are the key (all zeroes - hex 'F0').  Column 14 is
a
> status code (blank - hex '40').  The next 5 are a bill-to-number (00300- -
> hex 'F0F0F3F0D0.  The 'D' indicates a negative number.)  Moving out to
> column 28 begins the name.  Hex 'C3' is the letter 'C', x'88' is the
letter
> 'h', etc.  If I did something bizarre like put a hex '21' in column 28,
the
> machine might (depending on the program) interpret that x'21' as a
> workstation control (in this case, High Intensity.)
>
> About the only time you expect to see characters less than x'40' is in a
> packed or binary number:
>
> *...+... 1 ...+... 2
>
> 44444000000000004444
> 00000000F00F0F0F0000
>
> Starting at column 6 is a packed number (all zeroes - hex '0000000F'  The
> 'F' indicates a positive number.)
>
> So, if you had a program that accidentally moved a packed field onto a
> character field you could get strange results trying to display the name
> field which now contains control characters.
>   --buck
> _______________________________________________
> 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.
>