Backup Central

Hi,

I have an odd error relating to TSM requests. I had to cancel a tape checkin the otherday and ever since i have an orphaned request that is not troublesome, but annoying. How do i clear it away barring a restart of the server?

12:58:02 TSM : q req
ANR8345E QUERY REQUEST: No match found for this request number.
ANS8001I Return code 11.


12:58:43 TSM : show request
MMSV->opReqList: head=5E878878, tail=5E878878
OpRequest at 5E878878 for ANY volume TSM189:
next=00000000 (*NONE*), reqNum=001, type=13, mode=R/O,
cancelled=1, complete=0, replied=0, rc=2,
mountWait=10000, elapsed time=265:25:41
labelPrompt=


Cheers

Jim

Jim Young - Computer Operations Coordinator
IT Operations, Cattles Group IT.
Ext. 2424


Cattles plc Registered in England No: 543610
Kingston House, Centre 27 Business Park,
Woodhead Road, Birstall, Batley, WF179TD.

The views and opinions expressed herein are those of the author and not of Cattles plc or any of its subsidiaries.The content of this e-mail is confidential, may contain privileged material and is intended solely for the recipient(s) named above.

If you receive this in error, please notify the sender immediately and delete this e-mail.

Please note that neither Cattles plc nor the sender accepts any responsibility for viruses and it is your responsibility to scan the email and attachments(if any). No contracts or agreements may be concluded on behalf of Cattles plc or its subsidiaries by means of email communications.

This message has been scanned for Viruses
by Cattles and Sophos Puremessage scanning service.

The SHow REQuest output seems to say that the request number is 001,
so do Query REQuest 001 and see if that returns results, whereafter
you could try CANcel REQuest 001 and see if that works.

Also do Query PRocess F=D and Query SEssion F=D to see if any are
lingering on a mount request. The Checkin that you cancelled is
probably the thing that had incited the mount, and you believe that
process is gone. The circumstances suggest that the operation did not
complete either because of an absent tape or a tape drive problem,
where this is effectively an uncompleted hardware operation causing
the stuckee. You probably know the volume name, so can conduct a
search for that, and reinstate it if absent. Perform a check of your
drives, and perhaps use SHow LIBRary to look for anomalies. Manually
satisfying the tape introduction or mount request may resolve it.
Definitely check back in your Activity Log in the time period
suggested by the elapsed time value for evidence of a problem. If
nothing works, you'd have only the TSM restart recourse.

Richard Sims