UBEs not finishing on the AS/400

AClark

Active Member
B7331, SP 11.1, AS/400 V4R4M0, CO on AS/400


List:

I have had a curious error start happening recently, and JDE does not seem
to have an answer.... Currently, when we submit some, but not all, UBE's
they die on the AS/400. The job entries still remain in the F986110 (Job
Control Status Master) in a Processing status. The job is not running on
the AS/400.

Further inspection finds a job log on the AS/400 that has an error "Pointer
not set for location referenced" from procedure "jdeWriteLogEntry". This
message is MCH3601 on the AS/400. Here are the details:

==========================================================================================================

MCH3601 Escape 40 12/21/00 14:23:49 JDELIB
B7331SYS *STMT JDELIB B7331SYS *STMT
From module . . . . . . . . :
JDEDEBUG
From procedure . . . . . . :
jdeWriteLogEntry
Statement . . . . . . . . . : 70
To module . . . . . . . . . :
JDEDEBUG
To procedure . . . . . . . :
jdeWriteLogEntry
Statement . . . . . . . . . : 70
Message . . . . : Pointer not set
for location referenced.
Cause . . . . . : A pointer was
used, either directly or as a basing
pointer, that has not been set to an
address.
CEE9901 Escape 30 12/21/00 14:23:49 QLEAWI
QSYS *STMT QCMD QSYS 018C
From module . . . . . . . . : QLEDEH
From procedure . . . . . . : Q LE
leDefaultEh
Statement . . . . . . . . . : 232
Message . . . . : Application error.
MCH3601 unmonitored by JDELIB at
statement 0000000070, 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
JDELIB JDEDEBUG jdeWriteLogEntry. The program
was stopped at the high-level
language statement number(s) 0000000070 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.

==========================================================================================================

The only indication that I have in the JDE logs is in the JDEDEBUG.LOG
file. Here are the log entries:

==========================================================================================================

Dec 21 14:23:50 ** Dec 21 14:23:53 ** process 252 unregistered in entry 15
Dec 21 14:23:53 ** IPC3000001 - IPC function called with an invalid handle.
Dec 21 14:23:53 ** IPC3200001 - ipcUnlockResource called with an invalid
handle.
Dec 21 14:23:53 ** IPC3000001 - IPC function called with an invalid handle.
Dec 21 14:23:53 ** IPC3000001 - IPC function called with an invalid handle.

==========================================================================================================

The only reason I found this is because they are close to the same time as
the MCH3601 on the AS/400 JOB LOG.

Bouncing services repeatedly has not helped.

By the way, this happens in DEV733, CRP733, and a custom environment
COE733. The only change that was made recently was a full package build
against DEVB733 and CRPB733. COE733 uses a different path code that has
not changed since October. This problem started happening last week.

Any help that can be provided will be extremely helpful.

Thanks in advance,

Adam Clark
 

b_gilmore

Well Known Member
Re: [UBEs not finishing on the AS/400 ]

Here's a long shot. I've heard of problems with submitting BSFN logic to an
AS/400 Enterprise Server because of case in DEBUG stanza of the JDE.ini file
on the Server.

[DEBUG]
Output=NONE
Trace=FALSE
DebugFile=JDEB7332/jdedebug
JobFile=JDEB7332/jde.log
JDETSFile=/JDEB7332/JDETS.LOG
ClientLog=1

Try setting the DebugFile= and JobFile= values to all caps (like the JDETSFile
value)

Good luck.

AClark <[email protected]> wrote:
> B7331, SP 11.1, AS/400 V4R4M0, CO on AS/400
>
>
> List:
>
> I have had a curious error start happening recently, and JDE does not seem
> to have an answer.... Currently, when we submit some, but not all, UBE's
> they die on the AS/400. The job entries still remain in the F986110 (Job
> Control Status Master) in a Processing status. The job is not running on
> the AS/400.
>
> Further inspection finds a job log on the AS/400 that has an error "Pointer
> not set for location referenced" from procedure "jdeWriteLogEntry". This
> message is MCH3601 on the AS/400. Here are the details:
>
>
==========================================================================================================
>
> MCH3601 Escape 40 12/21/00 14:23:49 JDELIB
> B7331SYS *STMT JDELIB B7331SYS *STMT
> From module . . . . . . . . :
> JDEDEBUG
> From procedure . . . . . . :
> jdeWriteLogEntry
> Statement . . . . . . . . . : 70
> To module . . . . . . . . . :
> JDEDEBUG
> To procedure . . . . . . . :
> jdeWriteLogEntry
> Statement . . . . . . . . . : 70
> Message . . . . : Pointer not set
> for location referenced.
> Cause . . . . . : A pointer was
> used, either directly or as a basing
> pointer, that has not been set to an
> address.
> CEE9901 Escape 30 12/21/00 14:23:49 QLEAWI
> QSYS *STMT QCMD QSYS 018C
> From module . . . . . . . . : QLEDEH
> From procedure . . . . . . : Q LE
> leDefaultEh
> Statement . . . . . . . . . : 232
> Message . . . . : Application error.
> MCH3601 unmonitored by JDELIB at
> statement 0000000070, 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
> JDELIB JDEDEBUG jdeWriteLogEntry. The program
> was stopped at the high-level
> language statement number(s) 0000000070 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.
>
>
==========================================================================================================
>
> The only indication that I have in the JDE logs is in the JDEDEBUG.LOG
> file. Here are the log entries:
>
>
==========================================================================================================
>
> Dec 21 14:23:50 ** Dec 21 14:23:53 ** process 252 unregistered in entry 15
> Dec 21 14:23:53 ** IPC3000001 - IPC function called with an invalid handle.
> Dec 21 14:23:53 ** IPC3200001 - ipcUnlockResource called with an invalid
> handle.
> Dec 21 14:23:53 ** IPC3000001 - IPC function called with an invalid handle.
> Dec 21 14:23:53 ** IPC3000001 - IPC function called with an invalid handle.
>
>
==========================================================================================================
>
> The only reason I found this is because they are close to the same time as
> the MCH3601 on the AS/400 JOB LOG.
>
> Bouncing services repeatedly has not helped.
>
> By the way, this happens in DEV733, CRP733, and a custom environment
> COE733. The only change that was made recently was a full package build
> against DEVB733 and CRPB733. COE733 uses a different path code that has
> not changed since October. This problem started happening last week.
>
> Any help that can be provided will be extremely helpful.
>
> Thanks in advance,
>
> Adam Clark
>
>
>
>
>
>
> --------------------------
> To view this thread, visit the JDEList forum at:
>
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=3199

> *************************************************************
> This is the JDEList One World / XE Mailing List.
> Archives and information on how to SUBSCRIBE, and
> UNSUBSCRIBE can be found at http://www.JDELIST.com
> *************************************************************


____________________________________________________________________
Get free email and a permanent address at http://www.amexmail.com/?A=1
 

Jack_Crouch

Well Known Member
I thought I was being cute one day by creating a /home/jde directory in the IFS. Big mistake... Suddenly the jobs that run were having trouble finding /JDEB7332 to write their logs in. I couldn't find a log to tell me what was wrong. A bootstrap problem of sorts.

So I changed the home directory to root / and it all started writing to /JDEB7332 again. It almost sounds as if your system is having trouble accessing the IFS for some reason. Seems it would be all the time and not just on some...

Are you getting a .log file in the IFS for all jobs?

Do all jobs run under JDE on the 400? Or are you using user profiles? Have you done anything to your IFS settings (either on user profiles or the system)?



AS400 V4R4, B733.2, SP11.3, NT-SQL7 for CO
 
Top