Discussion:
OA53355 - USERKEY COMMON MIGRATION SUPPORT
(too old to reply)
Jousma, David
2018-04-24 18:45:42 UTC
Permalink
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
***@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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
Carmen Vitullo
2018-04-24 19:02:42 UTC
Permalink
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-***@LISTSERV.UA.EDU>
To: IBM-***@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
***@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 ***@listserv.ua.edu with the message: INFO IBM-MAIN


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Jousma, David
2018-04-24 19:23:02 UTC
Permalink
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
***@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-***@LISTSERV.UA.EDU] On Behalf Of Carmen Vitullo
Sent: Tuesday, April 24, 2018 3:04 PM
To: IBM-***@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-***@LISTSERV.UA.EDU>
To: IBM-***@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 ***@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 ***@listserv.ua.edu with the message: INFO IBM-MAIN


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
Martin Packer
2018-04-24 22:52:23 UTC
Permalink
It is, of course, just a set of flag bits in an existing section. Doesn’t
seem to me to be the most difficult of things to map and summarise.

Cheers, Martin

Sent from my iPad
On 25 Apr 2018, at 04:24, Jousma, David
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
1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H
p 616.653.8429
f 616.653.2717
-----Original Message-----
Behalf Of Carmen Vitullo
Sent: Tuesday, April 24, 2018 3:04 PM
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 -----
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
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
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
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send
email to ***@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,
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Carmen Vitullo
2018-04-25 12:24:39 UTC
Permalink
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-***@LISTSERV.UA.EDU>
To: IBM-***@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
***@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-***@LISTSERV.UA.EDU] On Behalf Of Carmen Vitullo
Sent: Tuesday, April 24, 2018 3:04 PM
To: IBM-***@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-***@LISTSERV.UA.EDU>
To: IBM-***@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 ***@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 ***@listserv.ua.edu with the message: INFO IBM-MAIN


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@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 ***@listserv.ua.edu with the message: INFO IBM-MAIN


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Jousma, David
2018-04-25 13:13:34 UTC
Permalink
Thanks Carmen. I'll take a look at this.

_________________________________________________________________
Dave Jousma
Manager Mainframe Engineering, Assistant Vice President
***@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-***@LISTSERV.UA.EDU] On Behalf Of Carmen Vitullo
Sent: Wednesday, April 25, 2018 8:26 AM
To: IBM-***@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-***@LISTSERV.UA.EDU>
To: IBM-***@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 ***@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-***@LISTSERV.UA.EDU] On Behalf Of Carmen Vitullo
Sent: Tuesday, April 24, 2018 3:04 PM
To: IBM-***@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-***@LISTSERV.UA.EDU>
To: IBM-***@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 ***@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 ***@listserv.ua.edu with the message: INFO IBM-MAIN


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@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 ***@listserv.ua.edu with the message: INFO IBM-MAIN


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
Ron hawkins
2018-04-25 06:55:56 UTC
Permalink
David,

If there us an MXG program to run through this, then it will be in the
product SOURCLIB.

I don't think anyone can share MXG with you if you don't have it licensed
already.

I'm not trying to be a dick about it, and you may have just meant to say
SAS. It just seemed like an odd request.

Ron

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-***@LISTSERV.UA.EDU> On Behalf Of
Jousma, David
Sent: Tuesday, April 24, 2018 11:47 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: [IBM-MAIN] 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 ***@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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Jousma, David
2018-04-25 10:45:29 UTC
Permalink
Ron we have both. Don't think there are any native MXG programs out there, I could be wrong. Just the widely used add-on for SAS to map everything SMF is all.

_________________________________________________________________
Dave Jousma
Manager Mainframe Engineering, Assistant Vice President
***@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-***@LISTSERV.UA.EDU] On Behalf Of Ron hawkins
Sent: Wednesday, April 25, 2018 2:57 AM
To: IBM-***@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**

David,

If there us an MXG program to run through this, then it will be in the product SOURCLIB.

I don't think anyone can share MXG with you if you don't have it licensed already.

I'm not trying to be a dick about it, and you may have just meant to say SAS. It just seemed like an odd request.

Ron

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-***@LISTSERV.UA.EDU> On Behalf Of Jousma, David
Sent: Tuesday, April 24, 2018 11:47 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: [IBM-MAIN] 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 ***@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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
Carmen Vitullo
2018-04-25 12:28:32 UTC
Permalink
I've never had an issue, or Barry has never had an issue with me sharing code, David would indeed need to have SAS or WPS and MXG to make my samples work.



