Re: Database server job routing to SBS by IP address disappeared...

This isn't one of those cases where you have more than one qusrwrk subsystem
in multiple libraries and one or the other is getting started. Your not
running some 3rd party vendor software that dictates what is allowed via
port etc or maybe an exit program possibly.

On Wed, Sep 29, 2010 at 1:09 PM, Charles Wilt <charles.wilt@xxxxxxxxx>wrote:

Rob,

I could be wrong, but I don't believe these values are kept in a subsystem.

In any event, we don't journal subsystem and even if we did, there's
at most one weeks journals on the system.

The change in question likely happened long ago.

Charles

On Wed, Sep 29, 2010 at 12:49 PM, <rob@xxxxxxxxx> wrote:

Do you journal subsystem changes? You can, HA software does. What does
your journal entries show?


Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Charles Wilt <charles.wilt@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 09/29/2010 12:46 PM
Subject: Re: Database server job routing to SBS by IP address
disappeared...
Sent by: midrange-l-bounces@xxxxxxxxxxxx



For specific clients, they were supposed to be yes.

And they were originally, but not now.

Charles

On Wed, Sep 29, 2010 at 10:33 AM, Jack Kingsley
<iseriesflorida@xxxxxxxxx> wrote:

Are you running these in another subsystem other than QUSRWRK.

On Wed, Sep 29, 2010 at 10:15 AM, Charles Wilt

<charles.wilt@xxxxxxxxx>wrote:

All,

Does anyone know of any way other than somebody going in and changing
it that the routing of database server jobs (QZDASOINIT) to a
particular SBS when the connection comes from a particular IP address,
could disappear?

This is configured in iNav:
• Click on: systemName->Network->Servers->iSeries Access
• Right-Click on Database and select Properties
• Click on Subsystems tab
• Click Specific Clients and click Add Client

Thanks!
Charles
--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.