• Subject: Re: Client Accesss Session/Job Name
  • From: neilp@xxxxxxxxxxx
  • Date: Fri, 24 Nov 2000 21:29:57 -0500


What version of OS/400 are you running, and what PTF cum package level ?  (There are PTF's required for some releases to support device naming via TCP/IP).
Also, What version of Client Access are you running, and what Service Pack level ?

Neil Palmer      DPS Data Processing Services Canada Ltd.
50 Acadia Avenue, Ste.102                   AS/400~~~~~
Markham, Ontario, Canada.   ____________          ___  ~    
Phone:(905) 474-4890 x303   |OOOOOOOOOO| ________  o|__||=  
Cell.:(416) 565-1682 x303   |__________|_|______|_|______)  
Fax:  (905) 474-4898         oo      oo   oo  oo   OOOo=o\  
mailto:NeilP@DPSlink.com  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
http://www.DPSlink.com     iSeries 400  The Ultimate Business Server

Leo Lefebvre <leo@tug.on.ca>
Sent by: owner-midrange-l@midrange.com

2000/11/24 16:24
Please respond to MIDRANGE-L

        To:        Midrange-L <MIDRANGE-L@midrange.com>
        Subject:        Client Accesss Session/Job Name

Hi everybody,

Up to now, getting a virtual device name QPADEVxxxx was not a problem.
Now, I would like to assign specific session name to specific

I've tried to change the 'Workstation ID' parameter on the 'Configure
PC5250' panel of CA but with no success. I still get a QPADEVxxxx
session name when I connect to the AS400 using TCP/IP.

When I connect through NS Router, I get the workstationname I assigned
in the configuration steps.

What am I missing? Is it that connecting through TCP/IP, I am at the
mercy of the AS/400?


Leo Lefebvre
Toronto Users Group for Midrange Systems
Visit our home page at <http://www.tug.on.ca>
Ph: (416) 606-5960   ---   Fx: (416) 495-0100

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].