Actually,
  I think it's complaining because the source filed is defined as signed, but the data in that source field is not signed.  It should be ok to go from one to the other as long as the source field data matches the definition.


Rich

   

Rich Trapp <mailto:[log in to unmask]>  

Consulting for Agilent Technologies, Loveland, Colorado.

Managed Business Solutions <http://www.mbsnav.com/>  
200 South College Avenue 
Fort Collins, Colorado 80524-2811 
970.679.2221 (voice) 
970.669.3071 (fax) 



-----Original Message-----
From: Paul D. Christensen [mailto:[log in to unmask]]
Sent: Thursday, August 15, 2002 12:51 PM
To: [log in to unmask]
Subject: Re: Cobol Ilegal Decimal digits...


At 07:23 PM 8/15/02 +0100, you wrote:

>Now I realise the best option here is to correct the data in the
>database, but that is not an option open to me. Is there a way I can I
>give a different definition of the data items in my Cobol program or is
>there a particular statement associated with the 'move' that I can use
>so that the move doesn't actually cause the program to abort?

Try defining the item as unsigned - PIC 9(3)V9(8) COMP-3
That's what is causing this problem.



Paul D. Christensen
PC Enterprises Inc.      [log in to unmask]
206 Central Avenue
P.O. Box 369
Osakis MN 56360-0369  (www.lakeosakismn.com)

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *