business function timeout

david

Active Member
Hello List-

Thanks for any tips in advance:

We are Xe, SP 15.1, AS\400 ent svr, NT wkstn.

We have a business function that is executed from a client workstation and runs on the server. After about 5 mins, the client receives an error message of 99 and about 20 secs after the client receives the message, the client (NOT the person at the wkstn) re-submits the BSFN. The first job, continues to run, and the new job is now running in parallel--not good. Again, after 5 mins, the client receives an error message of 99, only this time the client does NOT re-submit the BSFN--it moves on as if the server finshed--BUT BOTH JOBS ARE STILL RUNNING on the server.

Here is what we want the BSFN to do: We want the BSFN to run on the server until finished--could be awhile. We want the client to wait for the job to finish. We do not want the job to be re-submitted. We want it to run once!

Anyone with experience in this area?!

Thanks again,
David

David Schoenberger
Focus on the Family
Xe SP15.1, AS/400, NT workstations, 700+ fat client users
 

david

Active Member
NO! That is the problem--the timeout that the client receives then kicks off another BSFN on the server and runs with the first BSFN--We only want one to run and run until done WITHOUT a timeout/error code 99.

David Schoenberger
Focus on the Family
Xe SP15.1, AS/400, NT workstations, 700+ fat client users
 

franck_blettner

Active Member
Map the business function to the server with ocm mapping (Fast Path : ocm).
If you want more detail to use ocm mapping, send me an email.

Franck BLETTNER
Service Informatique RAVATE
Tel : 02 62 90 40 63
E-mail : franck.blettner@ravate.com


-----Message d'origine-----
De : owner-jdeowdevml@jdelist.com
[mailto:eek:wner-jdeowdevml@jdelist.com]De la part de david
Envoyé : lundi 9 juillet 2001 18:31
À : jdeowdevml@jdelist.com
Objet : business function timeout


Hello List-

Thanks for any tips in advance:

We are Xe, SP 15.1, AS\400 ent svr, NT wkstn.

We have a business function that is executed from a client workstation and
runs on the server. After about 5 mins, the client receives an error
message of 99 and about 20 secs after the client receives the message, the
client (NOT the person at the wkstn) re-submits the BSFN. The first job,
continues to run, and the new job is now running in parallel--not good.
Again, after 5 mins, the client receives an error message of 99, only this
time the client does NOT re-submit the BSFN--it moves on as if the server
finshed--BUT BOTH JOBS ARE STILL RUNNING on the server.

Here is what we want the BSFN to do: We want the BSFN to run on the server
until finished--could be awhile. We want the client to wait for the job to
finish. We do not want the job to be re-submitted. We want it to run once!

Anyone with experience in this area?!

Thanks again,
David

David Schoenberger
Focus on the Family
Xe SP15.1, AS/400, NT workstations, 700+ fat client users
--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OWDEV&Numbe
r=15687


Franck BLETTNER
Service Informatique RAVATE
Tel : 02 62 90 40 48
E-mail : franck.blettner@ravate.com
 
Call Orchestrations From Excel – The Easy Way to Make the Orchestrator Work for You.

Larry_Jones

Legendary Poster
David,

the point of an asynchronous call is that the caller does not wait - it calls the BSFN or UBE and then moves on. So a timeout condition due to a very long running process should not be an issue. The only issue is whether or not your application design needs values returned back - and it really shouldn't if this is a client process waiting. Clients should ideally not wait more than a few seconds. When your wait time is measured in minutes there are too many things that can go wrong.

Regards,

Larry Jones
ljones@wagstaff.com
OneWorld XE, SP 15.1
HPUX 11, Oracle SE 8.1.6
Mfg, Distribution, Financials
 

david

Active Member
Thanks to all who gave a few tips:

As it turns out, it is a foundational code "change" that occurred when we upgraded to SP15.1. JDE is working on a "one-off" to correct this. The problem has been diagnosed as the server not sending a reply to the client telling the client that the BSFN has started--AS IT SHOULD--and did before 15.1! The fact that the client is re-submitting the job shows us that it is doing EXACTLY what it is supposed to do! If the server doesn't talk back, then the client doesn't know any better!

Aaaah. Upgrades...

David Schoenberger
Focus on the Family
Xe SP15.1, AS/400, NT workstations, 700+ fat client users
 
Top