× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Actually, the best place to ask these questions is on IBM's EGL forums. Midrange.com isn't exactly EGL central, and in fact EGL questions were specifically directed away from the more general lists such as WEB400-L.

I've started spending more time over at IBM's forums, and the folks are pretty knowledgeable.

http://www.ibm.com/developerworks/forums/forum.jspa?forumID=2275

And as to your question, a lot has to do with how you define your services. EGL supports SOAP, REST and dedicated services (with dedicated services - new in V8 - you don't even have to worry about connections or URLs or WSDLs, EGL does it all for you). EGL also supports stateful services, which I think may be part of your problem. Stateful services are very powerful, but they require a bit more management.

I'd suggesting making a post or two over at the EGL forums.

Joe

Hello all,



I asked this question on the EGL list, but it seems to be low on users.



So with that being said, can someone tell me why there is a a large amount
of QZDASOINIT& QZRCSRVS jobs in QUSRWRK (over 100). When i look at the job
logs for these, it looks like calls to iseries programs from my RUI service
program. Many of the jobs have open files too. Some open files are also
repeating for the same job.



They all look like prestart jobs.



Is this normal?



Is there a better technique i should be using to avoid this?



Are the jobs eating up resources?





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.