HEADER statements

The HEADER statement is speci®c to the Builder, and is not a CICSPlex SM statement. It is produced by the Reporter, and is needed by the Builder to create unique transaction group names.

The Reporter generates temporary transaction group names (for example, CW.00000001 and TS.00000001) while it is running, and stores these names in the output data set for that run. However, the Builder can take several Reporter data sets as input, and may therefore get the same transaction group name from different input data sets (describing different affinity transaction groups).

To ensure that the transaction group names are unique, the input transaction group names are quali®ed by the input data set name. To do this, when the Builder reads a HEADER statement (the ®rst line of an input data set), it obtains the data set name from MVS. The HEADER statement is vital because without it the Builder cannot detect the change from one input data set to another.

If you omit a HEADER statement, the Builder may generate error messages or add transactions to the wrong group, and give incorrect line numbers in the error report and an incomplete report of data sets processed.

Output from the Builder

The Builder outputs a ®le containing a set of de®nitions for combined affinity transaction groups, and a report listing the combinations that occurred.

Combined affinity transaction group de®nitions

Before each de®nition of a combined group in the output ®le, the Builder adds a commented-out REMOVE command for that group. If you already have combined groups of the same name, check that it is appropriate to delete them before uncommenting the REMOVE command.

The name of each combined affinity transaction group is derived from the alphanumerically ®rst transaction identi®er in the combined group. For example, if ABCD was ®rst, the transaction group name would be ABCDGRP.

Note: For CICSPlex SM, the name of each combined affinity transaction group must be unique.

For example, Figure 11 on page 59 shows the set of combined de®nitions that correspond to the basic de®nitions in Figure 9 on page 47, assuming that a MATCH ®lter of LUNAME, a STATE of ACTIVE, and a CONTEXT of CICPLEX1 was speci®ed on the PARM statement.

58 CICS Transaction Affinities Utility Guide

Page 73 Page 75
Page 74
Image 74
IBM OS manual Header statements, Output from the Builder, Combined affinity transaction group denitions
Page 73 Page 75

OS specifications

IBM OS, or IBM Operating System, refers to a family of operating systems developed by IBM to support its hardware architectures. IBM has produced a range of OS versions tailored for different computing needs, such as mainframes, servers, and personal computers. Among the most notable operating systems in IBM's portfolio are OS/2, z/OS, and AIX, representing a blend of innovation and reliability that has defined IBM's reputation in the computing world.

One of the defining features of IBM OS is its robust multitasking capabilities. Both z/OS, predominantly used in IBM's mainframe environments, and AIX, the Unix-based system for IBM Power Systems, support multiple users and processes simultaneously. This ability allows organizations to run numerous applications in parallel efficiently, maximizing resource utilization and improving productivity.

In terms of security, IBM OS incorporates advanced features aimed at protecting data and maintaining integrity. z/OS offers multifactor authentication, data encryption, and a security model that adheres to the latest regulatory requirements. AIX provides Secure Virtualization, which enhances isolation and security in cloud environments, essential for enterprises handling sensitive information.

Another key characteristic is the adaptability of IBM OS to modern technologies. For instance, z/OS is designed to integrate with cloud computing, open source, and DevOps practices. This adaptability supports organizations in modernizing their infrastructure while retaining the stability associated with IBM solutions. AIX similarly supports containerization and virtualization, which are critical for optimizing resource usage in dynamic computing environments.

IBM's commitment to scalability is evident across its OS offerings. Organizations leveraging z/OS can handle enormous workloads and transactional volumes, making it a preferred choice for industries like finance and telecommunications. AIX also supports scalability, allowing businesses to expand their computing resources as demands grow without significant downtime.

The availability of development tools and environments is another noteworthy aspect of IBM OS. With robust IDEs and programming languages support, developers can create and deploy applications smoothly. This assists businesses in streamlining their development processes and improving time-to-market for innovative solutions.

In summary, IBM OS encompasses a suite of operating systems characterized by multitasking, security, adaptability to modern technologies, scalability, and comprehensive development support. These features have cemented IBM's position as a leader in enterprise solutions, allowing organizations across various industries to thrive in an increasingly digital world.
Top Page Image Contents