Thanks Carmen.   I'll take a look at this.

_________________________________________________________________
Dave Jousma
Manager Mainframe Engineering, Assistant Vice President
david.jou...@53.com
1830 East Paris, Grand Rapids, MIĀ  49546 MD RSCB2H
p 616.653.8429
f 616.653.2717

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Carmen Vitullo
Sent: Wednesday, April 25, 2018 8:26 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: OA53355 - USERKEY COMMON MIGRATION SUPPORT

**CAUTION EXTERNAL EMAIL**

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails**

here's some MSG code I used to report on storage used by a task 



OPTIONS NOSOURCE NOFMTERR SORT=90;
%INCLUDE SOURCLIB(VMACSMF,VMAC30);
DATA _VAR30
_SMF
_CDE30
RUN;
DATA TEMPA;
SET TYPE30_V;
IF TYPETASK= 'JOB';
IF JOB =:'D10YPF02';
DATE = DATEPART(READTIME);
TIME = TIMEPART(READTIME);
FORMAT DATE MMDDYY8.;
FORMAT TIME TIME.;
FREEUSR = REGREQST-PVTBOT;
FREESYS = PVTSZLOW-REGREQST-PVTTOP;
FREEBOT = FREEUSR/1000;
FREETOP = FREESYS/1000;
FORMAT FREEBOT MGBYTES.;
FORMAT FREETOP MGBYTES.;
RUN;
PROC PRINT DATA=TEMPA LABEL;
LABEL FREEBOT = 'FREE USER AREA';
LABEL FREETOP = 'FREE SYSTEM AREA';
VAR JOB JESNR SYSTEM DATE REGREQST PVTSZLOW PVTBOT PVTTOP FREEBOT FREETOP 
PVTSZHI USRSZHI LSQSZHI; RUN; 

I have some more samples, but they are specific to what I needed them for 


Carmen Vitullo 

----- Original Message -----

From: "David Jousma" <000001a0403c5dc1-dmarc-requ...@listserv.ua.edu>
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Tuesday, April 24, 2018 2:24:21 PM
Subject: Re: OA53355 - USERKEY COMMON MIGRATION SUPPORT 

Thanks Carmen. I'm not SASsy...Not much of a SAS coder these days. Seems like 
this is going to become a pretty common report that folks are going to be 
running over the next two years until V2.4 looms near. I was hoping to ride on 
someones coat-tails. 

_________________________________________________________________
Dave Jousma
Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com
1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Carmen Vitullo
Sent: Tuesday, April 24, 2018 3:04 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: OA53355 - USERKEY COMMON MIGRATION SUPPORT 

**CAUTION EXTERNAL EMAIL** 

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails** 

I have a bunch of MXG source to read the SMF_30, but not the variable you're 
looking for - let me know, I'd be happy to share 



Carmen Vitullo 

----- Original Message ----- 

From: "David Jousma" <000001a0403c5dc1-dmarc-requ...@listserv.ua.edu>
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Tuesday, April 24, 2018 1:46:59 PM
Subject: OA53355 - USERKEY COMMON MIGRATION SUPPORT 

So, has anyone written a SAS/MXG program to read through these SMF30 records 
yet, that they would care to share? Seems to be the easiest method to run 
through the daily data to determine who is using USER Key common? I see the 
slip noted in the APAR, and I could go that route, but still have to look 
through GTF data it seems. 

I know I have one long running home-grown system task for sure using it, but 
what I do not know if there are any short lived usage. We are already working 
on retiring the home-grown system task. 

SA38-0667-XX z/OS MVS System Management Facilities (SMF) Add the following new 
SMF Type 30 record fields in the Storage and Paging Section: 
Offsets Name Length Format... 
178 B2 SMF30_RAXFLAGS 1 binary... 
Description
Bit Meaning
0 When SMF30_USERKEYCOMMONAUDITENABLED is on, auditing of user key common 
storage usage attempts enabled for this step/job. 
SMF30_USERKEYCSAUSAGE, SMF30_USERKEYCADSUSAGE and SMF30_USERKEYCHANGKEYUSAGE 
are only applicable when this flag is on. 
1 When SMF30_USERKEYCSAUSAGE is on, attempts were made to obtain user key CSA 
storage for this step/job. 
This bit is only valid when
SMF30_USERKEYCOMMONAUDITENABLED is on. 
Once this bit is set on for an interval record, this bit will also be set on 
for all subsequent interval records for this step. 
Once this bit is set on for a job interval or step-end record, this bit will 
also be set on for step-total and job-end records. 
2 When SMF30_USERKEYCADSUSAGE is on, attempts were made to create a user key 
CADS for this step/job. 
This bit is only valid when
SMF30_USERKEYCOMMONAUDITENABLED is on. 
Once this bit is set on for an interval record, this bit will also be set on 
for all subsequent interval records for this step. 
Once this bit is set on for a job interval or step-end record, this bit will 
also be set on for step-total and job-end records. 
3 When SMF30_USERKEYCHANGKEYUSAGE is on, attempts were made to change the key 
of common ESQA storage to a user key (via CHANGKEY) for this step/job. 
This bit is only valid when
SMF30_USERKEYCOMMONAUDITENABLED is on. 
Once this bit is set on for an interval record, this bit will also be set on 
for all subsequent interval records for this step. 
Once this bit is set on for a job interval or step-end record, this bit will 
also be set on for step-total and job-end records. 



_________________________________________________________________
Dave Jousma
Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com
1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 

This e-mail transmission contains information that is confidential and may be 
privileged. 
It is intended only for the addressee(s) named above. If you receive this 
e-mail in error, please do not read, copy or disseminate it in any manner. If 
you are not the intended recipient, any disclosure, copying, distribution or 
use of the contents of this information is prohibited. Please reply to the 
message immediately by informing the sender that the message was misdirected. 
After replying, please erase it from your computer system. Your assistance in 
correcting this error is appreciated. 




----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN 


---------------------------------------------------------------------- 
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL 
EMAIL** 

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails** 

This e-mail transmission contains information that is confidential and may be 
privileged. It is intended only for the addressee(s) named above. If you 
receive this e-mail in error, please do not read, copy or disseminate it in any 
manner. If you are not the intended recipient, any disclosure, copying, 
distribution or use of the contents of this information is prohibited. Please 
reply to the message immediately by informing the sender that the message was 
misdirected. After replying, please erase it from your computer system. Your 
assistance in correcting this error is appreciated. 


---------------------------------------------------------------------- 
For IBM-MAIN subscribe / signoff / archive access instructions, 
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN 


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
**CAUTION EXTERNAL EMAIL**

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails**

This e-mail transmission contains information that is confidential and may be 
privileged.   It is intended only for the addressee(s) named above. If you 
receive this e-mail in error, please do not read, copy or disseminate it in any 
manner. If you are not the intended recipient, any disclosure, copying, 
distribution or use of the contents of this information is prohibited. Please 
reply to the message immediately by informing the sender that the message was 
misdirected. After replying, please erase it from your computer system. Your 
assistance in correcting this error is appreciated.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to