|
Hello Dan, this is the same old game again, but I try to explain in short: No matter what OS-Version you are, CAWIN Version numbers are no longer the same version numbers as the OS they come with, as you surely noticed. So, CAWIN V3R2 connects to all V3Rx and V4Rx systems, the only difference is CA Express V4R4 or V4R5, which need OS/400 V4R2 as a minimum requirement. I guess you got a licence for "Client Access for Windows" that was ordered with your V3R2 OS. This used to have something like 5763XA1/XB1/XC1/XD1 as licpgm-code where XA1 is sometimes called the family code and XD1 is the Win9x/NT part. With V4 this changed to a strange licence politics: CA-licences where split into an "old-fashioned part", now with the licpgm-code 5769XY1 which replaced the XA1/XB1/XC1-family (DOS/WIN3.x/DOS ext.) and the other "new part" which is licpgm 5769XW1 as the so called family-code (see explanation below) and XE1 (CA Express) and XD1 (same as CAWIN 3.2, as in OS V3) as the client side parts. Thats why 5763XD1 (V3) and 5769XD1 (V4) are synonym. V4 was the appereance of a licence manager in ClientAccess Server-Code on the AS/400 side (could be on V3R6/V3R7 RISC as well, I am not quite sure on this), which has to be installed and the demon must be running (STRHOSTSVR ... , you guessed it), to give your connection a valid "licence slot" and then allows a successful signon. This is done through the so called "managing system", when there are several systems on your network, you got to take care of this definition to keep track with your licences. Legally, as far as I know, you normally have the licence for XA1/XB1 and so on if on V3R2, or for a number of PCs for XY1 and/or XW1, if on V4Rx. This has nothing to do whith the version of CA-Client installation CD you initially received with your system. So either you ask your BP or your IBM rep to send you the most recent CA-CD (PC-media, which has SK2T-2547-04 in germany, sorry I don't have US-versions of these) for a shipping charge, or you find yourself another AS/400 user around to give you a CD for a copy. Normally, you should update the code on the AS/400, too, but my experience is that this is not that important. Early V3R2 systems shipped with V3R1M1,V3R1M2 or V3R1M3, some had already V3R2M0 as CA-licpgms with them, all these versions are/were the same "licence", the difficulty is to get the installation code for the AS/400. If you don't have any DOS/Win 3.x users anymore you could even transfer the XY1 licence(s) to XW1 to save the money, and if going to upgrade this saves a lot. I sure hope this helps you out. Again, regards from germany, Philipp Rusch D.BALE@handleman.com schrieb: > Thanks Phillip! > > Well, yes, CA V3R2M0... Is that usable on a V3R2 OS/400? > > If so, I've got another problem. I inheirited (sp?) 13 shrink-wrapped Client > Access CDs with a LOT of duplication. There *must* be a good reason why I > have 6 copies of the "Client Service Pack SF40828 CD" for V3R1M2. I've got > four copies of the "Windows 3.1 and Windows 95/NT CD-ROM". I even have one > copy of the "DOS, OS/2, and Windows 3.1 CD-ROM"! > > I do have a copy of the CA for Win95/NT Version 4 CD-ROM. Strangely enough, > though, the CD-ROM itself has on the label "Contains client; Windows 95/NT > 5763-XD1 V3R1M2". So I guess I'm really confused. The README.TXT file gives > no clues either. > > What is item number for the latest version of CA that can run on a V3R2 > OS/400? (I.e., SK3T-nnnn-nn) What version of OS/400 did it ship with? And, > if I am unable to find a copy of it around here, how do I get my hands on one > without having to pay anything more than a shipping charge? > > - Dan > Dan Bale says "BAN DALE!" > IT - AS/400 > Handleman Company > 248-362-4400 Ext. 4952 > D.Bale@Handleman.com > Quiquid latine dictum sit altum viditur. > (Whatever is said in Latin seems profound.) > > -------------------------- Original Message -------------------------- > Hello Dan, > ( see I got it right, too ;-) ) > > first of all, you really should update to CA V3R2M0 and install > SF64050 or higher immediately after it, this really makes a lot > things easier, especially when running on NT. > CA ServicePacks can be downloaded at > > http://www-1.ibm.com/servers/eserver/iseries/clientaccess/casp.htm > > HTH, and regards from germany, Philipp Rusch > > ----------------------------------------------------------------- > | EDV Beratung Rusch EDP Consulting Rusch | > | Philipp Rusch Mailto: Philipp.Rusch@rusch-edv.de | > | Am Errlich 9 WWW : http://www.rusch-edv.de/ | > | D-61191 Rosbach, | > | Germany | > | Phone: (+49) 6003 3972 Mobile : (+49) 172 89 86 230 | > | Fax : (+49) 6003 3795 | > | | > ----------------------------------------------------------------- > > D.BALE@handleman.com schrieb: > > > I am using Client Access for Win95/NT V3R1M2 (my lowest common denominator > is > > an AS/400 running V3R2). > > > > We also have Attachmate's Extra! personal client and connect via TN5250. > This > > is not my preferred 5250 client, but I use it whenever I have a connection > > problem that prevents me from signing on to one of our systems with the CA > > client. When this happens, our first remedy is to run STRHOSTSVR *ALL. > > > > I'm somewhat wary of running this command if for no other reason than that I > > have no idea what's being started. The documentation seems to suggest that > > Client Access requires STRHOSTSVR *ALL. It would be nice to know what each > of > > the server types do and what kind of jobs require each server type. The > > documentation instructs the reader to look at the help text - need I say > more? > > > > - Dan > > Dan Bale says "BAN DALE!" > > IT - AS/400 > > Handleman Company > > 248-362-4400 Ext. 4952 > > D.Bale@Handleman.com > > Quiquid latine dictum sit altum viditur. > > (Whatever is said in Latin seems profound.) > +--- > | 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 > +--- +--- | 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.