Path: utzoo!attcan!uunet!lll-winken!lll-lcc!lll-tis!ames!oliveb!intelca!mipos3!td2cad!clee From: clee@td2cad.intel.com (Master Of Darkness) Newsgroups: comp.os.vms Subject: Re: Pascal V3.7 query Message-ID: <874@td2cad.intel.com> Date: 6 Jun 88 10:37:13 GMT References: <8806060356.AA24436@ucbvax.Berkeley.EDU> Reply-To: clee@td2cad.UUCP (Master Of Darkness) Organization: Intel TD, Santa Clara CA Lines: 33 In article <8806060356.AA24436@ucbvax.Berkeley.EDU> SMITH@BKNLVMS.BITNET writes: >We recently upgraded VMS Pascal from V3.5 to V3.7. When I recompiled one of >my programs, it stopped working. It began to blow up with a call to reset >a file variable, and returned the error code INVFILVAR (Invalid file variable). >Through experimentation and sheer luck, I discovered that the presence of a >call to the $CrePrc System Service is what is causing the problem. The >following is a simplified version of the program. Compiling as is will show >the error, and commenting out the $CrePrc call will cause the program to >behave as expected (in this case, to report a missing file). Compiling with >and without NoOp makes no difference. Can anyone tell me what I'm doing >wrong/what the difference is/why this is happening? Any help will be greatly >appreciated! Thanks in advance, > >Greg Smith>Bucknell Computer Services > > > I had the same problem, except it was moving from Pascal V3.6 to V3.7 under VMS V4.5. It seems that making a System Service Call *ANYWHERE* in the program is going to generate the INVFILVAR error when the program executes. The program will Compile fine, without ANY ERRORS. DEC was able to confirm this, and recommended that we go back to Pascal V3.6 until we upgrade to VMS V4.6 (or higher). Hope that this helps, and Good Luck. Cecil Lee Intel Corp. The_Doctor%F3ACC1.INTEL.COM@RELAY.CS.NET