Re: OT: AMD Eypc processor -- RAM encrypt/decrypt built in
On Wed, May 09, 2018 at 08:29:14AM -0500, John McKown wrote: > This is interesting. Reminds me a bit of IBM's newest "Pervasive > Encryption". > > https://www.theregister.co.uk/2017/06/20/amd_epyc_launch/ > [...] > > You simply cannot effectively read one VM's memory contents from a > different VM. And you can't read data even if you have some sort of "rogue" > PCIe card installed to "sniff" the PCIe bus because the data on the bus is > encrypted. This bird seems to be dead, too (so it is not going to fly very far): - SEVered: Subverting AMD's Virtual Machine Encryption https://arxiv.org/abs/1805.09604v1 -- Regards, Tomasz Rola -- ** A C programmer asked whether computer had Buddha's nature. ** ** As the answer, master did "rm -rif" on the programmer's home** ** directory. And then the C programmer became enlightened... ** ** ** ** Tomasz Rola mailto:tomasz_r...@bigfoot.com ** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: How to get BPX loadhfs (BPX1LOD) to load module into writable memory?
Allowing reentrant programs to be writable for fetches from non-APF-authorized data sets / concatenations was something that had to be maintained for compatibility, but was not felt to have sufficient justification to accommodate for "new cases". "New cases" include loads via BPX1LOD and loads in a task that was attached with KEY=NINE. Those cases do not care about the APF state of the data set / concatenation when determining the subpool. The newer of those "new cases" is almost 20 years old now. Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: empty KSDS behavior - why?
Exactly. Presumably less overhead to just set the pointer (or whatever) rather than actually loading and deleting a record. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Sunday, May 27, 2018 10:38 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: empty KSDS behavior - why? On Sun, 27 May 2018 22:46:52 -0500, Edward Gould wrote: >> On May 27, 2018, at 8:51 PM, Charles Mills wrote: >> >> Exactly. I am no VSAM guy ... but whatever magic you have to do manually go >> get the VSAM file to be readable, why can't AMS just do that when it creates >> the file? Is there any reason anyone would want a "virginal" (unreadable) >> VSAM file specifically? >> >> How many ABENDs, how many application problems, how many stupid little >> customer fixup programs and PROCs could have been saved if AMS just did that >> from the get-go? >> >> Or am I missing something? As I say, I am no VSAM guy. >> >I like many others feel your pain. I can understand it in a way, say a KSDS >and (in your world) VSAM automagically adds a record. What key would IBM >possibly use that high end up without it being a duplicate key. RRDS would >automatically loose 1 record as the first record would be ??. IBM decided (I >think) to take it as its *YOUR* dataset and its up to you to prime it. > No, no! The suggestion was that it should automagically add one record, *then*delete*it*. (Others have said this suffices.) Or, in a shortcut initialize the data set in such a state. Once the record is gone, it doesn't matter what the key was. There's nothing for any record subsequently inserted to be a duplicate key of. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Performance impact of using DFSMS's Data Set Separation feature?
W dniu 2018-05-28 o 12:16, Peter Hunkeler pisze: I've been asked by my storage colleagues if I knew the impact of using DFSMS's Data Set Separation feature. I don't. Does anyone used it? Any pros and cons to share? While the number of data sets to keep separated is low, SMS will still need to search the list for *every* new allocation. How significant is the performance impact of this? AFAIK it wants to use separate controllers => separated DASD arrays nowadays. It is not applicable when you have one DASD box (which is not uncommon) and hardly reasonable in other cases. -- Radoslaw Skorupka Lodz, Poland == -- Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorized to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: kont...@mbank.plsąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2018 r. kapitał zakładowy mBanku S.A. (w całości wpłacony) wynosi 169.248.488 złotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Performance impact of using DFSMS's Data Set Separation feature?
I've been asked by my storage colleagues if I knew the impact of using DFSMS's Data Set Separation feature. I don't. Does anyone used it? Any pros and cons to share? While the number of data sets to keep separated is low, SMS will still need to search the list for *every* new allocation. How significant is the performance impact of this? -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
