Is this a KSAM file? If it is, the problem may be in your SELECT
statement. I've found in many cases if you have more than one key in
your file and they are not declared in the SELECT or declared
improperly, you get this 'fixed attribute' problem. For example, if a
key can be a duplicate you'll have to specify 'with duplicates'.

Hope this helps.

Shirley MacLaughlin
Crossley Carpet Mills, Truro

> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> Behalf Of Joe Howell
> Sent: Monday, February 01, 1999 11:41 AM
> To: [log in to unmask]
> Subject: Cobol Experts!
>
>
> My brain must not be working well this morning.  I am working on a Y2K
> remediation effort for a client, and we would need to get around the
> infamous error quoted below.  Yes, I know that older versions
> of CM Cobol
> did not enforce file sizes in FD's and now NM COBOL 85 does.
> My question
> is, isn't there a way (COBRUNTIME?) to tell Cobol to ignore
> this offending
> condition?  (for the time being, anyway) I looked up the COBRUNTIME
> settings on LaserRom and they didn't seem to address this problem.
>
> Any assistance will be most appreciated.
>
> Reply or call ASAP to [log in to unmask]  (or call 800-966-5284 ,,,
> *8,,4272)
>
> Thanks in Advance
>
>
> Joe
>
> 648      ERROR      FILE'S FIXED ATTRIBUTES DIFFER FROM PROGRAM [39]!
> (COBERR 648)
>          MESSAGE
>
>          CAUSE      The file organization declaration within the
> ENVIRONMENT DIVISION
>                     is different than the organization of the
> actual file
> for which an
>                     OPEN statement was executed.  Compare the two
> organizations and
>                     adjust as necessary to correct the
> problem.  This could
>  also occur
>                     if the record size does not match the
> size of the FD
> records.  It
>                     could also occur if the KEY types in an
> INDEXED file do
>  not match
>                     or the presence or absence of the WITH DUPLICATES
> clause does not
>                     match.  Use the RECORD CONTAINS clause to
> specify the
> minimum and
>                     maximum valid record sizes.
>