Date:         Tue, 9 Feb 1999 17:45:39 -0800
Reply-To:     "Berryhill, Timothy" <TWB2@PGE.COM>
Sender:       "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From:         "Berryhill, Timothy" <TWB2@PGE.COM>
Subject:      Re: (MVS) PEEK and PEEKC to get at CPU time
Comments: To: "Kowalczyk, Andrew" <AKowalczyk@NT.DMA.STATE.MA.US>
Content-Type: text/plain

Andrew,  The message of the day claims I am running MVS/ESA V4.3.0 - DFSMS
V1.3 - JES2 V3.1.3.
 
I ran your suggestion and got:
 
ASCBEJST=5.663025
 
ASCBEJST=5.866647
 
NOTE: The data set TESTMDMA.MDMALOG has 3240 observations and 11 variables.
 
INFO: Composite index FULLNAME defined.
 
INFO: Single index GDGNUM defined.
 
NOTE: The DATA statement used 1.05 CPU seconds and 5745K.
 
 
 
 
 
NOTE: The SAS session used 5.19 CPU seconds and 5745K.
 
NOTE: SAS Institute Inc., SAS Campus Drive, Cary, NC USA 27513-2414
 
The total, 5.86 is close to the 5.19 for the job.  The delta, 5.86-5.66 is
pretty small compared to the reported step time.  I will run some other
trials.
 
Tim Berryhill - Contract Programmer and General Wizard
TWB2@PGE.COM or http://www.aartwolf.com/twb.html
Frequently at Pacific Gas & Electric Co., San Francisco
The correlation coefficient between their views and
my postings is slightly less than 0
 
PS: QW -- command not found
 
> ----------
> From:         Kowalczyk, Andrew[SMTP:AKowalczyk@NT.DMA.STATE.MA.US]
> Reply To:     Kowalczyk, Andrew
> Sent:         Tuesday, February 09, 1999 1:37 PM
> To:   SAS-L@UGA.CC.UGA.EDU
> Subject:      (MVS) PEEK and PEEKC to get at CPU time
>
> OK - I figured out how to get the CPU time for the current Job Step:
>
> /* Elapsed Job Step Timing from Address Space Control Block */
> ascbejst =  /* in seconds */
> inputn(putc(peekc(peek(548)+64,8),'$binary52'),'binary52.')/1000000;
>
>  This is with MVS/SP 4.3.0 and JES2 - I would appreciate it if different
> MVS
> folks tried this out and see if it works on your system.
>
> This is a constantly increasing number since the beginning of the JCL step
> -
> so if you want to measure an individual DATA step you may need to retain
> the
> value from the first iteration and constantly take the difference.
>
> If you have Quick Ref (try typing QW on the command line) you can look up
> system control blocks.
>
>      Kim LeBouton posted the following question:
>
>      >I'm trying to determine if my program has been using up
>      >too much CPU, and then I want to stop my SAS program.
>      >
>      >Is there a way of getting to this information via a macro
>      >variable, and not scanning through a log.
>      >
>