WebLogic Educational Consultancy SYS-ED SYSED Computer Education Techniques

WebLogic Educational Consultancy SYS-ED SYSED Computer Education Techniques

CICS Transaction Server and WebSphere MQ

CICS Transaction Server Training Sitemap | WebSphere MQ Training Sitemap

Submit CICS and WebSphere MQ Questions

Knowledge Transfer

CICS Transaction Server Schedule

Definition of Service

Delivery Medium

WebSphere MQ Schedule


CICS Transaction Server and WebSphere MQ

Reliable Message Queuing

Operational Challenge Client Requirements - CICS Transaction Server and WebSphere MQ Training Qualifying Client-specific Subject Matter
Case Studies and Workshops Guidelines and Best Practices - CICS Transaction Server Guidelines and Best Practices - WebSphere MQ
Copyright Acknowledgement

Operational Challenge

Organizational enterprise is challenged to integrate back-end legacy systems with newer client/server and web-based systems and deliver reliable message queuing between applications. IBM WebSphere MQ is the industry leading software used for moving data between applications and different systems: SOA: service oriented architecture, web servicization, distributed processing, platform and application migration, mobile computing, and cloud computing.

There is considerable complexity associated with the efficient and reliable movement of data. An accurate modeling and specification of the business logic, structure of the data, and processing throughput will be required for cost effective repurposing of existing software assets and establishing a framework for long term maintainability are the primary goals.

Client Requirements - CICS Transaction Server and WebSphere MQ Training

The client organization requires CICS Transaction Server and WebSphere MQ topics for its information technology staff. The subject matter is not included in any single search engine course. Some of the topics are from the CICS TS: Command Level Programming - Advanced course. Overview topics from the CICS Transaction Server: Web Enablement - Introduction can be incorporated into the specialized course.

Subject matter and examples from the WebSphere MQ - Advanced course also will be included. The trigger topic in the WebSphere MQ Application Programming course will be taught inclusive of examples specific to the client installation. DB2 and MQ features will need to be incorporated into the courseware and sample programs.

Qualifying Client-specific Subject Matter

These topics will need to be presented.

CICS TS Command Level Advanced WebSphere MQ - Advanced

Use of channels and containers as an alternative to COMMAREA.

Use of MQExplorer, including the Tivoli Monitor, to detect potential problems in system resources.
Logical message building - BMS. Triggering with and without passing data to the triggered transaction and utilization of the trigger message header.
Printer output and EJES job submission. Message grouping.
Temporary storage control. Distribution lists.
Transient data control. Unit of work coordination.
Interval control. WMQ security.
File Browse commands. Trigger on first, on every, and on depth.
VSAM alternate index processing. Setting up the process for a trigger monitor.
CICS web support. Create an initiation queue.
Request/response capability of HTTP. Parsing the trigger message.
CICS State Management - web browser access to CICS. User-written formats.
XML/SOAP. Data conversion exit.
WSDL: Web Services Description Language. Creating and using distribution lists.
Message handler processing for SOAP messages. Parsing the dead-letter header.
Developing and implementing online provider and requester applications as web services. Handling queue threshold conditions.
Security mechanisms for web services applications. Design and employ workload management.

These additional areas need to be qualified:

  • Is the entire message processing under z/OS or are messages being retrieved from other platforms?

  • Are the applications coded in COBOL, Java, or both?

  • What is being used: WebSphere MQ classes or JMS?

  • Is there client documentation and guidelines for using WebSphere MQ?

Case Studies and Workshops

These exercises will be conducted:

  • Upgrading CICS Transaction Server for z/OS to allow broader access to legacy mainframe applications through web services.
  • How to efficiently utilize 64-bit storage for channels and containers.
  • The improvements to the Enterprise Workload Manager for CICS.
  • Enabling connections between CICS and the WebSphere MQ product.
  • Implementing the IBM WebSphere MQ CICS Adapter.
  • Implementing and utilizing the CICS Bridge.
  • Enabling CICS support for the HTTP and WebSphere MQ transport protocols.
  • Using CICS to parse XML using IBM z/OS XML System Services.
Vendor documentation and third party content is interpreted and incorporated selectively into our courseware and training aids.

Guidelines and Best Practices

The instructor will teach and demonstrate guidelines specific to the client environment.

CICS Transaction Server

  • How to analyze throughput rate and workload response times.
  • Using the CICS Transaction Gateway ping utility to examine network connectivity and analyze response time.
  • Design channels which take take advantage of the improvements in using containers for passing data; it can be used in place of COMMAREAs.
  • Upgrading the CICS Transaction Server for z/OS to allow more comprehensive access to legacy mainframe applications through web services.
  • Utilize 64-bit storage for channels and storage.


WebSphere MQ

  • Shared queues are limited by the application list structure size.
    • Determine the maximum depth expected during peak periods, the size of the messages, and the projected duration on the queue.
    • This information then can be used in specifying an efficient structure size.
  • Examine the SMF: System Management Facility queue accounting records - SMF116 for determining the message volumes and rates.
    • The size of the queue should be a low number.
    • The important factor is not how many messages pass through a queue, but the size of the queue.
  • Data serialization needs to be examined.
    • If the messages must be processed in a required sequence, then there can be only one putting and one getting application.
    • This will require queues to be sized for holding a larger number of messages.
    • However, the requirement that messages be processed sequentially will not always apply.
  • Some serialization requirements are driven by affinities between individual messages.
    • Messages are logically associated:
      1- When multiple messages make up an application transaction.
      2- When an initial order has been accepted a change or a cancellation can be processed and ordered based on type.
  • Use one backout queue per application, not per queue.

  • Do not use the queue-manager-defined dead letter queue as the backout queue.
    • The content of the backout queue usually is driven by the application.

Copyright Acknowledgement

CICS Transaction Server and WebSphere MQ are registered trademarks of IBM Corporation.