Re: AUDIT VOL with WAIT=YES ?
Hi Roger! Bear in mind that tapes with read or write errors will not always show up as read-only. In the past I came across multiple tapes with read or write errors which were still readwrite. In our shop I have TSMOR report all read-only tapes, unavailable tapes and also all tapes with number of read/write errors 0. We always do a move data against all of these volumes. I have seen multiple times that a tape had write errors, an move data showed numerous corrupted objects which could not be moved and the strange thing is that I could restore these objects from the copypool! This means that these objects were ok in the past and got corrupted somewhere down the line, probably during the last write action to the tape. By the way, we only use virtual tapes (EMC DL4106), reuse delay is 3 days. Kind regards, Eric van Loon AF/KLM Storage Engineering -Original Message- From: ADSM: 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 very few of them anyway. I am only doing a FIX=NO audit to see where the problems are. I'm capturing the results by Q ACTLOG ... SEARCH='PROCESS: ' and parsing msg ANR4133I for the audit results. If FIX=NO does not find any damaged files, as reported in ANR4133I, then the disk file volume is changed to READWRITE automatically. If the FIX=NO audit does find something wrong, then I will deal with it manually and carefully. I did not want to use Eric van Loon's suggestion of MOVE DATA, because that would really fill up this storage pool, considering we use a reuse delay. The advantage of AUDIT is that it does not cause any data movement other than one read pass, and most of the volumes will not have any problems. Thanks again, to both Eric and Alex. That was the obvious solution - a sleep loop querying processes after starting the AUDIT command. The improvement I added was to get the actual results via Q ACTLOG after it was finished. Roger Deschner University of Illinois at Chicago rog...@uic.edu ==I have not lost my mind -- it is backed up on tape somewhere.= On Tue, 6 Nov 2012, Alex Paschal wrote: Hi, Roger. I don't have one already made, but this should get you started. Hopefully there won't be too many typos. #!/usr/bin/ksh dsmadmc -id=id -pa=pa audit vol /path/file1 sleep 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 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 a time. I could have set up this storage pool with preallocated files instead of letting the operating system allocate and remove scratch volume files, but dsmfmt on 55TB of space to prepare the fixed volume files would take a very long time, like about a CPU-year. Roger Deschner University of Illinois at Chicago rog...@uic.edu ==I have not lost my mind -- it is backed up on tape somewhere.= For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286
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 very few of them anyway. I am only doing a FIX=NO audit to see where the problems are. I'm capturing the results by Q ACTLOG ... SEARCH='PROCESS: ' and parsing msg ANR4133I for the audit results. If FIX=NO does not find any damaged files, as reported in ANR4133I, then the disk file volume is changed to READWRITE automatically. If the FIX=NO audit does find something wrong, then I will deal with it manually and carefully. I did not want to use Eric van Loon's suggestion of MOVE DATA, because that would really fill up this storage pool, considering we use a reuse delay. The advantage of AUDIT is that it does not cause any data movement other than one read pass, and most of the volumes will not have any problems. Thanks again, to both Eric and Alex. That was the obvious solution - a sleep loop querying processes after starting the AUDIT command. The improvement I added was to get the actual results via Q ACTLOG after it was finished. Roger Deschner University of Illinois at Chicago rog...@uic.edu ==I have not lost my mind -- it is backed up on tape somewhere.= On Tue, 6 Nov 2012, Alex Paschal wrote: Hi, Roger. I don't have one already made, but this should get you started. Hopefully there won't be too many typos. #!/usr/bin/ksh dsmadmc -id=id -pa=pa audit vol /path/file1 sleep 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 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 a time. I could have set up this storage pool with preallocated files instead of letting the operating system allocate and remove scratch volume files, but dsmfmt on 55TB of space to prepare the fixed volume files would take a very long time, like about a CPU-year. Roger Deschner University of Illinois at Chicago rog...@uic.edu ==I have not lost my mind -- it is backed up on tape somewhere.=
Re: AUDIT VOL with WAIT=YES ?
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 backup data from the BA client, it gets backed up again next time, but it is a problem when this is TDP data. Your whole backup series is corrupted and you should schedule a new full backup as soon as possible. So my opinion is that r/o issues shouldn't be fixed automatically and unattended. Kind regards, Eric van Loon Royal Dutch Airlines -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Roger Deschner Sent: woensdag 7 november 2012 0:18 To: ADSM-L@VM.MARIST.EDU Subject: AUDIT VOL with WAIT=YES ? 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 a time. I could have set up this storage pool with preallocated files instead of letting the operating system allocate and remove scratch volume files, but dsmfmt on 55TB of space to prepare the fixed volume files would take a very long time, like about a CPU-year. Roger Deschner University of Illinois at Chicago rog...@uic.edu ==I have not lost my mind -- it is backed up on tape somewhere.= For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286
AUDIT VOL with WAIT=YES ?
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 a time. I could have set up this storage pool with preallocated files instead of letting the operating system allocate and remove scratch volume files, but dsmfmt on 55TB of space to prepare the fixed volume files would take a very long time, like about a CPU-year. Roger Deschner University of Illinois at Chicago rog...@uic.edu ==I have not lost my mind -- it is backed up on tape somewhere.=
Re: AUDIT VOL with WAIT=YES ?
Hi, Roger. I don't have one already made, but this should get you started. Hopefully there won't be too many typos. #!/usr/bin/ksh dsmadmc -id=id -pa=pa audit vol /path/file1 sleep 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 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 a time. I could have set up this storage pool with preallocated files instead of letting the operating system allocate and remove scratch volume files, but dsmfmt on 55TB of space to prepare the fixed volume files would take a very long time, like about a CPU-year. Roger Deschner University of Illinois at Chicago rog...@uic.edu ==I have not lost my mind -- it is backed up on tape somewhere.=
Wait=yes with multiple processes
We have a 5.4.2.0 TSM server running under mainframe Linus. Our daily housekeeping uses 'backup stgpool', 'migrate stgpool', and 'reclaim stgpool' commands that start multiple processes. The home-grown software 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 commands. How does this option behave with multiple processes? In particular, does the command end when the last of the multiple processes ends?
Re: Wait=yes with multiple processes
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 tape resources on our TSM server running Z/OS Our processes run serially not multiple though. If I wanted to support multiple I would run 2 separate scripts. Tim Brown Systems Specialist - Project Leader Central Hudson Gas Electric 284 South Ave Poughkeepsie, NY 12601 Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Phone: 845-486-5643 Fax: 845-486-5921 Cell: 845-235-4255 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Thomas Denier Sent: Wednesday, December 10, 2008 4:29 PM To: ADSM-L@VM.MARIST.EDU Subject: Wait=yes with multiple processes We have a 5.4.2.0 TSM server running under mainframe Linus. Our daily housekeeping uses 'backup stgpool', 'migrate stgpool', and 'reclaim stgpool' commands that start multiple processes. The home-grown software 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 commands. How does this option behave with multiple processes? In particular, does the command end when the last of the multiple processes ends?
Re: Wait=yes with multiple processes
On Dec 10, 2008, at 22:29 , Thomas Denier wrote: We have a 5.4.2.0 TSM server running under mainframe Linus. Our daily housekeeping uses 'backup stgpool', 'migrate stgpool', and 'reclaim stgpool' commands that start multiple processes. The home-grown software 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 commands. How does this option behave with multiple processes? In particular, does the command end when the last of the multiple processes ends? `look into the PARALLEL and SERIAL keywords for TSM server scripts. -- Met vriendelijke groeten, Remco Post [EMAIL PROTECTED] +31 6 248 21 622
Re: Wait=yes with multiple processes
Thomas Denier wrote: We have a 5.4.2.0 TSM server running under mainframe Linus. Our daily housekeeping uses 'backup stgpool', 'migrate stgpool', and 'reclaim stgpool' commands that start multiple processes. The home-grown software 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 commands. How does this option behave with multiple processes? In particular, does the command end when the last of the multiple processes ends? Yes. If you specify wait=yes, then it will wait until the last process finishes (or gets canceled). -- Todd D. Taft [EMAIL PROTECTED]
Re: wait=yes timeout??
I see the ANR2017I Administrator ADMIN issued command: BACKUP STGPOOL... in the actlog at the time that the command was first issues. The ba stgpool started and was running fine. 12 hours (exactly) later, the script reported the ANS1017E session rejected and went on to the next command, which was ba db..., however the ba stgpool was still running. There was nothing recorded in the actlog when the script reported the ANS1017E other than the commencement 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 rest of the script. I can find no time-related values in the server's configuration that is anywhere near 12 hours (43,200 seconds). I guess that at this point, I am comfortable in understanding what happened, and am now interested in finding out if that timeout can be adjusted. Thanks David -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Wednesday, September 19, 2007 6:25 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] wait=yes timeout?? 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 -Original Message- From: Taylor, David Sent: Wednesday, September 19, 2007 5:46 PM To: ADSM List Subject: wait=yes timeout?? 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 it is below. --- # synch the primary and copy storage pools # backup the TSM DBB to remote disk that appears local # make sure devconfig and volhist files are up to date dsmadmc -id=admin -pass=$TSMPWD ba stg collgoldprimarypool collgoldcopypool maxpr=3 wait=yes dsmadmc -id=admin -pass=$TSMPWD ba db type=full dev=remotedbbfileclass wait=yes dsmadmc -id=admin -pass=$TSMPWD ba devconfig dsmadmc -id=admin -pass=$TSMPWD ba volhist - An enormous amount of data came into the system last night and the storage pool backup was taking a LONG time. After running for almost exactly 12 hours (I can get it down to within 22 seconds), I received an ANS1017E Session rejected... error and the script continued processing, however the storage pool backup still hadn't completed. Basically the storage pool backup was orphaned and continued running while the script went on to the database backup. Because of the timing, I feel pretty confident that there must be a 12 hour timeout on a wait=yes, but would feel a lot better if someone could confirm it. I tried doing a lot of searches on it but couldn't find anything close to an answer. Thanks in advance! David ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.clearswift.com **
Re: wait=yes timeout??
David - It's strange that the TSM server Activity Log shows no ANR message of any kind relating to the dsmadmc session loss: I would expect at least some record of the session drop from its end. Based upon what you report, it would appear that the TSM server was not responsible for the dsmadmc session dropping, which is to say that there is no TSM timeout involved. I would thus look for other causes. Check for any incidental entry in the dsmerror.log. One place to look is in the AIX accounting records, searching for the dsmadmc process name, and to particularly look for ac_flag having the AXSIG (Killed by signal) bit being set, which would indicate that the session met a fate involving an OS event. If so, I would further look in the AIX Error Log for any record of the process demise, which would reveal cause. Miscellaneous things can cause mysterious terminations, the Tcsh autologout (http://www.erdc.hpc.mil/documentation/Tips_Tricks/ autologout) being a gross example. If you're going through a firewall facility of some kind, there may be some port use termination therein, based upon excessive duration. I run dsmadmc 24 x 5, and never see any session loss, per se. There is the standard ANR0482W session termination based upon the server IDLETimeout value, but that's under the covers and does not result in dsmadmc process loss: upon next keyboard action, the interaction resumes (ANR0402I) within the same ongoing dsmadmc process, which is to say no TSM login required. One thing for sure is that your script is way too simple, lacking any error handling, beginning with return code/status evaluation between command invocations. I would recommend using Perl, where you can readily program error detection, handling, logging, and recovery. what I can think of, Richard Sims On Sep 20, 2007, at 1:23 PM, Taylor, David wrote: I see the ANR2017I Administrator ADMIN issued command: BACKUP STGPOOL... in the actlog at the time that the command was first issues. The ba stgpool started and was running fine. 12 hours (exactly) later, the script reported the ANS1017E session rejected and went on to the next command, which was ba db..., however the ba stgpool was still running. There was nothing recorded in the actlog when the script reported the ANS1017E other than the commencement 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 rest of the script. I can find no time-related values in the server's configuration that is anywhere near 12 hours (43,200 seconds). I guess that at this point, I am comfortable in understanding what happened, and am now interested in finding out if that timeout can be adjusted.
wait=yes timeout??
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 it is below. --- # synch the primary and copy storage pools # backup the TSM DBB to remote disk that appears local # make sure devconfig and volhist files are up to date dsmadmc -id=admin -pass=$TSMPWD ba stg collgoldprimarypool collgoldcopypool maxpr=3 wait=yes dsmadmc -id=admin -pass=$TSMPWD ba db type=full dev=remotedbbfileclass wait=yes dsmadmc -id=admin -pass=$TSMPWD ba devconfig dsmadmc -id=admin -pass=$TSMPWD ba volhist - An enormous amount of data came into the system last night and the storage pool backup was taking a LONG time. After running for almost exactly 12 hours (I can get it down to within 22 seconds), I received an ANS1017E Session rejected... error and the script continued processing, however the storage pool backup still hadn't completed. Basically the storage pool backup was orphaned and continued running while the script went on to the database backup. Because of the timing, I feel pretty confident that there must be a 12 hour timeout on a wait=yes, but would feel a lot better if someone could confirm it. I tried doing a lot of searches on it but couldn't find anything close to an answer. Thanks in advance! David ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.clearswift.com **
Re: wait=yes timeout??
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
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 [mailto:[EMAIL PROTECTED] On Behalf Of Tim Brown Sent: den 4 juni 2007 17:32 To: ADSM-L@VM.MARIST.EDU Subject: tsm scripts and WAIT=yes 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 STGPOOL: WAIT parameter ANR2753I (DAILY_SCRIPT):not allowed from server console. Tim Brown Systems Specialist - Project Leader Central Hudson Gas Electric 284 South Ave Poughkeepsie, NY 12601 Email: [EMAIL PROTECTED] Phone: 845-486-5643 Fax: 845-486-5921 Cell: 845-235-4255 --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.
Re: tsm scripts and WAIT=yes
The problem was that I updated the schedules from via TSO on Z/OS thus the indicator for last update was server_console. I then updated them again using the Windows TSM Admin command line and all is ok Tim - Original Message - From: Henrik Wahlstedt [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU 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 [mailto:[EMAIL PROTECTED] On Behalf Of Tim Brown Sent: den 4 juni 2007 17:32 To: ADSM-L@VM.MARIST.EDU Subject: tsm scripts and WAIT=yes 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 STGPOOL: WAIT parameter ANR2753I (DAILY_SCRIPT):not allowed from server console. Tim Brown Systems Specialist - Project Leader Central Hudson Gas Electric 284 South Ave Poughkeepsie, NY 12601 Email: [EMAIL PROTECTED] Phone: 845-486-5643 Fax: 845-486-5921 Cell: 845-235-4255 --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.
tsm scripts and WAIT=yes
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 STGPOOL: WAIT parameter ANR2753I (DAILY_SCRIPT):not allowed from server console. Tim Brown Systems Specialist - Project Leader Central Hudson Gas Electric 284 South Ave Poughkeepsie, NY 12601 Email: [EMAIL PROTECTED] Phone: 845-486-5643 Fax: 845-486-5921 Cell: 845-235-4255
WAIT=YES
Hello All! If I create a script called nas_backup and it contains the following commands, to run it I just have to issue: run nas_backup. Will the 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 Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED]
Re: WAIT=YES
Joni, Yes it will. Or at least it should. ; ) I use that to control the flow of several of my scripts. cory *E-Mail Confidentiality Notice* This message (including any attachments) contains information intended for a specific individual(s) and purpose that may be privileged, confidential or otherwise protected from disclosure pursuant to applicable law. Any inappropriate use, distribution or copying of the message is strictly prohibited and may subject you to criminal or civil penalty. If you have received this transmission in error, please reply to the sender indicating this error and delete the transmission from your system immediately. [EMAIL PROTECTED] 03/11/05 8:04 AM Hello All! If I create a script called nas_backup and it contains the following commands, to run it I just have to issue: run nas_backup. Will the 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 Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED]
Re: Script timing issue with MOVE DATA WAIT=YES
Here's how i wait on a process to finish. Basically i query the process and if it's still running i re-spawn the schedule for ten minutes later. If you have any questions please let me know. john [EMAIL 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 active=yes startd=today startt=now+00:10 exp=today exit /* End of DAILY*/ /*SCRIPT1*/ /*Expire data bkup stg backup\archive pools*/ delete schedule chkproc type=admin q process if(rc_notfound) goto cont def schedule chkproc cmd=run script1 active=yes startd=today startt=now+00:10 exp=today exit cont: def schedule chkproc cmd=run backupstg active=yes startd=today startt=now+00:10 exp=today expire inventory exit /*End of SCRIPT1*/ /*Backupstg*/ delete schedule chkproc type=admin q process if(rc_notfound) goto cont def schedule chkproc cmd=run backupstg active=yes startd=today startt=now+00:10 exp=today exit cont: backup stg backuppool copypool /*End of Backupstg*/ -Original Message- Date:Sun, 19 May 2002 00:31:18 -0500 From:Roger Deschner [EMAIL PROTECTED] Subject: Script timing issue with MOVE DATA WAIT=YES 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, and I might not see when it completes. I might not even be awake. The problem is that I get the following error message: ANR8442E UPDATE LIBVOLUME: Volume CPM642 in library ATLP3000 is currently in use. The tape is still mounted according to QUERY MOUNT, because it is rewinding, unloading, and being put away in its slot by my robotic friend inside the library. Either: 1. There is some kind of SLEEP command for scripts that I am overlooking. 2. There is a bug in MOVE DATA WAIT=YES in that it does not wait for the tape to rewind and unload and get put away by the robot. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] --
Script timing issue with MOVE DATA WAIT=YES
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, and I might not see when it completes. I might not even be awake. The problem is that I get the following error message: ANR8442E UPDATE LIBVOLUME: Volume CPM642 in library ATLP3000 is currently in use. The tape is still mounted according to QUERY MOUNT, because it is rewinding, unloading, and being put away in its slot by my robotic friend inside the library. Either: 1. There is some kind of SLEEP command for scripts that I am overlooking. 2. There is a bug in MOVE DATA WAIT=YES in that it does not wait for the tape to rewind and unload and get put away by the robot. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED]
Re: Script timing issue with MOVE DATA WAIT=YES
Roger, I am aware of this problem. The only way I have been able to do this is with a KSH script that does a dsmadmc command in the backround and do a sleep for the proper amount of time or an elaborate script to process the output of the q mount after issuing a dismount against the volume and waiting until it is complete. What I have not not tried is to see if you used a dismount command after your commit with a commit following it and then the update command. It may be just enough to put the volume in a dismounting status to free the lock for update. By the way, what is your 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 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, and I might not see when it completes. I might not even be awake. The problem is that I get the following error message: ANR8442E UPDATE LIBVOLUME: Volume CPM642 in library ATLP3000 is currently in use. The tape is still mounted according to QUERY MOUNT, because it is rewinding, unloading, and being put away in its slot by my robotic friend inside the library. Either: 1. There is some kind of SLEEP command for scripts that I am overlooking. 2. There is a bug in MOVE DATA WAIT=YES in that it does not wait for the tape to rewind and unload and get put away by the robot. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED]
