|
I think this was already responded to but I have found a quirk with the named devices using Client Access. We recently had a ethernet line fail where we had to restart tcp/ip. When this happened, all of the "in-use" TCP devices are not used by the system again until an IPL even though their status looks ok. When a user is connecting and using the QPADEVxxxx devices this is not a problem because the system just creates more devices (until the system value maximum is hit). When you have named your device through your session, this is a problem because the system will not let you use that device. I even deleted the devices and still could not get connected. In order to get connected, I had to either remove the device name from each Client/Access session or change the name to something different. If all of users had been using named devices under Client/Access then this would have been quite a mess to get everyone connected back up. This is something to consider when deciding whether to use the named device function under Client Access. Anybody had a similar problem yet??? > -----Original Message----- > From: Joe Giusto [SMTP:JDG@patuxent.com] > Sent: Friday, July 17, 1998 7:48 AM > To: 'midrange-l@midrange.com' > Subject: Device Naming Using TCP/IP > > I have just started using TCP/IP to access the 400 and have noticed > that > it gives me a device name QPADEVxxxx (like when doing passthru). Is > there any way to get the same device name each time (like I did before > using the TCP/IP)? We have an application that uses the device name > and > user id to validate authority and this is going to be a mess if we > start > using TCP/IP company wide. > > thanks in advance, > > Joe Giusto > Patuxent Publishing Company > mailto:jdg@patuxent.com > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to > MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: > david@midrange.com > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.