× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: re: Workstation ID for Client Access
  • From: "Lemen, George (Contractor)" <george.lemen@xxxxxxxxxxxxxxxx>
  • Date: Wed, 22 Mar 2000 08:27:19 -0800

Nathan --
 If (and as far as I know only if) you configure your PC's to use SNA
(either directly or via ANYNET) you can get this done. When you set up SNA
in either case each PC MUST have an identifier in the configuration. Keep
the name to 8 characters or less, first character must be a letter....(etc
etc the usual SNA rules). This becomes the SNA CTL description name on the
AS/400. Then configure a workstation session to use the SNA link with blanks
in the "workstation ID" field. When you start the session, it will be named
as the PC's SNA name (the CTL description name) with "Sx" appended, where x
is 1, 2, 3,.... depending on how many sessions you start.

Be forewarned:
*       This requires the target AS/400 be set up for SNA or ANYNET over
whatever the link to the PC is.
*       If ANYNET is used there will be a job started in QSYSWORK that ALL
your sessions flow through. This can become a performance bottleneck if you
have a large configuration (I have had to isolate the ANYNET job to it's own
memory pool in larger situations -- say 150 to 200 workstations).
*       SNA requires a LOT of code on the PC. You WILL see a performance
impact on the PC.
*       ANYNET causes additional processing on BOTH sides of the
communications link
*       I have run into very tough bugs to shoot when using non-IBM terminal
emulators under ANYNET. Be sure you get the TCP/IP group PTF for your OS/400
release and make sure the support folks include any and all ANYNET related
fixes. They may not all be in the CUME's yet.

I have used ANYNET in several shops that have "TCP/IP ONLY" networks but had
applications that required a predictable workstation name. ANYNET was the
ONLY way to use 5250 emulation in these shops until we got TN5250e. (What a
difference the "e" made in the TN5250 environment!)

If you use this approach .... best of luck!

******************************************************** original copied
below for reference *************************
I was looking though the Network Station Manager help and saw where I could
give a name to 5250 emulation session with a "+3" or some other number
appended to the DISPLAY_NAME parameter.

This would allow three sessions to be started, all with different names, but
you only need to use the one icon.

E.g.. JOE+3 = sessions named JOE1, JOE2 and JOE3

Is there such an option available in CA.

If we could configure just one session but still have multiple sessions with
different defined names that would be heaps easier and better.

TIA.

Regards,

Nathan Simpson
Australian Wool Handlers
nathansimpson@optusnet.com.au
***********************************************************


George Lemen
Sr. Project Analyst, CIBER Inc
Weyerhaeuser CER Technical Support and Operations Manager
Weyerhaeuser phone: (253) 924-7975;  E-mail: george.lemen@weyerhaeuser.com
CIBER Phone (425) 451-2575 x142; E-mail: glemen@ciber.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 thread ...

Follow-Ups:

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

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.