I came across a Mainframe COBOL program reading messages one by one from MQ eueue, and does some processing and writes the output data to another MQ queue. It is a very simple program.
The read was destructive MQGET and MQPUT was done using MQPMO_NO_SYNCPOINT so messages were written to the output MQ queue immediately.
When I checked with application SMEs Why this program was designed this way instead of using plain sequential files.
The answer: restartability. If this program abends, you simply restart the program, no clean up is needed.
This kind of approach can significantly increase Mainframe CPU utilization and place additional load on the MQ subsystem.
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.