how to list NMSAP index with nsrinfo command for sap oracle backint saveset

There re 2 types of NMSAP Oracle backup configuration, in the SAP Brtools configuration - init<SID>.sap:
Specifying backint as the backup and restore utility - backup_dev_type = util_file
Specifying RMAN as the backup and restore utility - backup_dev_type = rman_util

[Case specification]
In this case, it is configuring backint - util_file to run backup, but afterwards running nsrinfo -n saporacle <client> command, it returned nothing.
--backup command:
./brarchive -u system/networker -d util_file -c -sd

--nsrinfo command:
# nsrinfo -n saporacle xxx
scanning client `xxx' for all savetimes from the saporacle namespace
0 objects found

With mminfo, it's showing the backint:xxx savset which is just backed up:
xxx.002 clientname 04/01/16  6 KB    full  backint:xxx
xxx.002 clientname 04/01/16  4 KB    full  backint:xxx

Once changing the namespace to 'backup', now we can see the records output of archivelog.
xxx:~ # nsrinfo -n backup <clientname> | grep -i dbf
/mnt/oracle/CER/saparch/1_3248_851208123.dbf, date=1459469144 Fri Apr  1 08:05:44 2016
/mnt/oracle/CER/saparch/1_3247_851208123.dbf, date=1459468847 Fri Apr  1 08:00:47 2016

Explanation:
While using util_file, NMSAP treats the saveset as normal File system backup (retrieved in Oracle backup mode), so it s reasonable to categorize it to  backup  namespace.
 
This is also validated in our old version (NMSAP 8.2) Admin Guide, but just very vague. See following statement:
To query the NetWorker client file index, type the nsrinfo command. For example:
nsrinfo [-v] -n saporacle -s NetWorker_server client   =>!!!!Notice that there s a context here, it s stated in the document section Reviewing the NMSAP NSM backup records
 
Query the information about the backed-up files in the client file index by using the nsrinfo command. For example:
nsrinfo -s NetWorker_server_hostname NMSAP_client_hostname

Note: This behaviour changed after NMSAP 9.x version. In the 9.x version, run nsrinfo -n saporacle <client> even for utl_file type backup.
For 8.2.x and prior version, still use nsrinfo -n backup <client> or nsrinfo <client> to query utl_file type SS.

See this in the latest NMSAP 9.2 admin guide:
Reviewing the NMSAP NSM backup records
The NetWorker server records information about each NMSAP NSM backup in the online client file index and media database. The NetWorker client file index for NMSAP NSM backups is stored under the saporacle namespace, same as used for nonsnapshot NMSAP backups.

[Another statement regarding backup_dev_type = rman_util]
When configuring backup_dev_type = rman_util, the SS namespace is not  saporacle  either, but  oracle . See following outputs:
 
# mminfo
volume        client       date      size   level  name
82nmdamysql.002 xxx 04/01/16 12 MB    full  RMAN:CER_besvtqqz.65_1
82nmdamysql.002 xxx 04/01/16 1025 KB  full  RMAN:CER_besvtqqz.66_1
 
82nmdamysql:~ # nsrinfo -n oracle <client>
scanning client `xxx' for all savetimes from the oracle namespace
CER_besvtqqz.65_1, date=1459469659 Fri Apr  1 08:14:19 2016
CER_besvtqqz.66_1, date=1459469658 Fri Apr  1 08:14:18 2016
 
[Summary]
In NMSAP 8.2 and prior version, run
nsrinfo -n backup <client> for utl_file type SS;
nsrinfo -n oracle <client> for rman_util type SS;

In the 9.x and above version, run 
nsrinfo -n saporacle <client> for utl_file type SS;
nsrinfo -n oracle <client> for rman_util type SS;

See this in the latest NMSAP 9.2 admin guide:
Reviewing the NMSAP NSM backup records
The NetWorker server records information about each NMSAP NSM backup in the online client file index and media database. The NetWorker client file index for NMSAP NSM backups is stored under the saporacle namespace, same as used for nonsnapshot NMSAP backups.

In NMSAP 8.2 and prior version, run
nsrinfo -n backup <client> for utl_file type SS;
nsrinfo -n oracle <client> for rman_util type SS;

In the 9.x and above version, run 
nsrinfo -n saporacle <client> for utl_file type SS;
nsrinfo -n oracle <client> for rman_util type SS;