having amended the column definitions in bp.conf (as per instruction in Admin Guide II) :
"...
Add BPDBJOBS_COLDEFS entries to the bp.conf file to customize the output of bpdbjobs. Add a BPDBJOBS_COLDEFS entry for every column you want to include in the output using the following format:
BPDBJOBS_COLDEFS = COLDEFS_ENTRY[minimum_size[true| false]]
Where: COLDEFS_ENTRY is the name of the column to include in the output. See the following table for valid BPDBJOBS_COLDEFS entries. minimum_sizeis the minimum column width. If not specified, the default is a width of 5. trueindicates that the column should expand as needed. If not specified, true is the default. false indicates that the column should not expand beyond the minimum_size.
The order of the entries determines the order that the column headings appear.
Example
BPDBJOBS_COLDEFS = JOBID 5 true
BPDBJOBS_COLDEFS = TYPE 4 true
BPDBJOBS_COLDEFS = STATE 5 true
BPDBJOBS_COLDEFS = STATUS 6 true
BPDBJOBS_COLDEFS = POLICY 6 true
BPDBJOBS_COLDEFS = SCHEDULE 8 true
BPDBJOBS_COLDEFS = CLIENT 6 true
BPDBJOBS_COLDEFS = DSTMEDIA_SERVER 12 true
BPDBJOBS_COLDEFS = ACTPID 10 true
------------------------------------------------------------------------------------------------------------------------------------------------
Note: Keep in mind the following ramifications of a BPDBJOBS_COLDEFS entry in the bp.conf conditions:
* The addition of any BPDBJOBS_COLDEFSentry overrides all default columns.
* All users on the local system see only those columns that are specified in the bp.conf file.
------------------------------------------------------------------------------------------------------------------------------------------------
..."
and added the above plus the following entry to the bp.conf file:
BPDBJOBS_COLDEFS = DESTMEDIAD 10 true

This worked - but only partially. Of the three media that were currently loaded in drives it only reported on two of them & I've yet to find a reason why.

The only way I have found so far is to run a bpdbjobs -all_columns, then grep (sorry if you're not running UNIX) out your media id & cut out the fields that are relevant to you:

e.g
# bpdbjobs -all_columns|grep 300468|cut -d "," -f1,5,6,7     (where fields 1,5,6 & 7 are JobID, Policy, Schedule & Client respectively)

981541,UNIX_All_Local,Full_UNIX_All_Local,client1
981528,UNIX_nas_backups,Wed_Full_UNIX_nas_backups,client2
981527,UNIX_nas_backups,Wed_Full_UNIX_nas_backups,client3
981525,UNIX_nas_backups2,Wed_Full_UNIX_nas_backups,client4
981494,Windows_SQL,Wed_Full_Windows_SQL,client5

The only reason I think you achieve more this way is that the bpdbjobs -all_columns output includes a LOT of text entries from the job details such as "granted resource 300468"

Thank you. But i dont see any media IDs

could grep only the media ids for me please....i am asking it for unix it self.

i'll do the rest of editing. i was just looking for the present days media. will try that.

I added an idea to have this display in admin console

https://www-secure.symantec.com/connect/idea/active-media-id-column-java-admin-console

If you run "nbrbutil -dump | grep <barcode>" it will show you the info you are looking for.

For example..........

nbrbutil -dump | grep VB0579

         index=172 (Allocation: id={xxxx} provider=MPXProvider resourcename=apaha369_edlb masterserver=apaha058 groupid={xxxx} userSequence=0 userid="jobid=13570353" (Media_Drive_Allocation_Record: allocationKey=22722196 (Media_Drive_Record: MediaKey=4013424 MediaId=VB0579 MediaServer=apaha369 DriveKey=2002593 DriveName=lto4edlb68 PrimaryPath=/dev/rmt108.1

Not sure if this will help but thought I would throw it out there.

There is a ton more info you get with the however I just showed the first couple of lines