On 25 Jun 2013 10:18, Gerald Kern wrote:
I've noticed that since I've installed RDi V9 I get a lot of these
dumps but I'm not sure why. My guess is it's PTF related but which
PTF? Were there any prerequisites before installing RDi V9? We are at
VR7.1 and TR 4.
<<MCH0602 dump details reformatted as a symptom kwd string:>>
msgMCH0602 F/Ex0602BoundaryAlignment x/0000C4
t/QB5IDEAL tm/B5CTLBASE
tp/__dt__Q2_3std4listXTP12ChangePacketTQ2_3std9all stmt/0000000009
for object type x/1AEF ofs/5D20 QB5SERVER server job
For the archives, knowing what was the preceding message(s) and
message details\context, as recorded in the spooled joblog of the server
JOB(061219/GERALDK/QB5SERVER) [or another job with the same re-create],
might benefit someone else. The following clarifies why there is a
presumption that there might be a more pertinent preceding message.
For reference only: The same error message in an apparent older
release server where the to-program QB5IDEAL was apparently OPM, the
dump was an apparent side effect of a *prior* message that was logged in
the server job. So very likely the preceding error is the origin for a
problem, and the error\termination phase back then and still now,
manifests that alignment error for which the /unmonitored/ effect
according to the dump feature of the message identifier MCH0602 is to
spool that information. Thus even if the unmonitored MCH0602 is a
defect, probably the preceding error needs to be investigated first, as
the source of an error which merely proliferates as further problem(s).
An old APAR SE49401 was opened but then closed as unreproducible, so
IMO having obtained a missing PTF possibly correcting the issue seems
likely for that incident as well as the one recorded above:
http://www.ibm.com/support/docview.wss?uid=swg1SE49401
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.