RE: IPL Startup and Odd Changes? -- MIDRANGE-L

Have you looked at the startup program system value and the actual startup program. Was it changed?

Chris Bipes
Director of Information Services
CrossCheck, Inc.

707.665-2100, ext. 1102
707.793.5700 FAX
chris.bipes@xxxxxxxxxxxxxxx
www.cross-check.com

Notice of Confidentiality: This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify me by e-mail (by replying to this message) or telephone (noted above) and permanently delete the original and any copy of any e-mail and any printout thereof. Thank you for your cooperation with respect to this matter.

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

Yep, it's active.

Controlling subsystem . . . : QCTL
Library . . . . . . . . . : QSYS

Subsystem description: QCTL Library: QSYS
Status: ACTIVE

On Wed, Dec 2, 2020 at 10:16 AM Rob Berendt <rob@xxxxxxxxx> wrote:

DSPSYSVAL SYSVAL(QCTLSBSD)
Record the value.
WRKSBS
F11=Display system data
Is the status of the controlling subsystem ACTIVE? If not, then
someone may have done a CHGIPLA STRRSTD(*YES) before the last IPL

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com

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

CAUTION: This email originated from outside of the organization. Do
not click links or open attachments unless you recognize the sender
and know the content is safe.

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