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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Initializing and Configuring <strong>SAS</strong> Software Working with Your <strong>SAS</strong> Support Consultant 29<br />

STOP<br />

This method is the equivalent of an application requesting a normal shutdown.<br />

You should have no problems with your files.<br />

CANCEL<br />

The operating system initiates the termination of <strong>SAS</strong>, but application error<br />

handlers can still run and cleanup is possible. Your files will be closed, and the<br />

buffers will be flushed to disk. However, there is no way to ensure that the<br />

shutdown will always be orderly. Your files could be corrupted.<br />

MEMTERM (also know as FORCE)<br />

The operating system terminates all application processes with no recovery. This<br />

is the equivalent to what would happen if the system were rebooted.<br />

Some databases, such as DB2, are able to recover from both the CANCEL and<br />

MEMTERM types of failures. These applications accomplish this task by logging every<br />

change so that, regardless of when a failure occurs, the log can be replayed to enable<br />

recovery to a valid state. However, some transactions could still be lost.<br />

Although you can terminate <strong>SAS</strong> using these techniques, you should try one of the<br />

three preferred techniques listed first.<br />

What If <strong>SAS</strong> Doesn’t Start?<br />

If <strong>SAS</strong> does not start, the <strong>SAS</strong> log might contain error messages that explain the<br />

failure. Any error messages that <strong>SAS</strong> issues be<strong>for</strong>e the <strong>SAS</strong> log is initialized are<br />

written to the <strong>SAS</strong> Console Log, which is the <strong>SAS</strong>CLOG ddname destination. Under<br />

TSO, that will normally be the terminal, but the destination might have been changed<br />

by the <strong>SAS</strong> Support Consultant by changing the CLIST that invoked <strong>SAS</strong>. For a batch<br />

job or started task, that will normally be a spooled SYSOUT class, but it might have<br />

been changed by the <strong>SAS</strong> Support Consultant by changing the <strong>SAS</strong> cataloged procedure<br />

used to invoke <strong>SAS</strong>.<br />

Support <strong>for</strong> <strong>SAS</strong> Software<br />

Support <strong>for</strong> <strong>SAS</strong> software is shared by <strong>SAS</strong> and your installation or site. <strong>SAS</strong><br />

provides maintenance <strong>for</strong> the software; the <strong>SAS</strong> Installation Representative, <strong>SAS</strong><br />

Support Consultant, and the <strong>SAS</strong> Training Coordinator <strong>for</strong> your site are responsible <strong>for</strong><br />

providing you with direct user support.<br />

3 The <strong>SAS</strong> Installation Representative receives all shipments and correspondence<br />

and distributes them to the appropriate personnel at your site.<br />

3 The <strong>SAS</strong> Support Consultant is a knowledgeable <strong>SAS</strong> user who supports the other<br />

<strong>SAS</strong> users at your site. The <strong>SAS</strong> Technical Support Division is available to assist<br />

your <strong>SAS</strong> Support Consultant with problems that you encounter.<br />

3 The <strong>SAS</strong> Training Coordinator works with the <strong>SAS</strong> Education Division to arrange<br />

training classes <strong>for</strong> <strong>SAS</strong> users.<br />

Working with Your <strong>SAS</strong> Support Consultant<br />

At your site, one or more <strong>SAS</strong> Support Consultants have been designated as the first<br />

point of contact <strong>for</strong> <strong>SAS</strong> users who need help resolving problems.

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

Saved successfully!

Ooh no, something went wrong!