Re: DFSMSRMM Server/Client setup
Mark, Like I said in my other post, the requirement for the OMVS segment is documented in the Coms Server: IP Configuration Guide. There is nothing about that need for OMVS segment in the rmm books. There will be a reminder added into the IC C/S implementation steps with a pointer to the Coms Server IP Conf Guide for the next release of our books. Mike Wood RMM Development On Tue, 6 May 2008 08:46:56 -0400, Mark Pace [EMAIL PROTECTED] wrote: Thanks, Mike - I don't have to, or want to share the TCDB any longer, I just wanted to be sure that it would continue to work. Where can I find documentation on setting up the OMVS segment for RMM? I didn't find it in the Implementation guide. Mark Pace -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DFSMSRMM Server/Client setup
Mark, Although we would expect a client and its server to not be sharing the TCDB, theoretically you could do that. However, since one main driver for client/server is that there is no shared DASD, usuallly there is no other DASD sharing. RMM has no default PORT, that is a mandatory operand within the CLIENT and SERVER operands on the OPTION command in parmlib. Mike Wood RMM Development On Fri, 2 May 2008 13:21:29 -0400, Mark Pace [EMAIL PROTECTED] wrote: What happens with OAM and the VOLCAT when you run in a Client/Server configuration? I'm currently running 2 LPARs sharing the VOLCAT and the RMM files. Will I still need to share the VOLCAT between the 2 systems? I've also been unable to find the default port that RMM will use on TCPIP. -- Mark Pace Mainline Information Systems -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DFSMSRMM Server/Client setup
Thanks, Mike - I don't have to, or want to share the TCDB any longer, I just wanted to be sure that it would continue to work. Where can I find documentation on setting up the OMVS segment for RMM? I didn't find it in the Implementation guide. On Tue, May 6, 2008 at 8:29 AM, Mike Wood [EMAIL PROTECTED] wrote: Mark, Although we would expect a client and its server to not be sharing the TCDB, theoretically you could do that. However, since one main driver for client/server is that there is no shared DASD, usuallly there is no other DASD sharing. RMM has no default PORT, that is a mandatory operand within the CLIENT and SERVER operands on the OPTION command in parmlib. Mike Wood RMM Development On Fri, 2 May 2008 13:21:29 -0400, Mark Pace [EMAIL PROTECTED] wrote: What happens with OAM and the VOLCAT when you run in a Client/Server configuration? I'm currently running 2 LPARs sharing the VOLCAT and the RMM files. Will I still need to share the VOLCAT between the 2 systems? I've also been unable to find the default port that RMM will use on TCPIP. -- Mark Pace Mainline Information Systems -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- Mark Pace Mainline Information Systems -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DFSMSRMM Server/Client setup
Mark, You are correct we do not document that requirement within the rmm pubs. The requirement is here http://publibz.boulder.ibm.com/cgi- bin/bookmgr_OS390/BOOKS/f1a1b370/1.2.11.1? SHELF=EZ2ZO10J.bksDT=20070604150102 in the Comm Svr: IP Configuration Guide. Mike Wood RMM Development On Mon, 5 May 2008 11:20:40 -0400, Mark Pace [EMAIL PROTECTED] wrote: I also can not find in the Implementation Guide anything about the OMVS segment that is required. Is that documented elsewhere? -- Mark Pace Mainline Information Systems -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DFSMSRMM Server/Client setup
I also can not find in the Implementation Guide anything about the OMVS segment that is required. Is that documented elsewhere? -- Mark Pace Mainline Information Systems -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DFSMSRMM Server/Client setup
What happens with OAM and the VOLCAT when you run in a Client/Server configuration? I'm currently running 2 LPARs sharing the VOLCAT and the RMM files. Will I still need to share the VOLCAT between the 2 systems? I've also been unable to find the default port that RMM will use on TCPIP. -- Mark Pace Mainline Information Systems -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DFSMSRMM Server/Client setup
Crispin, The most likely reason for this is that you have missing coexistance/toleration maintenance. Refer to the z/OS Migration book and PSP buckets for the releases you plan to bring in as clients for what toleration maintenance is required. Also, there were a couple of apars we shipped particularly to address certain aspects of a mixed client/server environment. There were pre-conditioning PTFs and then exploitation PTFs. Be sure to not be running exploitation on one system but missing pre-conditioning on others. (OA14136, OA16523, OA14717, OA16524) Mike WoodRMM Development On Mon, 28 Apr 2008 13:27:49 +0100, Crispin Hugo [EMAIL PROTECTED] wrote: I am trying to set up DFSMSRMM Server client support on a z/OS 1.7 system. The z/OS 1.7 is defined Server with another z/OS 1.7 system as client. There is NO pack/file sharing. This works fine. Should I be able to add to more clients that are z/OS 1.8 and z/OS 1.9 ? When DFSMSRMM starts on these other systems, it fails. . . . Crispin Hugo Systems Programmer Macro 4 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DFSMSRMM Server/Client setup
On Wed, 30 Apr 2008 09:38:55 +0100, Crispin Hugo [EMAIL PROTECTED] wrote: Hi There, Crispin, There are people out there with client/server implemented and they have been through from z/OS 1.6 to 1.9 mixing their environment as they go. The statement '...at least at this release level' is confusing - it originally meant V1.6 (and still does) but seen in a 1.8 or 1.9 book - confusing. We have fixed the book for z/OS V1.10 'All client and server systems must be at a currently supported release level.' You can share the CDS within a RMMplex, mixed, supported releases, with toleration/coexistance maintenance installed. RMMplex includes standard, server, and client systems. Mike Wood RMM Development Anybody out there using DFSMSRMM server/Client on systems that are using different levels of z/OS? The DFSMSRMM Implementation and Customization Guide has confusing statement in it. Which of these two are true ? 'All client and server systems must be at least at this release level. You can share the control data set with other systems that run any supported level of DFSMSrmm with any supported level of DFSMSrmm that has appropriate toleration maintenance installed. Crispin Hugo Systems Programmer Macro 4 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DFSMSRMM Server/Client setup
Hi There, Anybody out there using DFSMSRMM server/Client on systems that are using different levels of z/OS? The DFSMSRMM Implementation and Customization Guide has confusing statement in it. Which of these two are true ? 'All client and server systems must be at least at this release level. You can share the control data set with other systems that run any supported level of DFSMSrmm with any supported level of DFSMSrmm that has appropriate toleration maintenance installed. Crispin Hugo Systems Programmer Macro 4 Direct Line: +44 (0)1293 872121, Switchboard: +44 (0)1293 872000, Fax: +44 (0)1293 872001 This email has been scanned for all known viruses by the MessageLabs Email Security Service and the Macro 4 plc internal virus protection system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DFSMSRMM Server/Client setup
Hugo, We have shared the RMM environment across muliple releases of the operating system. Our SYSPROG, Test, and Production Sysplexes share RMM. Toleration maintenance allows this to operate fine. Contact me off list if you would like more info. Jimmy -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DFSMSRMM Server/Client setup [EMAIL PROTECTED]
I don't see any conflict in those statements. As I understand it, client/server doesn't share the control dataset, only the server accesses the CDS - the client makes requests through the server. Crispin Hugo [EMAIL PROTECTED] 4/30/2008 4:38 AM Hi There, Anybody out there using DFSMSRMM server/Client on systems that are using different levels of z/OS? The DFSMSRMM Implementation and Customization Guide has confusing statement in it. Which of these two are true ? 'All client and server systems must be at least at this release level. You can share the control data set with other systems that run any supported level of DFSMSrmm with any supported level of DFSMSrmm that has appropriate toleration maintenance installed. Crispin Hugo Systems Programmer Macro 4 Direct Line: +44 (0)1293 872121, Switchboard: +44 (0)1293 872000, Fax: +44 (0)1293 872001 This email has been scanned for all known viruses by the MessageLabs Email Security Service and the Macro 4 plc internal virus protection system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html Note that my email domain has changed from jo-annstores.com to joann.com. Please update your address book and other records to reflect this change. CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains confidential and privileged information intended only for the addressee. If you are not the intended recipient, please be advised that you have received this material in error and that any forwarding, copying, printing, distribution, use or disclosure of the material is strictly prohibited. If you have received this material in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the material. Emails are not secure and can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
DFSMSRMM Server/Client setup
I am trying to set up DFSMSRMM Server client support on a z/OS 1.7 system. The z/OS 1.7 is defined Server with another z/OS 1.7 system as client. There is NO pack/file sharing. This works fine. Should I be able to add to more clients that are z/OS 1.8 and z/OS 1.9 ? When DFSMSRMM starts on these other systems, it fails. EDG0204I DFSMSRMM BEING INITIALIZED FROM MEMBER EDGRMMPR IN PROD.SYS1.PA RMLIB EDG0362I TCP/IP COMMUNICATION SUCCESSFULLY INITIALIZED FOR CLIENT - HOST NAME ZOS19 ADDRESS 10.0.40.90 PORT NUMBER 2000 EDG0354I CONNECTION TO SERVER M4ZOSA SUCCESSFUL. IP ADDRESS 10.0.40.11 PORT NUMBER 2000 IEA794I SVC DUMP HAS CAPTURED: 805 DUMPID=011 REQUESTED BY JOB (DFRMM ) DUMP TITLE=EDGAMGR UNEXPECTED ERROR DETECTED BPXP018I THREAD 1E6207E1, IN PROCESS 83951749, ENDED 806 WITHOUT BEING UNDUBBED WITH COMPLETION CODE 88AE, AND REASON CODE . EDG0104E DFSMSRMM SUBSYSTEM INITIALIZATION FAILED Before I go through the dumps, just wanted to know if there were any restrictions that anyone knew of. Cheers Crispin Hugo Systems Programmer Macro 4 This email has been scanned for all known viruses by the MessageLabs Email Security Service and the Macro 4 plc internal virus protection system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