Carmen Vitullo

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

From: "Ron hawkins" <***@SBCGLOBAL.NET>
To: IBM-***@LISTSERV.UA.EDU
Sent: Wednesday, April 25, 2018 1:57:15 AM
Subject: Re: OA53355 - USERKEY COMMON MIGRATION SUPPORT

David,

If there us an MXG program to run through this, then it will be in the
product SOURCLIB.

I don't think anyone can share MXG with you if you don't have it licensed
already.

I'm not trying to be a dick about it, and you may have just meant to say
SAS. It just seemed like an odd request.

Ron

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-***@LISTSERV.UA.EDU> On Behalf Of
Jousma, David
Sent: Tuesday, April 24, 2018 11:47 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: [IBM-MAIN] 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 ***@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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

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


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Ron hawkins
2018-04-25 13:50:36 UTC
Permalink
Carmen,

Indeed, David would have to have a copy of MXG to use the SAS code that you shared.

That was my point: you didn't share MXG code.

Ron

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

I've never had an issue, or Barry has never had an issue with me sharing code, David would indeed need to have SAS or WPS and MXG to make my samples work.



Carmen Vitullo

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

From: "Ron hawkins" <***@SBCGLOBAL.NET>
To: IBM-***@LISTSERV.UA.EDU
Sent: Wednesday, April 25, 2018 1:57:15 AM
Subject: Re: OA53355 - USERKEY COMMON MIGRATION SUPPORT

David,

If there us an MXG program to run through this, then it will be in the product SOURCLIB.

I don't think anyone can share MXG with you if you don't have it licensed already.

I'm not trying to be a dick about it, and you may have just meant to say SAS. It just seemed like an odd request.

Ron

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-***@LISTSERV.UA.EDU> On Behalf Of Jousma, David
Sent: Tuesday, April 24, 2018 11:47 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: [IBM-MAIN] 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 ***@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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

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


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

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Carmen Vitullo
2018-04-25 13:58:00 UTC
Permalink
ah ! blonde moment strikes again!



Carmen Vitullo

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

From: "Ron hawkins" <***@SBCGLOBAL.NET>
To: IBM-***@LISTSERV.UA.EDU
Sent: Wednesday, April 25, 2018 8:51:53 AM
Subject: Re: OA53355 - USERKEY COMMON MIGRATION SUPPORT

Carmen,

Indeed, David would have to have a copy of MXG to use the SAS code that you shared.

That was my point: you didn't share MXG code.

Ron

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

I've never had an issue, or Barry has never had an issue with me sharing code, David would indeed need to have SAS or WPS and MXG to make my samples work.



Carmen Vitullo

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

From: "Ron hawkins" <***@SBCGLOBAL.NET>
To: IBM-***@LISTSERV.UA.EDU
Sent: Wednesday, April 25, 2018 1:57:15 AM
Subject: Re: OA53355 - USERKEY COMMON MIGRATION SUPPORT

David,

If there us an MXG program to run through this, then it will be in the product SOURCLIB.

I don't think anyone can share MXG with you if you don't have it licensed already.

I'm not trying to be a dick about it, and you may have just meant to say SAS. It just seemed like an odd request.

Ron

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-***@LISTSERV.UA.EDU> On Behalf Of Jousma, David
Sent: Tuesday, April 24, 2018 11:47 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: [IBM-MAIN] 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 ***@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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

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


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

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


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Jousma, David
2018-04-27 13:15:36 UTC
Permalink
Thought I'd share the SAS/MXG code that one of my team mates whipped up. We already rollup SMF30's into a daily PDB, so it's just pulling from that. I'll run it weekly until the report is empty.

