Database Software

DBA Colleagues,
I have a quick question concerning leveraging the NSR_RMAN_ARGUMENTS parameter with the new version of EMC Networker & NMDA. In past EMC Networker versions, when the EMC Scheduler was used to initiate the backup jobs, there was a shell script called nsrnmo that could leverage unix variables and os commands to construct the path/filename for all rman output files such as:

NSRMMO defintion(/usr/bin/nsrnmo--shell script):
NSR_RMAN_ARGUMENTS="msglog '/nsr/applogs/${ORACLE_SID}_msglog_`date +%Y-%m-%d_%H:%M:%S`.log' append"

NSRNMO output which would produce an rman output logfile of(this was able to used OS vars and commands):
/nsr/applogs/MYDB_msglog_2012-06-04_11:43:02.log

Now in the latest version of EMC Networker, there are config files that are not shell scripts, but still use the same definition:

NMDA config file (/nsr/apps/config/MYDB.cfg)
ORACLE_SID=MYDB
NSR_RMAN_ARGUMENTS="msglog '/nsr/applogs/${ORACLE_SID}_msglog_`date +%Y-%m-%d_%H:%M:%S`.log' append"

MNDA Output which produce rman output logifle(no translation of the varaibles...no MYDB or date format returned in logfile name):
/nsr/applogs/${ORACLE_SID}_msglog_`date +%Y-%m-%d_%H:%M:%S`.log

Has anyone converted from Networker 7.5(NMO) or ealier to Networker 7.6(NMDA)..and what specification was useful for rman output logfile naming??

Kind Regards,
. . . Todd . . .