02.05.2013 Views

SAS(R) 9.1.3 Companion for z/OS

SAS(R) 9.1.3 Companion for z/OS

SAS(R) 9.1.3 Companion for z/OS

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

290 Macro Functions Chapter 15<br />

Macro Functions<br />

Autocall Libraries<br />

Under z/<strong>OS</strong>, the %SYSEXEC statement works exactly like the %TSO statement.<br />

The two statements are different only if you transport your <strong>SAS</strong> program to a<br />

different operating environment. Because %SYSEXEC statements are recognized<br />

on multiple operating environments, each operating environment expects<br />

commands that are appropriate <strong>for</strong> that operating environment.<br />

The following macro functions have behavior specific to z/<strong>OS</strong>:<br />

%SCAN<br />

under z/<strong>OS</strong> and other systems that use the EBCDIC collating sequence, if you<br />

specify no delimiters, <strong>SAS</strong> treats all of the following characters as delimiters:<br />

blank . < ( + | & ! $ * ); − /,%¦¢<br />

%SYSGET<br />

under TSO, %SYSGET allows you to retrieve the values of the CLIST variables<br />

with which <strong>SAS</strong> was invoked.<br />

An autocall library contains files that define <strong>SAS</strong> macros. Under z/<strong>OS</strong>, an autocall<br />

library is a partitioned data set. Each autocall macro should be a separate member in a<br />

partitioned data set. <strong>SAS</strong> supplies some autocall macros in the system autocall library;<br />

you can also define autocall macros yourself in a user autocall library. In order to use<br />

the autocall facility, the <strong>SAS</strong> option MAUT<strong>OS</strong>OURCE must be in effect. (See <strong>SAS</strong><br />

Language Reference: Dictionary <strong>for</strong> details about MAUT<strong>OS</strong>OURCE.)<br />

Specifying a User Autocall Library<br />

You can designate a physical file, or a concatenation of physical files, as your<br />

user-written autocall library in any of the following ways:<br />

3 with the <strong>SAS</strong>AUT<strong>OS</strong>= system option. You can designate one or more filerefs or<br />

data set names as your autocall library. See “<strong>SAS</strong>AUT<strong>OS</strong>= System Option” on<br />

page 495 <strong>for</strong> more in<strong>for</strong>mation.<br />

3 with the <strong>SAS</strong>AUT<strong>OS</strong> parameter of the <strong>SAS</strong> CLIST (under TSO). In this case, <strong>SAS</strong><br />

concatenates the user autocall library in front of the system autocall library, which<br />

is specified by the CLIST parameter MAUTS.<br />

3 with the <strong>SAS</strong>AUT<strong>OS</strong>= parameter of the <strong>SAS</strong> cataloged procedure.<br />

Example: Specifying an Autocall Library in Batch Mode<br />

In batch mode, you could use the following JCL statements to specify an autocall<br />

library:<br />

single autocall library:<br />

//MYJOB JOB account. ...<br />

// EXEC <strong>SAS</strong>,OPTIONS=’MAUT<strong>OS</strong>OURCE’<br />

//<strong>SAS</strong>AUT<strong>OS</strong> DD DSN=MY.MACR<strong>OS</strong>,DISP=SHR

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!