|
1. Something causes the go downs. 2. The go downs can damage objects which then need to be repaired. 3. This needs to be repaired. 4. Failure to repair this could independently cause a go down.I do not know if this needs "special coding" or if you can just rename the damaged object and recreate a replacement. I do know that you cannot do a backup when a damaged object is involved.
midrange.com
Ok finally found something that might point us in the right direction,
although I am unsure how to address it. I was reviewing the outq and found
the following from yesterday:
MCH1604 Escape 40 10/08/06 21:22:43 #cfdamst
001514 QMHSNDPM QSYS 076C
Message . . . . : System object
QJOBMSGQ damaged. Internal dump ID 01001F97.
Error class 0, device number X'0000'.
Cause . . . . . : This damaged system
object QJOBMSGQ has an error class 0,
and a device number X'0000'. The
following error classes indicate how
damage was detected: 0000-previously
marked damage; 0001-detected abnormal
condition; 0002-logically invalid
device sector; 0003-device error. For
error class 0003, the device number
identifies the damaged device or it
contains zero if main storage is
damaged.
Any idea what steps I should take on this?
Douglas
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.