DATA LIMIT;
SET PDB1.SMFINTRV PDB2.SMFINTRV PDB3.SMFINTRV PDB4.SMFINTRV
PDB5.SMFINTRV PDB6.SMFINTRV PDB7.SMFINTRV ;
IF CPUTM NE . ;
IF SMF30_RAXFLAGS='80'X THEN DELETE;
/* 10000000 = 80 = AUDIT ON */
/* 10010000 = 90 = CHANGE KEY */
/* 10100000 = A0 = CADS USAGE */
/* 10110000 = B0 = CADS+CHANGE KEY */
/* 11000000 = C0 = CSA USAGE */
/* 11010000 = D0 = CSA+CHANGE KEY */
/* 11100000 = E0 = CSA+CADS */
/* 11110000 = F0 = CSA+CADS+CHANGEKEY */
IF SMF30_RAXFLAGS='90'X THEN USERKEY='CHGKEY' ;
IF SMF30_RAXFLAGS='A0'X THEN USERKEY='CADS' ;
IF SMF30_RAXFLAGS='B0'X THEN USERKEY='CADS+CHGKEY' ;
IF SMF30_RAXFLAGS='C0'X THEN USERKEY='CSA' ;
IF SMF30_RAXFLAGS='D0'X THEN USERKEY='CSA+CHGKEY' ;
IF SMF30_RAXFLAGS='E0'X THEN USERKEY='CSA+CADS' ;
IF SMF30_RAXFLAGS='F0'X THEN USERKEY='CSA+CADS+CHGKEY' ;
RUN;
PROC MEANS DATA=LIMIT SUM NWAY MISSING NONOBS PRINT;
CLASS SYSTEM JOB PROGRAM SMF30_RAXFLAGS USERKEY;
VAR CPUTM;
OUTPUT OUT=POSTAV1(DROP=_TYPE_) SUM = GCPU ;

PROC PRINT DATA=POSTAV1;
TITLE 'SMF30_USERKEY';
ID SYSTEM PROGRAM SMF30_RAXFLAGS USERKEY ;
VAR JOB;
RUN;

_________________________________________________________________
Dave Jousma
Manager Mainframe Engineering, Assistant Vice President
***@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-***@LISTSERV.UA.EDU] On Behalf Of Ron hawkins
Sent: Wednesday, April 25, 2018 9:52 AM
To: IBM-***@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**

Carmen,

Indeed, David would have to have a copy of MXG to use the SAS code that you shared.

That was my point: you didn't share MXG code.

Ron

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

I've never had an issue, or Barry has never had an issue with me sharing code, David would indeed need to have SAS or WPS and MXG to make my samples work.



Carmen Vitullo

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

From: "Ron hawkins" <***@SBCGLOBAL.NET>
To: IBM-***@LISTSERV.UA.EDU
Sent: Wednesday, April 25, 2018 1:57:15 AM
Subject: Re: OA53355 - USERKEY COMMON MIGRATION SUPPORT

David,

If there us an MXG program to run through this, then it will be in the product SOURCLIB.

I don't think anyone can share MXG with you if you don't have it licensed already.

I'm not trying to be a dick about it, and you may have just meant to say SAS. It just seemed like an odd request.

Ron

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-***@LISTSERV.UA.EDU> On Behalf Of Jousma, David
Sent: Tuesday, April 24, 2018 11:47 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: [IBM-MAIN] 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 ***@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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

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


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

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
Carmen Vitullo
2018-04-27 13:19:01 UTC
Permalink
Very nice, now if I only has SAS/MXG again :(
thank you



Carmen Vitullo

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

From: "David Jousma" <000001a0403c5dc1-dmarc-***@LISTSERV.UA.EDU>
To: IBM-***@LISTSERV.UA.EDU
Sent: Friday, April 27, 2018 8:16:56 AM
Subject: Re: OA53355 - USERKEY COMMON MIGRATION SUPPORT

Thought I'd share the SAS/MXG code that one of my team mates whipped up. We already rollup SMF30's into a daily PDB, so it's just pulling from that. I'll run it weekly until the report is empty.

DATA LIMIT;
SET PDB1.SMFINTRV PDB2.SMFINTRV PDB3.SMFINTRV PDB4.SMFINTRV
PDB5.SMFINTRV PDB6.SMFINTRV PDB7.SMFINTRV ;
IF CPUTM NE . ;
IF SMF30_RAXFLAGS='80'X THEN DELETE;
/* 10000000 = 80 = AUDIT ON */
/* 10010000 = 90 = CHANGE KEY */
/* 10100000 = A0 = CADS USAGE */
/* 10110000 = B0 = CADS+CHANGE KEY */
/* 11000000 = C0 = CSA USAGE */
/* 11010000 = D0 = CSA+CHANGE KEY */
/* 11100000 = E0 = CSA+CADS */
/* 11110000 = F0 = CSA+CADS+CHANGEKEY */
IF SMF30_RAXFLAGS='90'X THEN USERKEY='CHGKEY' ;
IF SMF30_RAXFLAGS='A0'X THEN USERKEY='CADS' ;
IF SMF30_RAXFLAGS='B0'X THEN USERKEY='CADS+CHGKEY' ;
IF SMF30_RAXFLAGS='C0'X THEN USERKEY='CSA' ;
IF SMF30_RAXFLAGS='D0'X THEN USERKEY='CSA+CHGKEY' ;
IF SMF30_RAXFLAGS='E0'X THEN USERKEY='CSA+CADS' ;
IF SMF30_RAXFLAGS='F0'X THEN USERKEY='CSA+CADS+CHGKEY' ;
RUN;
PROC MEANS DATA=LIMIT SUM NWAY MISSING NONOBS PRINT;
CLASS SYSTEM JOB PROGRAM SMF30_RAXFLAGS USERKEY;
VAR CPUTM;
OUTPUT OUT=POSTAV1(DROP=_TYPE_) SUM = GCPU ;

PROC PRINT DATA=POSTAV1;
TITLE 'SMF30_USERKEY';
ID SYSTEM PROGRAM SMF30_RAXFLAGS USERKEY ;
VAR JOB;
RUN;

_________________________________________________________________
Dave Jousma
Manager Mainframe Engineering, Assistant Vice President
***@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-***@LISTSERV.UA.EDU] On Behalf Of Ron hawkins
Sent: Wednesday, April 25, 2018 9:52 AM
To: IBM-***@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**

