How are ACF2 IMS messages defined and generated?
This document explains how ACF2 IMS are messages defined and generated.
The ACF2 IMS interface generates all messages using a starting message number and an ACF2 Message Table. The interface also adds DFSU to all messages generated in the interface. It is important to note that the ACF2 IMS messages are considered IMS user messages. The interface provides the support needed to update the internal IMS User message table. This process is part of the ACF2 IMS install.
The install of the ACF2 IMS interface requires that a starting message number be defined via the MSGBASE option of the ACF2 IMS OPTS record. This option sets the base number that will be used when the ACF2 IMS interface generates a message. The interface also requires that all ACF2 IMS messages be copied into the IMS User message Table. The ACF2 IMS messages are in ACF2IMS.ACFMAC(ACFDCMSG).
Once the interface is installed and the IMS control region is started, the ACF2 IMS interface will issue IMS User messages (DFSUnnn) for various security issues like: idle processing, security violations, max violations. All of these messages will have the following format: DFSUxxy, where 'xx' is the starting message base value as defined in the MSGBASE option of the ACF2 IMS OPTS record. The value of 'y' is the message number associated with the error as found in the ACF2 IMS Message Table.. For example a DFSU901 is the standard ACF2 IMS security violation. This message suggests that the message base number is 900 and the first entry in the ACF2 IMS message table is related to security violations, thus the value is 901. The text of this message is: ACF2/IMS: SECURITY VIOLATION
All the messages start with DFSUnnn, where nnn is the value generated for the message.
All the ACF2 IMS user messages are found in the ACF2 messages guide chapter-12.
Please consult the Chapter 5: System Control Options in the CA ACF2 for z/OS IMS Support Guide for more details.