|
There are some preparation PTF's for V5R3 that came with your software. Y'all: If you think you may be going to V5R3 but not sure when, put these preparation PTF's on prior to your next IPL and follow their instructions. That way you'll have one less IPL when it comes to upgrade weekend. Read the Memo to Users, twice. I think they purposefully obfuscate items so as to not say "we made this really drastic change - it's more like the 'standards' but it will bust some chops for sure". The information about the /tmp directory definitely has an influence on SNDEMAIL. Either use: - use the workaround specified to change the bit on the /tmp directory - change SNDEMAIL to not use the /tmp directory - change SNDEMAIL to make QMSF the owner of the stuff it puts into the /tmp directory - you come up with something else. I did the first one. (Probably goes against what Scott Klement said earlier.) "CPYFRMIMPF command changes. No conversion performed if TOFILE field has no CCSID or a 65535 CCSID." Let me translate that for you. If you do the following CRTPF QTEMP/MYFILE RCDLEN(xxx) CPYFRMIMPF FROMSTMF('/MYDIR/MYFILE.TXT') TOFILE(QTEMP/MYFILE) The resulting data will now be garbage. Possible workarounds. 1) Figure out a magic combination of CCSID and/or code page that will work. 2) Do a CPYFRMSTMF then follow it with CPYFRMIMPF. Or just use CPYFRMSTMF. 3) Instead of doing a CRTPF with a RCDLEN either use DDS or SQL. For additional information on ways to handle CPYFRMIMPF command changes in V5R3, please refer to Informational APAR II13784. When you upgrade your system to V5R3 from V5R2, and if you are running the V5R2 iSeries Access for Web, then there are some manual steps you will have to run before you can use iSeries Access for Web. What happens is that the V5R2 iSeries Access for Web will automatically be upgraded to V5R3 iSeries Access for Web and some manual steps need to be run post upgrade. It involves the use of the command CFGACCWEB2. Please see the individual instructions for upgrading iSeries Access for Web. I lobbied for this to be included in the Memo to Users but don't know if it made it there. Folks. Don't use this as an excuse to not upgrade to V5R3. Because I don't think IBM will change these situations even with cum #27 or higher. Yes we have found other issues. But most of them have been resolved. Honestly, I have several open incidents with V5R2. And y'all know there have been several cumes out already for V5R2. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Corbett" <tcorbett@xxxxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 07/01/2004 09:56 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To <midrange-l@xxxxxxxxxxxx> cc Fax to Subject V5R3 - ready for prime-time? Al? Hi all, I'm just wondering, should I go ahead and jump on V5R3. I received a shipment from IBM yesterday, haven't had a chance to open yet but I assume it's my copy of V5R3 which I recently ordered. Usually, I'd wait for the first CUM, but it seems that lately IBM has caught on to this and, at least for 5.2, the first cum comes out almost immediately. Al, as always, I follow your lead, is it ready? Or should we wait a little longer? Tony Corbett, IT Director Space Flooring and Supplies, Inc. http://www.spaceflooring.com <http://www.spaceflooring.com/> tcorbett@xxxxxxxxxxxxxxxxx (770) 333-5134 (770) 431-8282 (fax) (404) 784-4737 (cell) -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx 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-2025 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.