The situation is that existing MRT definitions are "somehow" being dropped/lost/deleted form the SSM database. ... Our weekly housekeeping processing consists of the following actions against the SSM Site Master (in which, of course, the MRT definitions are stored):
Several customers have expressed interest in mapping SSM actions into their current trouble ticket system. ("Trouble ticket" systems may also be called incident tracking systems, help desk systems, or similar names. Commercial examples include Serena TeamTrack or Serena Business Mashups, IBM Info/Man, and BMC Remedy.)
I do not understand the nature of this problem (origin/symptom), nor what actions can be taken to correct/resolve this condition. The $INTEGs have also had similar
Application Programmer Action : Correct the device name subparameter and resubmit the allocation request. If the device name subparameter correctly identifies a device in the current configuration and a dynamic configuration change has just occurred, resubmit the request.
Related Note: MLS and MRT Administration each have their own SAF Profile now, and are no longer automatically associated with any other form of administrative authority. Developments statement regarding the nature of the delivered functionality:
