DSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Roger Deschner
Sent: vrijdag 9 november 2012 4:34
To: ADSM-L@VM.MARIST.EDU
Subject: Re: AUDIT VOL with WAIT=YES ?
I wound up using Alex Paschal's method - thanks!
I am not worried (yet!) about damaged files. There are probably
ep 10
>while dsmadmc -id=id -pa=pa -comma q pr | grep -qi audit ; do
>sleep 10
>done
>dsmadmc -id=id -pa=pa update vol /path/file1 acc=readw
>
>On 11/6/2012 3:17 PM, Roger Deschner wrote:
>> Does anybody have a script or program that can issue a TSM AUDIT VOLUME
>> com
Hi Roger!
Why don't you use a MOVE DATA against r/o volumes? It has a WAIT=YES
parameter and it's better than using the AUDIT VOLUME command.
When you have a read error on a primary pool volume, the audit command
(with FIX=YES) removes the backup data from the tape. Not a problem for
b
=pa update vol /path/file1 acc=readw
On 11/6/2012 3:17 PM, Roger Deschner wrote:
Does anybody have a script or program that can issue a TSM AUDIT VOLUME
command and wait for it to finish - as though WAIT=YES existed?
I keep getting r/o vols in my DEVCLASS FILE storage pools. I want to
audit t
Does anybody have a script or program that can issue a TSM AUDIT VOLUME
command and wait for it to finish - as though WAIT=YES existed?
I keep getting r/o vols in my DEVCLASS FILE storage pools. I want to
audit them before changing them back to r/w. I want an automatic process
to do that, one at
figures
out when each of these activities is done by examining data
piped from an administrative client session with the console
option. I am looking into the possibility of simplifying the
management software by using the 'wait=yes' option of the
various commands. How does this option behav
that manages our housekeeping figures
out when each of these activities is done by examining data
piped from an administrative client session with the console
option. I am looking into the possibility of simplifying the
management software by using the 'wait=yes' option of the
various co
We use TSM scripts. I started out using a homegrown process
that did what you are doing but with REXX execs which examined
TSM output. It was not flexible. I later found a TSM script
that someone shared with me that does it all. We do use wait=yes
for the processes since we have limitations with
of these activities is done by examining data
piped from an administrative client session with the console
option. I am looking into the possibility of simplifying the
management software by using the 'wait=yes' option of the
various commands. How does this option behave with multiple
proces
ent of the ba db
command.
It appeared that command line 'dsmadmc -id=admin -pass=$TSMPWD "ba stg
collgoldprimarypool collgoldcopypool maxpr=3 wait=yes"' timed-out
waiting on a return from the command. It,or all practical purposes,
orphaned the ba stg and continued processing the
stg
collgoldprimarypool collgoldcopypool maxpr=3 wait=yes"' timed-out
waiting on a return from the command. It,or all practical purposes,
orphaned the ba stg and continued processing the rest of the script.
I can find no time-related values in the server's configuration that is
anywher
David -
The "ANS1017E Session rejected..." message should have a
corresponding ANR message in the Activity Log, so look there - and
check your server timeout values (e.g., IDLETimeout) for the value
you observe.
Richard Sims
Can anyone confirm that there is a 12 hour time limit for a scripted
dsmadmc command where "wait=yes" is set?
I have an AIX script that performs basically synchs up my production TSM
server with one at our DR site. A portion of i
D]>
To:
Sent: Tuesday, June 05, 2007 2:15 AM
Subject: Re: tsm scripts and WAIT=yes
Hi Tim,
Check 'help ba stg', it says something about wait=yes parameter.
"You cannot specify WAIT=YES from the server console."
//Henrik
-Original Message-
From: ADSM: Dist Stor Manager
Hi Tim,
Check 'help ba stg', it says something about wait=yes parameter.
"You cannot specify WAIT=YES from the server console."
//Henrik
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Tim Brown
Sent: den 4 juni 2
TSM server is Z/OS
Have script that is scheduled to run daily with a number of commands
with wait=yes coded
I received this error today , I didnt try to run the schedule today it was
already scheduled to run at 4:00AM
The server log had these messages
ANR2753I (DAILY_SCRIPT):ANR2043E BACKUP
first backup have to complete before the second backup
job
starts?
Thanks in advance!
BACKUP NODE NAS_SERVER_2 MODE=DIFFERENTIAL WAIT=YES TOC=PREFERRED
BACKUP NODE NAS_SERVER_2_OFFSITE MGMTCLASS=nas_offsite
MODE=DIFFERENTIAL
WAIT=NO TOC=PREFERRED
***
MODE=DIFFERENTIAL WAIT=YES TOC=PREFERRED
BACKUP NODE NAS_SERVER_2_OFFSITE MGMTCLASS=nas_offsite MODE=DIFFERENTIAL
WAIT=NO TOC=PREFERRED
Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]
PROTECTED]
--
/*DAILY*/
/*backup db*/
delete schedule chkproc type=admin
q process
if(rc_notfound) goto cont
def schedule chkproc cmd="run daily" active=yes startd=today
startt=now+00:10 exp=today
exit
cont:
backup db dev=bakdrive type=full wait=yes
def schedule chkproc cmd="run Script1
MOUNTRETENTION for the device class?
Paul D. Seay, Jr.
Technical Specialist
Naptheon, INC
757-688-8180
-Original Message-
From: Roger Deschner [mailto:[EMAIL PROTECTED]]
Sent: Sunday, May 19, 2002 1:31 AM
To: [EMAIL PROTECTED]
Subject: Script timing issue with MOVE DATA WAIT=YES
This is a tsm
This is a tsm script: (AIX 4.2.1.9)
MOVE DATA $1 WAIT=YES
COMMIT
UPDATE LIBVOL ATLP3000 $1 STATUS=PRIVATE
The idea is, when moving data off of tapes that I suspect have media
problems, to avoid having the tape become an available scratch tape and
get reused. MOVE DATA can take a long time
21 matches
Mail list logo