|
Vernon Hamberg wrote: > Jim > > At 12:50 AM 7/4/1998 -0400, you wrote: > >Hi > > > >Anyone have some examples of a routing entry program that will route two > >QPADEV* users in the MIS department into a seperate interactive > >subsystem ( MISINTER )... > > > >Once we get the device id naming working with v4r2 I imagine we can just > >use ADDWSE > > > >The reason for doing this of course is so we can stay active when Qinter > >is ended. > > > >Sound like a plan ? Any ideas ? > > Are you talking about Client Access only? If so, you don't need to wait for > v4r2 for named devices. There are PTFs for all releases of OS/400 back to > v3r2 that enable this feature. Go to <http:/www.as400.ibm.com/clientaccess> > and look for the info APARs. One of them lists the PTFs for all releases. I > think it's APAR II10918. > > HTH > > Vernon Hamberg > Systems Software Programmer > Old Republic National Title Insurance Company > 400 Second Avenue South > Minneapolis, MN 55401-2499 > (612) 371-1111 x480 Well we'll be using Client Access as well as a Telnet app running on a Winframe server...( possibly TNHOST from ipswitch.com, looks good...). I'll be trying out powerterm tomorrow... Far as the device id naming...we'll the mis mgr and I have been involved in a bang up job bringing up the new 400 and the Winframe Server...we're a little disorganized...too much going on all at once. We have a cume ptf for v4r2 we we're told to wait a couple weeks before installing, not even sure which one it is... Everything thus far is working other than some clunky pc's we are having problems with, plus we have some jet direct cards to setup yet for some printers. The Winframe is setup as DHCP server which seems to work great for the thin clients. Looks like we'll have our hands full for awhile till we iron out all the networking problems, who gets what...etc... Client Access installs nicely and upgrades over the old version. I may have missed something in the setup to make the device id naming work, unless what it needs is that ptf we haven't put on yet. Be nice if the company would do away with some of the older pc's but this is one of those mfg company's that run on shoestring budgets...if there's anything i hate it's dealing with a 386! Anyway So I can have a simple CL program as an intial program that just does a TFRJOB to MISINTER? that would be easy enough. I noticed the powerterm telnet client says it supports device id naming too so maybe that will be the ticket... Originally we were told Client Access would work with the Winframe but it doesn't. Then it was Lynx...ES/95 which works but the fonts don't look too good. So now were trying some others before we go live Monday morning... Nothing like good planning aye ? lol -- Jim W http://www.netcom.com/~jimwelsh/welcome/welcome.html mailto:jimwelsh@ix.netcom.com I just work here man... +--- | 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.
midrange.com
