See table 9-2 "Permissible Moves" in the Cobol manual, page 9-64.  This
isn't a bug, it's a high-effort built-in and waiting-to-bite you Feature,
which you'll soon remember:

If you make the mistake of cleaning up this code...
01 SSN.
   05  SSN-1 PIC XXX.
   05  SSN-2 pic XX.
   05  SSN-3 PIC XXXX.
01 UN-NEEDED-REDEF-TO-AVOID-GROUP-GOTCHA REDEFINES SSN PIC X(9).
01 SSN-DISPLAY PIC XXXBXXBXXXX.
...
MOVE UN-NEEDED-REDEF TO SSN-DISPLAY

...by removing the quite obviously un-needed redef and say...
MOVE SSN TO SSN-DISPLAY
...you lose the editting features of the receiving field.  Similarly but a
tad more sinister, if your original definition was...
01 SSN       PIC X(9).
01 SSN-REDEF.
   05  SSN-1 PIC XXX.
   05  SSN-2 PIC XX.
   05  SSN-3 PIC XXXX.
MOVE SSN to SSN-DISPLAY
...all is well until you remove the "obviously unnecessary" redefinition.
WHY?  Personally, I would have quite deliberately lumped GROUP and
ALPHANUMERIC together, on both sending and receiving sides of this table.

Tracy Pierce






> -----Original Message-----
> From: Glenn Koster [mailto:[log in to unmask]]
> Sent: Tuesday, June 12, 2001 9:48 AM
> To: Tracy Pierce
> Subject: Re: [HP3000-L] Attempt to have execution for XEQ Commands
>
>
> Tracy,
>
> On the HP3000-L list you wrote:
> >
> > (and I'd much rather see them fix my 20-year-outstanding
> Cobol gripe re
> > group fields not being treated as X fields!)
> >
>
> Fill me in?  What do you mean by them not being treated as
> "X" fields.  I
> use them all the time in my COBOL as "X" fields without any
> repercussions at
> all.
>
> Glenn Koster, Sr.
> Quintessential School Systems
> Developers of QWEBS (www.qss.com)
>

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