> > What about:
> >
> > #! /bin/sh
> >
> > cat <<! |
> > . type: nsr group;status: running
> > show status;name
> > print
> > !
> > nsradmin -i -
>
> that should do the trick.
> If I'd leave the 'type: nsr group' away I'd probably get
> the jobs that are initiated by the clients (SAP) as well.
>
Unfortunately it doesn't do the trick :(
I've searched the documentation for valid entries for the nsradmin command.
With the example provided by Maarten I didn't get any results on jobs
initiated by the SAP client.
I guess I'll have to check the hidden attributes when a job is running...
(based on man resource(5) and NSR_Resource(5).)

Any suggestions are very welcome... ;)
(some sort of global status which is valid for all running savesets/backups,
including those which don't belong to a named group, as is the case with
client initiated SAP backups)

Cor.

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=