Skip to content

Managing Message IDs

MDCMS provides the ability to add, delete or modify a message ID in an existing message file.  It works much like the MDCMS *DTAGRP functionality.

Advantages:

  • Modifying a message doesn’t require a lock on the message file.
  • Several people can manage messages without locking others out of the file.
  • Each checkout/object request is against a specific message ID, which lessens the impact of making a check.
  • Message IDs are backed up and rolled back just like any object.
  • The new/modified messages can be moved along with the other changed objects for a particular request.
  • Tracking of changes is part of an RFP process and therefore becomes part of object/RFP history.

Keep the following in mind when configuring a Message File in MDCMS:

  • MDCMS administrative authorities are required.
  • The attribute that’s created will use an object type of *MSGD.
  • A best practice is to make the attribute name the same name as the message file.
  • The message file and the associated library are defined in the Source File parameters.
  • The complete message file should exist at each test and production level.
  • For more details on this topic, scan for *MSGD in the MDCMS User Guide.

Example of Attribute Configuration:

Example of making a change to a message file in MDCMS:

There are many times when customers make the message file additions to the file in their first test level and have defined the message ID as the object in the object request with a target of *NONE.  Another option is to create the message file in your developer library.

  • The Message file name is DKWMSGF
  • The Message ID that is being added is DKW003