If installing the entire SAS 9 load library into the LNKLST or
LPALST, the SAS 9 load module "SAS" can cause a conflict when
implicitly executing a CLIST with the name of "SAS" (e.g. "TSO SAS").
Attempting to implicitly invoke the SAS CLIST will terminate with the
following error:

ERROR:      OPTION NOT RECOGNIZED
BPXP018I THREAD 1E6FC30000000003, IN PROCESS 16777249, ENDED 777
WITHOUT BEING UNDUBBED WITH COMPLETION CODE 000003E7,
AND REASON CODE 00000000.

Possible circumventions include:

- Execute the CLIST explicitly.
  (e.g. "exec 'tso.clist.lib(SAS)' ")
- When the SAS CLIST is being invoked from ISPF, add "SAS" to the
  ISPF TSO Command Table (ISPTCM) as a CLIST with the appropriate
  FLAGBYTE setting to indicate it is to be treated as a CLIST.  See IBM
  documentation for details.
- Execute the "SAS" CLIST with prefix of %  (e.g.  "TSO %SAS")
- Rename the CLIST to something other than "SAS".
- Rename the load module "SAS" to a different name.  Make
  appropriate modifications to all SAS JCL Procedures and CLISTs
  to reflect the renamed entry point.
  (Note: This circumvention is not recommended.)


This possible conflict became more visable in SAS 9 with the new entry
points of SAS, SASB and SASLPA.  When implicitly executing a command,
the command is not always a clist.  It can also be an executable
module; thus the conflict of having a CLIST and a executable module in
the
linklst or LPA with the same name.

Operating System and Release Information