IBM OS manual Requesting region, Routing region, Target region

Page 18

CICS Transaction Server for OS/390 Release 3 introduces extended dynamic

routing facilities, that allow the dynamic routing of:

v Transactions initiated at a terminal

v EXEC CICS START requests that are associated with a terminal

v EXEC CICS START requests that are not associated with a terminal

v Dynamic program link (DPL) requests that are received using:

± The CICS Web support

± The CICS Transaction Gateway

± External CICS interface (EXCI) client programs

± Any CICS client workstation products using the External Call Interface (ECI)

± Distributed Computing Environment (DCE) remote procedure calls (RPCs)

± Open Network Computing (ONC) RPCs

± Internet Inter-Object Request Block Protocol (IIOP)

± Any function that issues an EXEC CICS LINK PROGRAM request

v Transactions associated with CICS business transaction services (CICS BTS)

activities.

New terms have been introduced that describe the roles played by CICS regions in

dynamic routing:

Requesting region

The CICS region in which the dynamic routing request originates. For

transactions initiated at a terminal, and inbound client DPL requests, this is

typically a TOR. For terminal-related EXEC CICS START commands, for

non-terminal-related EXEC CICS START commands, for peer-to-peer DPLs,

and for CICS BTS activities, the requesting region is typically an AOR.

Routing region

The CICS region in which the decision is taken on where the transaction or

program should be run. For transactions initiated at a terminal, for EXEC

CICS START commands associated with a terminal, and for inbound client

DPL requests, this is typically a TOR. For non-terminla-related EXEC CICS

START commands, for peer-to-peer DPL requests, and for CICS BTS

activities, the routing region is typically an AOR.

Target region

The CICS region in which the transaction or program runs. For all

dynamically-routed requests, this is typically an AOR.

Full details about the new dynamic routing facilities are described in CICS

Intercommunication Guide.

The dynamic routing facility removes the need to specify the remote system name

of a target region in the transaction de®nition. Instead, you let the routing determine

dynamically to which target region it should route incoming transactions. Unlike

static routing, where there can only ever be one target region to which the routing

region can route a transaction, dynamic routing gives you the means to create

several target regions with the capability to process any given workload, and to let

the routing regions choose the best one from a candidate list.

2 CICS Transaction Affinities Utility Guide

Page 17 Page 19
Image 18
Page 17 Page 19
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 CICSPlex SM books for Cics Transaction Server for OS/390 Other Cics booksSummary of changes Xiv Cics Transaction Affinities Utility Guide Introducing transaction affinities Affinities, see the Cics Application Programming GuideRequesting region Routing regionTarget region Benets of dynamic routing What does dynamic routing cost?Transaction affinities Affinity relations Inter-transaction affinityTransaction-system affinity GlobalAffinity lifetimes Cics programming techniques for transaction affinitySuspect programming techniques Safe programming techniquesUnsafe programming techniques Avoiding the effects of transaction affinityProtecting applications from one another What next? Introducing the Transaction Affinities Utility Important noteAffinity utility program components Commands detected by the Transaction Affinities Utility Scanner component Detector componentWhat is detected Detector componentsWhat is not detected Worsening of transaction affinities relationsControlling the Detector How the affinity data is collectedSaving affinity data Affinity data Vsam les Control record Vsam leBuilder component Detector performanceReporter 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 Dening the Vsam les to Cics #termidsPreparing to use the affinity utility program Cics Transaction Affinities Utility Guide Running the Scanner Creating a summary reportAffmod DD statement Creating a detailed report Cics Transaction Affinities UtilityContents 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 Displaying the Detector control screen CAFF01When you can start collecting affinity data Starting the collection of affinity dataWhen you can resume collecting affinity data Pausing the collection of affinity dataWhen you can pause affinity data collection Resuming the collection of affinity dataWhen you can stop collecting affinity data Stopping the collection of affinity dataChanging the Detector options CAFF02Restore data on start „1… The control options Perform periodic savesTransid prex „4… Last update by useridSize of dataspace „2… Detect affinity typesDetector errors Cics Transaction Affinities Utility Guide CAUAFF1, CAUAFF2, and CAUAFF3 DD statements Running the ReporterRequesting a report from the Reporter Caucntl DD statementsOutput from the Reporter Cmdgrps DD statementTrangrps DD statement Affinity report System„3… Affinities reports „1… Incorrect affinity types„2… Affinity types reported TrangroupAffinity RecoverableCommand LifetimeBTS Task Producing affinity transaction group denitionsTerminal Total TransactionsUsing the affinity report Afflifesystem Descaddress CWARemove false affinities Understanding the affinitiesModifying affinity transaction groups Remove affinity relation worseningCompressing affinity data ENQUEUEs/DEQUEUEs Using the IBM Cross System ProductSPI commands Shared storageDetailed affinity analysis ENQUEUE/DEQUEUEGetmain 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 Error report Sample group merge reportSample error report Cics Transaction Affinities Utility Guide Appendix A. Details of what is detected ENQ/DEQTS commands Load HOLD/RELEASEAddress CWA CANCEL/DELAY/POST/START SPI commands Wait 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 Reason code values Detector Cafb request queue manager diagnosticsDate formatter diagnostics 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