Il 03/02/2026 16:48, Marco Facchinetti ha scritto:
Hi Luca, we also have several clients on the same machine, but we don't
allow access with the same profile between different clients.
Another issue to consider when working with different libraries is the
presence of triggers. So the solution we use is to submit a new job with
the authorized profile and the correct jobd.
HTH
Hi Marco, thanks for the reply.
Just to explain: in our "Power Server + IBM i," we manage different scenarios:
we have a single-company scenario and a multi-company one. I think the first
speaks for itself: one company = a job description with a specific list of
libraries.
In the multi-company scenario, we have a job description per company, with a
specific list of libraries that typically contains one or more common
multi-company data libraries, but each sub-company within the multi-company has
a different company-specific data library. My program intervenes in the
multi-company scenario, where the name of the company data library changes each
time based on the different messages/data that need to be dispatched to the
different companies in a top-down communication style; the message/data is
generated in the main company or lead company or group leader and propagates to
some or all of the others.
For single companies, we adopt your same solution.
Best regards.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 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.