Ah, that might be part of (or all of) the problem. Our system is connected
via our ISP. That is, the DNS is on their system, not local. That means
that, even though the system is sitting about a foot (about .33 meters) from
me as I type this, I have to go through the ISP to make the connection using
the System i's IP address.
I've tried to get that rectified but our part-time sys admin (aka the boss'
son) is adamant that the System i is a "piece of junk" and is the root cause
of the problem. Indirectly he may have a point since we're at V5R1 and I
ain't a network or admin guru. That said, I still have to restrain myself
from slapping the s**t out of him whenever he's in the office (which
thankfully isn't often).
Jerry C. Adams
IBM i Programmer/Analyst
Debugging is at least twice as hard as writing the program in the first
place. So if your code is as clever as you can possibly make it, then by
definition you're not smart enough to debug it.
--
A&K Wholesale
Murfreesboro, TN
615-867-5070
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Porterfield, Sean
Sent: Thursday, July 19, 2012 8:40 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries
Subject: Re: [WDSCI-L] WDSc Needs to Reconnect Daily
Are you on the same local switch as your system? I had problems with
disconnects due to our firewall closing connections. That shouldn't be a
factor if you're local, though.
--
Sean Porterfield
________________________________________
From: wdsci-l-bounces@xxxxxxxxxxxx [wdsci-l-bounces@xxxxxxxxxxxx] On Behalf
Of Jerry C. Adams [midrange@xxxxxxxx]
Sent: Thursday, July 19, 2012 09:33
To: 'Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries'
Subject: Re: [WDSCI-L] WDSc Needs to Reconnect Daily
Thanks, Mike. Ours is currently set at the default (120).
Jerry C. Adams
IBM i Programmer/Analyst
When putting something into memory, always remember where you put it.
--
A&K Wholesale
Murfreesboro, TN
615-867-5070
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Smith, Mike
Sent: Thursday, July 19, 2012 7:55 AM
To: 'Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries'
Subject: Re: [WDSCI-L] WDSc Needs to Reconnect Daily
Jerry,
This seems like a problem I had a long time ago. I'm not absolutely
positive, but I think the solution was to lower the TCP keep alive value.
Ours is currently set to 5.
Hope this helps.
Mike
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Jerry C. Adams
Sent: Thursday, July 19, 2012 8:47 AM
To: 'Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries'
Subject: Re: [WDSCI-L] WDSc Needs to Reconnect Daily
I just did the reconnect. The subsystem (QUSRWRK) was already set to 4 0
*Seclvl but, since it is running, there is no joblog. The job (QZRCSRVS)
was set to 4 0 *NoList so I changed that to *Seclvl. Maybe tomorrow morning
there will be a joblog with some useful information.
Jerry C. Adams
IBM i Programmer/Analyst
Computers don't make errors. What they do they do on purpose.
--
A&K Wholesale
Murfreesboro, TN
615-867-5070
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of MichaelQuigley@xxxxxxxxxx
Sent: Wednesday, July 18, 2012 2:20 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] WDSc Needs to Reconnect Daily
If you don't find an answer any other way, you could change the jobs in
QUSRWRK to generate a joblog. Then check the generated joblogs for any
indication as to why the jobs are ending.
wdsci-l-bounces@xxxxxxxxxxxx wrote on 07/18/2012 01:00:07 PM:
----- Message from "Jerry C. Adams" <midrange@xxxxxxxx> on Tue, 17 Jul
2012 14:27:26 -0500 -----
To:
"'Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries'" <wdsci-l@xxxxxxxxxxxx>
Subject:
Re: [WDSCI-L] WDSc Needs to Reconnect Daily
Won't have to wait that long, after all.
I decided to check (WRKACTJOB) to see if QUSRSYS subsystem was running.
It
wasn't, but QUSRWRK was (which is what I think you meant, David). But
there
were no jobs running in it.
So, I went to WDSc and that @#$% think needed to reconnect. After it
made
the connection, I checked QUSRWRK again, and it now has two jobs:
QZHQSSRV
and QZRCSRVS. Both are pre-start jobs. I'll do some research
Thursday, but, in the meantime, anyone has a guess why the jobs would
be ending, suggestions would be appreciated.
Jerry C. Adams
IBM i Programmer/Analyst
Art is the lie that tells the truth. Pablo Picasso
--
A&K Wholesale
Murfreesboro, TN
615-867-5070
This email is confidential, intended only for the named recipient(s) above
and may contain information that is privileged. If you have received this
message in error or are not the named recipient(s), please notify the sender
immediately and delete this email message from your computer as any and all
unauthorized distribution or use of this message is strictly prohibited.
Thank you.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list To post a message
email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.
midrange.com
