Date: Mon, 30 Nov 1998 09:17:00 -0500
Reply-To: Michael Hines <mshines@PURDUE.EDU>
Sender: "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From: Michael Hines <mshines@PURDUE.EDU>
Subject: Re: (MVS): Re: SAS MVS SMF SVC...
In-Reply-To: <"SSW 981127111049084721*/G=MICHAEL/S=RAITHEL/OU=RAITHM49/O=US
Customs Service/PRMD=GOV+CUSTOMS/ADMD=TELEMAIL/C=US/"@MHS>
Content-Type: text/plain; charset="us-ascii"
You will want to get Merrill's Guide to Performance Analysis from SAS
Institute... it is a set of routines for performing SMF analysis using
SAS.
Technical Information for Users of MXG Software from Merrill Consultants
has a web page at http://www.mxg.com which explains the software more
thoroughly.
SAS/Connect usage should be recorded in the SMF logs as TSO sessions,
though I've not yet dug into the details - I do plan to.
The relevant MXG procs seem to be
%include sourclib(vmacsmf,vmactsom,imackeep)
data
_vartsom
_smf
_cdetsom
to extract the data... hope this points you in the right direction.
Perhaps we can share experiences.
At 11:10 AM 11/27/98 -0500, you wrote:
> Zzequiel Torres posted the following (very interesting)
> question:
>
> >I need help from someone who has installed SAS on MVS,
> >Version 6.09.
> >
> >My over all goal is: Monitor and report (by userid if
> >possible ) PCSAS usage when connected to Mainframe SAS
> >6.09. Problem: Job class is not available (from what i've
> >been told) for Interactive SAS/Connect(PCSAS), which we
> >use in Batch SAS to monitor CPU time and other related
> >stats.
> >
> >I've been advised that a quick way to monitor PCSAS
> >activity when connected to the MAINFRAME is with SMF
> >reporting. Question: Is this easy and worth it for USAGE
> >monitoring of PCSAS when connected to MF?
> >
> >I was not the person who installed it on the system (he is
> >no longer with the company) and I need to determine if the
> >SMF reporting option was enabled or installed. Question:
> >How do I determine this? Its not in Proc Options.
> >Otherwise I have to install this which would mean I have
> >to wait till after our HOLIDAY system change lock out.
> >I understand that SAS libnames and SYSTEM libnames are
> >site specific. Yet I have to believe that there should be
> >some quick and painless way to see if it was ever
> >installed.
> >
> >If its not installed and I cant wait until after my site
> >allows SYSTEM installations/changes is there any other
> >option or method that someone might know of?
> >
> >Heck I even thought of reading the SYSLOG for activity but
> >there are security issues within the company for that to
> >happen regularly(production) vs once in a while (special
> >req).
> >
> >If installation is required has anyone had difficulties to
> >advise me of prior to my starting this.
> >
>
> Zzequiel, what a great question; what a drag that I was not
> allowed to install the SAS SMF exit here! So, the first
> part of the following discussion is theory only, but may
> point you to the answer that you seek.
>
> First, the information that you need to determine how to
> install the SAS SVC routine and SMF exit are in the
> document:
>
> Installation Instructions and Systems Manager's Guide,
> The SAS System under MVS,
> Release ?.???
>
> The publication, above, is a blue-cover document that comes
> to your SAS System Administrator, and helps him/her to
> install the SAS System. (Replace the ??, above, with the
> current release of SAS Software at your site, eg. 6.08 or
> 6.09E). You will want to review the sections titled:
>
> Installing the SAS SVC Routine
> Installing the SAS SMF Exit
>
> In the first section, you will see that the SAS System
> Administrator has some flexibility in coding the name of
> the SAS SVC, so it will be hard for you to look for a
> specific SVC name in SYS1.LPALIB, SYS1.SVCLIB,
> SYS1.LINKLIB, etc.
>
> In the second section, above, the SAS System Administrator
> _MUST_ specifically code a member of the SAS System
> (supplied) CNTL Partitioned Data Set (PDS), member BASMF,
> to assemble and link the SAS SMF exit. I would do the
> following detective work:
>
> 1. look at the BASMF member of the CNTL PDS and determine
> if it has been modified.
>
> 2. If it _HAS_ been modified, I would look at the library
> pointed to by the SYSLMOD DD statement.
>
> 3. You should see the SMF exit load module in that library.
>
> Now, to do the SVC installation and SMF exit installation
> "by the book", your SAS System Administrator is supposed to
> create a "Restricted Options Table. (See above reference,
> section: "Create a Restricted Options Table (optional)").
> To do this, the person must modify and execute the JCL
> member BAOPTS2 in the SAS System CNTL PDS. The person may
> or may not have modified the SASOPTRS and SMFEXIT members
> of the SAS System BAMISC PDS. I would do the following:
>
> 1. look at the BASOPTS2 member of the CNTL PDS and
> determine if it has been modified. If so, this is
> circumstantial evidence that your SAS System
> Administrator has enabled either the SVC or SMF exit.
>
> Of course, an easier way to go is to ask the SAS System
> Administrator what he/she did and did not install. But, you
> seemed to indicate that this person was gone-zo...
>
>
> "And now for something completely different."
>
> If you are working at a site that runs Merrill's MXG, then
> there is a "relatively" straightforward way to get the MVS
> resource usage of PC/SAS users who are connected to--and
> using--MVS. In the MXG PDB, access the STEPS SAS data set.
> Subset this data set for all observations with a a TYPETASK
> of "TSU "; that is, all TSO-related observations:
>
> where typetask = "TSU ";
>
> You now have a choice of approach, depending upon how
> much you know about your PC/SAS-to-Mainframe user
> community.
>
> 1. If you know their user id's, then, you could select all
> of their observations based on the variable JOB. JOB
> stores the 7-character TSO userid.
>
> 2. If you do not know (or care about) their userids, but
> know the logon proc that they use to log into TSO (and
> directly into SAS) from the PC session, use the variable
> PROCSTEP. PROCSTEP contains the name of the logon proc.
>
> 3. You could use the STEPNAME variable and subset on a
> STEPNAME of "SAS" (for all TSO users). This would give
> you the problem of determining which were "your" target
> PC/SAS-to-Mainframe users and which were the others.
>
> If/when you are successful with any of the above, you will
> want to use the following variables to measure MVS system
> resources:
>
> CPUTM - Total CPU Time
> EXCPTOTL - Totlal EXCPs (Tape and DASD)
>
> Other variables of interest are:
>
> INITTIME - When the TSO session was initiated (started)
> EXECTM - How long the TSO session lasted.
>
> If you are in a CA-MICS site, then there are MICS variables
> analogous to the ones above. Some bright MICS
> Administrator should be able to advise you.
>
> Zzequiel, best of luck to you in determining the MVS
> resources of your PC/SAS-to-Mainframe population of users!
>
> I hope that this suggestion proves helpful now, and in the
> future!
>
> Of course, all of these opinions and insights are my own,
> and do not reflect those of my organization or my
> associates.
>
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Michael A. Raithel
> "The man who wrote the book on performance"
> E-mail: maraithel@mcimail.com
> Author: Tuning SAS Applications in the MVS Environment
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> ...Brave Helios wake up your steeds, bring us the warmth
> the countryside needs...
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
===================================================================
Internet: mshines@purdue.edu | Michael S. Hines CDP,CISA,CIA,CFE
Voice: (765) 494-5338 | Coordinator of Systems and Programming
FAX: (765) 496-1466 | Purdue University
| 1280 Engineering Administration
| West Lafayette, IN 47907-1280
| 
