I believe with COBOL the understanding is when 2 objects are being worked
upon that spaces are padded make each object the same size. Thus in your
example 'if new-flag > " "' the " " should have been expanded to 4 spaces
and then compared. With a new compiler, I would look for compiler flags
which may control this and check their defaults. Interesting that this would
break. I would lean towards a bug unless a compiler flag was introduced.
Check current definition of compare operators. I will look on mine, but I
don't have the latest, will have to look on http://www.docs.hp.com for the
answer.

James

> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> Behalf Of Curt Brimacomb
> Sent: Friday, February 26, 1999 2:35 PM
> To: [log in to unmask]
> Subject: Attention all COBOL programmers
>
>
> I have a question for all you COBOL programmers.  I have run across a
> problem and do not understand why I have to fix it the way I do.
>
> Program(s) worked fine in compatability mode.  Moved to native mode and
> seemed to work fine until new OS update (5.5 pp6) with a new compiler.
>
> Have lines like this:
> 77 new-flag pic x(4) value spaces.
> .
> .
> .
> If new-flag > " "
>      move spaces to next-flag.
>
> I now have to change the if line to say 'if new-flag not =
> spaces' before it
> will work the same as in compatability mode.  I have also tried
> 'if new-flag
> > "    "' but that also does not work correct.
>
> Can someone set me straight on why it no longer works likes it used to?
>
> Curt Brimacomb                             http://www.magiclink.com
> System Manager                             http://www.idahocomputer.net
> Idaho Computer Services, Inc.              http://www.datanow.net
> PO Box 446                                 Voice: (208) 734-2245
> Twin Falls, ID 83301                       Fax: (208) 733-9663
>
> "It is easier to ask a stupid question that it is to fix a stupid mistake"
>