LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (October 2005, week 1)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Tue, 4 Oct 2005 12:06:06 -0400
Reply-To:     Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
Subject:      Re: SAS Components being used on the mainframe
Content-Type: text/plain; charset=ISO-8859-1

Hi Harry, I don't think that this is what Gary needs! It is a problem to find out, what is really USED, not what is in the license! E.g. you have SAS/LAB and nobody needs it! Question is: what is SAS used for at your site? Are there any applications? Do you know the SAS users or the departments which are using SAS? Send them a mail and ask them! Be careful: some things you never be aware of that you use them, e.g. SAS/FSP. If you have RACF (or whatever you have) profiles for SAS libraries, you might have a chance to identify the SAS users or at least groups / departments. Do you have a job scheduler? Identify the calls to SAS-PROCs in your production jobs and analyze, what they need (base, graph, stat, ...). That should be the minimum you need. Ask the users, what they need else. Make a copy of the SASHELP library, get a test-setinit from SAS Institute with all what you really need and apply the setinit. Add a welcome text for SAS sessions to tell the users which number thay can call if they have problems.

Another thing is the SAS SMF record. I'm not sure, if you get all informations about the PROCs which are called, but that might help. It's a bit of work to install it (you neeed to install a SVC and some things more) and I'm not really sure, if that is what you need, but it's a chance.

On Tue, 4 Oct 2005 11:08:11 -0400, Droogendyk, Harry <harry.droogendyk@RBC.COM> wrote:

>proc setinit; > alias; >run; > >Will surface a bunch of stuff. Not sure it'll let you know is included in bundles you may have licensed. > >-----Original Message----- >From: owner-sas-l@listserv.uga.edu >[mailto:owner-sas-l@listserv.uga.edu]On Behalf Of G B >Sent: Tuesday, October 04, 2005 10:56 AM >To: SAS-L@LISTSERV.UGA.EDU >Subject: SAS Components being used on the mainframe > > >Is it possible to identify what components of SAS that we are licensed for are actually being used on the mainframe? > >We have almost all components they offer and are wanting to discontinue some of them to save maintenance fees. > >Thanks, >Gary >__________________________________________________________________________________________________________________________________ > >This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. >Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. >If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately. > >Ce courrier électronique est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. >Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. >Si vous recevez ce courrier électronique par erreur, veuillez m'en aviser immédiatement, par retour de courrier électronique ou par un autre moyen.


Back to: Top of message | Previous page | Main SAS-L page