|
If the tape needs to be changed, the system sends it's own message, which is likely getting ignorted. Have you considered creating a unique message queue for every tape drive that needs to be enrolled (e.g.: if the tape drive is TAP01, call the message queue TAP01) and write a message handling program that hangs on that message and sends the messages. Seems like a lot less overhead to me. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com "Leland, David" <dleland@Harter.com To: "'midrange-l@midrange.com'" <midrange-l@midrange.com> > cc: Sent by: Subject: RE: DSPTAP takes too long midrange-l-admin@mi drange.com 09/24/01 12:49 PM Please respond to midrange-l This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Have you looked at CHKTAP? Will that give you enough info? Dave -----Original Message----- From: Jim Langston [mailto:jlangston@celsinc.com] Sent: Monday, September 24, 2001 11:47 AM To: midrange-l@midrange.com Subject: DSPTAP takes too long I've been given the task to write something to start checking the tape in our tape drive around 7:00 in the morning and start sending a message every hour until the tape is changed. Not a difficult task, it would seem, simply do a DSPTAP, get a file date/time or tape date/time and save the value, and compare every hour until it changes. I do a DSPTAP to an outfile, and it takes quite a long time to complete (over half hour). I tried to see if I can just get the first label, but with outfile it starts at the label number you specify. So... my question is, are there any tap APIs I could use that could perhaps be faster? Just allow me to grab the beginning tape information as that's all I need. Thanks in advance, Jim Langston _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.