|
midrange.com
Extensive hardware upgrades on 570 this weekend. (You know things are
getting tense when screwdrives fly across the room - and the pitcher was
the IBM CE.)
10 of 11 DPARs on the one lpar are behaving. One, however, will not
start.
Submitted pmr electronically but didn't get pmr number back. Waiting for
email that pmr was really created. Refreshing the list of pmr's isn't
getting updated.
5722SS1 V5R4M0 060210 Display Job Log GDIHQ
07/31/06 07:28:28 Page 1
Job name . . . . . . . . . . : SERVER User . . . . . . :
QNOTES Number . . . . . . . . . . . : 456170
Job description . . . . . . : GDSSALES Library . . . . . :
QUSRNOTES
MSGID TYPE SEV DATE TIME FROM
PGM LIBRARY INST TO PGM LIBRARY INST
CPI3BC4 Information 20 07/31/06 07:20:29.726224 QLGSJATR
QSYS 0336 QWTPIIPP QSYS 0251
Message . . . . : Job attributes
not set from locale.
Cause . . . . . : The user profile
associated with this job has the
SETJOBATR value set to use some of
the locale fields as job attributes. If
the value in the locale is not
valid for a job attribute, the job attribute
will be set from the user profile.
Use the reason number to determine if a
job attribute was selected and set
from the locale. Job attribute for CCSID
-- Reason 0 Job attribute for date
format -- Reason 0 Job attribute for date
separator -- Reason 0 Job attribute
for time separator -- Reason 0 Job
attribute for sort sequence --
Reason 1 Job attribute for decimal format --
Reason 0 Reason 0 - Job attribute
selected and set from locale. Reason 1 -
Job attribute selected but not set
from locale. Reason 2 - Job attribute not
selected. See previous messages in
the job log for additional information.
CPF1124 Information 00 07/31/06 07:20:29.733280 QWTPIIPP
QSYS 066E *EXT *N
Message . . . . : Job
456170/QNOTES/SERVER started on 07/31/06 at 07:20:29
in subsystem GDSSALES in QUSRNOTES.
Job entered system on 07/31/06 at
07:20:29.
MCH3402 Escape 40 07/31/06 07:20:30.033136 LIBNOTES
QDOMINO654 *STMT LIBNOTES QDOMINO654 *STMT
From module . . . . . . . . : CLEANUP
From procedure . . . . . . :
OSFaultRecoveryRemovePid
Statement . . . . . . . . . : 1
To module . . . . . . . . . : CLEANUP
To procedure . . . . . . . :
OSFaultRecoveryRemovePid
Statement . . . . . . . . . : 1
Message . . . . : Tried to refer to
all or part of an object that no longer
exists.
Cause . . . . . : The most common
cause is that a stored address to an
object is no longer correct because
that object was deleted or part of the
object was deleted.
CEE9901 Escape 30 07/31/06 07:20:30.094888 QLEAWI
QSYS *STMT QP0ZPCPN QSYS *STMT
From module . . . . . . . . : QLEDEH
From procedure . . . . . . : Q LE
leDefaultEh
Statement . . . . . . . . . : 183
To module . . . . . . . . . :
QP0ZPCPN
To procedure . . . . . . . :
InvokeTargetPgm__FP11qp0z_pcp_cb
Statement . . . . . . . . . : 210
Message . . . . : Application
error. MCH3402 unmonitored by LIBNOTES at
statement 0000000001, instruction
X'0000'.
Cause . . . . . : The application
ended abnormally because an exception
occurred and was not handled. The
name of the program to which the
unhandled exception is sent is
LIBNOTES CLEANUP OSFaultRecoveryRemovePid.
The program was stopped at the
high-level language statement number(s)
0000000001 at the time the message
was sent. If more than one statement
number is shown, the program is an
optimized ILE program. Optimization does
not allow a single statement number
to be determined. If *N is shown as a
value, it means the real value was
not available. Recovery . . . : See
the low level messages previously
listed to locate the cause of the
exception. Correct any errors, and
then try the request again.
CPF24A3 Escape 40 07/31/06 07:20:30.123024 QMHSNDPM
QSYS 0BA6 QLEAWI QSYS *STMT
To module . . . . . . . . . : QLEDEH
To procedure . . . . . . . : Q LE
leDefaultEh
Statement . . . . . . . . . : 183
5722SS1 V5R4M0 060210 Display Job Log GDIHQ
07/31/06 07:28:28 Page 2
Job name . . . . . . . . . . : SERVER User . . . . . . :
QNOTES Number . . . . . . . . . . . : 456170
Job description . . . . . . : GDSSALES Library . . . . . :
QUSRNOTES
MSGID TYPE SEV DATE TIME FROM
PGM LIBRARY INST TO PGM LIBRARY INST
Message . . . . : Value for call
stack counter parameter not valid.
Cause . . . . . : The value 4,
specified for call stack counter parameter,
is not valid. The value was
specified in parameter number 7 on the API.
Recovery . . . : Correct the
value for call stack counter parameter and
try the request again. This value
must be greater than or equal to 0 but
cannot be larger than the number of
entries on the call stack.
CEE9901 Diagnostic 30 07/31/06 07:20:30.134008 QLEAWI
QSYS *STMT QP0ZPCP2 QSYS *STMT
From module . . . . . . . . : QLETOOL
From procedure . . . . . . : Q LE
CPF24A3_handler
Statement . . . . . . . . . : 3
To module . . . . . . . . . :
QP0ZPCP2
To procedure . . . . . . . :
_CXX_PEP__Fv
Statement . . . . . . . . . : *N
Message . . . . : Application
error. CEE9901 unmonitored by QP0ZPCPN at
statement 0000000210, instruction
X'0000'.
Cause . . . . . : The application
ended abnormally because an exception
occurred and was not handled. The
name of the program to which the
unhandled exception is sent is
QP0ZPCPN QP0ZPCPN
InvokeTargetPgm__FP11qp0z_pcp_cb.
The program was stopped at the high-level
language statement number(s)
0000000210 at the time the message was sent.
If more than one statement number
is shown, the program is an optimized ILE
program. Optimization does not
allow a single statement number to be
determined. If *N is shown as a
value, it means the real value was not
available. Recovery . . . : See
the low level messages previously listed
to locate the cause of the
exception. Correct any errors, and then try the
request again.
CPC1219 Completion 50 07/31/06 07:20:30.139264 QWTPITP2
QSYS 0601 *EXT *N
Message . . . . : This job ended
abnormally.
Cause . . . . . : An error occurred
that caused this job to end abnormally.
Recovery . . . : See the
previously listed messages in the job log for
this job. Correct the errors and
try the request again.
CPF1164 Completion 00 07/31/06 07:20:30.139848 QWTMCEOJ
QSYS 00D7 *EXT *N
Message . . . . : Job
456170/QNOTES/SERVER ended on 07/31/06 at 07:20:30; 1
seconds used; end code 30 .
Cause . . . . . : Job
456170/QNOTES/SERVER completed on 07/31/06 at 07:20:30
after it used 1 seconds processing
unit time. The job had ending code 30.
The job ended after 1 routing steps
with a secondary ending code of 0. The
job ending codes and their meanings
are as follows: 0 - The job completed
normally. 10 - The job completed
normally during controlled ending or
controlled subsystem ending. 20 -
The job exceeded end severity (ENDSEV job
attribute). 30 - The job ended
abnormally. 40 - The job ended before
becoming active. 50 - The job ended
while the job was active. 60 - The
subsystem ended abnormally while
the job was active. 70 - The system ended
abnormally while the job was
active. 80 - The job ended (ENDJOBABN command).
90 - The job was forced to end
after the time limit ended (ENDJOBABN
command). Recovery . . . : For
more information, see the Work Management
topic in the Information Center,
http://www.ibm.com/eserver/iseries/infocenter.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.