Carmen,

Indeed, David would have to have a copy of MXG to use the SAS code that you shared.

That was my point: you didn't share MXG code.

Ron

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

I've never had an issue, or Barry has never had an issue with me sharing code, David would indeed need to have SAS or WPS and MXG to make my samples work.



Carmen Vitullo

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

From: "Ron hawkins" <***@SBCGLOBAL.NET>
To: IBM-***@LISTSERV.UA.EDU
Sent: Wednesday, April 25, 2018 1:57:15 AM
Subject: Re: OA53355 - USERKEY COMMON MIGRATION SUPPORT

David,

If there us an MXG program to run through this, then it will be in the product SOURCLIB.

I don't think anyone can share MXG with you if you don't have it licensed already.

I'm not trying to be a dick about it, and you may have just meant to say SAS. It just seemed like an odd request.

Ron

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-***@LISTSERV.UA.EDU> On Behalf Of Jousma, David
Sent: Tuesday, April 24, 2018 11:47 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: [IBM-MAIN] 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 ***@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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

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


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

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@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 ***@listserv.ua.edu with the message: INFO IBM-MAIN


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Ravi Gaur
2018-04-25 11:39:45 UTC
Permalink
if you are licensed for SAS/MXG it's easy to get PDB created as below :

//STEP1 EXEC MXGSAS,WORK='1600,1600'
//LIBRARY DD DISP=SHR,DSN=XXXXX.MXG.FORMATS
//SMF DD DISP=SHR,DSN=XXXXX
//PDB DD DSN=XXXXXXX.PDB.TYPE30,DISP=(NEW,CATLG),
// UNIT=SYSDA,SPACE=(CYL,(100,50))
//SYSIN DD *
%INCLUDE SOURCLIB(VMACSMF,VMAC30,IMACKEEP);
DATA
_VAR30
_SMF
_CDE30
_S30
RUN;
PROC COPY IN=WORK OUT=PDB;
//


Then use that pdb to generate whatever report you like (including USERKEYALLOW) - It's just an example however to look at what variables you need in output etc you should look at MXG.SOURCLIB (ADOC30)

//STEP1 EXEC MXGSAS,WORK='1600,1600'
//WORK DD UNIT=SYSDA,SPACE=(CYL,(150,50))
//LIBRARY DD DISP=SHR,DSN=SYS3A.MXG.FORMATS
//PDB DD DISP=OLD,DSN=XXXXXXX.PDB.XXXX
//SOURCLIB DD DISP=SHR,DSN=SYS3A.MXG.SOURCLIB
//SYSIN DD *
options nodate ps=max nocenter ls=255;
data job_rpt;
set pdb.type30_5;
date_read = datepart(readtime);
time_read = timepart(readtime);
time_Init = timepart(jinitime);
format time_read time5.0 date_read date7. SMF30HQT time12.2
smf30sqt time12.2 time_init time5.0;
dprty=input(put(dprty,hex4.),hex4.);
if job =:'xxxxxx';
proc sort data=job_rpt nodupkey out=job_rpt1;
by descending smf30sqt;
run;
proc print data=job_rpt1 noobs split='/';
var date_read time_read time_Init job jesnr jobclass rptclass
smf30hqt smf30pfl smf30rqt smf30sqt;
title 'PCRBST Job Report For Time(01:00-04:30ET)';
label
job = 'Job-Name'
time_read = 'Job-In/Time'
time_init = 'Job-Start/Time'
DPRTY = 'Dispatch/Priority'
Jesnr = 'Job/Number'
Jobclass = 'Job/Class'
Rptclass = 'Wlm/Reporting Class'
SMF30HQT = 'Job Class/Queue Hold'
SMF30PFL = 'Job/Scheduling Env '
SMF30RQT = 'Ineligible Due to System/scheduling environment'
SMF30SQT = 'Waited for WLM/Initiator';
run ;



