So, I'm now caught up on my reading and, tho' *very* late, I wanted to plug
Option 6 for FDReport clients.
In a recent version (L78? L80 is better), Innovation added DATATYPE=[CA1VOL,
CA1DSN] to the PRINT command inventory. I've been using it in production for
3+ months now to automate the housekeeping on my FDRABR.LASTAPE.** datasets.
In the past, I would regularly [1] uncatalogue those datasets to keep from
having tape sets with too many volumes. Unfortunately, it would often leave
mostly-empty tapes depleting the scratch pool. Now, my daily routine detects
whether the 500G tape has passed the 95%+ mark and generates an un-catalogue
action. [2] This way, the tape is used to its fullest and keeps tape sets to
one or two members. [3]
and, yes, I am a *very* satisfied FDR customer/supporter. *grin* [4]
[1] ie. monthly, quarter, annually, using the ESP scheduler with IF
TODAY('FIRST/LAST WORKDAY OF period').
[2] I don't even have to manually track the names like before. Instead the
routine retrieves all catalogue matches for FDRABR.LASTAPE.** and goes from
there.
[3] Since I started, I've only encountered one set with more than 2 tapes. It
was an adhoc utility process that ran at the same time as my daily routine so
the .Last Ape was not catalogued at that moment.
[4] I gave Innovation my .Last Ape routines so they could provide an example
of the new reporting capability.
--------> signature = 6 lines follows <--------
Neil Duffee, Joe Sysprog, uOttawa, Ottawa, Ont, Canada
telephone:1 613 562 5800 x4585 fax:1 613 562 5161
mailto:NDuffee of uOttawa.ca http:/ /aix1.uOttawa.ca/ ~nduffee
“How *do* you plan for something like that?” Guardian Bob, Reboot
“For every action, there is an equal and opposite criticism.”
“Systems Programming: Guilty, until proven innocent” John Norgauer 2004
-----Original Message-----
From: Tim Hare [mailto:[email protected]]
Sent: May 26, 2015 01:37
Subject: Re: CA-1 programming example
First: You catalog all of your tape datasets I hope.
Second: No one mentioned the 'TI' (Tape Inquiry) command shipped with later
versions of CA-1? It can be used as a line command in ISPF 3.4 and gives you
information about those datasets and some info about the volumes.
Third: I wrote a TAPELIST command once - dealing with the complex multi-volume
multi-file situation isn't fun. I think my program is correct (back when some
CA-1 source was shipped I tried to compare it to CA's source for reporting in
such a situation) but I always had nagging doubts.
Fourth: If you have MXG it has members to read TMC info (in SAS) and put it in
a PDB.
Fifth: In answer to Russ Witt's query, I think more and more people want some
sort of query-able interface to all of their system management data, and they
seem to either want SQL or XML. My ideal (and this is just my personal
opinion) would be for CA-1 to supply DB2 UDFs (User-Defined Functions) that
would read CA-1 information and return a relational result set.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
