|
Thanks all.
The problem appears to be related to running the job in debug (in RDi).
Eventually after trying options, I found doing a Ignore to the message and
letting the job continue. It does continue and it appears to complete
without a problem.
Running without debug, it executes normally without issue.
Darryl.
On Tue, Apr 24, 2018 at 7:36 PM, James H. H. Lampert <
jamesl@xxxxxxxxxxxxxxxxx> wrote:
I remember problems with SQL when I tried to run two different programs
that used SQL CLI APIs in the same job. Had to consolidate all the SQL CLI
calls into a single program (in its own activation group, if I remember
right), that would then be called by the others.
Don't remember what the error message was, though.
--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
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.