I set up the PDO logs to swap just like the SMF logs,
When HSM would swap from X to Y, Automation would kick off a IEBGENER to
copy it to a "permanent " dataset with the System & Time stamps as dataset
name and HSM/SMS Management Class to keep them around for 45 days with No
backup and 0 days
We use to use ABARS to backup application with migrated datasets,
The ABARS task would backup both the dasd datasets and the Migrated
datasets, In migrated format, It would Stage the ML2 "Tape" for a read of
the "Tape" files. We used that for some Application Backups where the data
would
We set up a every half hour DCollect to catpture a snap shot of the Dasd
(Volumes) Pools usage.
We also had a program that would read (SAS/MXG) the Dcollect data and report
and issue minor and major alerts, Plus a quick readable sequencaly file
with the Poll usage by 30mins for the last
uot;Peter" <dbajava...@gmail.com>
Newsgroups: bit.listserv.ibm-main
To: <IBM-MAIN@LISTSERV.UA.EDU>
Sent: Monday, March 12, 2018 12:48 PM
Subject: Re: GDG with timestamp
So how would the GDG base definition would look like so that all the tape
GDG has creation date ?
On 12-
Years ago, we had a vendor application that was setup to create a Hourly Log
File in a GDG.
Sometime in early December a Step in the Monthly Cycle jobs would create the
GDG's for the next year (A program created 366 Define GDG Cards) , Then
trigger a "Admin" job that had the authority to
Been retired for Almost two years now but from what I recall:
Two Different SysPlex: One has 2 MVS Systems, Other has 6 MVS Systems
The Smaller one was in the 900K lines per day, Larger one in the 5M lines
per day
They were both accessed Daily
Kept on Online for 45 days, with HSM backups
