8.9 AS/400 UBEs error intermittently

[b_gilmore]

Hi all.

Was wondering if anyone is running 8.9 on the AS/400 V5R2.
We are at SP 8.93_D1 with the latest and greatest cumulative update and CAX
SP.

About 15 UBEs out of about 1000 per day return an error in work with submitted
reports. The user who submitted the job will resubmit it and it will most
times run successfully. We build full packages every weekend and delete
SQLPKGs every Saturday. The IPC section of my JDE.INI is:
[JDEIPC]
maxNumberOfResources=1000
startIPCKeyValue=2101
avgResourceNameLength=15
maxMsgqEntries=1024
maxMsgqBytes=65536
ipcTrace=0


In every job that errors. The following can be found in the log.
**********************************
INFO: Done setting IPC Handle State structures to abandoned. Process exiting.
iParam: 0000005218
**********************************

Is anyone else seeing this behavior?

Thanks.
Bruce Gilmore

 

[Jack_Crouch]

Yes, we are experiencing the same deal. We have E8.10 at 8.93 G1 (in development at the moment).

I have case# 3619390 opened with PSFT on it. Join the case (if possible) to help raise the issue up.

I suspect you will see that these are blowing up with MCH3601 in program DLAPDFL502. DLA is the Data Logics modules used to produce and deal with PDFs.

I know what DLA is because we have had a bad experience a long time ago on Service Pack 11. Basically, this same MCH3601 was occurring randomly with many of our production UBE jobs. It got so bad that a JDE and DLA developer were sent on site with us to witness and deal with the problem.

Anyway... I think we are seeing a variant of that same issue.

 

[Cesar]

I have the same problem with DLAPDFL502 (V5R2, 8.93_D1). I received a new version of this program to test and it seems to work fine, no jobs ended abnormally in the past 2 days in our development AS/400 system.

If you look at the objetc DLAPDFL502 in B9SYS, the old one has the text 'APDFL v5.0.2PlusP4e - PDFL Core' . The text of the new object is 'APDFL 5.0.2PlusP4k XAP disabled '.

Tomorrow I'm going to install this new version on the production system and follow closely the execution of UBEs.

 

[HolderAndrew]

Hi Cesar,

how did you get on with the new version, are your UBEs working ok now?

I posted the message below a couple of months ago but we are still seeing this problem from time to time which I think is similar to the problem on this thread. Apologies to everyone for posting this a second time but we have now upgraded to V5R2 and are on SP22 but are still facing the same problem.

******************
Hi All,

we are running many subsystem UBEs and 'normally' submitted UBEs daily on AS400 iseries (R810) V4R5M0 with Xe Base. We have had a relatively trouble free production environment now for the last couple of years but recently we have been experiencing some serious UBE failures. The first thing that we notice were job failures from the UBEs which are submitted from Job Scheduler via the RUNUBE command. The log on the AS400 is as follows:

*************** START *********
C2M1601 Escape 30 30/09/04 19:18:05 QC2UTIL1 QSYS *STMT RUNUBE B7333SYS *STMT

From module . . . . . . . . : QC2SIGNL
From procedure . . . . . . : raise
Statement . . . . . . . . . : 5
To module . . . . . . . . . : RUNUBE
To procedure . . . . . . . : main
Statement . . . . . . . . . : 334 *PRCLT
Message . . . . : Signal SIGABRT raised (abnormal termination).
Cause . . . . . : The signal SIGABRT was raised to indicate an abnormal
termination.
************ END ********************

Initially I thought that this might be related to the MCH3601 errors that we got about 2 years ago and which was related to a DataLogics PDF support PTF that we needed. The module in question for those errors was DLAPDFLKG. But I don't think that this is the same problem. This error has happened now about 6 or 7 times in the last week. When the error occurs we shut down services and restart. The strange thing is sometimes jobs still fail immediately after the restart and others work ok.

