Here is the jmap usage message when Serviceability Agent (SA) is present:

Usage:
    jmap [option] <pid>
        (to connect to running process)
    jmap [option] <executable <core>
        (to connect to a core file)
    jmap [option] [server_id@]<remote server IP or hostname>
        (to connect to remote debug server)

where <option> is one of:
    <none> to print same info as Solaris pmap
    -heap to print java heap summary
    -histo[:live] to print histogram of java object heap; if the "live"
                         suboption is specified, only count live objects
    -permstat to print permanent generation statistics
    -finalizerinfo to print information on objects awaiting finalization
    -dump:<dump-options> to dump java heap in hprof binary format
                         dump-options:
                           live dump only live objects; if not specified,
                                        all objects in the heap are dumped.
                           format=b binary format
                           file=<file> dump heap to <file>
                         Example: jmap -dump:live,format=b,file=heap.bin <pid>
    -F force. Use with -dump:<dump-options> <pid> or -histo
                         to force a heap dump or histogram when <pid> does not
                         respond. The "live" suboption is not supported
                         in this mode.
    -h | -help to print this help message
    -J<flag> to pass <flag> directly to the runtime system


Here is the jmap usage message when the Serviceability Agent (SA)
is not present:

Usage:
    jmap -histo <pid>
      (to connect to running process and print histogram of java object heap
    jmap -dump:<dump-options> <pid>
      (to connect to running process and dump java heap)

    dump-options:
      format=b binary default
      file=<file> dump heap to <file>

    Example: jmap -dump:format=b,file=heap.bin <pid>


This second usage message is incorrect because the '-histo:live' option
is available and works when SA is not present. It is entirely likely
that other valid options are also missing from second usage message.