Table 7.6 shows the SAS/C Libraries
that can be linked with your program, for both OS/390 and CMS. This information
may be valuable if you are linking your program without using a standard batch
PROC or the COOL CLIST or EXEC. Note that in general, you should define the
base run-time library and one other library, depending on the intended execution
environment, as autocall libraries. Optionally, a version of the all-resident
library can be added. Do not attempt to link using more than one environmental
library at once, as the effects are unpredictable. For instance, never specify
both the standard library and the SPE library together as autocall libraries.
Note that on OS/390 the name shown below must be augmented
by a site-assigned prefix. For instance, the name of the base library is
shown as prefix.BASEOBJ. The prefix part of
the filename will be replaced by a prefix chosen by your site. For instance,
if your site uses the prefix VDR.SASC600, then the full name of the base library
will be VDR.SASC600.BASEOBJ.
For OS/390, two library names are shown for some libraries.
The names ending in OBJ are object module libraries. The names ending in
LIB or SUB are the equivalent load module libraries.
Note:
The ILC library should not be used
as an autocall library. Under CMS these files are organized as a collection
of TEXT files rather than as a TXTLIB. See the SAS/C Compiler Interlanguage
Communication Feature User's Guide for more information on linking
ILC programs. ![[cautionend]](../common/images/cautend.gif)
Copyright © 2001
by SAS Institute Inc., Cary, NC, USA. All rights reserved.
