ASAP Migration Guide for NSX and OMF Users

ASAP Migration Guide for NSX and OMF Users—520627-001
B-1
B
OMFCOM Versus ASAP 2.0 Commands
This Appendix provides a guide to understand how the old OMFCOM commands can
now be achieved in ASAP 2.0 command interpreter:
•
Only entities supported by OMF are listed. ASAP 2.0 supports other entities that are
not in this table.
•
Additional functions in ASAP 2.0 that are not related to any OMFCOM commands
are not in this table.
Table B-1. OMFCOM Versus ASAP 2.0 Commands (page 1 of 3)
Function OMFCOM ASAP 2.0
Add a CPU * -> add cpu 01 +monitor cpu 01
Add a Disk -> add disk $data +monitor disk $data
Add a File -> add file
$system.system.userid
+monitor file
$system.system.userid
Add a
subvolume
Not supported +monitor file
$data.mysubvol
Add a Process -> add process $Xyz +monitor process $Xyz
Add Spooler
components
-> add spoolsup $spls
-> add spoolcol $s,
superv-name $spls
-> add spooldev $dev1,
superv-name $spls
-> add spoolprint $prt,
superv-name $spls
+monitor spooler $spls
Add Tape -> add tapemounts +monitor tape $tape1
Add TMF -> add tmfauditdump
-> add tmfaudittrail
-> add tmftransaction
+monitor tmf auditdump
+monitor tmf
audittrail
+monitor tmf
transactions
+monitor tmf tmf
* OMF had some default threshold values; for example, all CPUs had a default busy threshold of 90%. In
ASAP, you can select an object to monitor, but do not have to specify objectives for an attribute. You can also
specify global attribute objectives; for example, RANK CPU, BUSY < 90 Critical which applies to all CPUs,
or identify objectives for a particular CPU; for example, RANK CPU 3, BUSY < 75 Info. With ASAP, users
get greater flexibility in choosing attribute objectives.