RE: Passing numeric fields to COBOL program

Dean, I was looking for something else and found the
following in the option for CRTBNDCBL, I think we have the
answer.
 

  *NOCHGPOSSGN

      Hexadecimal F is used as the default positive sign for
zoned and       
      packed numeric data.  Hexadecimal F is the system
default for          
      the OS/400 operating system.

 

  *CHGPOSSGN

      Hexadecimal C is used as the default positive sign for
zoned and       
      packed numeric data.  This applies to all results of
the MOVE,         
      ADD, SUBTRACT, MULTIPLY, DIVIDE, COMPUTE, and
INITIALIZE               
      statements, as well as the results of the VALUE
clause.                
 


> ----------
> From:         Weatherly, Howard
> Sent:         Thursday, June 11, 1998 11:40 AM
> To:   'MIDRANGE-L@MIDRANGE.COM'
> Subject:      RE: Passing numeric fields to COBOL program
> 
> Hmm, Dean,
> 
> I was speaking COBOL not DB2 and probably was in
> MainFrameLand mentally, in any case, I did not know that,
> thanks for the correction and new information!
> 
>       -----Original Message-----
>       From:   DAsmussen@aol.com [SMTP:DAsmussen@aol.com]
>       Sent:   Wednesday, June 10, 1998 3:25 PM
>       To:     MIDRANGE-L@MIDRANGE.COM
>       Subject:        Re: Passing numeric fields to COBOL
> program
> 
>       Howard,
> 
>       In a message dated 98-06-10 10:35:41 EDT, you write:
> 
>       > The sign is the 'F' part of your example, if it
> were a
>       >  numeric field vs. a date field, the first time
> any
>       >  arithmetic operation was done on the field the
> 'Fox' would
>       >  change to 'C' or 'D' depending upon the value of
> the result.
>       <<snip>>
> 
>       Now _that's_ interesting!  I didn't know that
> DB2/400 had started using the
>       "C".  We transferred data from a mainframe to the
> /400 under V3R0M05, some of
>       which contained packed, unsigned fields that had the
> "C" in the sign byte.  It
>       took two days to figure out that, despite the fact
> that the file wasn't open
>       for update, the "C" was automatically converted to
> an "F" in the database when
>       the data was read -- immediately disabling our
> "position to" function in a
>       subfile against the same data (which still held the
> "C" value) on the first
>       invocation after data transfer!!!  Does this mean
> that the "C" would no longer
>       be converted in the latter instance?
> 
>       TIA!
> 
>       Dean Asmussen
>       Enterprise Systems Consulting, Inc.
>       Fuquay-Varina, NC  USA
>       E-Mail:  DAsmussen@aol.com
> 
>       Things you never hear -- Bill Clinton saying "Yeah,
> I did it.  So what?"
>       +---
>       | 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
+---