- 1. remarkeble Q EVENT (score: 1)
- Author: Henk ten Have <hthta AT SARA DOT NL>
- Date: Mon, 26 Aug 1996 13:52:36 +0200
- Don't make ADSM fool on you: q event * t=a gives the following output: Scheduled Start Actual Start Schedule Name Status -- -- -- -- 08/26/96 07:00:00 08/26/96 07:00:01 BACKUP_COPY Completed 08/26/96
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1996-08/msg00502.html (13,048 bytes)
- 2. Re: remarkeble Q EVENT (score: 1)
- Author: Dwight Cook <decook AT AMOCO DOT COM>
- Date: Mon, 26 Aug 1996 10:19:42 -0500
- Item Subject: remarkeble Q EVENT If you are not at 2.1.0.8 GO TO IT NOW ! ! ! ! ! We've been running with only two 3590 tape drives in a 3494 atl and were experiencing difficulties with mount request
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1996-08/msg00505.html (15,174 bytes)
- 3. Re: remarkeble Q EVENT (score: 1)
- Author: Mark Stapleton <mstaple AT INSYNC DOT NET>
- Date: Wed, 28 Aug 1996 11:29:13 GMT
- Let me second that. Now jobs do not hang up when a mount fails; it merely unmounts the tape and tries again on the next available tape drive. (At least it does on *our* 3590 drives in our 3494.) **AL
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1996-08/msg00563.html (10,673 bytes)
This search system is powered by
Namazu