ISSUE 82 - Change the OID assignment as Jeff Case and David
Perkins suggest:
>        jobmonMIB
>        jobmonMIB.1 jobmonMIBObjects
>        jobmonMIB.1.1 jmGeneral
         jobmonMIB.1.1.1 jmGeneralTable
         jobmonMIB.1.1.1.1 jmGeneralEntry
         jobmonMIB.1.1.1.1.1 jmGeneralJobSetIndex
         jobmonMIB.1.1.1.1.2 jmGeneralNumberOfActiveJobs
         jobmonMIB.1.1.1.1.3 jmGeneralOldestActiveJobIndex
         jobmonMIB.1.1.1.1.4 jmGeneralNewestActiveJobIndex
         jobmonMIB.1.1.1.1.5 jmGeneralJobPersistence
         jobmonMIB.1.1.1.1.6 jmGeneralAttributePersistence
         jobmonMIB.1.1.1.1.7 jmGeneralJobSetName

>        jobmonMIB.1.2 jmJobID
         jobmonMIB.1.1.1 jmJobIDTable
         jobmonMIB.1.1.1.1 jmJobIDEntry
         jobmonMIB.1.1.1.1.1 jmJobSubmissionID
         jobmonMIB.1.1.1.1.2 jmJobIDJobSetIndex
         jobmonMIB.1.1.1.1.3 jmJobIDJobIndex

>        jobmonMIB.1.3 jmJob
         jobmonMIB.1.1.1 jmJobStateTable
         jobmonMIB.1.1.1.1 jmJobStateEntry
         jobmonMIB.1.1.1.1.1 jmJobIndex
         jobmonMIB.1.1.1.1.2 jmJobState
         jobmonMIB.1.1.1.1.3 jmJobStateReason1
         jobmonMIB.1.1.1.1.4 jmNumberOfInterveningJobs
         jobmonMIB.1.1.1.1.5 jmJobKOctetsRequested
         jobmonMIB.1.1.1.1.6 jmJobStateKOctetsProcessed
         jobmonMIB.1.1.1.1.7 jmJobImpressionsRequested
         jobmonMIB.1.1.1.1.8 jmJobStateImpressionsCompleted
         jobmonMIB.1.1.1.1.9 jmJobOwner

>        jobmonMIB.1.4 jmAttribute
         jobmonMIB.1.1.1 jmAttributeTable
         jobmonMIB.1.1.1.1 jmAttributeEntry
         jobmonMIB.1.1.1.1.1 jmAttributeTypeIndex
         jobmonMIB.1.1.1.1.2 jmAttributeInstanceIndex
         jobmonMIB.1.1.1.1.3 jmAttributeValueAsInteger
         jobmonMIB.1.1.1.1.4 jmAttributeValueAsOctets

         jobmonMIB.2     jobmonMIBNotifications  -- reserved

>        jobmonMIB.3    jobmonMIBConformance
         jobmonMIB.3.1  jobmonMIBCompliance
         jobmonMIB.3.2  jmMIBGroups
         jobmonMIB.3.2.1 jmGeneralGroup
         jobmonMIB.3.2.2 jmJobIDGroup
         jobmonMIB.3.2.3 jmJobGroup
         jobmonMIB.3.2.4 jmAttributeGroup

Correct?
>yes, if
>    1.  jobmon is not somewhere under printmib
>    2.  you don't have something like
>         jobmonMIB.2 jobmonNotifications
>        in which case then
>         jobmonMIB.3 jobmonMIBconformance
>        would move down one arc
Closed:  Yes, including reserving an OID for traps, in case
we need them in the future.
Closed:  Add jmGeneralJobSetIndex to jmGeneralTable and
jmJobIndex to jmJobTable to follow SMI rules, even though
previous version compiles cleanly.  This will avoid what
David Perkins refers to as "illegal" indexing.  Then have to
rename the two columns in the jmJobIDTable to not conflict.