Hello,

It is definitely important to check the Info APAR often, as it is updated
whenever a new issue is discovered by the SSA GT or IBM Support Centers.
This is a changeable document.

Just to clarify the below note, as the word conversion is used and in this
case, it does not refer to any BPCS file data conversion.

The IBM PTF mentioned covers a case where some logical files did not convert
from an older OS/400 release format into the V5R1 DB2 file format, causing
various SQL errors when running BPCS - this could happen in either Mixed
Mode or Client/Server releases of V6 or V8. The PTF corrects the operating
system database conversion issue when upgrading your OS/400 release to V5R1.

Thanks,

Genyphyr Novak
SSA GT

----- Original Message -----
From: "Karlin, Jerry (AP-MIS)" <Jerry.Karlin@UAP.com>
To: <bpcs-l@midrange.com>
Sent: Thursday, February 14, 2002 7:57 PM
Subject: RE: BPCS 5.01.01 AS/400 V5R1


> Hello,
>
> Regarding the APAR II12963, especially v6.X users, do yourself favor and
> review the APAR II12963 frequently prior to your upgrade.  The APAR was
> updated last week, right AFTER we did our conversion.  There are some
> additional notes at the end of the APAR regarding the conversion bypassing
> some logical files.  This 'skipping' of the conversion caused some
> interesting problems with Client/Server.  The latest information is
> regarding PTF SI02796, which has at least one co-requisite PTF requiring
an
> IPL.
>
> The OGS staff were most helpful in quickly identifying this, and I noticed
> upon revisiting the APAR that the revision is now in the APAR II12963.
>
> Regards,
>
>
>
> Jerry Karlin
> IT Mfg Project Lead
> United Agri Products
> Greeley, CO
> BPCS v6.0.04 m/m




This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].