> > #! /bin/sh
> >
> > cat <<! |
> > . type: nsr group;status: running
> > show status;name
> > print
> > !
> > nsradmin -i -
> >
> > Maarten
> Thanx Maarten,
>
> 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.

The 'nsradm' information will give information about any running group,
whether the group is started via the scheduler, or via a 'savegrp'
invocation.

It will not give any information about ad-hoc saves, where 'save' is run
on the client outside of any group.

Unrestricting the query string so that it's not constrained to type: nsr
group won't help at all.  I can't think of any other nsradmin value that
would be similarly useful for determining ad-hoc saves.

At that point, you're back to looking for 'nsrexec' processes on the
server, or parsing the 'session statistics' attribute from 'type:NSR'.

When any save is running (inside or outside of a group), it should be
present there.

nsradmin> show session statistics
nsradmin> print type:nsr

--
Darren Dunham                                           ddunham AT taos DOT com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=