Yep, that worked for me as well. On Fri, May 18, 2018 at 9:28 AM Jousma, David < [email protected]> wrote:
> Although a SET DIAG=00 when coding the same parm without the VSM on the > front of it. And a D DIAG shows > > IGV007I 10.27.59 DIAG DISPLAY 034 > VSM TRACK CSA(ON) SQA(ON) > VSM TRACE GET(OFF) FREE(OFF) > VSM CHECKREGIONLOSS(665K,50M) > VSM ALLOWUSERKEYCSA(YES) > VSM BESTFITCSA(NO) > VSM USEZOSV1R9RULES(YES) > TRAPS NAME() > CBLOC > VIRTUAL24() > VIRTUAL31() > REUSASID(YES) > ALLOWUSERKEYCADS(NO) > AUTOIPL SADMP(NONE) MVS(NONE) > FREEMAINEDFRAMES(YES) > FF31HIGH(YES) > > _________________________________________________________________ > Dave Jousma > Manager Mainframe Engineering, Assistant Vice President > [email protected] > 1830 East Paris, Grand Rapids, MI 49546 > <https://maps.google.com/?q=1830+East+Paris,+Grand+Rapids,+MI%C2%A0+49546&entry=gmail&source=g> > MD RSCB2H > p 616.653.8429 > f 616.653.2717 > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Jousma, David > Sent: Friday, May 18, 2018 10:23 AM > To: [email protected] > Subject: Re: [EXTERNAL] Re: IBMVSM,ZOSMIGV2R3_NEXT_VSM_USERKEYCOMM > > **CAUTION EXTERNAL EMAIL** > > **DO NOT open attachments or click on links from unknown senders or > unexpected emails** > > Yes, failed for me on V2.3 > > IEE252I MEMBER DIAG00 FOUND IN SYS1.PARMLIB > ASA003I SYNTAX ERROR IN PARMLIB MEMBER=DIAG00 ON LINE 31, 018 > POSITION 6: ALLOWUSERKEYCADS WAS SEEN, WHERE ONE OF > (DETECT PROTECT CHECKREGIONLOSS TRACE > TRACK PRIVATEBUFFER ALLOWUSERKEYCSA USEZOSV1R9RULES > BESTFITCSA) > WOULD BE CORRECT. > DETECTING MODULE IS IGVDITMS. INPUT LINE: > VSM ALLOWUSERKEYCADS(NO) > IEE536I DIAG VALUE 00 NOW IN EFFECT > > _________________________________________________________________ > Dave Jousma > Manager Mainframe Engineering, Assistant Vice President > [email protected] > 1830 East Paris, Grand Rapids, MI 49546 > <https://maps.google.com/?q=1830+East+Paris,+Grand+Rapids,+MI%C2%A0+49546&entry=gmail&source=g> > MD RSCB2H p 616.653.8429 f 616.653.2717 > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Michael Babcock > Sent: Friday, May 18, 2018 10:19 AM > To: [email protected] > Subject: Re: [EXTERNAL] Re: IBMVSM,ZOSMIGV2R3_NEXT_VSM_USERKEYCOMM > > **CAUTION EXTERNAL EMAIL** > > **DO NOT open attachments or click on links from unknown senders or > unexpected emails** > > This keyword was not accepted by my z/OS 2.2 system when I did a SET DIAG= > > VSM ALLOWUSERKEYCADS(NO) > > On Fri, May 18, 2018 at 6:06 AM Jousma, David < > [email protected]> wrote: > > > Thanks Jim! > > > > _________________________________________________________________ > > Dave Jousma > > Manager Mainframe Engineering, Assistant Vice President > > [email protected] > > 1830 East Paris, Grand Rapids, MI 49546 > > <https://maps.google.com/?q=1830+East+Paris,+Grand+Rapids,+MI%C2%A0+49 > > 546&entry=gmail&source=g> > > MD RSCB2H > > p 616.653.8429 > > f 616.653.2717 > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] > > On Behalf Of Jim Mulder > > Sent: Thursday, May 17, 2018 6:43 PM > > To: [email protected] > > Subject: Re: [EXTERNAL] Re: IBMVSM,ZOSMIGV2R3_NEXT_VSM_USERKEYCOMM > > > > **CAUTION EXTERNAL EMAIL** > > > > **DO NOT open attachments or click on links from unknown senders or > > unexpected emails** > > > > It was implemented in z/OS 1.11, and disclosed it to the ISVs, but > > it was not documented at that time because it would not be useful to > > customers until software vendors had time to get their products into > compliance. > > > > Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. > > Poughkeepsie NY > > > > IBM Mainframe Discussion List <[email protected]> wrote on > > 05/17/2018 06:58:28 AM: > > > > > From: "Jousma, David" > > > <[email protected]> > > > To: [email protected] > > > Date: 05/17/2018 06:35 PM > > > Subject: Re: [EXTERNAL] Re: IBMVSM,ZOSMIGV2R3_NEXT_VSM_USERKEYCOMM > > > Sent by: IBM Mainframe Discussion List <[email protected]> > > > > > > Jim, > > > > > > You said: > > > > > > On any currently supported release of z/OS, in DIAGxx, you can > > > specify > > > > > > ALLOWUSERKEYCADS(NO) > > > > > > > > > I don't see that in Init & Tuning? Is this an undocumented option? > > > > > > _________________________________________________________________ > > > Dave Jousma > > > Manager Mainframe Engineering, Assistant Vice President > > > [email protected] > > > 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f > > > 616.653.2717 > > > > > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to [email protected] 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 [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to [email protected] 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 [email protected] 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 [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
