I've posted the 1.3 JMP MIB as agreed in Tucson as:
ftp://ftp.pwg.org/pub/pwg/jmp/mibs/jmp.dicftp://ftp.pwg.org/pub/pwg/jmp/mibs/jmp-mib.docftp://ftp.pwg.org/pub/pwg/jmp/mibs/jmp-mib.mibftp://ftp.pwg.org/pub/pwg/jmp/mibs/jmp-mib.pdfftp://ftp.pwg.org/pub/pwg/jmp/mibs/jmp-mib.txtftp://ftp.pwg.org/pub/pwg/jmp/mibs/jmp-mib-rev.docftp://ftp.pwg.org/pub/pwg/jmp/mibs/jmp-mib-rev.pdf
It compiles. The .mib file is the result of stripping the headers.
If Ron agrees, it is ready for him to send out to the PWG-ANNOUNCE mailing
list for PWG Last Call.
The .txt file should be renamed to:
draft-ietf-printmib-job-monitor-08.txt
when we send it as an Internet-Draft. I did NOT post it in the
Internet-Drafts directory yet on the PWG server and did NOT send it to the
IETF. (The IETF isn't accepting I-Ds until after their meeting in December.
Here is the change history:
1.1 Changes to produce version 1.3, dated November 8, 1998
The following changes were made to version 1.2, dated October 2, 1998 to
make version 1.3, dated November 8, 1998:
1. Added the Mirror table.
2. Moved the JmJobSubmissionIDTypeTC, JmJobStateReasons1TC,
JmJobStateReasons2TC, JmJobStateReasons3TC, and JmJobStateReasons4TC
assignments out of the MIB and into the Introduction.
3. Added the MANDATORY jmSystemGroup that contains the
jmSystemVersionString, jmSystemOptionSupport, and jmSystemAttributeSupport
objects.
Here is the new System Group that we discussed adding in Tucson to help a
management application determine what parts of the MIB the agent was
supporting:
-- The System Group (MANDATORY)
-- (This group was added in version 1.3 of this MIB).
-- The jmMirrorAttrGroup consists entirely of objects that summarize
-- the implementation of this MIB on a system.
jmSystem OBJECT IDENTIFIER ::= { jobmonMIBObjects 6 }
jmSystemVersionString OBJECT-TYPE
SYNTAX JmUTF8StringTC
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minor and minor version of this MIB implemented
by this system.
The format of the string SHALL be the ASCII major
version number followed by an ASCII PERIOD (.), followed by the ASCII minor
version number, i.e., '1.3' for this version."
DEFVAL { '312E33'H } -- version 1.3
::= { jmSystem 1 }
jmSystemOptionSupport OBJECT-TYPE
SYNTAX INTEGER(0..2147483647) -- biggest int 2**31 - 1
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The options of the MIB specification that this
implementation supports specified as a bit mask.
The current set of values (which may be extended in
the future)
is given below:
1 : jmMirrorAttrGroup -- 2**0
OPTIONAL
Example: An implementation supporting the
jmMirrorAttrGroup would return an integer value of { 1 }.
This object helps a management application determine
which MIB options are supported in this system."
DEFVAL { 0 } -- no options are required
::= { jmSystem 2 }
jmSystemAttributeSupport OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..63))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The attributes of the MIB that this implementation
supports specified as a bit array.
The value of this object is a sparse bit array in
which bit n is present if attribute n is supported, where n is the value of
the enumerated attribute type in the JmAttributeTypeTC used in
jmAttributeTypeIndex (and the jmMirrorAttrTypeIndex if the jmMirrorAttrTable
is implemented). The high order bit of the first octet in this octet string
corresponds to an attribute type of 0 (reserved), i.e., Big Endian bit
string. Compare with the BITS data type in SMIv2 [SMIv2-SMI] which has the
same format but requires contiguous enumerated bits.
Note: private attributes cannot be represented in
this bit array because their enum values are in the range 2**30 to 2**31-1.
See section 3.3.8.
Example: An implementation supporting the
attributes: jobStateReasons2(3), jobStateReasons3(4), and jobName(23)
would return a value of { '180001'H }.
This object helps a management application determine
which attributes MAY be present on jobs in this system."
DEFVAL { ''H } -- no attributes are required
::= { jmSystem 3 }
Tom Hastings
(310) 333-6413