Re: define a service class in wlm by batch
Unless the OP wants to define a serviceclass daily when Prodbatch starts and delete it when it is finished, to prevent illegal use. So again: what is the thought behind the question? Kees. > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Allan Staller > Sent: 28 September, 2018 15:43 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: define a service class in wlm by batch > > Short answer ... No. > Long answer. Yes, if you want to spend a lot more time than it will take > to do it from within the WLM dialog. > > HTH > > -Original Message- > From: IBM Mainframe Discussion List On Behalf > Of Jason Cai > Sent: Thursday, September 27, 2018 10:13 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: define a service class in wlm by batch > > Hi all > > Could we define a service class in WLM by batch job? Thanks a lot! > > > > Best Regards, > Jason Cai > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
CAVMEN Revival Meeting October 18 - FIRST NOTICE
Greetings, The fourth quarter revival meeting of the Chicago Area VM (and Linux) Enthusiasts will be held on Thursday, October 18. Meeting Location: This quarter's meeting will once again be held at Alight (formerly AON Hewitt) West Campus' located at 4 Overlook Point, in Lincolnshire, IL (same location as previously) . I do not currently have instructions for entry, so please pay attention to future e-mails. Please be attentive to where you park and where you attempt to enter the building.Security has been instructed to send you to the correct entrance. If you have not attended a meeting at this location before and do not know the location of this entrance, please go to www.cavmen.org . Check the links out!!! There is a lot of information on the this site for your benefit!!! Attendance: We would like to request a count of expected attendees by the Monday before the meeting, so that we may plan appropriately for arranging the facilities.ch. If you are planning to attend, PLEASE send an E-Mail by that date to jslav...@comcast.net with a subject line of "Meeting Attendance". This is meant to be a facilities planning aid and should not be interpreted as a registration requirement. If you suddenly become available at the last minute, please feel free to attend even if you have not responded. Thank you in advance for your cooperation in this matter. It is only necessary to reply once concerning attendance. Meeting Agenda: TBA. It will include Bruce Hayden of IBM, Rich Smrcina of Velocity Software and myself. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ICSF crypto domain sharing
Frank, You did your job by entering same master keys. Now, different domain are "compatible" - then can share CKDS/PKDS. You wanted to share domain, which is impossible (and that's good IMHO). Of course there another story behind,: should one share crypto between prod and dev? We just answered how it's possible, not is it recommended. Regards -- Radoslaw Skorupka Lodz, Poland W dniu 2018-09-28 o 20:34, Frank Swarbrick pisze: Let me explain a bit more what I was trying to ask. We have 3 LPARs (production, dev/test, sandbox) on the same CPC. Sandbox up to this point did not have master keys loaded. We quickly needed to load some, so I recommended we use the same keys as dev/test. I had hoped that we could have Sandbox use the same crypto domain as dev/test; thus the question. I ended up just loading the same keys, rather than attempting to "share" the same domain. But I still wondered if the latter could be done. It sounds like you are saying no. From: IBM Mainframe Discussion List on behalf of R.S. Sent: Friday, September 28, 2018 8:43 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ICSF crypto domain sharing W dniu 2018-09-28 o 12:54, Jousma, David pisze: Yes, they can be shared. Our PROD lpars are all on the same domain. IMHO no, domains cannot be shared. Maybe your prod LPARs reside on different CPC each? Some remarks: 1. Single LPAR can have more than one domain, but z/OS ICSF can use only one at a time. However you can change domain number in PARMLIB and recycle ICSF. 2. Domain number cannot be assigned to more than one active LPAR. Deactivated LPARs could share domain id. 3. In the old days it was possible to have i.e. 40 LPARs and number of domains was 16. In that case More crypto engines were needed, for example Crypto 1 and 3 were assigned to LPARs 01-0F, Crypto engines 2 and 4 were assigned to LPARs 10-1F and remaining LPARs had no access to Crypto engines (CPACF is not affected). In that case LPAR 01 and LPAR 11 may have Domain Id 2 assigned, but on separated Crypto engines. 4. It is impossible to have i.e. Domain 12 on Crypto1 and Domain 07 on Crypto2 at a time. 5. It is also possible to have the same master keys on different domains (and even different CPCs) - in that case, CKDS/PKDS can be shared/copied between that systems. -- Radoslaw Skorupka Lodz, Poland == Jeśli nie jesteś adresatem tej wiadomości: - powiadom nas o tym w mailu zwrotnym (dziękujemy!), - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś na dysku). Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać karze. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2018 r. wynosi 169.248.488 złotych. If you are not the addressee of this message: - let us know by replying to this e-mail (thank you!), - delete this message permanently (including all the copies which you have printed out or saved). This message may contain legally protected information, which may be used exclusively by the addressee.Please be reminded that anyone who disseminates (copies, distributes) this message or takes any similar action, violates the law and may be penalised. == Jeśli nie jesteś adresatem tej wiadomości: - powiadom nas o tym w mailu zwrotnym (dziękujemy!), - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś na dysku). Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać karze. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2018 r. wynosi 169.248.488 złotych. If you are not the addressee of this message: - let us know by replying to this e-mail (thank you!), - delete this message permanently (including all the copies which you have printed out or saved). This message may contain legally protected information, which may be used exclusively by the addressee.Please be reminded that anyone who disseminates (copies, distributes) this message or takes any similar action, violates the law and may be penalised. mBank
