|
well, actually he would have to do something like: CWBCFG >> Z:\VERSION.TXT and ALSO append soemthing that gives a computer identifier. Z:\ will have to be some public writeable network share so that he will have one nice report. What's the point of goign around to people's computer to look at the report locally? He could just open client access and see the version then. I think he wants to avoid going around. Adam Lang Systems Engineer Rutgers Casualty Insurance Company http://www.rutgersinsurance.com ----- Original Message ----- From: "Steve Landess - Hotmail" <steve_landess@hotmail.com> To: <midrange-l@midrange.com> Sent: Thursday, August 15, 2002 4:12 PM Subject: Re: Need to find out Client Access version on many clients > Use the pc command CWBCFG > VERSION.TXT in the logon script. The file > created (VERSION.TXT) will have the information that you need. > > ----- Original Message ----- > From: "Stefan Tageson" <Stefan.Tageson@intentia.se> > To: <midrange-l@midrange.com> > Sent: Thursday, August 15, 2002 3:41 PM > Subject: Need to find out Client Access version on many clients > > > > Anybody knows of a way to retrieve the Client Access version? We have a > customer with 3000-4000 pc's running Client Access V3R2 and Client Access > V4R5. We are now planning to upgrade OS/400 from V4R5 to V5R1 and need to > know what pc's to take care of before the upgrade. It would be nice to > temporarily insert something in the login script to catch the CA version > and write it to a logfile. > > Any thoughts welcome. > > Best Regards > > Stefan Tageson > Intentia Consulting Sverige AB > Propellergatan 1, SE-211 19 Malmö, Sweden > Phone: +46 (0)40 691 35 00 > Cell: +46 (0)733 913 813 > Fax: +46 (0)40 691 3900 > E-mail: stefan.tageson@intentia.se > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > >
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.