RE: MATAGPAT strange behavior?

I have no problem with the need to enter the bug through the APAR process.
These guys[1] in Rochester watch this list out of the goodness of their
hearts, not because it's part of their job description. I'm very grateful
for the help they've provided but I don't expect them to raise these things
themselves.

The "owner" probably took a quick look at the code and said, "Yup, it's a
bug." A process that probably took 60 seconds of his time. On the other
hand, if he then had to open an APAR, describe the problem, enter it into
the bug tracking system, etc. he would have spent _much_ more time on this
issue. If these guys can provide quick "in and out" answers to our questions
they're likely to lurk here, but if they have to spend lots of time on
things that aren't in their schedule then we're likely to loose them.

Now, if it was somebody's job in Rochester to watch this list then I'd
agree... <G>

-Walden

[1] Editorial use of masculine pronoun, don't mean to offend.

PS. Hope this doesn't sound pissy, I'm just tired.


------------
Walden H Leverich III
President
Tech Software
(516) 627-3800 x11
(208) 692-3308 eFax
WaldenL@TechSoftInc.com
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)



-----Original Message-----
From: Dan Bale [mailto:dbale@samsa.com]
Sent: Thursday, April 04, 2002 15:38
To: mi400@midrange.com
Subject: RE: [MI400] MATAGPAT strange behavior?


The technical issue is way over my head.  I personally have no involvement
this "deep" in the MI to worry about it (yet).

I'm glad that Paul from IBM has publically indicated that this has been
confirmed as a bug.  This is a good practice.

Is it just me, or does anyone else find it silly that, although the "owner"
of this has confirmed the bug, that the customer (Gene) must still go
through the APAR rigamarole (sp?).  So, if Gene or any other customer fails
to open an APAR on this, will it forever go unfixed?  Are IBM'ers not
allowed to squeal on themselves?

Also, this is just a curiosity question, and perhaps there's a valid
technical reason, but why can't this be fixed in V5R1?  Isn't V5R1 still
supported?  Is MATAGPAT buggy in any of the supported V4 releases?

- Dan Bale
(I am *NOT* "Dale"
http://archive.midrange.com/midrange-l/200105/msg00281.html ) SAMSA, Inc.
989-790-0507 DBale@SAMSA.com <mailto:DBale@SAMSA.com>
  Quiquid latine dictum sit altum viditur.
  (Whatever is said in Latin seems profound.)

-----Original Message-----
From: mi400-admin@midrange.com [mailto:mi400-admin@midrange.com]On
Behalf Of Paul Godtland
Sent: Thursday, April 04, 2002 3:03 PM
To: mi400@midrange.com
Subject: Re: [MI400] MATAGPAT strange behavior?

The person who owns this instruction implementation confirms that you have
detected a bug, apparently introduced in v5r1. Please feel free to open an
APAR. In this case the problem would get fixed in the next release anyway.
However, a report on a general mailing list doesn't guarantee an official
response, as I'm sure you can understand.

Thanks for asking about this problem.

Paul Godtland
plg@us.ibm.com; t/l 553-7103; Rochester, MN; 030-2, A412

_______________________________________________
This is the MI Programming on the AS400 / iSeries (MI400) mailing list To
post a message email: MI400@midrange.com To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/mi400
or email: MI400-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mi400.