Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info
Summary: CAST AIP 8.3.16 introduces a number of features and changes as listed below. To view the impacts of these changes on analysis results, see: Changes in results post upgrade.

Mainframe Analyzer - support for IBM MQSeries

In CAST AIP ≥ 8.3.16, Mainframe Analyzer supports the publisher/subscriber mode and point-to-point mode for IBM MQSeries. Publisher/Subscriber objects will be generated and Call links between Cobol objects and IBM MQ objects and between IBM MQ objects and Cobol objects will be generated by the Web Services Linker extension - you must ensure that v. ≥ 1.6.8 of this extension is installed, otherwise no links will be generated.

You can find out more information about this support in Mainframe - Technical notes

CAST Extension Downloader

...

If you have custom scripts that fetch data from any of the existing tables, please ensure that you update these scripts yourself.

MAINFRAME new feature.

IBM MQSeries.

From 8.3.16, Mainframe analyzer support the publisher/subsrcirber mode and point to point mode for IBM MQSeries.

Two type implementation:

  • Point to Point: MOVE MQOT-Q TO MQOD-OBJECTTYPE:

    In point-to-point, message producers are called senders and message consumers are calledreceivers. Senders produce messages to a queue, and receivers asynchronously consume messages from that queue.

    For point-to-point to work, connected applications need to know the name of the queue through which they interact.

    A queue could have a single receiver or be scaled to many, in which case each message is only consumed by one receiver, distributing the workload across them all.

    This style of messaging is built around the concept of message queues, and around the processing of messages by a single consumer.

Publisher/Subscriber MOVE MQOT-TOPIC-Q TO MQOD-OBJECTTYPE:

The producer of a message is known as a publisher, and message consumers are known as subscribers. The publishing and subscribing applications within the infrastructure agree on the name of a topic. For a consumer to signal that they want to receive messages on that topic, they create a subscription to it.

Any message published to a topic will be delivered to all the subscriptions, so every subscriber gets a copy. There could be many publishers and many subscribers to each topic, MQ handles the delivery of messages between all of them.

...

Example Publisher/Subscriber:

Publisher a topic:

...

.

...

Subscriber a topic

Code Block
01 SUB-DESCRIPTOR.
	COPY CMQSDV.
ADD MQSO-CREATE MQSO-MANAGED MQSO-FAIL-IF-QUIESCING
									GIVING MQSD-OPTIONS.
MOVE ‘Vegetal/Meal’ TO TARGET-TOPIC.
SET MQSD-OBJECTSTRING-VSPTR TO ADDRESS OF TARGET-TOPIC.
MOVE 18 TO MQSD-OBJECTSTRING-VSLENGTH.

...
CALL 'MQSUB' USING HCONN,
			SUB-DESCRIPTOR,
			Q-HANDLE,
			SUB-HANDLE,
			MQCC,
			REASON.

CALL 'MQGET' USING HCONN,
			Q-HANDLE,
			MESSAGE-DESCRIPTOR,
			GMOPTIONS,
			BUFFER-LENGTH,
			BUFFER,
			DATA-LENGTH,
			MQCC,
			REASON.




Result in enlighten:

Image Removed

The link is created by WebServiceLinker from 1.6.8-funcrel.