Well you can put anything you want in the scripts.
If you want job information then use the bpdbjobs command.
This is a useful output provided by

Blayne Puklich on 1/28/05 posted to this mail group:

I believe these are correct for bpdbjobs -all_columns, -most_columns and
even -gdm.  I got a little tired of counting the field offsets all the time
so I created this to help.

Field all_columns       most_columns            gdm
 0/ 1 jobid             jobid                   jobid
 1/ 2 jobtype           jobtype                 jobtype
 2/ 3 state             state                   state
 3/ 4 status            status                  status
 4/ 5 class             class                   class
 5/ 6 schedule          schedule                schedule
 6/ 7 client            client                  client
 7/ 8 server            server                  server
 8/ 9 started           started                 started
 9/10 elapsed           elapsed                 elapsed
10/11 ended             ended                   ended
11/12 stunit            stunit                  stunit
12/13 try               try                     subtype?
13/14 operation         operation               classtype?
14/15 kbytes            kbytes                  schedule_type?
15/16 files             files                   masterserver
16/17 pathlastwritten   pathlastwritten         kbytes
17/18 percent           percent                 files
18/19 jobpid            jobpid                  percent
19/20 owner             owner
20/21 subtype           subtype
21/22 classtype         classtype
22/23 schedule_type     schedule_type
23/24 priority          priority
24/25 group             group
25/26 masterserver      masterserver
26/27 retentionunits    retentionunits
27/28 retentionperiod   retentionperiod
28/29 compression       compression
29/30 kbyteslastwritten kbyteslastwritten
30/31 fileslastwritten  fileslastwritten
31/32 filelistcount     filelistcount (always 0)
32/33 [files]...        trycount (always 0)
trycount
[trypid,trystunit,tryserver,trystarted,tryelapsed,tryended,
trystatus,trystatusdescription,trystatuscount,[trystatuslines]...,
trybyteswritten,tryfileswritten]...

There's extra junk after the tryfileswritten that I don't know how to
interpret just yet.  Also, three of the -gdm fields are guesses right now.

For folks that don't know the -all_columns output has a variable number of
fields after field 31/32.  -most_columns really gives you about everything
you need anyways, and it runs a LOT faster.

There's one gotcha I ran across this week with the -gdm output.  The lines
from bpdbjobs have comma-separated fields, but for a Vault job the storage
unit has an unescaped comma in it which throws the field count off when
you're trying to parse it.  -most_columns handles this correctly.  I don't
know if this is a known bug, a feature or what.

Enjoy! 

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Ungaro, 
Matt
Sent: Wednesday, March 02, 2005 9:19 AM
To: David Rock; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Post backup scripts?

Hi David,
        Thanks for sending that, I read it yesterday, but it's not really
giving me the information I need. I would love to be able to know how much
data was backed up. That's probably the most important thing. But from what
the Veritas Docs say, I really don't get that passed to the bpend_notify
script.

Matt

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of David Rock
Sent: Tuesday, March 01, 2005 11:21 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Post backup scripts?


* Ungaro, Matt <mjungaro AT capitolindemnity DOT com> [2005-03-01 14:30]:
> I would like to have a script run after a certain backup policy runs 
> that
can
> e-mail me the size of the amount of data backed up. I don't want to do 
> this globally for all policies. I'm running NB Enterprise 5.1 MP1 on 
> Windows Server 2003 backing up a Server 2003 client. If there's a way 
> to specify
that
> after the policy runs to run a certain VBScript, that would be great. 
> It would also be good to know how to pass variables to the script for 
> various information that I may need, such as policy name, schedule, 
> backup type,
and
> image number. Thanks!

You are looking for bpend_notify.bat it gets placed on the client.

http://ftp.support.veritas.com/pub/support/products/NetBackup_Server/264236.
p
df

Check out the section on notify scripts, PDF page 159

--
David Rock
david AT graniteweb DOT com

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu