IBM OS manual Syntax for input to the Builder, Repgrps DD statement, Affgrps DD statement

Page 72

Specify the name of the Transaction Affinities Utility load library where you have installed the Builder program, CAUBLD.

vThe REPGRPS DD statement

Specify the (concatenation of) names of the sequential data sets containing the basic affinity transaction groups to be input to the Builder. The Builder reads the lines of the input data sets, and checks them for syntax and logic errors. For information about the valid syntax, see ªSyntax for input to the Builderº.

vThe AFFGRPS DD statement

Specify the name of the sequential data set where the combined affinity transaction groups are to be sent. This data set is suitable for input to CICSPlex SM.

vThe SYSPRINT DD statement

Specify the destination for the report output by the Builder.

 

Syntax for input to the Builder

 

The syntax in the sequential data sets input to the Builder is similar (but not

identical) to that allowed by CICSPlex SM. (For more information, see CICS

Transaction Server for OS/390 Installation Guide.) The differences are given in the

 

following list:

1.The only statements you can supply are:

v CREATE statements for TRANGRPs and DTRINGRPs.

vREMOVE statements for TRANGRPs.

vTEXT statements and line comments. (A line comment is a line that starts with an asterisk (*) in column 1.)

vHEADER statements for the Builder, and not for a CICSPlex SM statement.

2.Block comments delimited by '/*' and '*/' are not recognized.

3.Transaction group names of up to 11 characters are allowed. (CICSPlex SM allows only 8 characters.)

4.A CREATE TRANGRP statement must have exactly one NAME, one AFFINITY, and one AFFLIFE value. MATCH and STATE values are optional and ignored (they are overridden by the values on the PARM statement or the default). A DESC value is optional and ignored. Any other keywords are reported as errors.

5.A CREATE DTRINGRP statement must have exactly one TRANGRP and one TRANID value. Any other keywords are reported as errors.

6.REMOVE TRANGRP statements are optional and are ignored by the Builder. However, if a REMOVE TRANGRP statement appears in an input data set, it must have exactly one NAME value. Any other keywords are reported as errors.

7.CONTEXT statements in the input data set are optional and are ignored by the Builder. They are overridden by the CONTEXT operand of the PARM statement (if speci®ed) or the default.

8.A HEADER statement requires no keyword. APPLID, SAVEDATE, and SAVETIME are all optional, and if speci®ed their values are not validated. The HEADER statement must end in a semi-colon and should not span lines. Each input data set must start with a HEADER statement. (See ªHEADER statementsº on page 58.)

56 CICS Transaction Affinities Utility Guide

Page 71 Page 73
Image 72
Page 71 Page 73
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 Inter-transaction affinity Transaction-system affinityAffinity relations GlobalAffinity lifetimes Cics programming techniques for transaction affinitySafe programming techniques Unsafe programming techniquesSuspect 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 leDetector performance Reporter componentBuilder 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 dataPausing the collection of affinity data When you can pause affinity data collectionWhen you can resume collecting affinity data 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 saves„4… Last update by userid Size of dataspaceTransid prex „2… Detect affinity typesDetector errors Cics Transaction Affinities Utility Guide Running the Reporter Requesting a report from the ReporterCAUAFF1, CAUAFF2, and CAUAFF3 DD statements Caucntl DD statementsOutput from the Reporter Cmdgrps DD statementTrangrps DD statement Affinity report System„1… Incorrect affinity types „2… Affinity types reported„3… Affinities reports TrangroupRecoverable CommandAffinity LifetimeProducing affinity transaction group denitions TerminalBTS Task Total TransactionsUsing the affinity report Afflifesystem Descaddress CWAUnderstanding the affinities Modifying affinity transaction groupsRemove false affinities Remove affinity relation worseningCompressing affinity data Using the IBM Cross System Product SPI commandsENQUEUEs/DEQUEUEs 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 Detector Cafb request queue manager diagnostics Date formatter 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