Re: Autonaming TCPIP - PTFs - and more fun!!

SNDPTFORD command to order (can be downloaded via ECS modem).  WRKPRB,
option 5, F9 to see cover letters after download (or STRPDM and look in
file QAPZCOVER in QGPL library).  APYPTF to apply.
See chapter on PTF's in Basic System Operations Manual (that was shipped
in a real paper book for V3R7 - up to around V4R4 or V4R5 I think).

INFORMATION APAR II10918

INTRODUCTION
____________

AS/400 Client Access for Windows 95/NT V3R1M3 and V3R2M0
and Client Access Express provide the following TCP/IP
enhancements:
provide 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.  This information APAR lists the requirements
for both, along with known restrictions.

 HOST REQUIREMENTS
 _________________

 OS/400 Ver 3 Rel 7 Mod 0 :

    PRODUCT    PTF
    -------  -------
    5716TC1  SF50019
    5716999  MF21135
    5716SS1  SF47406 & SF51875

  Additional PTFs for DBCS Support on V3R7:
    PRODUCT    PTF
    -------  -------
    5716SS1   SF53089

 Only some of the above PTFs can be applied immediately.
 Software Service recommends applying all the PTFs at
 the same time and therefore recommends setting all
 the above PTFs to apply Delayed.  Please read cover
 letters and verify that all co-req's and pre-req's
 to the above five PTFs are also applied.

...Neil



Well, the saga continues.  I was able to solve a big issue with the
whole naming convention things we talked about by just defining the
default printer in user profiles.  Why?  Well, that's my problem.

Most AS/400s I work on aparently are V3R7M0 (I assume that means Version
3 Release 7 Mod 0).  As I was on the phone with BOS tech support they
told me that I needed to have certain PTFs installed so that session
names were auto created on the AS400 when specified in their (or any
other) software.  They linked me to
http://www.bosweb.com/bntcp_ptf.html.  (listed below) I checked if the
PTFs (what are PTFs?  I assumed they are like system libs) they want for
V3R7M0 using a command (that I forgot to write down and could use again
:P) that listed all installed PTFs.  I saw no PTFs that start SF____ and
the other PTF they say we need was not installed!  BOS Tech support told
me I need those PTFs and with those, the software will be able to name
those.  I was on a newer AS400 (I forgot to check OS version or if its
PTFs were installed that BOS requests) and the naming the session in the
software worked just fine there.  Would these PTFs be on a CD that most
likely came with the system?  Can I grab PTFs off another AS400 or do I
have to buy these things from IBM?  If I have them, how the frig do I
install them?  OR... Does that have nothing to do with the fact.  FYI:
What was happening was that when we would enter anything into the
session name in the BOS software, the connection would just drop and the
software would try to reconnect over and over again but we never got a
login screen.  If we switched to names that already existed (say DSP07
or whatever the long auto assigned name was) the same thing happened.
Anybody know what to check for if its not these PTFs?  I know some
offices really will need to keep session specific settings, but if this
doesn't work - ill just create a second user for them so they can have
two different sets.

Also - if anyone knows how to specify the session name in mochasoft OR
how to auto connect in mochasoft to a specified hostname or IP - that
would kick butt too!


OS/400 Ver 3 Rel 7 Mod 0
PRODUCT PTF

------------------------------------------------------------------------
--------

5716TC1 SF50019
5716999 MF21135
5716SS1 SF47406 & SF51875