AS/400 Y2K bug

Neil wrote:
>Marty,
>
>Just a comment here, and maybe this has already been done but it's just
>not in the area you work in.  You mention it's a known problem and the
>fix is built into a future release.  As it's a Y2K bug problem this fix
>should automatically trigger a PTF to be created for all Y2K compliant
>releases whether or not one of our Midrange-L colleagues in Japan opens
>a support call which would to trigger an APAR.  In fact, shouldn't
>someone in Rochester (whoever discovered the problem) already have
>opened an APAR internally against V3R2/V3R7/V4R1/V4R2 & V4R3 for this ?
>
>If not I'm sure we'd like to know why it would take a customer to
>complain specifically before an APAR was opened for a known Y2K bug.
>
>
>Neil Palmer         DPS Data Processing Services Canada Ltd.

Neil,
You raise good questions, but I am not the one to answer them.  You need
to work through your normal support channels for questions about APARs,
PTFs, and Y2K fix policy.

Thankfully, I haven't had a Y2K bug in my code yet.  I've looked, and
tested, and don't think there is one, but I'll fix it if one is
discovered.  So, I really don't know what the policy is, and can't
answer your questions.  I don't even know which releases are
certified to be Y2K compliant, although I know who to ask if the need
arises.

Please, please ask your normal support channels.  I made a mistake in
even answering the first inquiry, since it was not code I own, and
any attempt I make to answer further questions about areas outside
my responsibility will only make things worse.

As I said earlier, I am sorry if I misled anyone.  This is the last
I can say on the matter.

Sincerely,
Marty Keech
IBM AS/400 APPC, Payment Server, 'N Stuff (but *not* Y2K policy!)
+---
| 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
+---