I am currently writing some scripts to help automate our DR build. So here is my question.
In writing my script I am wondering if there is a switch that I can add to my script that will force screen response before moving on. Example.
update vol * access=readonly wherestgpool=
update vol * access=readonly wherestgpool=
What I would like to do is force the halt between these two commands and force keyboard response before moving on to the next stg pool.
I have found doing this with multiple stg pool commands some of the commands get stepped on and do not complete. Any thoughts would be greatly appreciated.
Thanks
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
... another solution could be running the commands from a shell script.
But this would imply calling dsmadmc for each command -
#!/bin/ksh
dsmadmc -id=xxx -pass=xxx upd vol ......
echo "Shall we continue?"
read response
[ "$response" != "Y" ] && exit
dsmadmc -id=xxx -pass=xxx upd vol ......
echo "Shall we continue?"
What do you think?
I'd suggest putting this question into the TSM zone, too.
There might be someone with a better idea ...
wmp
I like that solution I think this is right along the lines of what I am looking for..
I will take that and work with it... I think that will work.
I am going to do some initial testing this afternoon and will update the question...
What I meant by stepped on was this.
When running the script I created for the update vol * wherestgpool=Name_of_offsi
I was running this for 31 offsite pools.. There were a couple that did not get updated. What I found was that was never shown in the act log or on the console.
I think that it just got missed and did not show up on the console.... So these stgpools not getting update was something I didnt realize until I was running a restore that needed tapes from the non-updated pool.
Thanks again... Will let you know how it goes.
Business Accounts
Answer for Membership
by: woolmilkporcPosted on 2008-12-04 at 08:16:34ID: 23096640
Hi,
since you set ALL volumes in the stgpool to readonly, why not set the stgp itself readonly? Or is it a NEXTSTGPOOL?
upd stgp [name] acc=reado
Since scripts are meant to run unattendedly, there is no switch to force a response.
Even the delete commands which require confirmation when run intreractively complete without asking questions when called from within a script.
But, what do you mean exactly with 'stepped on'?
Perhaps we can find another solution.
wmp