RE: Morning Routine

After seeing Paul's email, I was reminded that we use commercial software to monitor for certain conditions 24x7.  Our shop has SLAs of I forget how many nines of uptime, so we're quick to respond to critical issues.  The SQL procedure I detailed earlier helps us mostly to be proactive.

- Dan Bale

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces-+hD5IHI5Xscn3HwCXmMcX9BPR1lH4CV8@public.gmane.org> On Behalf Of Dan Bale via MIDRANGE-L
Sent: Monday, July 6, 2026 11:44 AM
To: Midrange Systems Technical Discussion <[email protected]>
Cc: Dan Bale <dan.bale-EkiVQpMPPJH8R359/[email protected]>
Subject: RE: Morning Routine

I have an SQL procedure that, via DDM and 3-part naming, connects to all 30 of our partitions and queries:
** QUSRSYS.QASXPROB (replicates WRKPRB, to check for problems)
** qsys2.asp_info (replicates TAATOOL's WRKASP, to check for storage reaching capacity thresholds)
** QSYS2.HARDWARE_RESOURCE_INFO (replicates WRKHDWRSC, to check for Inoperative or Not Detected statuses, for types *CMN & *STG. WARNING: Complex query required to pare down data to match what WRKHDWRSC shows.)
** QSYS2.MEDIA_LIBRARY_INFO (replicates WRKMLBSTS, to check for non-Active statuses)
** QSYS2.IFS_READ('/qibm/Qzrdhasm/qzrdhasm.log') (replicates High Availability command VIEWLOG)
** QSYS2.SYSTEM_STATUS_INFO (replicates WRKSYSSTS, primarily to capture "% temp addresses")
** QSYS2.JOB_INFO (replicates DSPJOB 000000/QSYS/SCPF, to capture last IPL date, used to calc trend of "% temp addresses" reaching threshold)

Each of these is exported to their own tabs in a spreadsheet (except for the last two, which are combined into one tab), which is then emailed to our team.

We schedule this to run on Monday and Thursday mornings.  We haven't found the need to run it more often than that.

- Dan Bale

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces-+hD5IHI5Xscn3HwCXmMcX9BPR1lH4CV8@public.gmane.org> On Behalf Of Sizer, Joseph via MIDRANGE-L
Sent: Monday, July 6, 2026 9:42 AM
To: Midrange Systems Technical Discussion <[email protected]>
Cc: Sizer, Joseph <[email protected]>
Subject: Morning Routine

Reaching out to IBM i admins.

What are some of the common tasks that you perform each morning to verify that the system is running cleanly?  Realizing every system has its own unique attributes, I am just curious to see how much we are alike.

*** CONFIDENTIALITY NOTICE: The information contained in this communication may be confidential, and is intended only for the use of the recipients named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender. ***
-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: [email protected]
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request-+hD5IHI5Xscn3HwCXmMcX9BPR1lH4CV8@public.gmane.org
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support-FMtJrHiV//lnDLsaKlm4mFaTQe2KTcn/@public.gmane.org for any subscription related questions.