RE: IBM overhauls iSeries for the long haul

And that Memo to Users also documents some serious changes in CPYFRMIMPF. 
Buries it in a lot of gobbly gook.  But basically they've went hog wild on 
CCSID and you gotta get the planets just in the right alignment to get it 
to work.  Odds are high some application changes might be necessary.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Kevin Wright <Kevin.Wright@xxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
08/16/2004 06:18 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
RE: IBM overhauls iSeries for the long haul






Hi James,

Au contraire! I can think of 3 things with V5R3 that must have caused many
vendors much grief, and made them very happy to be on the Early Ship
program. Neither of them to my mind are hacks:
 - change to the rules for unlinking etc from the /tmp directory in the 
IFS
 - change to the QSYGETPH api parameter rules when specifying a password
 - change to system value QIGC

In the 1st case there is a documented method to get the pre V5R3 behaviour
which needed a PTF to make it stick across IPLs, while in the 2nd case 
there
is a PTF with special instructions to get the pre V5R3 behaviour for 6
months (then 6 months more and so on). 

Admittedly the QSYGETPH change was foreshadowed in the V5R2 Memo to Users.

How many vendors (& inhouse developers) will be caught out by things
foreshadowed in the V5R3 Memo to Users? eg 

 - Programs that use customzed versions of IBM-supplied commands
 - Library QGY disappearing sometime
 
Regards,

Kevin Wright
Software vendor employee

> -----Original Message-----
> From: James H H Lampert [mailto:jamesl@xxxxxxxxxxx]
> Sent: Tuesday, 17 August 2004 8:30 AM
> To: midrange-l@xxxxxxxxxxxx
> Subject: Re: IBM overhauls iSeries for the long haul
> 
> 
> > Would I be more impressed by a vendor that supported V2R3 
> or a vendor
> > who  participated in the early ship program?  Early ship program -
> > without a  doubt.  I want someone who's software is going 
> to run on the
> > latest  hardware and software.  Not someone who is going to 
> be one of
> > the later  ones to be compatible.
> 
> Actually, we HAVE participated in the Early Ship program. We 
> haven't for
> V5, but we've done V5 compatibility testing on other systems, mostly
> courtesy of IBM, and my guess is that we'll be getting a V5 
> box for other
> projects (but that will be available for testing our 
> already-established
> products) sometime this year.
> 
> And if a vendor actually NEEDS the latest hardware and OS in 
> order to be
> confident of COMPATIBILITY with the latest hardware and OS, 
> that kind of
> suggests that the vendor's products use a lot of hacks.
> 
> --
> JHHL
> 
> 
> 
> 
> --
> 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.
> 
--
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.