Thanks for the reply Dave
I was the cause to my own problem
I just sent out what I forgot to do
Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
'If you're going through hell, keep going.'
Winston Churchill
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of dlclark@xxxxxxxxxxxxxxxx
Sent: Tuesday, November 14, 2017 4:53 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: SQLSTATE 08S03, SQLCODE -30060.
"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
--
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300
Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331
*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary information. If you have received this message in error, please immediately notify the sender and delete and destroy the message and all copies. All unauthorized direct or indirect use or disclosure of this message is strictly prohibited. No right to confidentiality or privilege is waived or lost by any error in transmission.
*********************************************************************************************
--
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
midrange.com
