I haven't got any scripts for operation you described but you can try this:

1. Policies by client name
/usr/openv/netbackup/bin/admincmd/bppllist -byclient CLIENTNAME | grep CLASS | cut -d' ' -f2
2. Delete client from policy
/usr/openv/netbackup/bin/admincmd/bpplclients POLICY -delete CLIENTNAME

NetBackup Commands (Unix, Linux and Windows)
ftp://exftpp.symantec.com/pub/support/products/Net...

I have these commands. I was hoping for a script where I can pass the CLIENT name. The removed its self from its POLICY.

to put Marek's suggestion into a fairly simply bourne shell script, you would type up something like this:

#!/bin/sh

main ()
             {
              for clientname in $@ ; do
              /usr/openv/netbackup/bin/admincmd/bppllist -byclient $clientname | grep CLASS | cut -d' ' -f2
              done
              }

delpolicy ()
                  {
                   for policy in $@ ; do
                   /usr/openv/netbackup/bin/admincmd/bpplclients POLICY -delete $policy
                   done
                   }
help ()
                   {
                   echo $0 "clientname [clientname] [clientname] ....
                   exit 0
                    }
if $1 = "-?" ; then
                     help
                     else
                     main
                     fi
exit 0

now that is without giving an error message in the case of bad clientnames or no clientnames, only showing help information in the case of a -? commandline switch for the first argument in the program. This listing can be named whatever you wish - help automatically will used the invoked name of the script to self-explain. I *think* I typed that up right. If you have issues, I will gladly doublecheck that and fix it if necessary. This is assuming that Marek's commandlines are accurate - I honestly am just a UNIX admin who is learning the ropes on NetBackup so I am more helpful on the administration side, where I have years of experience.

HTH

Kris Long
Unix Geek
IBM GSC

If I understand the request correctly, you want the CLIENT to remove itself from policies?
Since the policies live on the master server, the commands need to be executed on the master server. This means that you will have to enable rsh/ssh comms at root lecel without password between clients and master - major security risk....

I posted a script here and you asked questions about it.  Have you tried it?