Thanks
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jousma, David Sent: Wednesday, May 16, 2018 8:23 AM To: [email protected] Subject: Re: UserKEY CSA/Dataspace scope=common Remdiation Pretty much as I posted, but here it is verbatim: "If you know the owning address space(s) of the data space(s) in question, and can get an SVC dump (a console dump will do) that includes those address spaces, RASP (ASID 3), and RASP's data spaces, then you can use the RSMDATA DSPACE ASID(xx) command to list out the data spaces owned by the specified ASID. That display will include information on SCOPE (you want "C" for common) and KEY for each data space listed." My console dump command was: Dump comm='dspace dump' R xx,jobname=(owningstc,rasp),dspname=('owningstc'.*,'rasp'.*),end IPCS took a bit to read the data, but came up with (some data masked): JOBNAME ASID DSP NAME OWNG TCB CUR B MAX B K T S R F TOT R DG DG -------- ---- -------- -------- ----- ----- - - - - - ----- -------- -------- xxxxxxxx 0132 xxxxxxxx 00AC6AD8 090F6 090F6 8 B C E Y 00877 00801B80 80003802 xxxxxxxx 0132 xxxxxxxx 00AC6E08 07DE4 07DE4 8 B C E Y 03B99 00800C00 80001902 xxxxxxxx 0132 xxxxxxxx 00AFC170 337FA 337FA 8 B C E Y 2188A 00807C80 8000FA00 _________________________________________________________________ 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 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Allan Staller Sent: Wednesday, May 16, 2018 8:42 AM To: [email protected] Subject: Re: UserKEY CSA/Dataspace scope=common Remdiation **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Can you post the instructions for all of us to use? -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jousma, David Sent: Wednesday, May 16, 2018 7:14 AM To: [email protected] Subject: Re: UserKEY CSA/Dataspace scope=common Remdiation Walt, and all... I was misreading/misunderstanding, relearning as I go.... As Walt correctly points out, when KEY is not specified on the DSPSERV CREATE, it does default to CALLERKEY. The program in question starts in KEY(8), and since we didn’t set a KEY on the MODE=SUP statement either, it defaulted to KEY(8). I did open a PMR with IBM, and the nice gentleman provided me with console dump instructions to dump both the address space that owns the Dataspaces in question, and RASP, and to include the DSPNAME from both asid's, and then run a RSMDATA DSPACE ASID(xx) command to get the details on the data spaces in question. That worked beautifully, and provided the data that I needed. _________________________________________________________________ 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 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Walt Farrell Sent: Tuesday, May 15, 2018 5:03 PM To: [email protected] Subject: Re: UserKEY CSA/Dataspace scope=common Remdiation **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** On Tue, 15 May 2018 16:53:33 +0000, Jousma, David <[email protected]> wrote: >Ok, quick eye-ball verification from the guru's that are better ASM programmer >than I... > >SMF30 RAXFLAGS is kicking out the a module for which I selectively pulled out >the DSPSERV code for allocating USERKEY SCOPE=COMMON Data space. Is it >possible that this line "DSPSERV DC A(*+4+X'80000000')" is what is setting >the storage key just prior to execution? i.e. KEY 8? I didn't create the >code, I'm just trying to understand it. > > MODESET MODE=SUP SET TO SUPERVISOR STATE > L R15,DSPSERV INSURE 31 BIT MODE > BSM 0,R15 SET 31 BIT MODE >DSPSERV DC A(*+4+X'80000000') >* > DSPSERV CREATE, CREATE A DATA SPACE > STOKEN=DSPSTOKN, PUT STOKEN HERE > NAME=DSPNAME, USE THIS NAME > ORIGIN=DSPORIGN, PLACE ORIGIN ADDRESS HERE > SCOPE=COMMON, COMMON DATA SPACE > BLOCKS=(DSPBLCKS,DSPBLCKS) THIS MAX AND INITIAL >* > ST R15,RETCODE SAVE THE RETURN CODE > ST R0,REASCODE SAVE THE REASON CODE > MODESET MODE=PROB SET TO PROBLEM PROGRAM STATE > > >Alternatively, I know the DataSpace names that are being allocated from a D >A,stcname. Again, this is territory I don't tread into often, but is there >an >easy way to determine the storage key of them? What key is your program running in? The default for DSPSERV CREATE (as I read the manual) is CALLERKEY, so if it's running in key 8 that would be your problem. -- Walt ---------------------------------------------------------------------- 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 ::DISCLAIMER:: -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------- 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
