×
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.
"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 11/14/2017
04:31:17 PM:
Hi Dave
Thanks for your response
The subsystem definition is there
JVAGATEJOB O100 BCH .0 PGM-STRJVAGATE TIMW
QP0ZSPWP O100 BCI .0 JVM-de.bender_ THDW
QZSHSH O100 BCI .0 PGM-QZSHSH EVTW
I have the WRKRDBDIRE entries in place
I take it that your JVAGATE is not running in its own subsystem?
Not sure if that is a problem or not. But, I see that your STRJVAGATE job
is type BCH rather than type ASJ as it is in my case. Also, from the
other responses, it may be an authentication issue. Is your remote DBMS a
MS SQL Server instance, or what? We have issues here every time we start
a new remote database connection that we have to keep telling the remote
DBAs not to use Windows Authentication for our connections. They have to
be able to accept the user and password for authentication at the database
connection level.
Subsystem/Job User Type CPU % Function Status
JVAGATE QSYS SBS .0 DEQW
JVAGATE JVAGATEUSR ASJ .0 PGM-STRJVAGATE TIMW
QP0ZSPWP JVAGATEUSR BCI .0 JVM-de.bender_ THDW
QZSHSH JVAGATEUSR BCI .0 PGM-QZSHSH EVTW
Sincerely,
Dave Clark
As an Amazon Associate we earn from qualifying purchases.