• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

RUNUBE issue

cflick

Member
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C06348.6AA88CC0
Content-Type: text/plain;
charset="iso-8859-1"

JDEList:

I am needing help with the RUNUBE command. Below, please see the
description of the problem and attempts made to identify the crux of the
problem with using RUNUBE. Let me know if you have any information or can
lead us to a solution of more information to assist us in fixing this
problem, or if anyone has encountered the same situation.

Problem Description: UBE R5547011, which processes normally when it is
run on the server through OW, does not process the same way when it is run
using RUNUBE command in AS400 CL program. When running UBE R5547011
through CL using RUNUBE command, an error code M1 is produced and shows in
the output report.
This error code results during the call to JDE standard business function
B4200310.
In summary, we cannot determine the cause of the error code produced
from the call to B4200310 by R5547011 when the UBE is called from CL, while
no error code is produced when the UBE is run in OW.

We have made the following attempts so far to resolved the issue:

(1) We ran the UBE both ways (CL and OW) and produced JDE debug joblogs
and faxed the logs showing the differences to JDE OW support group on
11/1/00.
We were told that they have not heard this type of problem from any of their
other clients. JDE has told us that, since this issue deals with a custom
UBE and a custom CLP, they cannot be responsible for the problem. They
offered me to speak with one of their AS400 specialists to talk about RUNUBE
command in more detail -- I am awaiting for that person to call me in the
near future.

(2) We have rebuilt the JDE standard business functions and their
related data structures in CRP. The Sales Order business functions
(B4200310 and B4200311) were rebuilt in CRP last week. However, this was a
futile attempt as it did not make any difference.

(3) We ran the UBE in a Development environment in an attempt to isolated
the problem as an environment-specific one (i.e. it only occurrs in CRP
environment). But the same discrepancy occurred in Development as well.

It seems like when the UBE is called through CL, the objects on the
server that get used to process the call are different from those that get
used when the call is made from OW. (FYI: this sort of problem has never
surfaced in Production environment.)

The severity of this issue has escalated as we are about to run EDI in CRP
as parallel testing to PROD -- we need to run the CL in an automated
fashion through job scheduler.

------_=_NextPart_001_01C06348.6AA88CC0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2652.35">
<TITLE>RUNUBE issue</TITLE>
</HEAD>
<BODY>



<FONT SIZE=3D2>JDEList:</FONT>
</P>



<FONT SIZE=3D2>I am needing help with the RUNUBE command. =
Below, please see the description of the problem and attempts made to =
identify the crux of the problem with using RUNUBE. Let me know =
if you have any information or can lead us to a solution of more =
information to assist us in fixing this problem, or if anyone has =
encountered the same situation.</FONT></P>



<FONT SIZE=3D2>Problem Description: UBE R5547011, which processes =
normally when it is</FONT>

<FONT SIZE=3D2>run on the server through OW, does not process the =
same way when it is run</FONT>

<FONT SIZE=3D2>using RUNUBE command in AS400 CL =
program. When running UBE R5547011 through CL using RUNUBE =
command, an error code M1 is produced and shows in the output =
report.</FONT></P>



<FONT SIZE=3D2>This error code results during the call to JDE =
standard business function</FONT>

<FONT SIZE=3D2>B4200310.</FONT>

<FONT SIZE=3D2>In summary, we cannot determine the cause of the =
error code produced</FONT>

<FONT SIZE=3D2>from the call to B4200310 by R5547011 when the UBE =
is called from CL, while no error code is produced when the UBE is run =
in OW.</FONT></P>



<FONT SIZE=3D2>We have made the following attempts so far to =
resolved the issue:</FONT>
</P>



<FONT SIZE=3D2>(1) We ran the UBE both ways (CL and OW) and =
produced JDE debug joblogs</FONT>

<FONT SIZE=3D2>and faxed the logs showing the differences to JDE OW =
support group on 11/1/00.</FONT>

<FONT SIZE=3D2>We were told that they have not heard this type of =
problem from any of their other clients. JDE has told us that, =
since this issue deals with a custom UBE and a custom CLP, they cannot =
be responsible for the problem. They offered me to speak with one =
of their AS400 specialists to talk about RUNUBE command in more detail =
-- I am awaiting for that person to call me in the near =
future.</FONT></P>



<FONT SIZE=3D2>(2) We have rebuilt the JDE standard business =
functions and their</FONT>

<FONT SIZE=3D2>related data structures in CRP. The Sales =
Order business functions (B4200310 and B4200311) were rebuilt in CRP =
last week. However, this was a futile attempt as it did not make =
any difference.</FONT></P>



<FONT SIZE=3D2>(3) We ran the UBE in a Development environment =
in an attempt to isolated the problem as an environment-specific one =
(i.e. it only occurrs in CRP environment). But the same =
discrepancy occurred in Development as well.</FONT></P>



<FONT SIZE=3D2>It seems like when the UBE is called through CL, the =
objects on the</FONT>

<FONT SIZE=3D2>server that get used to process the call are =
different from those that get used when the call is made from OW. =
(FYI: this sort of problem has never surfaced in Production =
environment.)</FONT></P>



<FONT SIZE=3D2>The severity of this issue has escalated as we are =
about to run EDI in CRP</FONT>

<FONT SIZE=3D2>as parallel testing to PROD -- we need to run the CL =
in an automated</FONT>

<FONT SIZE=3D2>fashion through job scheduler. </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C06348.6AA88CC0--
 
3 thoughts:

1. try recreating the problem with a vanilla pristine R47011. If it fails you might get more support from jde to solve it.

2. try using CALL RUNUBE instead of the command

3. try the command interactively from a terminal emulation session. I've had different results between a batch and an interactive call of the command. I ended up specifying an outq when submitting the job to batch.

Good luck !

Frank Eckelmann
B733 SP11.3; AS/400; NT; Citrix 6; pcAnywhere 8; CreatePrint
 

Jack_Crouch

Well Known Member
Do you have success with RUNUBE and other UBEs? Is it just this one
custom UBE that does not work?

Has it ever worked or did something happen that indicated the start of this
situation?

It would be interesting to see what the OS/400 job log looks like on this
one - may have a clue or two in it.

Next, you might want to make sure that the Server - Logic OCM is correct for
the UBE and data.

When using RUNUBE you must make sure the specs are up on the Enterprise
Server. So, users must click on Advanced and check the "Submit specs to
Enterprise Server" to get the version specifications up to the path code.
Otherwise, when RUNUBE runs, it has nowhere to get data selection and the
like.



AS400 V4R4, B733.2, SP10USER2, NTSQL7
 
Top