The IMMSv conforms to the IMM Service specification described in the SAF document SAI-AIS-IMM-A.02.1 with the following exceptions:
| Section | Description | Support |
| 3.2 | Internal Persistent Repository | No. IMM will always start from a configured XML file. Dumps may be generated to replace that file. |
| 3.3 | Unavailability of the IMM API on a Non-Member Node | No. IMM does not use the CLM service. |
| 4.5 | ObjectSearch | Partly Compliant. Search/iteration with attribute matching is not supported for matching plain runtime attributes. The saImmOmSearchInitialize will return ERR_LIBRARY if this is attempted. |
| 4.8.2 | saImmOmCcbObjectCreate () | Partly compliant. The immsv in OpenSAF does not allow the creation of configuration objects with a runtime object as parent. The standard currently allows such as create, with a persistent runtime object as parent. |
| 4.9.3 | saImmOmAdminOperationContinue() | No. |
| 4.9.3 | saImmOmAdminOperationContinueAsync() | No. |
| 4.9.4 | saImmOmAdminOperationContinueClear() | No. |
| 6 | IMM Service UML Information Model | No. |
| 7 | IMM Service Administration API | No. The immdump CLI command provides basically the same functionality. |
Note that the semantics of saImmOiClassImplementerSet is vague on the point of interference with saImmOiObjectImplementerSet in versions A.02.01 and A.01.01 of the IMM standard. A clarification is made in A.03.01 that saImmOiClassImplementerSet will return SA_AIS_ERR_EXIST not only when there is already a class implementer set for the class, but also if any of the instances of the class has an implementer set via saImmOiObjectImplementerSet. The clarification is made in A.03.01 and this implementation is of version A.02.01, but since it is a clarification that restricts behavior, we have implemented this restriction now.
