Status Code 98, but assigned volume pool media is available and present.

[Learning_Everyd]

Current policy is configured the same as four others exactly like it.  Same storage unit and volume pool, but this policy is generating a 98.  Other complete because media is available. 

Any suggestions?

1/3/2012 3:00:00 AM - requesting resource Development

1/3/2012 3:00:00 AM - requesting resource ma-atl06.us.manh.com.NBU_CLIENT.MAXJOBS.RH53AP02.earth.com

1/3/2012 3:00:00 AM - requesting resource ma-atl06.us.manh.com.NBU_POLICY.MAXJOBS.RH53AP02

1/3/2012 3:00:07 AM - awaiting resource Development Reason: Drives are in use, Media Server: ma-atl101,

                 Robot Number: 0, Robot Type: ACS, Media ID: N/A, Drive Name: N/A,

                 Volume Pool: LTO4_Tapes, Storage Unit: ma-atl103-hcart, Drive Scan Host: N/A

1/3/2012 10:25:34 AM - granted resource ma-atl06.us.manh.com.NBU_CLIENT.MAXJOBS.RH53AP02.earth.com

1/3/2012 10:25:34 AM - granted resource ma-atl06.us.manh.com.NBU_POLICY.MAXJOBS.RH53AP02

1/3/2012 10:25:34 AM - granted resource LT4072

1/3/2012 10:25:34 AM - granted resource HP.ULTRIUM4-SCSI.001

1/3/2012 10:25:34 AM - granted resource ma-atl103-hcart

1/3/2012 10:25:35 AM - estimated 548544 kbytes needed

1/3/2012 10:25:37 AM - started process bpbrm (8764)

1/3/2012 10:25:38 AM - connecting

1/3/2012 10:25:39 AM - connected; connect time: 00:00:01

1/3/2012 10:25:44 AM - mounting LT4072

1/3/2012 10:56:36 AM - Error bptm(pid=8084) error requesting media, TpErrno = Robot operation failed    

1/3/2012 10:56:37 AM - Warning bptm(pid=8084) media id LT4072 load operation reported an error    

1/3/2012 10:56:37 AM - current media LT4072 complete, requesting next resource Any

1/3/2012 11:26:56 AM - Error bpbrm(pid=8764) from client RH53AP02.earth.com: ERR - Cannot write to STDOUT. Errno = 104: Connection reset by peer

1/3/2012 11:26:58 AM - end writing

error requesting media (tpreq)(98)

[mph999 · Accepted solution]

Run vmquery -m LTE4072 write down the robot slot number from the output. Run robtest, from the robot control host. In robtest, select the robot, then run s d make a note of an empty drive Now run m sx dy where x is the slot number and y is the drive number This should move the media from slot to drive, does this work or fail. If it works, move the tape back using m dy sx substitute the numbers for x and y as before. Make sure you exit robtest . Martin

[Marianne]

Please note that status 98 is not related to insufficient media (status 96).

Your problem is the following:
Error bptm(pid=8084) error requesting media, TpErrno = Robot operation failed
Warning bptm(pid=8084) media id LT4072 load operation reported an error

Job details seems to suggest your robot type is ACS, right?
Other details in your post seem to list more than one media server :
'Drives are in use, Media Server: ma-atl101'
... 'Storage Unit: ma-atl103-hcart' ....

Please verify which media server is defined in STU  ma-atl103-hcart properties?

I agree to test mount/dismount with robtest as suggested by Martin.
If robot type is ACS, you need to run the command on the media server. Robtest syntax for ACS robot is a bit different (See 4.2 in this TN: http://www.symantec.com/docs/TECH31526 :(

4.2.3  Command to Mount a Volume

m 000040 0,0,0,2

MOUNT complete

4.2.4  Command to Dismount a Volume

dm 000040 0,0,0,2 f

DISMOUNT complete 

[Nicolai]

Located in /export/home/ACSSS/log/event.log

If the media is incompatible with the drive type there will be a record in the event.log.