Naming Devices within Client Access
scarbrough
I am currently managing a network with 500 something pc's. The majority of
my clients are running win95, and client access v3r2 over tcp/ip to the 400.
I am only vaguely familiar with the AS/400 so please bear with me. As I
understand it this is how it works. When the clients start a session with
the 400 their device names show up as QDAPXXXXX, of some variant of that.
Which as I understand it is some type of virtual device. We need to be able
to give these sessions a static name that it uses everytime someone starts a
session on that PC. Is this possible??? My 400 operator doesn't know
because he only "operates" the 400. So the ball has been thrown in my lap.
I hope my queston is clear. Thank you for all your help in advance.
J.A. Scarborugh
Goodier Father
I think this condition as you mention is NOT POSSIBLE.
It's look like AS/400 will generated Virtual Device (QPADEVXXXX )
automatically.
Correct me if I'm wrong
--
Wisnu Hermawan
System Engineer
mailto:goo...@mailcity.com
scarbrough <jeb...@mindspring.com> wrote in article
<6joed5$do9$1...@camel25.mindspring.com>...
Frank Healy
One of the enhancements made to V3.1.3 of CA is the ability to define
the Workstation name.
FYI, you mention that your CA is at V3.2. That is the release of the
AS/400 Operating system and usually everything else is at the same
level, however, CA has not been released at the V3.2 level -- its latest
level is V3.1.3.
Frank Healy
Alan D. Brittain
>I am currently managing a network with 500 something pc's. The majority of
>my clients are running win95, and client access v3r2 over tcp/ip to the 400.
>I am only vaguely familiar with the AS/400 so please bear with me. As I
>understand it this is how it works. When the clients start a session with
>the 400 their device names show up as QDAPXXXXX, of some variant of that.
>Which as I understand it is some type of virtual device. We need to be able
>to give these sessions a static name that it uses everytime someone starts a
>session on that PC. Is this possible??? My 400 operator doesn't know
>because he only "operates" the 400. So the ball has been thrown in my lap.
>I hope my queston is clear. Thank you for all your help in advance.
>
>J.A. Scarborugh
>
Below is a sample of a section of a workstation profile (.ws). I first
edit the profile with the appropriate LUName and save this profile,
then on the AS400, I rename the devices QPADEVxxxx (they must first
be offline and varied off to rename) to the corresponding LUName. This
is a round about way to get the job done, but it works for our
situation.
[Telnet5250]
HostPortNumber=23
LUName=LAN1135A
AutoReconnect=N
ExtendedColor=N
ATTN=6CFFEFFFF3
SYSREQ=F0FFEF
Best Regards,
Alan Brittain
Regal Manufacturing
OSITim
In order to specify a device name for TN5250 sessions, you must have V4R2 and
CA V3R1M3 or an emulator that supports device naming for TN5250 (such as
BOSaNOVA)
IBM has announced (and may have released) PTFs to allow V4R1, V3R7, and V3R2 to
allow TN5250 device naming support.
missilen
be aware that when assigned a device name to a PC then it will not
automatic pick a new virtual device when you open another session.
Timothy
OSITim <osi...@aol.com> wrote in article
<199805181733...@ladder03.news.aol.com>...
Cameron J Hall
APAR#:
II10918
Component:
INFOAS400 - AS/400 Information
Release(s):
R410
Abstract
REQUIREMENTS FOR PC5250 SUPPORT OF TCP/IP ENHANCEMENTS
Error Description
** Last updated 05/15/98 **
INTRODUCTION
____________
AS/400 Client Access for Windows 95/NT V3R1M3 is providing
the following TCP/IP enhancements:
1) PC5250 Print Emulation
2) Workstation ID Support
3) Bypass Signon Support (AutoLogon)
In order for users to be able to take advantage of this
new support, PTFs will be required on both the Client
and Server.
SERVER SUPPORT
______________
At present the Server Support is available for PCs
connecting to AS/400 systems running OS/400 V3R7, V4R1, and
V4R2. Plans are in place to add this support to the
following releases of OS/400:
- V3R2 (target 2Q98)
This Information APAR will be updated with the necessary
PTFs as soon as they are available.
HOST REQUIREMENTS
_________________
OS/400 Ver 4 Rel 2 Mod 0
PRODUCT PTF
------- -------
5769TC1 SF45762 & SF46013 (GA Cum Tape)
5769999 MF18061 (on GA Cum Tape)
5769SS1 SF46155 (on GA Cum Tape)
Note: These PTFs are on the AS/400 Cumulative PTF
package available at GA. However, you should
check for supercedes to these PTFs.
OS/400 Ver 4 Rel 1 Mod 0
*** NOTE!! Until further notice, do not use the following
V4R1 PTFs if you are using the S/36 environment or are
using TFRJOB. See the "Known Problems for V4R1 and V3R7"
section below for a description of the problems found in
those two environments. ***
PRODUCT PTF
------- -------
5769TC1 SF47602 & SF46544
5769999 MF18869
5769SS1 SF47990 & SF48012
OS/400 Ver 3 Rel 7 Mod 0
*** NOTE!! Until further notice, do not use the following
V3R7 PTFs if you are using the S/36 environment or are
using TFRJOB. See the "Known Problems for V4R1 and V3R7"
section below for a description of the problems found in
those two environments. ***
PRODUCT PTF
------- -------
5716TC1 SF46543 & SF47007
5716999 MF18448
5716SS1 SF46693 & SF47030
KNOWN PROBLEM FOR V4R1 and V3R7:
________________________________
S/36 Environment:
We have seen problems with R370 and R410 as follows:
- Users log on to AS/400 via TELNET from Windows 95 or
Windows NT PCs
- Users get a signon screen and successfully sign on to
the AS/400.
- Users enter STRPASTHR command to their guest S/36 SSP
operating system.
- Users successfully sign on to the S/36.
- Users start using a S/36 application which transfers
data back to their PC.
- The PC "locks up": i.e., the screen never gets
completely written to the user's PC.
At R370, the removal of PTFs MF18448, SF47007, and SF47030
eliminated the S/36 environment job hangs.
TFRJOB environment:
- User signs on to local AS/400 via PCOM (TELNET)
- User issues a STRPASTHR command to reach AS/400
System B
- User logs on to System B
- User then issues a Transfer Job command.
- The Transfer job command works, but subsequent commands
hang.
CLIENT SUPPORT
______________
The Client Support is only available for PCs connecting
to AS/400s when the PCs have Client Access for Windows
95/NT V3R1M3 installed. In addition to the base V3R1M3
code, Service Pack SF46891 or later is required.
Language environments supported are:
- All SBCS languages
- DBCS Japanese
- DBCS English Upper Case Only
- DBCS English Upper/Lower Case
This Information APAR will be updated when the following
language environments are supported:
- DBCS Korean
- DBCS Simplified Chinese
- DBCS Traditional Chinese
Problem Summary
Problem Conclusion
Temporary Fix
Comments
This is an Information APAR.
Circumvention
PTFs Available
Affected Modules
Affected Publications
Summary Information
Status................. CLOSED CAN
HIPER.................. No
Component..............
Failing Module.........
Reported Release....... R410
Duplicate Of...........
IBM disclaims all warranties, whether express or implied, including, but
not limited to, the implied warranties of merchantability and fitness
for a
particular purpose. By furnishing this document, IBM grants no
licenses to any related patents or copyrights. Copyright (c) 1994, 1995,
1996,1997,1998 IBM Corporation. Any trademarks and product or brand
names referenced in this document are the property of their respective
owners. Consult your product manuals for complete
trademark information.
jsav...@mindspring.com
>I am currently managing a network with 500 something pc's. The majority of
>my clients are running win95, and client access v3r2 over tcp/ip to the 400.
>I am only vaguely familiar with the AS/400 so please bear with me. As I
>understand it this is how it works. When the clients start a session with
>the 400 their device names show up as QDAPXXXXX, of some variant of that.
>Which as I understand it is some type of virtual device. We need to be able
>to give these sessions a static name that it uses everytime someone starts a
>session on that PC. Is this possible??? My 400 operator doesn't know
>because he only "operates" the 400. So the ball has been thrown in my lap.
>I hope my queston is clear. Thank you for all your help in advance.
>
>J.A. Scarborugh
>
>
You can switch to using anynet on the AS/400. the common name is
called MPTN. When you use this option you are essentially using SNA
encapsulatted over TCP/IP. But this option will allow you to name
each and every device for both printer sessions and terminal emulation
sessions.
Native 5250 right now is forced to use QPAD* naming convention. Try
ANYNET until IBM has the PTF's ready to allow you to use a tn5250
naming convention.
Hope this helps !!!
Paul Nicolay
Hi,
Ahhhh... don't tell anybody to use Anynet (and the crappy Netsoft router)
!!!
Otherwise we get questions like why is CA so bad again.
Native TCP/IP is the only stable and fast connection (and the required
PTF's for V3R2 to have fixed device names and printing should be released
in 2Q98) Just check
http://as400service.rochester.ibm.com/as4sde/NAS4APAR.NSF/bd3862dddaa03fb186
2564c00079d11a/89fdbac713829e2a8625654f002e4bee?OpenDocument
Regards,
Paul
_________________
jsav...@mindspring.com wrote in article
<358480d6...@news.mindspring.com>...
The contents of this message express only the sender's opinion.
This message does not necessarily reflect the policy or views of
my employer, Merck & Co., Inc. All responsibility for the statements
made in this Usenet posting resides solely and completely with the
sender.
Andrew Cathrow
Can I just backup Paul on what he is saying
Unless you have a very good reason DO NOT USE NETSOFT
It's unstable, slow and consumes a lot of memory.
If you can afford to wait for the v3r2 ptf's then please do.
Aic
Paul Nicolay wrote in message <01bd982d$4bd5e060$4e44...@merck.com>...
Richard Knechtel
Andrew Cathrow wrote:
>
> Can I just backup Paul on what he is saying
>
> Unless you have a very good reason DO NOT USE NETSOFT
>
> It's unstable, slow and consumes a lot of memory.
> If you can afford to wait for the v3r2 ptf's then please do.
>
> Aic
Yes, NETSOFT SUCKS! We went to native TCP/IP from anynet and WOW what a
difference! (and all those people that say IBM's product sucks and that
Netsoft etc.. is stable and good, HAH!).
--
Richard Knechtel
CENTROBE
(an EDS company)
(Systems Engineer/System Administrator)
(Aspiring AS/400 GURU)
(Aspiring Linux GURU)
(Aspiring Visual Basic Programmer)
The contents of this message express only MY opinion.
This message does not necessarily reflect the policy or views of
my employer, EDS. All responsibility for the statements
made in this posting resides solely and completely with the
ME.
I Ex-Spaminate spammers!
See US Code Title 47, Sec.227(a)(2)(B), Sec.227(b)(1)(C)
and Sec.227(b)(3)(C).
Rob Dixon
I have the same problem which I posted 9 June at 08.32. Paul Nicolay
responded that Client Access V3R1M3 does support named devices under
TCP/IP. I later read a note that I had missed from Adam Greenblum dated 7
June at 16.08 listing PTF's (fixes) for OS/400 3.7 or later that allowed
named devices (only with his company's product?). I have not yet tried
these.
Here are their responses -
1.
Hi Rob,
The new version of CA, V3R1M3 supports fixed device names under native
TCP/IP, and is supported on V3R7.
Regards,
Paul
2.
On June 3 I posted the following:
>Ericom Software Ltd's. PowerTerm terminal emulation software supports
Device
>Naming under AS/400. The technology offers users the advanced capacity to
>specify device names for TN5250 display and print sessions when working
with
>direct TCP/IP. This will allow users to work with TCP/IP only, without
the
>need for an SNA server or router software, which provides a huge cost
>savings for customers and less overhead for system administrators. The
only
>thing users need to load is the TCP/IP stack, and if they are using
Windows
>95 or NT, then TCP/IP is already loaded.
>
>You can download a full-featured demo from Ericom's web site at
>www.ericom.com. For more information you can send email to
in...@ericom.com.
>
As a clarification, this feature works with version 4.2 of the AS/400
operating system. For versions 3.7 and 4.1 you need PTFs from IBM.
Unfortunately, there are no PTFs for versions prior to 3.7.
The PTFs required for Device Naming over TCP/IP in TN5250 emulation are as
follows:
4.2: None required, works as is.
4.1:
Product #5769TC1
PTF #SF47602
#SF46544
Product #5769999
PTF #MF18869
Product #5769SS1
PTF #SF47990
#SF48012
3.7:
Product #5716TC1
PTF #SF46543
#SF47007
Product #5716999
PTF #MF18448
Product #5716SS1
PTF #SF96693
#SF47030
I apologize for any misunderstandings.
Adam Greenblum
p...@ericom.co.il
Jack Hefner
There are PTF's for V3R7 to allow telnet devices to enter a device name
before connecting. It works great!.....I can't remember the shareware
telnet software we used(we currently are only testing options), but the
PTF's from IBM is what was needed(along with a telnet client that will
allow device naming)