CETi 1982 Technology
Technology Driven IT Training



CICS Technology Update Knowledge Base Computer Education CETi

CICS Transaction Server

CICS Transaction Server for z/OS, Version 5 Release provides new and enhanced capabilities for utilization as a service delivery platform for cloud computing.

Capacity Workloads can be run in fewer regions.
Managed operations Task thresholds can be set for data access requests, storage use, program loops, and processor time used. Policy breaches can be managed by issuing messages, abending tasks, or emitting events for triggering additional actions. Policies can be applied dynamically or during runtime operations.
Availability Upgrades can be performed without restarting z/OS and SSL certificates can be refreshed dynamically without restarting CICS regions.
Platform CICS regions can be grouped as platforms for rapid application deployment and decoupling applications from the underlying topology.
Interfaces A web container is available for deployment of lightweight Java servlets and JSP: Java Server Pages.

CICS Transaction Server for z/OS includes web services capabilities which support the new standards, interoperability profiles, and sending large amounts of binary data.

CICSPlex SM: CICSPlex System Manager systems can be backed-up and restored without manual overrides. IPIC has added support for IBM IMS communications; this improves integration and error recovery.

CICS Transaction Server can run Java applications more efficiently. A prerequisite for the CICS TS 4.2, the 64-bit Java SDK Version 6.0.1 runs Java within the IBM z/OS mainframe operating system. It has been optimized to operate on the IBM System z mainframe operating system: instruction sets, garbage collection, just-in-time compiler, and code execution on an zAAP: IBM System z Application Assist Processor. Java SDK Version 6.01 can not be used in conjunction with prior version SDKs. CICS Transaction Server does not support the 31-bit version.

The 64-bit SDK support enables Java applications under CICS without affecting the storage of existing 31-bit applications and increases the amount of storage available to Java applications. It also can be used with JVM servers and existing pooled JVMs. The allocation of the Java stack and heap in 64-bit storage allows significantly more pooled JVMs to run in each region. This can be performed in conjunction with larger cache and reduce the frequency of garbage collection. Existing Java applications will not have to be changed; it will be necessary to verify that the Java Native Interface can run in 64-bit mode. The 64-bit drivers are available for accessing DB2 and WebSphere MQ.


CICS applications can be extended to SOA: service oriented architecture and also support the SSL security protocol.

  • A URIMAP RDO: Resource Definition Online object determines how inbound, outbound, and pipeline web service requests are handled and how to process inbound requests.
  • HTTP 1.1 time and date formats are supported using the services EXEC CICS CONVERTTIME/FORMATTIME.
  • EXEC CICS WEB OPEN/CONVERSE/CLOSE enables communication with a remote server.
  • Message pipelining/chunking, persistent sessions, and EXEC CICS WEB PARSE URL are provided.
  • A container is roughly equivalent to a Commarea; a channel is a group of containers.

    • An EXEC CICS API command set is provided for containers and channels.

  • CICS Web Services Assistant enables the transformation of a CICS application into a web service.

In addition to performance and system management updates, the CICSPlex System Manager Web User Interface has been extended.

SYS-ED's workshops explain and demonstrate:

  • How to reuse applications and deploy web services into CICS using a wide range of programming languages and XML data types.
  • Enhancements for traditional VSAM-based applications.
  • Changes to the API: programming interface(s).
  • Modifications to CICS which support open standards.
  • Support for WSDL: Web Services Description Language and interoperation with other SOA tools and environments.
  • Web services support for the SOAP MTOM: Message Transmission Optimization Mechanism and XOP: XML Optimized Packaging.
  • Support for WS-Trust specification in WS-Security through the use of a STS: Security Token Service.
  • Improved performance for DPLs: Distributed Program Links over TCP/IP.
  • Traditional CICS applications can utilize thread-safe file and journal commands.
  • Shared data tables that can be larger than 2GB through the use of multiple data spaces up to the limit of 100 per CICS.
  • Extended ESDS: Entry Sequenced Datasets.
  • Utilization of 64-bit storage for data held in containers.

CICS 5.1 specific workshops include:

  • Using the web container for the deployment of lightweight Java servlets and JSP: Java Server Pages.
  • Capturing CICS events on operator writes and system messages.
  • Passing messages larger than 32K between WebSphere MQ and IMS Transaction Server.
  • Developing a 64-bit Java 7 application.

CICS 4.2 specific workshops include:

  • How to use the CICS Explorer for creating customizable task-oriented views and managing CICS regions.
  • Utilization of event technology for configuring CICS to feed business event processing engines and business dashboards.
  • How run-time for applications in COBOL, PL/1, Assembler, C, C++, and Java provide a language-neutral approach to building and deploying new applications.
  • How CICS provides open standards-based connectivity consistent with the preferred web services implementation.