Subject: | |
From: | |
Reply To: | |
Date: | Mon, 1 Feb 1999 10:45:49 -0600 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Actually, I was thinking of STAT74. STAT74 has the following entry on
the CD-ROM:
STAT74.
This option allows you to specify that file status codes should be
returned in the manner specified in ANSI COBOL 1974 (the way the ANSI74
entry point works) when the ANSI85 entry point is used. This allows you
to use the ANSI COBOL 1985 features together with the old file status
codes.
I don't think that using this is getting "around" the features of the
language. It's more of the best of both worlds (74 and 85).
Later.
> -----Original Message-----
> From: Glenn J. Koster, Sr. [SMTP:[log in to unmask]]
> Sent: Monday, February 01, 1999 10:21 AM
> To: [log in to unmask]
> Subject: Re: Cobol Experts
>
> R. Horner (in response to a question from Joe Howell):
>
> > There is, look at "SYNC74" or at least with something with 74 in it.
> > If you place this in the $control statement, it will apply the
> cobol74
> > rules on the record sizes.
>
> Well, actually the $CONTROL option is "DIFF74=<option>" - and it flags
> the potential problems. You can either have obsolete (=OBS) or
> incompatible (=INC) features flagged. This is useful for flagging
> incompatabilities - but, IMHO, should not be used to bypass the
> features
> of the language.
>
> Glenn
> --
> ______________
> | Navigators | Under contract to Hewlett-Packard ISG (Greeley, CO)
> | |) |
> | | ) | Glenn J. Koster, Sr. [log in to unmask]
> | | ) | Managed Business Solutions http://www.mbsnav.com
> | | ) | 214 S. College, Suite 201 970 350-5337
> | |---- | Fort Collins, CO 80524 970 224-1016
> | ============ |
> | \__________/ |
> | of Change | aka: [log in to unmask]
> |______________| home: http://members.aol.com/MichiTex
|
|
|