UBE Waiting

[fmpadron]

I have Oneworld Xe and I have problems with UBE´s because theirs dont run properly, when I send one of them the UBE stay in Waiting Status and I cant correct this, Please Help me with any idea.
For any answer THX a lot.

 

[Tricia_Rosas]

We were having this problem with our AS400 Ube's would go into a MTXW
status and would lock out other jobs from running. Our users would start
calling because their jobs would be in a waiting status in OW. We
installed ESU 4083190 and this took care of the problem.

We are B733.2/SP11.3/AS400/WNNT/SQL7.0.


Tricia Rosas
Edwards Cardiovascular Resources
Assoc. Technical Specialist
(WK) 858-798-7113 (FAX) 858-675-7113
(Email) [email protected]



fmpadron
<fmpadron@hotmail To: [email protected]
.com> cc:
Sent by: Subject: UBE Waiting ~~0:3018
owner-jdelistml@j
delist.com


12/20/00 12:47 PM
Please respond to
jdelist






I have Oneworld Xe and I have problems with UBE$B!-(Bs because theirs dont run
properly, when I send one of them the UBE stay in Waiting Status and I cant
correct this, Please Help me with any idea.
For any answer THX a lot.


--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat
=&Board=OW&Number=3018
*************************************************************
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
*************************************************************

 

[brother_of_karamazov]

The queue is not up and running properly.



--- fmpadron <[email protected]> wrote:
> I have Oneworld Xe and I have problems with UBE´s
> because theirs dont run properly, when I send one of
> them the UBE stay in Waiting Status and I cant
> correct this, Please Help me with any idea.
> For any answer THX a lot.
>
>
> --------------------------
> Visit the forum to view this thread at:
>
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=3018
>
>
*************************************************************
> 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
>
*************************************************************
>


__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/

 

[SSAJAROFF]

Please, describe your platform (OS,RDBMS,SP,Clients)

Thanks

-----Mensaje original-----
De: fmpadron [mailto:[email protected]]
Enviado el: miércoles 20 de diciembre de 2000 17:48
Para: [email protected]
Asunto: UBE Waiting ~~0:3018


I have Oneworld Xe and I have problems with UBE´s because theirs dont run
properly, when I send one of them the UBE stay in Waiting Status and I cant
correct this, Please Help me with any idea.
For any answer THX a lot.


--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=3
018
*************************************************************
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
*************************************************************

 

[fmpadron]

The platform is NTServer 4.0 SP6a with SQL7.0 SP2 HotFix851, MDAC 2.5, C++ 6.0 SP3 in both servers

 

[got_to_love_jde]

Certainly there is something wrong with the services. You can cause this problem if you start the queue service before the network service. You can also cause this problem if you do not wait a short period of time (30 seconds to 1 minute) after starting network service before you start the queue service.
Also, check to make sure you have valid users with valid passwords in the jde.ini on the enterprise server. there are user and password entries for the network, one world & the sql data base.
good luck,
dave



NT 4.0 SP5, SQL 7.0, One World B7321 SP12.4, Citrix

 

[MSiebenschuh]

Is it a particular queue (meaning you are running multiple queues)? Is it
just this particular report or do all reports going to this queue go into a
permanent wait status? Does this queue run for a period of time before
making all reports go to a W status? My initial thought would be that either
the queue service for that defined queue has died or was never started when
you bounce OW. Pretty simple to check in UNIX you would just do a ps
-ef|grep [QUEUE NAME]. If you see it in the listing then you might want to
just kill that job and restart it. You also need to make sure that your are
really using the right queue (i.e. Server starts a queue called QBATB733 as
defined in your startup script but the users JDE.INI has the queue set to
QBAB733) I'm not sure how you would do this on an AS400 or NT. We have had
such a problem with UBE's killing queues that we moded our config to
auto-restart any queue process that dies after it e-mails us. Hope this
helps.

Mark Siebenschuh
HP9000
Oracle 8.0.5
JDEB733 Base SP3

 

[jgersic]

I don't know if this pertains to you, but..At my last employer for a long
time we had the same problem of UBE's going into a wait state. The only way
we could get them 'unstuck' was to start/stop the queue service on the
enterprise server. The unique thing with our setup was that we had two
enterprise servers, one for crp/dev and one for prod and central objects
were on the DEV/CRP box (this is because we had never thought we would have
a second enterprise and when we added it we did not move the objects
immediately). Anyways, after we moved central objects from the crp/dev box
to the enterprise box, the issue went away. This was a huge issue for us,
and we had JDE consultants/advanced technologies, as well as numerous
business partners and they never figured it out.
If you have two or more enterprise servers, are your central objects
residing on your production box? I know this should not make a difference,
and shouldn't have for us, but it is the only thing that changed in our
circumstance which leads me to believe maybe there was a communications
issue between the boxes and it would just timeout (nope, nothing in any logs
about jdenet timing out)...
I just bought the JDE complete reference, and they have a section in there
on troubleshooting, maybe there will be something in there that is new....

John

 

[got_to_love_jde]

another thought....this can also happen if you kill the services and then start them back up before all of the kill* jobs are done. go into the Task Manager on the enterprise server after ending the services and make sure these jobs end before you re-start the services.


NT 4.0 SP5, SQL 7.0, One World B7321 SP12.4, Citrix

 

[AGARIA]

Does your porttest work on your Enterprise Server? Verify it works.