RE: Unload Tape from CL Pgm?

["Jones, John (US)" <John.Jones@xxxxxxxxxxxxxxxxxxxxxxx>]

When I need to eject a tape from a command line or in a CL, I usually
use:

DSPTAP DEV(TAPxx) OUTPUT(*PRINT) ENDOPT(*UNLOAD)
MONMSG CPF0000 

John A. Jones
Americas Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787 F: +1-312-601-1782
John.Jones@xxxxxxxxxxxxxxxxxxxxxxx

-----Original Message-----
From: Michael Naughton [mailto:michael_naughton@xxxxxxxxxxxx] 
Sent: Tuesday, August 17, 2004 10:32 AM
To: Midrange Systems Technical Discussion
Subject: Unload Tape from CL Pgm?

Hi Everyone,

I thought I had seen a discussion of this a while back, but I've
searched the archives and come up with nothing. We've got a batch job
that does various things and then copies some files from a tape.

The CPYF command is set to unload the tape when it's done, but if the
job runs into a problem before it gets there the tape never unloads. I'd
like to put in an error handler that will abort the job and unload the
tape, but I don't see a CL command that does that. I tried RMVTAPCTG,
but that seems to apply to media library devices, which we don't have.
All I want to do is what the CPYF command does with the *UNLOAD option.

Any suggestions as to what I might try?  Thanks very much,

Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA  01376
413-863-4357 x444
mnaughton@xxxxxxxxxxxx

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.



This email is for the use of the intended recipient(s) only.  If you have 
received this email in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this email without the author's prior permission.  
We have taken precautions to minimize the risk of transmitting software 
viruses, but we advise you to carry out your own virus checks on any attachment 
to this message.  We cannot accept liability for any loss or damage caused by 
software viruses.  The information contained in this communication may be 
confidential and may be subject to the attorney-client privilege. If you are 
the intended recipient and you do not wish to receive similar electronic 
messages from us in future then please respond to the sender to this effect.