Creating the Hash Notification Message Set IBM-CICS

Before the broker can perform any work on messages we choose to send it, we need to tell it about the formats of these messages. We need the broker to be able to handle the following two types of messages:

  • Simple 12-character strings: the hash notifications
  • The WSDL-defined Web-service messages for our GetHash and RetrieveAddress CICS web-services

We need to create a Message Set project to contain these message definitions, but it is best practice to separate different types of messages into separate projects; therefore, we will create two Message Set projects: one for the hash notification messages and another for the WSDL-defined messages.

  1. Switch to the Broker Application Development perspective.
  2. Select File → New → Message Set Project. We call our CICSWSAPMQMsgSet, which reflects the origin of the message. Figure appears:
  3. Create a new Message Set Project

    Create a new Message Set Project

    Creating the Message Set project also creates a Message Set. Here we get to name the message set, and set Use Namespaces flag. We kept the Message Set name the same as the Message Project name.

    Figure defines the type of messages contained in this message set and in theory the whole project. For the simple, 12-char string type messages, we use the CWF format.

    Set the Physical Format of the Message Set

    Set the Physical Format of the Message Set

  4. Press finish to create the Message Set Project, the Message Set, and to open the Message Set editor.
  5. The Message Set editor

    The Message Set editor

  6. Next, we need to define the format of our simple, 12-char string format in this message set. While this could be done manually, it is better to import a language structure such as a COBOL CopyBook or C Structure and let the WMB broker do the work message in our application. We just MQPUT a 12-char string onto CICSWSAP.PUBLICATION.QUEUE. However, it is a trivial matter to create a C structure to map this message. To do this we create a C header file in the Broker toolkit under the CICSWSAPMQMsgSet project (File → New → Other → Simple → File: MQFMT.h) This invokes a simple text editor window into which we can place our C structure, as seen in Figure .
  7. Define a C Header for the MQ Message Format

    Define a C Header for the MQ Message Format

    Save this file.

  8. Now we must import this file into our CICSWSAPMQMsgSet message set. We do this by creating a new Message Definition File (New → Message Definition File).
  9. Import the C Header file

    Import the C Header file

  10. Next, we must indicate the location of the C Header file, which is what we just created, as shown in Figure.
  11. Select the C Header file

    Select the C Header file

  12. Select the MQFMT in the source structure, then press the “>” button. Check the MQFMT in the imported structures.
  13. Complete the C header input

    Complete the C header input

  14. We chose to set the prefix for the structure to “gh”, which stands for GetHash, which reflects the function that generated the hash code. We now click the Finish button to complete the import.

At this point, we created a definition so that WMB can understand the content of the message being taken from our publication queue. Next we must create very simple Message Flow to do the actual publication to the CICSWSAP/AddressChange topic.


All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

IBM-CICS Topics