The jde.log that we are getting (on the server) on both manually submitted UBEs and on UBEs submitted from Job Scheduler is as follows:


******** START OF JDE.LOG ***************
Sep 30 19:44:50 ** **** jdeDebugInit -- output disabled in INI file.
4551665

18276 Thu Sep 30 19:44:49 2004 ipcpub.c2903
process 18276 <B7333SYS/PRINTUBE> registered in entry 87

18276 Thu Sep 30 19:44:49 2004 runbatch.c631
Startup for User=SUIHKJOF, Env=PDFIN7333, Job#=4551665

18276 Thu Sep 30 19:44:49 2004 ipccrt.c216
IPC2100004 - ~Krnl18276RspQ not created, maxNumberOfResources parameter (1000) exceeded on allocation of IPCData.

18276 Thu Sep 30 19:44:49 2004 jdb_ctl.c1991
Net init failed or not initialized

18276 Thu Sep 30 19:44:51 2004 runbatch.c1101
RUNBATCH: Remote CP=1252, Remote OS=5, Local CP=37, ConvertToASCII=0

******** END OF JDE.LOG **************

The debug log (first page only!) is as follows:

********** START OF DEBUG.LOG ************
Sep 30 19:58:04 ** **** jdeDebugInit -- output to file.
<B7333SYS/RUNUBE> registered in entry 90

/RUNUBE> registered in entry 90
18307 Thu Sep 30 19:58:03 2004 runube.c537
Startup for User=WHSBATCH, Env=PDFIN7333, Report=R592000S, Version=TF8004

Sep 30 19:58:03 ** KERNEL type = KERNEL_UBE
Sep 30 19:58:03 ** JDERT_IsRealTimeEnabled setting g_IsRealTimeEnabled as 0
Sep 30 19:58:03 ** JDERT_IsRealTimeEnabled setting g_IsXAPIEnabled as 0
Sep 30 19:58:03 ** ONEWORLD Session started in ENV PDFIN7333 for WHSBATCH
Sep 30 19:58:03 ** Entering JDB_InitEnv
Sep 30 19:58:03 ** IPC2100004 - ~Krnl18307RspQ not created, maxNumberOfResources parameter (1000) exceeded on allocation of IPCData.
18307 Thu Sep 30 19:58:03 2004 ipccrt.c216
IPC2100004 - ~Krnl18307RspQ not created, maxNumberOfResources parameter (1000) exceeded on allocation of IPCData.

18307 Thu Sep 30 19:58:03 2004 jdb_ctl.c1991
Net init failed or not initialized

Sep 30 19:58:03 ** Entering JDB_SetEnv
Sep 30 19:58:03 ** Entering JDB_InitUser with commit mode 0.
Sep 30 19:58:03 ** Entering JDB_BeginTransaction
Sep 30 19:58:03 ** Locking /PD7333/specfile/gbrlink.ddb in READ mode.
Sep 30 19:58:03 ** LOCK: Total READ locks after operation: 1

********** END OF DEBUG LOG ************


It appears that we are now exceeding somekind of limit with IPC resources?

Part of our jde.ini file (which I hope is the relevant bit!)is as follows:


^JDEIPC]
maxNumberOfResources=1000
startIPCKeyValue=3001
avgResourceNameLength=15
maxMsgqEntries=1024
maxMsgqBytes=65536
ipcTrace=0

^JDENET]
serviceNameListen=6010
serviceNameConnect=6010
maxNetProcesses=20
maxNetConnections=2800
netShutdownInterval=15
maxKernelProcesses=100
maxKernelRanges=13
netTrace=0

I would be very grateful if somebody could suggest some actions that might help us to solve this problem. We could of course just increase the 1000 resource parameter but it would be nice to know why we have suddenly reached this limit? And anyway we are not sure that by just raising this value might introduce some other errors! We have contacted peoplesoft for their advice but I was hoping that some of you experienced guys out there have already seen this problem and know the answer!

Thanks for any replies in advance.

*******************