Even though it violates everything about being Managed by SMS.
IDCAMS Delete Noscratch on a dataset that is SMS controlled will indeed leave
the
dataset on the volume. Found this out the hard way by the use of a
restart/rerun
vendor product. You can send me a note offlist and I can give you
, March 22, 2012 9:51 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: UNABLE TO DELETE DUPLICTE DSN
On Thu, 22 Mar 2012 07:42:39 -0700, Pesce, Andy wrote:
Even though it violates everything about being Managed by SMS.
IDCAMS Delete Noscratch on a dataset that is SMS controlled will indeed
leave
2 incidents at a shop where I no longer work.
1) Fire alarm started sounding. Checked the zones and found an electrical
smell, but no flames.
Couldn't find the fire, and the Ops Manager said Everyone out!. The Halon
dumped. Sounded like
the building collapsing. That was in the good ole
Same experience here as well. The white paper listed below was a great guide.
I have some processes
that I run to offload the data once a day to a daily gdg. I have not had any
problems.
I would not suggest doing this for LOGREC, yet. I encountered a lot of
problems with running
reports.
IBM has told us that would like us to move our HMC so that they can change the
call home server to use the Internet. I am sure there are some white papers
and articles about security. Our security dept. is concerned about putting it
on the internal network since it is just another Linux box.
5 matches
Mail list logo
