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