Index Index for
Section 8
Index Alphabetical
listing for M
Bottom of page Bottom of
page		 

mosy(8)


NAME

  mosy - The managed object syntax compiler.


SYNOPSIS

  /usr/sbin/mosy [-d] [-i] [-o output_file] [-s] [-1] input_file


OPTIONS

  -d  Specifies no duplicate entries in the output file.  By default, if
      duplicate entries exist in the input file, they will also exist in the
      output file.

  -i  Specifies that errors are ignored. This option causes the mosy program
      to create an output file even if it encounters errors.  The default
      behavior is that the mosy program generates no output file when errors
      are encountered.

  -o output_file
      Specifies the file to create for mosy output.  If not specified, the
      output file is derived from the input file name by replacing the suffix
      .my with .defs or appending .defs.  If the input_file is not specified
      (or is specified as a hyphen (-) for standard input), output goes to
      standard output.

      You can also use a hyphen (-) to specify the output file name, which
      means output to standard out.

  -s  Indicates silent mode which turns off the default behavior of printing
      out objects names, type names, and identifiers.

  -1  Specifies that the mosy program will perform only the first validation
      pass when compiling. The mosy program prints the input_file contents as
      it parses, which is useful when debugging syntax errors.


OPERANDS

  input_file
      Specifies a text file in MIB format describing a set of managed
      objects.	If you do not specify an input_file or specify a hyphen (-),
      the program accepts input from standard input.


DESCRIPTION

  The mosy program reads a description of an SNMP-managed objects module
  (extracted from a MIB) and produces a simple ASCII file containing
  equivalent definitions.  The output file is used by various management
  applications.	 In particular, mosy output files are used as input to the
  snmpi program when developing extensible SNMP subagents for Tru64 UNIX.

  The input_file is typically obtained by cleaning up an RFC file that
  defines a MIB.  (You can use the /usr/examples/esnmp/mib_converter.sh
  script to perform this task.)

  For a complete description of using mosy and developing subagents refer to
  the Network Programmer's Guide.


EXAMPLES

   1.  Compile the file chess.my with the output going to the file
       chess.defs.
	    # mosy chess

   2.  Clean up the MIB defined in RFC1514.txt and compile it, placing the
       output in file fred.objects
	    # /usr/examples/esnmp/mib-converter.sh < rfc1514.txt > rfc1514.my
	    # /usr/sbin/mosy -o fred.objects rfc1514.my

       You must copy the /usr/examples/esnmp/mib-converter.sh program to
       another directory and make it executable in order to perform this
       operation.


FILES

  /usr/examples/esnmp/mib_converter.sh


SEE ALSO

  Commands: snmpd(8), snmpi(8), snmp_request(8)

  Network Programmer's Guide


IDENTIFICATION

  Marshall T. Rose, Performance Systems International

  This work was partially supported by the U.S. Defense Advanced Research
  Projects Agency and the Rome Air Development Center of the U.S. Air Force
  Systems Command under contract number F30602-88-C-0016.

  It has been modified for use in Tru64 UNIX extensible SNMP.

Index Index for
Section 8
Index Alphabetical
listing for M
Top of page Top of
page