Hi,

I use Autocall libraries to reuse my macros. As most of my things, the
autoexec that loads this was made years and years ago. I have now
upgraded my SAS from 9.1 to 9.2 and lost my autoexec file (I
missplaced the backup).

I am now trying to get it back to work and I cannot access my macros.

The autoexec has the following line
Filename DB 'd:\alves\research\sas\databases\macros\';
Filename MPHD 'd:\alves\research\sas\phd\macros\';
Filename MUtils 'D:\alves\Research\SAS\utils\';
Options SASAutos  = (MUtils MPHD DB SASAutos) ;

when I try to access a macro in the Mutils, I get the following error:

649  %XLSOpen ("D:\Research\CEG\SPM_II\data_spm\opera.xls", spm, YES,
yes);
     -
     180
WARNING: Apparent invocation of macro XLSOPEN not resolved.

ERROR 180-322: Statement is not valid or it is used out of proper
order


Any help?

Thanks.

PA

On Sep 2, 7:18=A0am, alves <alves.pa...@gmail.com> wrote:
> Hi,
>
> I use Autocall libraries to reuse my macros. As most of my things, the
> autoexec that loads this was made years and years ago. I have now
> upgraded my SAS from 9.1 to 9.2 and lost my autoexec file (I
> missplaced the backup).
>
> I am now trying to get it back to work and I cannot access my macros.
>
> The autoexec has the following line
> Filename DB 'd:\alves\research\sas\databases\macros\';
> Filename MPHD 'd:\alves\research\sas\phd\macros\';
> Filename MUtils 'D:\alves\Research\SAS\utils\';
> Options SASAutos =A0=3D (MUtils MPHD DB SASAutos) ;
>
> when I try to access a macro in the Mutils, I get the following error:
>
> 649 =A0%XLSOpen ("D:\Research\CEG\SPM_II\data_spm\opera.xls", spm, YES,
> yes);
> =A0 =A0 =A0-
> =A0 =A0 =A0180
> WARNING: Apparent invocation of macro XLSOPEN not resolved.
>
> ERROR 180-322: Statement is not valid or it is used out of proper
> order
>
> Any help?
>
> Thanks.
>
> PA

Change "filename" to "libname"

HTH

Ya

You need to find the source code for XLSOPEN macro.  SAS is expecting
to find a file named 'xlsopen.sas' for the autocall to work.

Your old autoexec might have pre-compiled the XLSOPEN macro from some
other file.
Your files might have been moved.  Perhaps D is no longer the correct
drive letter to use?
Check for duplicate file names in your different directories and the
order of you directories in the SASAUTOS option.  Perhaps you have two
versions of the same macro and with a different search order you are
getting different behaviour.


Not sure how LIBNAMES would work for SASAUTOS unless the macros were
compiled into a catalog.
But if they are compiled they will need to be recompiled with the new
version of SAS.


On Sep 2, 12:39=A0pm, Ya <huang8...@gmail.com> wrote:
> On Sep 2, 7:18=A0am, alves <alves.pa...@gmail.com> wrote:
>
>
>
>
>
> > Hi,
>
> > I use Autocall libraries to reuse my macros. As most of my things, the
> > autoexec that loads this was made years and years ago. I have now
> > upgraded my SAS from 9.1 to 9.2 and lost my autoexec file (I
> > missplaced the backup).
>
> > I am now trying to get it back to work and I cannot access my macros.
>
> > The autoexec has the following line
> > Filename DB 'd:\alves\research\sas\databases\macros\';
> > Filename MPHD 'd:\alves\research\sas\phd\macros\';
> > Filename MUtils 'D:\alves\Research\SAS\utils\';
> > Options SASAutos =A0=3D (MUtils MPHD DB SASAutos) ;
>
> > when I try to access a macro in the Mutils, I get the following error:
>
> > 649 =A0%XLSOpen ("D:\Research\CEG\SPM_II\data_spm\opera.xls", spm, YES,
> > yes);
> > =A0 =A0 =A0-
> > =A0 =A0 =A0180
> > WARNING: Apparent invocation of macro XLSOPEN not resolved.
>
> > ERROR 180-322: Statement is not valid or it is used out of proper
> > order
>
> > Any help?
>
> > Thanks.
>
> > PA
>
> Change "filename" to "libname"
>
> HTH
>
> Ya- Hide quoted text -
>
> - Show quoted text -

Fixed!!!

When upgrading I made a backup of my SAS folder which contains all my
SAS programs (in subfolders) together with profile and some other
config files. I deleted all the configuration/profile files and
restarted SAS... and the problem just dissapeared!

I guess some config file from the old version was messing the system

Thanks for the help

PA

PS: The code is correct, it is Filename and not Libname