I found the answer -- here it is in case anyone else runs into it:

SN-002856 COMPATIBILITY ISSUE

Change in FILEEXT= system option generates "Apparent invocation of macro not resolved"

Product: Base SAS Component: OPTIONS statement/window/procedure Priority: N/A

In Version 8 of the SAS System, the FILEEXT= option should be set to IGNORE (the default) when using autocall macros. Specifying any other value may generate the following messages in the SAS Log:

WARNING: Apparent invocation of macro XXXXX not resolved. ERROR 180-322: Statement is not valid or it is used out of proper order.

In Version 6 of the SAS System, the default value for FILEEXT is VERIFY. However, it was incorrectly functioning as if IGNORE was specified. This was corrected in Version 8 so that FILEEXT=VERIFY looks for an extension of .SAS, and correctly causes the messages listed above.

> -----Original Message----- > From: Sterling Price > Sent: Thursday, December 06, 2001 9:00 AM > Subject: OS/390 v609E->v8.2 problem > > Greetings, all. > > I've been elected to do some compatibility testing in our company to > prepare > for the migration to version 8.2 on the mainframe. > > Unfortunately, SAS crashes on the second line of code in the first program > I'm testing. The line does a %INCLUDE to include a member from the > autocall > library: > > %INCLUDE SASAUTOS(SSFOPAC); > > The error message I'm getting says: > > "ERROR: Member name SSFOPAC.sas contains an extension. The system option > FILEEXT=is set to VERIFY which requires the last qualifier of the PDS or > PDSE to match the extension." > > The same code runs in 6.09E with no error. I checked the value of the > FILEEXT option and it is set to VERIFY in both 6.09E and 8.2. I also > looked > at the procs for 6.09E and 8.2 and found that they were using different > autocall libraries (with the 8.2 library appearing to be just a clone of > the > 6.09e library). I thought that might be the problem, so I created my own > copy of the 8.2 proc and pointed SASAUTOS at the old library. I ran with > that proc and still had the same problem. Can anyone suggest what I might > try to overcome this? > > Thanks, > > Sterling Price > > > [ > > > > ********************************************************************** > This email and any files transmitted with it are confidential > and intended solely for the individual or entity to > whom they are addressed. If you have received this email > in error destroy it immediately. > **********************************************************************