×
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.
I'm working with a client who is trying to do everything correctly:
service programs, commitment control, activation groups. And they've
run into an interesting and painful situation. The issue is that when
they use the Java toolbox to invoke stored procedures, the commitment
control is scoped to the activation group of the QZDASOINIT job, and
that job is running <drum roll> in the default activation group!!! The
upshot is that all programs that need to run under the standard
commitment control of the JDBC driver in the toolbox must run in the
default activation group.
This begs a larger question: has anybody thought of a way (or even
considered the need) to force IBM server jobs to run in an ILE
activation group? It would make sense to me that there would be some
way to force a job to run in at least a *NEW group. We toyed with the
idea of an ILE version of QCMD that you could then use as the program in
your routing step, but that seems like an awful lot of work and a good
way to shoot yourself squarely in the foot.
Any ideas?
Joe
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
