Years ago, before HSM, I wrote some code to deal with issues like this.
IIRC, it went something like this.
- About 4 times a day a job would run to identify problem packs
(volumes) by relative ranking, noting the 4 worst of each. IIRC, it used
the LSPACE(?) macro.
- Low free space.
- Many high extent datasets.
- Many over allocated datasets.
- High fragmentation. (Probably not needed today at most sites.)
- etc.
- The collected statistics and problem flags were stored in ISPF tables,
one per volume. An ISPF dialog allowed review of the chronological
movement of the state of each volume. The information allowed day and
shift when a problem began. A DASD manager could manually flag additional
volumes for specific mitigation(s).
- At about 3 AM, a second job would run to process the list of "problem
children" and submit various DFDSS jobs to address the specific problems
identified on the specific packs.
- Defrag fragmented packs.
- Compress high extent PDSs.
- Free unused space on over allocated datasets.
- Migrate dataset high extent datasets from fullis packs to high free
space packs.
- etc.
This was before the SCHEDULE JCL statement, ISPF LMDINIT/LMDLIST, and REXX
on z/OS, so it should be a piece of cake to do something like this today
today.
OREXXMan
Would you rather pass data in move mode (*nix piping) or locate mode
(Pipes) or via disk (JCL)? Why do you think you rarely see *nix commands
with more than a dozen filters, while Pipelines specifications are commonly
over 100s of stages, and 1000s of stages are not uncommon.
REXX is the new C.
On Thu, Nov 4, 2021 at 8:08 AM kekronbekron <
[email protected]> wrote:
> Hi Dave,
>
> What you've mentioned will work.
> A cyclic automation rule that runs a REXX which does the following:
> 1. D SMS,SG(ALL) and parse its output (or maybe individual commands for
> just the SGs you're interested in, to simplify parsing)
> 2. Check for availability of DISNEW volumes
> 3. V SMS command to ENABLE the volume
> https://www.ibm.com/docs/en/zos/2.4.0?topic=command-changing-sms-status-storage-group-volume
> 4. Email about the performed action and maintain a simple status file
>
>
> - KB
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>
> On Thursday, November 4th, 2021 at 4:30 PM, Dave Jousma <
> [email protected]> wrote:
>
> > All,
> >
> > I'm sure someone has solved this. I'm now managing DASD management at my
> shop. One thing that bothers me is my guys getting off-shift calls because
> some active storage pools fall below a % threshold of freespace. We arent
> skimpy on provisioning, but dont want to over-provision either. We are IBM
> system automation shop, and I asked IBM if there was any "out-of-the-box"
> automation for SMS we could start with and tailor to our needs. Nothing.
> Not looking to fully automate storage pool management, but something along
> the lines of having some number of volumes in DISNEW status, that could be
> enabled via automation - saving that middle of the night call-out, but to
> follow-up on next business day.
> >
> > Anyone doing anything like this, case to share?
> >
> > Thanks in advance, Dave
> >
> >
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> >
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> >
> > send email to [email protected] with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