Now We have DIAGxx member which is SET after IPL and also during shutdown which has ALLOWUSERKEYCSA(NO) so that overcome what would be restricted with 2.3.
VSM ALLOWUSERKEYCSA(NO)

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Jousma, David
2018-04-25 11:51:09 UTC
Permalink
Thanks Ravi for the starting point! And yes, that’s the point I want to get too. But I know I have at least one long running task using userkeycsa that needs to be retired.

_________________________________________________________________
Dave Jousma
Manager Mainframe Engineering, Assistant Vice President
***@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-***@LISTSERV.UA.EDU] On Behalf Of Ravi Gaur
Sent: Wednesday, April 25, 2018 7:41 AM
To: IBM-***@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**

if you are licensed for SAS/MXG it's easy to get PDB created as below :

//STEP1 EXEC MXGSAS,WORK='1600,1600'
//LIBRARY DD DISP=SHR,DSN=XXXXX.MXG.FORMATS
//SMF DD DISP=SHR,DSN=XXXXX
//PDB DD DSN=XXXXXXX.PDB.TYPE30,DISP=(NEW,CATLG),
// UNIT=SYSDA,SPACE=(CYL,(100,50))
//SYSIN DD *
%INCLUDE SOURCLIB(VMACSMF,VMAC30,IMACKEEP);
DATA
_VAR30
_SMF
_CDE30
_S30
RUN;
PROC COPY IN=WORK OUT=PDB;
//


Then use that pdb to generate whatever report you like (including USERKEYALLOW) - It's just an example however to look at what variables you need in output etc you should look at MXG.SOURCLIB (ADOC30)

//STEP1 EXEC MXGSAS,WORK='1600,1600'
//WORK DD UNIT=SYSDA,SPACE=(CYL,(150,50))
//LIBRARY DD DISP=SHR,DSN=SYS3A.MXG.FORMATS
//PDB DD DISP=OLD,DSN=XXXXXXX.PDB.XXXX
//SOURCLIB DD DISP=SHR,DSN=SYS3A.MXG.SOURCLIB
//SYSIN DD *
options nodate ps=max nocenter ls=255;
data job_rpt;
set pdb.type30_5;
date_read = datepart(readtime);
time_read = timepart(readtime);
time_Init = timepart(jinitime);
format time_read time5.0 date_read date7. SMF30HQT time12.2
smf30sqt time12.2 time_init time5.0;
dprty=input(put(dprty,hex4.),hex4.);
if job =:'xxxxxx';
proc sort data=job_rpt nodupkey out=job_rpt1;
by descending smf30sqt;
run;
proc print data=job_rpt1 noobs split='/';
var date_read time_read time_Init job jesnr jobclass rptclass
smf30hqt smf30pfl smf30rqt smf30sqt;
title 'PCRBST Job Report For Time(01:00-04:30ET)';
label
job = 'Job-Name'
time_read = 'Job-In/Time'
time_init = 'Job-Start/Time'
DPRTY = 'Dispatch/Priority'
Jesnr = 'Job/Number'
Jobclass = 'Job/Class'
Rptclass = 'Wlm/Reporting Class'
SMF30HQT = 'Job Class/Queue Hold'
SMF30PFL = 'Job/Scheduling Env '
SMF30RQT = 'Ineligible Due to System/scheduling environment'
SMF30SQT = 'Waited for WLM/Initiator';
run ;



Now We have DIAGxx member which is SET after IPL and also during shutdown which has ALLOWUSERKEYCSA(NO) so that overcome what would be restricted with 2.3.
VSM ALLOWUSERKEYCSA(NO)

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
Tom Russell
2018-04-26 21:46:06 UTC
Permalink
Post by Jousma, David
So, has anyone written a SAS/MXG program to read through these SMF30 records
yet, that they would care to share?

