RE: IPL Startup and Odd Changes?

Brad,

wrkjob qstrupjd

This will list all your IPL's select the one you need to look at.

Paul

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Brad Stone
Sent: Wednesday, December 02, 2020 2:56 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: IPL Startup and Odd Changes?

________________________________
CAUTION: This email originated from outside of the PENCOR network. Do not click on any links or open attachments unless the sender is known, and the content is verified as safe.
________________________________

Steve,

I can find the job description. I thought the job log for QSTRUP was under QPGMR? I did find that with user data of QSTRUPJ.

I see a lot of these:
Routing entry sequence number 600 already exists.

followed by:

Host server daemon job already active.

Example:

Cause . . . . . : A request was issued to start the *DATABASE daemon job.

However, this daemon job is either already active or the daemon job is not
active but it's program, QSYS/QZDASRVSD, is allocated by another job.


On Wed, Dec 2, 2020 at 1:34 PM Steve McKay <samckay1@xxxxxxxxx> wrote:

Brad -

Can you find job QSTRUPJD? Unless you've changed something, this
would contain a joblog showing what the QSTRUPPGM did. Comparing this
joblog to the source code for QSTRUPPGM (QSTRUP unless you've changed
the system
value) would verify that what was executed matches what you think the
QSTRUPPGM should be doing.

Thanks,

Steve McKay
(205) 585-8424
samckay1@xxxxxxxxx



On Wed, Dec 2, 2020 at 2:20 PM Steinmetz, Paul via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

Brad,

With the move to the new building, would this now be on a
different/new network/and/or firewalls?

Paul



-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf
Of Brad Stone
Sent: Wednesday, December 02, 2020 10:50 AM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx

Subject: IPL Startup and Odd Changes?

Ok, this is a little strange so bear with me.

I work with a client and they recently moved buildings. Yesterday
when they brought the system back up there were some oddities:

1. Every web server instance was started, including APACHEDFT
(which is set to not autostart). This of course stopped their real
web server instance from starting. Easily fixed.

2. The QUSRWRK subsystem was not started. This caused the SSHD
server

to

not start which in turn means their node job(s) weren't running.
This again was fixed by starting the subsystem, starting SSHD and
then

starting

the node job.

3. QNTC wasn't showing any shares available (which are very
important in their applications). I couldn't get those back.

So, we thought something went wrong with the IPL. Didn't see
anything in the job log or QSYSOPR or in QPGMR for the job log for QSTRUP.

So they IPLd last night again.

This morning QHTTPSVR subsystem and NO web jobs were running (which
is opposite of what happened before).

QUSRWRK was not running. I started the web jobs and QUSRWRK, SSHD
and then checked QNTC (after doing this, I wish I would have
before). All

the

shares were now there.

So this is odd... why would these subsystems/etc be not starting
during

an

IPL? And why the oddities with QNTC?

They IPL once a week and never had this issue before. I don't think
the move to the new building would have had any effect, but I
thought I'd mention it since it's the only thing we can think of that changed.

No PTFs installed recently either. V7R3.

Bradley V. Stone
www.bvstools.com
Native IBM i e-Mail solutions for Microsoft Office 365, Gmail, or
any Cloud Provider!
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To

subscribe,

unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.

Help support midrange.com by shopping at amazon.com with our
affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.

Help support midrange.com by shopping at amazon.com with our
affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com