IBM OS manual Affinity lifetimes, Cics programming techniques for transaction affinity

Page 21

 

Userid

 

A group of transactions where all instances of the transactions that are

 

initiated from a terminal and executed on behalf of the same userid must

execute in the same target region for the lifetime of the affinity. The affinity

 

lifetime for userid relations can be pseudoconversation, signon, system, or

 

permanent.

 

Affinity lifetimes

The affinity lifetime determines when the affinity is ended.An affinity lifetime can be

 

classi®ed as one of:

 

System

 

The affinity lasts for as long as the target region exists, and ends whenever

the target region terminates (at a normal, immediate, or abnormal

 

termination). (The resource shared by transactions that take part in the

 

affinity is not recoverable across CICS restarts.)

 

Permanent

 

The affinity extends across all CICS restarts. (The resource shared by

 

transactions that take part in the affinity is recoverable across CICS

 

restarts.) This is the most restrictive of all the inter-transaction affinities.

Process

The affinity exists until the process completes.

Activity

The affinity exists until the activity completes.

 

Pseudoconversation

 

The (LUname or userid) affinity lasts for the whole pseudoconversation, and

 

ends when the pseudoconversation ends at the terminal.

 

Logon

 

The (LUname) affinity lasts for as long as the terminal remains logged on to

 

CICS, and ends when the terminal logs off.

 

Signon

 

The (userid) affinity lasts for as long as the user is signed on, and ends

 

when the user signs off.

Notes:

1.For userid affinities, the pseudoconversation and signon lifetimes are possible only in those situations where one user per userid is permitted. Such lifetimes are meaningless if multiple users are permitted to be signed on with the same userid at the same time (at different terminals).

2.If an affinity is both userid and LUname (that is, all instances of all transactions in the group were initiated from the same terminal and by the same userid), LUname takes precedence.

CICS programming techniques for transaction affinity

Associated with transaction affinity, there are three broad categories of CICS programming techniques:

vSafe programming techniques

vUnsafe programming techniques

vSuspect programming techniques

Chapter 1. Introducing transaction affinities 5

Page 20 Page 22
Image 21
Page 20 Page 22
Contents IBM Page IBM Third edition March Contents Appendix A. Details of what is detected Reporter output Scanner output Examples Vi Cics Transaction Affinities Utility Guide Vii Trademarks Preface Argument zero Bibliography Cics Transaction Server for OS/390Cics books for Cics Transaction Server for OS/390 Other Cics books CICSPlex SM books for Cics Transaction Server for OS/390Summary of changes Xiv Cics Transaction Affinities Utility Guide Affinities, see the Cics Application Programming Guide Introducing transaction affinitiesRequesting region Routing regionTarget region Benets of dynamic routing What does dynamic routing cost?Transaction affinities Transaction-system affinity Inter-transaction affinityAffinity relations GlobalCics programming techniques for transaction affinity Affinity lifetimesUnsafe programming techniques Safe programming techniquesSuspect programming techniques Avoiding the effects of transaction affinityProtecting applications from one another What next? Important note Introducing the Transaction Affinities UtilityAffinity utility program components Commands detected by the Transaction Affinities Utility Detector component Scanner componentDetector components What is detectedWorsening of transaction affinities relations What is not detectedHow the affinity data is collected Controlling the DetectorSaving affinity data Control record Vsam le Affinity data Vsam lesReporter component Detector performanceBuilder component Report presenting the affinity data in a readable formIntroducing the Transaction Affinities Utility Cics Transaction Affinities Utility Guide Preparing to use the affinity utility program Creating the Vsam lesEstimating the size of the MVS data space and Vsam les #termids Dening the Vsam les to CicsPreparing to use the affinity utility program Cics Transaction Affinities Utility Guide Creating a summary report Running the ScannerAffmod DD statement Cics Transaction Affinities Utility Creating a detailed reportContents of a detailed report Is an example of a detailed report produced by the Scanner Cics Transaction Affinities Utility Guide Running the Detector Changing the stateChanging the options CAFF01 Displaying the Detector control screenStarting the collection of affinity data When you can start collecting affinity dataWhen you can pause affinity data collection Pausing the collection of affinity dataWhen you can resume collecting affinity data Resuming the collection of affinity dataStopping the collection of affinity data When you can stop collecting affinity dataCAFF02 Changing the Detector options„1… The control options Perform periodic saves Restore data on startSize of dataspace „4… Last update by useridTransid prex „2… Detect affinity typesDetector errors Cics Transaction Affinities Utility Guide Requesting a report from the Reporter Running the ReporterCAUAFF1, CAUAFF2, and CAUAFF3 DD statements Caucntl DD statementsOutput from the Reporter Cmdgrps DD statementTrangrps DD statement System Affinity report„2… Affinity types reported „1… Incorrect affinity types„3… Affinities reports TrangroupCommand RecoverableAffinity LifetimeTerminal Producing affinity transaction group denitionsBTS Task Total TransactionsAfflifesystem Descaddress CWA Using the affinity reportModifying affinity transaction groups Understanding the affinitiesRemove false affinities Remove affinity relation worseningCompressing affinity data SPI commands Using the IBM Cross System ProductENQUEUEs/DEQUEUEs Shared storageENQUEUE/DEQUEUE Detailed affinity analysisGetmain Shared SPI commands Cics Transaction Affinities Utility Guide Running the Builder DSPSIZE=16numberCONTEXT=plexname Syntax for input to the Builder Repgrps DD statementAffgrps DD statement Builder input syntax Header statements Output from the BuilderCombined affinity transaction group denitions Combining basic affinity transaction groups Relation a Relation B Resultant relation C Data sets processed report Empty transaction groups reportGroup merge report Sample group merge report Error reportSample error report Cics Transaction Affinities Utility Guide ENQ/DEQ Appendix A. Details of what is detectedLoad HOLD/RELEASE TS commandsAddress CWA CANCEL/DELAY/POST/START Wait commands SPI commandsCics Transaction Affinities Utility Guide Reporter output Scanner outputExamples Example 2±VS Cobol Which occurs for the rst Move Move Logon or System when Pconv expected Cobol affinitiesUnrecognized Transids Cics Transaction Affinities Utility Guide Appendix D. Diagnostics Detector table manager diagnosticsFunction code values Table identier values Reason code values Date formatter diagnostics Detector Cafb request queue manager diagnosticsReason code values This sectionIndex Bappl Vsam Cics Transaction Affinities Utility Guide Sending your comments to IBM Ibmr IBM

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