I have written a Rexx program that I use to extract data from SMF30s. After running a test job stream, I use it to extract some data into a CSV file for Excel, but I "say" several extra fields if I run it verbosely. Not every field in the SMF T30 is extracted, but the structure is clear, and extensions are fairly easy to add. It's a bit of a Heathkit but it does print the new RAX values if they are non-zero. Drop me a note if you want a copy.

Cheers, Tom

G. Tom Russell “Stay calm. Be brave. Wait for the signs” — Jasper FriendlyBear
“… and remember to leave good news alone.” — Gracie HeavyHand

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Barry Merrill
2018-04-27 20:40:08 UTC
Permalink
Change 35.212 Support for SMF 30 User Key CSA Audit Enhancements adds
VMAC30 new SMF30_RAXFLAGS to TYPE30_1, TYPE30_V, TYPE30_4 and
Sep 28, 2017 the TYPE30_5 datasets. This code change has been in MXG
Feb 28, 2018 35.09 and later, but this change text replaced previous
"Reserved Change" on Feb 28, 2018. This field was added
by APAR OA53355, but will only be needed thru z/OS 2.3,
as User Key Common Storage usage support ends there.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On
Behalf Of Jousma, David
Sent: Tuesday, April 24, 2018 1:47 PM
To: IBM-***@LISTSERV.UA.EDU
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 ***@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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Edward Finnell
2018-05-04 21:30:03 UTC
Permalink
IIRC the ANAL30DD was a user contributed pgm. Without too much labor it was modified to produce several very handy reports. Seems like IBM would produce a SORT solution for reporting USER key usage. The SLIP on a z14 reduces it from boogity, boogity to boog, boog, boog-single step instruction mode? 


In a message dated 4/27/2018 3:41:49 PM Central Standard Time, ***@MXG.COM writes:

 
Change 35.212 Support for SMF 30 User Key CSA Audit Enhancements adds

VMAC30 new SMF30_RAXFLAGS to TYPE30_1, TYPE30_V, TYPE30_4 and
Sep 28, 2017 the TYPE30_5 datasets. This code change has been in MXG

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Andrew Rowley
2018-05-03 01:38:52 UTC
Permalink
Post by Jousma, David
So, has anyone written a SAS/MXG program to read through these SMF30 records yet, that they would care to share?
I have added a program to the EasySMF Java samples to do this. In Java
it looks like this:

import java.io.*;
import com.blackhillsoftware.smf.SmfRecord;
import com.blackhillsoftware.smf.SmfRecordReader;
import com.blackhillsoftware.smf.smf30.Smf30Record;

public class UserKeyCommon
{
    public static void main(String[] args) throws IOException
    {
        try (SmfRecordReader reader = SmfRecordReader.fromDD("INPUT"))
        {
            reader.include(30);
            boolean foundAuditEnabled = false;
            int userKeyCommonFound = 0;
            for (SmfRecord record : reader)
            {
                Smf30Record r30 = new Smf30Record(record);
                if (r30.storageSection() != null)
                {
                    if (!foundAuditEnabled &&
r30.storageSection().smf30UserKeyCommonAuditEnabled())
                    {
                        foundAuditEnabled = true;
                    }
                    if
(r30.storageSection().smf30UserKeyCommonAuditEnabled()
                        && (r30.storageSection().smf30UserKeyCsaUsage()
                            || r30.storageSection().smf30UserKeyCadsUsage()
                            ||
r30.storageSection().smf30UserKeyChangKeyUsage()))
                    {
                        userKeyCommonFound++;
                        System.out.format(
                            "%-23s %-4s %-8s %-8s %-10s %-10s %-10s%n",
                            r30.smfDateTime(),
                            r30.system(),
r30.identificationSection().smf30jbn(),
r30.identificationSection().smf30jnm(),
r30.storageSection().smf30UserKeyCsaUsage() ? "CSA" : "",
r30.storageSection().smf30UserKeyCadsUsage() ? "CADS" : "",
r30.storageSection().smf30UserKeyChangKeyUsage() ? "KEYCHANGE" : "");
                    }
                }
            }
            if (!foundAuditEnabled)
            {
                System.out.println("No records found with User Key
Common Audit Enabled!");
            }
            else
            {
                System.out.format("%d records flagged%n",
userKeyCommonFound);
            }
        }
    }
}

I don't have any data where user key common is in use but I have tested
it as well as I can without that.

There is a 30 day trial available if anyone wants to try it out on their
system:
https://www.blackhillsoftware.com/30-day-trial/

Andrew Rowley
--
Andrew Rowley
Black Hill Software
+61 413 302 386

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