Discussion:
MCH3601-CPI2417 "Job message queue for ... has been wrapped" - IXS
(too old to reply)
Stanguru
2006-07-17 13:35:24 UTC
Permalink
posted again, in hopes of someone having same problem(with solution):
Job message queue for 124778/QSYS/IPCSSERVER has been wrapped.

error in IXS job MCH3601 CPI2417

v5r3r0 IXS 2892-002 (Integrated Server...aka IPCS)

QSYSOPR message queue gets CPI2417 "Job message queue for ... has been
wrapped"

which is the IXS(IPCS) job getting a MCH3601 "Pointer not set for
location referenced." (this gets posted like 200x per minute)

i get have gotten this 4 times since upgrading to v5r3 over 6mths ago
now sure i can reboot the NT side and its fine, but i cant do it until
a better opportunity. i have combed over the NT side and cant find any
info/logs on something blowing up...and i search through the 400 side
and cant come up with anything.

call stack is this (in which i think the last 2 programs/procedures is
maybe messing up with a incorrect dataqueue call)
QCMD
XX_PEP__Fv ADMINMON QVNAAMON Yes
main ADMINMON QVNAAMON No
_6DaemonFv DAEMON QVNAAMON No
7ComRockPv HOUSEHAN QVNAAMON No
rP7ComRock HOUSEHAN QVNAAMON No
00_net_env ENVSTAT QVNAAMON No
00_net_env ENVSTAT QVNAAMON No
ion_router QC2SIGNL QC2UTIL1 No
ss__FUiPvc QC2SIGNL QC2UTIL1 No


here is the joblog message:

Message ID . . . . . . : MCH3601 Severity . . . . . . . : 40

Date sent . . . . . . : 07/17/06 Time sent . . . . . . :
09:28:09
Message type . . . . . : Escape
65535
From program . . . . . . . . . : QVNAAMON
From library . . . . . . . . : QNTAP

From module . . . . . . . . : ENVSTAT

From procedure . . . . . . . :
ExtractNetContents__5StatEFP14aix400_net_
env

From statement . . . . . . . : 57


i have cleared all the event logs on the NT side thinking that might
be the problem
its eating my CPU, but not bad enough to kick everyone off
immediately

TIA

StanMan
nsm
2006-07-17 21:29:24 UTC
Permalink
I think you're problem is in OS/400. The server job obviously crashes
if the joblog is wrapped.

I don't know if you have a weekly time scheduled for IPL'ing your
AS/400 (recommended). This would minimize the risk of joblogs running
full.

If this IS the case, you might want to change some of the system
values, which control the maximum size of joblogs, whether extra space
can be added and so on ..

If you don't have regular IPL's on your system, and don't want to have
them, you might wan't to change the jobs logging values, to ensure that
as little as possible is logged to the joblog, within the specific job.
The disadvantage is that you have to do this, WHEN you decide to IPL --

Niels
Post by Stanguru
Job message queue for 124778/QSYS/IPCSSERVER has been wrapped.
error in IXS job MCH3601 CPI2417
v5r3r0 IXS 2892-002 (Integrated Server...aka IPCS)
QSYSOPR message queue gets CPI2417 "Job message queue for ... has been
wrapped"
which is the IXS(IPCS) job getting a MCH3601 "Pointer not set for
location referenced." (this gets posted like 200x per minute)
i get have gotten this 4 times since upgrading to v5r3 over 6mths ago
now sure i can reboot the NT side and its fine, but i cant do it until
a better opportunity. i have combed over the NT side and cant find any
info/logs on something blowing up...and i search through the 400 side
and cant come up with anything.
call stack is this (in which i think the last 2 programs/procedures is
maybe messing up with a incorrect dataqueue call)
QCMD
XX_PEP__Fv ADMINMON QVNAAMON Yes
main ADMINMON QVNAAMON No
_6DaemonFv DAEMON QVNAAMON No
7ComRockPv HOUSEHAN QVNAAMON No
rP7ComRock HOUSEHAN QVNAAMON No
00_net_env ENVSTAT QVNAAMON No
00_net_env ENVSTAT QVNAAMON No
ion_router QC2SIGNL QC2UTIL1 No
ss__FUiPvc QC2SIGNL QC2UTIL1 No
Message ID . . . . . . : MCH3601 Severity . . . . . . . : 40
09:28:09
Message type . . . . . : Escape
65535
From program . . . . . . . . . : QVNAAMON
From library . . . . . . . . : QNTAP
From module . . . . . . . . : ENVSTAT
ExtractNetContents__5StatEFP14aix400_net_
env
From statement . . . . . . . : 57
i have cleared all the event logs on the NT side thinking that might
be the problem
its eating my CPU, but not bad enough to kick everyone off
immediately
TIA
StanMan
Loading...