Re: Portmap start task
Tim, We run HSC/Libstation for an EMC product called Alphastore and have not experienced any problems. We run our Port mapper at SC SYSSTC. Also while moving the Libstation to its own LPAR we discovered HSC needs the port mapper. One more thing about HSC 6.0. It does not support all the TCPIP.DATA keyword in z/OS 1.7 such as using SEARCH to replace DOMAINORIGIN. Regards, Listen. Think. Solve. Steve Wolf Rockwell Automation 414-382-4308 Leitner, Timothy [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 02/25/2008 01:42 PM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject Portmap start task All, Has anybody run into an issue with the portmap started task running in a default service class rather than sysstc like tcpip? We use STK (SUN) HSC and libstation and have had some odd things happening with our Veritas system. We have found that there will be a number (20-30) connections in TCPIP left for long periods of time all pointing back to the Veritas environment. We can drop the connections and things will clear up. Any ideas? Thanks. Tim Leitner OSF Healthcare System Manager, Technical Services 309-683-7452 == The information in this message is confidential and may be legally privileged. Access to this message by anyone other than the addressee is not authorized. If you are not the intended recipient, or an agent of the intended recipient, any disclosure, copying, or distribution of the message or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. If you have received this message in error, please contact the sender immediately and permanently delete the original e-mail, attachment(s), and any copies. == -- 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 -- 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
Portmap start task
All, Has anybody run into an issue with the portmap started task running in a default service class rather than sysstc like tcpip? We use STK (SUN) HSC and libstation and have had some odd things happening with our Veritas system. We have found that there will be a number (20-30) connections in TCPIP left for long periods of time all pointing back to the Veritas environment. We can drop the connections and things will clear up. Any ideas? Thanks. Tim Leitner OSF Healthcare System Manager, Technical Services 309-683-7452 == The information in this message is confidential and may be legally privileged. Access to this message by anyone other than the addressee is not authorized. If you are not the intended recipient, or an agent of the intended recipient, any disclosure, copying, or distribution of the message or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. If you have received this message in error, please contact the sender immediately and permanently delete the original e-mail, attachment(s), and any copies. == -- 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: Portmap start task
I also run libstation. We have hangs from the Veritas side. We have to stop/start Libstation to get things flowing again. It is a problem that we have never been able to resolve. At this time we are running an old release of HSC/Libstation but we have had this problem in more than one release. We have not been able to find any problems on the HSC side. It appears to be a Veritas problem, but we have not been able to confirm this. Pat Mihalec Rush University Medical Center Senior System Programmer (312) 942-8386 [EMAIL PROTECTED] Leitner, Timothy [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 02/25/2008 01:42 PM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject Portmap start task All, Has anybody run into an issue with the portmap started task running in a default service class rather than sysstc like tcpip? We use STK (SUN) HSC and libstation and have had some odd things happening with our Veritas system. We have found that there will be a number (20-30) connections in TCPIP left for long periods of time all pointing back to the Veritas environment. We can drop the connections and things will clear up. Any ideas? Thanks. Tim Leitner OSF Healthcare System Manager, Technical Services 309-683-7452 == The information in this message is confidential and may be legally privileged. Access to this message by anyone other than the addressee is not authorized. If you are not the intended recipient, or an agent of the intended recipient, any disclosure, copying, or distribution of the message or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. If you have received this message in error, please contact the sender immediately and permanently delete the original e-mail, attachment(s), and any copies. == -- 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 -- 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: Portmap start task
On Mon, 25 Feb 2008 13:42:48 -0600, Leitner, Timothy [EMAIL PROTECTED] wrote: All, Has anybody run into an issue with the portmap started task running in a default service class rather than sysstc like tcpip? We use STK (SUN) HSC and libstation and have had some odd things happening with our Veritas system. We have found that there will be a number (20-30) connections in TCPIP left for long periods of time all pointing back to the Veritas environment. We can drop the connections and things will clear up. Any ideas? Thanks. Who's default, STC or OMVS? Did you try and classify it? TCPIP may be classified or may be getting SYSSTC via PPT HIDP attribute. Or perhaps it needs to be classified under OMVS. We don't run it here so I am not sure how it runs (and didn't research). Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- 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: Portmap start task
-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Leitner, Timothy Sent: Monday, February 25, 2008 1:43 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Portmap start task All, Has anybody run into an issue with the portmap started task running in a default service class rather than sysstc like tcpip? We use STK (SUN) HSC and libstation and have had some odd things happening with our Veritas system. We have found that there will be a number (20-30) connections in TCPIP left for long periods of time all pointing back to the Veritas environment. We can drop the connections and things will clear up. Any ideas? Thanks. Tim Leitner We run PORTMAP in a service class called DAEMON. Its WLM classification is Importance=1, velocity=50. I have __no__ idea how this relates to Libstation, HSC, et al. The only thing that I know of that uses this is NFS. Perhaps your portmap is not the standard portmap? The standard portmap simply keeps track of port names with their associated logical names. That way, a client can ask portmap: What port should I connect to in order to access service bubba?. The bubba service, running on the z/OS system, would have previously sent a request to portmap on the order of: Hey! This here is bubba, what port do you want me to listen on for work?. Portmap would then tell bubba what port to listen on. A client would ask portmap what port bubba was listening on and connect to that port in order to talk to bubba. Portmap sees very little use around here. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- 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: Portmap start task
It is the standard Portmap. The only thing we had to do was to start PORTMAP in TCP. Pat Mihalec Rush University Medical Center Senior System Programmer (312) 942-8386 [EMAIL PROTECTED] McKown, John [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 02/25/2008 02:27 PM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject Re: Portmap start task -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Leitner, Timothy Sent: Monday, February 25, 2008 1:43 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Portmap start task All, Has anybody run into an issue with the portmap started task running in a default service class rather than sysstc like tcpip? We use STK (SUN) HSC and libstation and have had some odd things happening with our Veritas system. We have found that there will be a number (20-30) connections in TCPIP left for long periods of time all pointing back to the Veritas environment. We can drop the connections and things will clear up. Any ideas? Thanks. Tim Leitner We run PORTMAP in a service class called DAEMON. Its WLM classification is Importance=1, velocity=50. I have __no__ idea how this relates to Libstation, HSC, et al. The only thing that I know of that uses this is NFS. Perhaps your portmap is not the standard portmap? The standard portmap simply keeps track of port names with their associated logical names. That way, a client can ask portmap: What port should I connect to in order to access service bubba?. The bubba service, running on the z/OS system, would have previously sent a request to portmap on the order of: Hey! This here is bubba, what port do you want me to listen on for work?. Portmap would then tell bubba what port to listen on. A client would ask portmap what port bubba was listening on and connect to that port in order to talk to bubba. Portmap sees very little use around here. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- 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 -- 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: Portmap start task
I'm sorry but I can't resist. You might be a redneck if you call your service names bubba! --- [EMAIL PROTECTED] wrote: From: McKown, John [EMAIL PROTECTED] To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Portmap start task Date: Mon, 25 Feb 2008 14:27:05 -0600 -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Leitner, Timothy Sent: Monday, February 25, 2008 1:43 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Portmap start task All, Has anybody run into an issue with the portmap started task running in a default service class rather than sysstc like tcpip? We use STK (SUN) HSC and libstation and have had some odd things happening with our Veritas system. We have found that there will be a number (20-30) connections in TCPIP left for long periods of time all pointing back to the Veritas environment. We can drop the connections and things will clear up. Any ideas? Thanks. Tim Leitner We run PORTMAP in a service class called DAEMON. Its WLM classification is Importance=1, velocity=50. I have __no__ idea how this relates to Libstation, HSC, et al. The only thing that I know of that uses this is NFS. Perhaps your portmap is not the standard portmap? The standard portmap simply keeps track of port names with their associated logical names. That way, a client can ask portmap: What port should I connect to in order to access service bubba?. The bubba service, running on the z/OS system, would have previously sent a request to portmap on the order of: Hey! This here is bubba, what port do you want me to listen on for work?. Portmap would then tell bubba what port to listen on. A client would ask portmap what port bubba was listening on and connect to that port in order to talk to bubba. Portmap sees very little use around here. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology _ Netscape. Just the Net You Need. -- 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: Portmap start task
Portmap runs in class stclo - discretionary. I just changed it to stcmd - imp 3 vel 30. Will see if that makes a difference. Tim Leitner OSF Healthcare System Manager, Technical Services 309-683-7452 -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Monday, February 25, 2008 2:27 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Portmap start task -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Leitner, Timothy Sent: Monday, February 25, 2008 1:43 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Portmap start task All, Has anybody run into an issue with the portmap started task running in a default service class rather than sysstc like tcpip? We use STK (SUN) HSC and libstation and have had some odd things happening with our Veritas system. We have found that there will be a number (20-30) connections in TCPIP left for long periods of time all pointing back to the Veritas environment. We can drop the connections and things will clear up. Any ideas? Thanks. Tim Leitner We run PORTMAP in a service class called DAEMON. Its WLM classification is Importance=1, velocity=50. I have __no__ idea how this relates to Libstation, HSC, et al. The only thing that I know of that uses this is NFS. Perhaps your portmap is not the standard portmap? The standard portmap simply keeps track of port names with their associated logical names. That way, a client can ask portmap: What port should I connect to in order to access service bubba?. The bubba service, running on the z/OS system, would have previously sent a request to portmap on the order of: Hey! This here is bubba, what port do you want me to listen on for work?. Portmap would then tell bubba what port to listen on. A client would ask portmap what port bubba was listening on and connect to that port in order to talk to bubba. Portmap sees very little use around here. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- 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 == The information in this message is confidential and may be legally privileged. Access to this message by anyone other than the addressee is not authorized. If you are not the intended recipient, or an agent of the intended recipient, any disclosure, copying, or distribution of the message or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. If you have received this message in error, please contact the sender immediately and permanently delete the original e-mail, attachment(s), and any copies. == -- 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: Portmap start task
We have been running it at stcmed, but still have the problem of Vertias loosing the connection sometimes. The resolution is to stop/start Libstation and Veritas is able to connect again. Pat Mihalec Rush University Medical Center Senior System Programmer (312) 942-8386 [EMAIL PROTECTED] Leitner, Timothy [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 02/25/2008 03:05 PM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject Re: Portmap start task Portmap runs in class stclo - discretionary. I just changed it to stcmd - imp 3 vel 30. Will see if that makes a difference. Tim Leitner OSF Healthcare System Manager, Technical Services 309-683-7452 -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Monday, February 25, 2008 2:27 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Portmap start task -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Leitner, Timothy Sent: Monday, February 25, 2008 1:43 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Portmap start task All, Has anybody run into an issue with the portmap started task running in a default service class rather than sysstc like tcpip? We use STK (SUN) HSC and libstation and have had some odd things happening with our Veritas system. We have found that there will be a number (20-30) connections in TCPIP left for long periods of time all pointing back to the Veritas environment. We can drop the connections and things will clear up. Any ideas? Thanks. Tim Leitner We run PORTMAP in a service class called DAEMON. Its WLM classification is Importance=1, velocity=50. I have __no__ idea how this relates to Libstation, HSC, et al. The only thing that I know of that uses this is NFS. Perhaps your portmap is not the standard portmap? The standard portmap simply keeps track of port names with their associated logical names. That way, a client can ask portmap: What port should I connect to in order to access service bubba?. The bubba service, running on the z/OS system, would have previously sent a request to portmap on the order of: Hey! This here is bubba, what port do you want me to listen on for work?. Portmap would then tell bubba what port to listen on. A client would ask portmap what port bubba was listening on and connect to that port in order to talk to bubba. Portmap sees very little use around here. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- 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 == The information in this message is confidential and may be legally privileged. Access to this message by anyone other than the addressee is not authorized. If you are not the intended recipient, or an agent of the intended recipient, any disclosure, copying, or distribution of the message or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. If you have received this message in error, please contact the sender immediately and permanently delete the original e-mail, attachment(s), and any copies. == -- 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 -- 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: Portmap start task
-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Richard Pinion Sent: Monday, February 25, 2008 2:32 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Portmap start task I'm sorry but I can't resist. You might be a redneck if you call your service names bubba! Or if they all end with -bob (john-bob, billy-bob, etc-bob). -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- 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: Portmap start task
Pat, What's weird is that we have a NonStop (Tandem) and a Siemens PACS system that get their mounts through libstation even when Veritas does not. Tim Leitner OSF Healthcare System Manager, Technical Services 309-683-7452 -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Pat Mihalec Sent: Monday, February 25, 2008 3:15 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Portmap start task We have been running it at stcmed, but still have the problem of Vertias loosing the connection sometimes. The resolution is to stop/start Libstation and Veritas is able to connect again. Pat Mihalec Rush University Medical Center Senior System Programmer (312) 942-8386 [EMAIL PROTECTED] Leitner, Timothy [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 02/25/2008 03:05 PM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject Re: Portmap start task Portmap runs in class stclo - discretionary. I just changed it to stcmd - imp 3 vel 30. Will see if that makes a difference. Tim Leitner OSF Healthcare System Manager, Technical Services 309-683-7452 -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Monday, February 25, 2008 2:27 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Portmap start task -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Leitner, Timothy Sent: Monday, February 25, 2008 1:43 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Portmap start task All, Has anybody run into an issue with the portmap started task running in a default service class rather than sysstc like tcpip? We use STK (SUN) HSC and libstation and have had some odd things happening with our Veritas system. We have found that there will be a number (20-30) connections in TCPIP left for long periods of time all pointing back to the Veritas environment. We can drop the connections and things will clear up. Any ideas? Thanks. Tim Leitner We run PORTMAP in a service class called DAEMON. Its WLM classification is Importance=1, velocity=50. I have __no__ idea how this relates to Libstation, HSC, et al. The only thing that I know of that uses this is NFS. Perhaps your portmap is not the standard portmap? The standard portmap simply keeps track of port names with their associated logical names. That way, a client can ask portmap: What port should I connect to in order to access service bubba?. The bubba service, running on the z/OS system, would have previously sent a request to portmap on the order of: Hey! This here is bubba, what port do you want me to listen on for work?. Portmap would then tell bubba what port to listen on. A client would ask portmap what port bubba was listening on and connect to that port in order to talk to bubba. Portmap sees very little use around here. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- 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 == The information in this message is confidential and may be legally privileged. Access to this message by anyone other than the addressee is not authorized. If you are not the intended recipient, or an agent of the intended recipient, any disclosure, copying, or distribution of the message or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. If you have received this message in error, please contact the sender immediately and permanently delete the original e-mail, attachment(s), and any copies. == -- 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 -- For IBM-MAIN subscribe
Re: Portmap start task
I don't think the problem is in Libstation. I think it is a Veritas problem, but we could never get our Unix/Veritas team to bother looking for the problem. The answer has been that it must be a mainframe problem. It does not occur on a regular basis. Only once in 3 to 4 months. We do not stop/start Portmap, just Libstation. Since we could not get anyone on the Veritas group to look at it this has been our resolution. Pat Mihalec Rush University Medical Center Senior System Programmer (312) 942-8386 [EMAIL PROTECTED] Leitner, Timothy [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 02/25/2008 03:35 PM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject Re: Portmap start task Pat, What's weird is that we have a NonStop (Tandem) and a Siemens PACS system that get their mounts through libstation even when Veritas does not. Tim Leitner OSF Healthcare System Manager, Technical Services 309-683-7452 -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Pat Mihalec Sent: Monday, February 25, 2008 3:15 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Portmap start task We have been running it at stcmed, but still have the problem of Vertias loosing the connection sometimes. The resolution is to stop/start Libstation and Veritas is able to connect again. Pat Mihalec Rush University Medical Center Senior System Programmer (312) 942-8386 [EMAIL PROTECTED] Leitner, Timothy [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 02/25/2008 03:05 PM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject Re: Portmap start task Portmap runs in class stclo - discretionary. I just changed it to stcmd - imp 3 vel 30. Will see if that makes a difference. Tim Leitner OSF Healthcare System Manager, Technical Services 309-683-7452 -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Monday, February 25, 2008 2:27 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Portmap start task -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Leitner, Timothy Sent: Monday, February 25, 2008 1:43 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Portmap start task All, Has anybody run into an issue with the portmap started task running in a default service class rather than sysstc like tcpip? We use STK (SUN) HSC and libstation and have had some odd things happening with our Veritas system. We have found that there will be a number (20-30) connections in TCPIP left for long periods of time all pointing back to the Veritas environment. We can drop the connections and things will clear up. Any ideas? Thanks. Tim Leitner We run PORTMAP in a service class called DAEMON. Its WLM classification is Importance=1, velocity=50. I have __no__ idea how this relates to Libstation, HSC, et al. The only thing that I know of that uses this is NFS. Perhaps your portmap is not the standard portmap? The standard portmap simply keeps track of port names with their associated logical names. That way, a client can ask portmap: What port should I connect to in order to access service bubba?. The bubba service, running on the z/OS system, would have previously sent a request to portmap on the order of: Hey! This here is bubba, what port do you want me to listen on for work?. Portmap would then tell bubba what port to listen on. A client would ask portmap what port bubba was listening on and connect to that port in order to talk to bubba. Portmap sees very little use around here. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- 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 == The information in this message is confidential and may be legally privileged. Access to this message by anyone other than the addressee is not authorized. If you are not the intended recipient
Re: Portmap start task
Our veritas support guys must be related to your veritas support guys. Your comment fits them to a T. but we could never get our Unix/Veritas team to bother looking for the problem Thanks for your input. Tim Leitner OSF Healthcare System Manager, Technical Services 309-683-7452 -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Pat Mihalec Sent: Monday, February 25, 2008 3:40 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Portmap start task I don't think the problem is in Libstation. I think it is a Veritas problem, but we could never get our Unix/Veritas team to bother looking for the problem. The answer has been that it must be a mainframe problem. It does not occur on a regular basis. Only once in 3 to 4 months. We do not stop/start Portmap, just Libstation. Since we could not get anyone on the Veritas group to look at it this has been our resolution. Pat Mihalec Rush University Medical Center Senior System Programmer (312) 942-8386 [EMAIL PROTECTED] Leitner, Timothy [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 02/25/2008 03:35 PM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject Re: Portmap start task Pat, What's weird is that we have a NonStop (Tandem) and a Siemens PACS system that get their mounts through libstation even when Veritas does not. Tim Leitner OSF Healthcare System Manager, Technical Services 309-683-7452 -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Pat Mihalec Sent: Monday, February 25, 2008 3:15 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Portmap start task We have been running it at stcmed, but still have the problem of Vertias loosing the connection sometimes. The resolution is to stop/start Libstation and Veritas is able to connect again. Pat Mihalec Rush University Medical Center Senior System Programmer (312) 942-8386 [EMAIL PROTECTED] Leitner, Timothy [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 02/25/2008 03:05 PM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject Re: Portmap start task Portmap runs in class stclo - discretionary. I just changed it to stcmd - imp 3 vel 30. Will see if that makes a difference. Tim Leitner OSF Healthcare System Manager, Technical Services 309-683-7452 -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Monday, February 25, 2008 2:27 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Portmap start task -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Leitner, Timothy Sent: Monday, February 25, 2008 1:43 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Portmap start task All, Has anybody run into an issue with the portmap started task running in a default service class rather than sysstc like tcpip? We use STK (SUN) HSC and libstation and have had some odd things happening with our Veritas system. We have found that there will be a number (20-30) connections in TCPIP left for long periods of time all pointing back to the Veritas environment. We can drop the connections and things will clear up. Any ideas? Thanks. Tim Leitner We run PORTMAP in a service class called DAEMON. Its WLM classification is Importance=1, velocity=50. I have __no__ idea how this relates to Libstation, HSC, et al. The only thing that I know of that uses this is NFS. Perhaps your portmap is not the standard portmap? The standard portmap simply keeps track of port names with their associated logical names. That way, a client can ask portmap: What port should I connect to in order to access service bubba?. The bubba service, running on the z/OS system, would have previously sent a request to portmap on the order of: Hey! This here is bubba, what port do you want me to listen on for work?. Portmap would then tell bubba what port to listen on. A client would ask portmap what port bubba was listening on and connect to that port in order to talk to bubba. Portmap sees very little use around here. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances
Re: Portmap start task
Don't know too much about portmap but it seems like a candidate for SYSSTC. Have you encountered problems that make you reluctant to put it there. Check the link. IBM's sample policy has it defined there. http://www-03.ibm.com/servers/eserver/zseries/zos/wlm/documents/sample/samplepol.html Leitner, Timothy [EMAIL PROTECTED] wrote: Portmap runs in class stclo - discretionary. I just changed it to stcmd - imp 3 vel 30. Will see if that makes a difference. Tim Leitner OSF Healthcare System Manager, Technical Services 309-683-7452 -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Monday, February 25, 2008 2:27 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Portmap start task -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Leitner, Timothy Sent: Monday, February 25, 2008 1:43 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Portmap start task All, Has anybody run into an issue with the portmap started task running in a default service class rather than sysstc like tcpip? We use STK (SUN) HSC and libstation and have had some odd things happening with our Veritas system. We have found that there will be a number (20-30) connections in TCPIP left for long periods of time all pointing back to the Veritas environment. We can drop the connections and things will clear up. Any ideas? Thanks. Tim Leitner We run PORTMAP in a service class called DAEMON. Its WLM classification is Importance=1, velocity=50. I have __no__ idea how this relates to Libstation, HSC, et al. The only thing that I know of that uses this is NFS. Perhaps your portmap is not the standard portmap? The standard portmap simply keeps track of port names with their associated logical names. That way, a client can ask portmap: What port should I connect to in order to access service bubba?. The bubba service, running on the z/OS system, would have previously sent a request to portmap on the order of: Hey! This here is bubba, what port do you want me to listen on for work?. Portmap would then tell bubba what port to listen on. A client would ask portmap what port bubba was listening on and connect to that port in order to talk to bubba. Portmap sees very little use around here. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology -- 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
