Brad,

This is a new one to me.  I just tried your program example and it too compiled with the lower case version of "clock".  My summation is that either the COBOL compiler has been enhanced to look for the intrinsic in both lower and/or upper case when using intrinsic option of the call statement, or that the SYSINTR file has been modified to be "smarter" when requests are made for the intrinsics being called.    One possible thing you can do is to check your compiler versions on both systems and also check you SYSINTR files to see if they are the same.  I believe this is a new enhancement that has been added.  I am unable to locate the 5.5 PP6 Communicator to see if this enhancement was listed.  I was unable to find it in the previous releases.

Just to let you know, it appears it does not matter what the case of the intrinsic name is.  I also compiled with the intrinsic "Clock" and "ClocK" and they both compiled without any errors, warnings,  or questions.

Walter Murray (HP Lab), Is this a new enhancement with 5.5 PP6 or was it part of another release?  This use to be more stringent when calling intrinsics.  Can you point us to the article discussing any new additional features of the compiler.  Please let us know.

Tom Renz

>>> "FEAZELL, Brad" <[log in to unmask]> 03/15 2:39 PM >>>
Tom,

Why would it work on one machine and not on another?

Brad Feazell



> -----Original Message-----
> From: TechServ TechServ [mailto:[log in to unmask]] 
> Sent: Monday, March 15, 1999 3:34 PM
> To: [log in to unmask]; [log in to unmask] 
> Subject: Re: INTRINSIC print NOT FOUND IN INTRINSIC FILE
> 
> 
> Brad,
> 
> You need to specify the intrinsic in upper-case.  The 
> compiler is interpreting the intrinsic name you placed in 
> quotes as a lower-case intrinsic function, which doe not 
> exist in the SYSINTR.PUB.SYS file.  Cobol will upshift all of 
> the code in your source file except for data within quotation marks.
> 
> tom renz