Robert,
I did it a different way as HSM used to choke on 100+ commands at a
time.
One thing I did was to break it up to say 75 at one time.
Good suggestion.
Ed
On Apr 10, 2007, at 10:08 PM, Robert A. Rosenberg wrote:
At 16:13 -0400 on 04/10/2007, Richbourg, Claude wrote about DFHSM
cleanup of orphaned MCC records.:
They say one has to manually issue the HSEND FIXCDS C 'dataset name'
DELETE command for each record and it has to be done
manually. We have a very large amount of these errors and it could
take
a couple days to do it with only one person.
Do any of you know any way to automate this? Can these records be
'pulled' from the CDS and 'wrapped' by code to
do all the deletes?
While I am not familiar with the messages, I can pass on a trick I
use in these types of situations. If the error messages come from a
report, you can read the report into SPF and then edit it so that
you have the file names needed for the command. Turn the list of
names into a set of Macro Calls and write a macro that does a PUNCH
' HSEND FIXCDS C ''&DSN'' DELETE' for each macro call. You then
just assemble the module under SPF 4.1 and merge the OBJ deck into
a Job Steam to feed the HSEND commands as SYSIN to the requisite
HSM Utility.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
