IBM OS manual Data sets processed report, Empty transaction groups report, Group merge report

Page 77

Table 11. Resultant affinity lifetimes (GLOBAL relation)

Lifetime X

Lifetime Y

Resultant lifetime Z

 

 

 

PERMANENT

Any lifetime

PERMANENT

 

 

 

Any other lifetime combination

 

SYSTEM

 

 

 

Data sets processed report

This report gives the names of all the input data sets (speci®ed on the REPGRPS

DDstatement) that were read. This is produced even if errors occur in the input data sets.

Note: Only data sets that contain a HEADER statement appear in the report.

CICS TRANSACTION AFFINITIES UTILITY

 

 

1995/11/28

Page

1

BUILDER REPGRPS DATASETS PROCESSED REPORT

 

 

 

 

 

Dataset Name

CICS

Detector Last

Detector Last

 

 

 

APPLID

Save Date

Save Time

 

 

--------------------------------------------

--------

--------------

--------------

 

 

CICSPDN1.TRANGRPS.MERGE1

CICSPDN1

95/11/25

09:05:09

 

 

CICSPDN1.TRANGRPS.MERGE2

CICSPDN1

95/11/26

15:22:34

 

 

CICSPDN1.TRANGRPS.ONE

CICSPDN1

95/11/27

12:00:51

 

 

Figure 12. Sample data sets processed report

Empty transaction groups report

This report gives all basic transaction groups (trangroups) that were de®ned, but contained no transactions. It is produced only if the input data sets have no errors. An empty trangroup probably indicates that you have made a mistake. (The Reporter cannot produce empty trangroups, so you must have created the input by hand, and probably omitted some corresponding CREATE DTRINGRP statements.)

CICS TRANSACTION AFFINITIES UTILITY

 

 

 

 

1995/11/28

Page

2

BUILDER EMPTY TRANGROUP DEFINITIONS

 

 

 

 

 

 

 

CICSPDN1.TRANGRPS.EMPTY1

 

 

 

 

 

 

 

G1

(GLOBAL SYSTEM )

G2

(GLOBAL PERMANENT)

G3

(GLOBAL SYSTEM

)

CICSPDN1.TRANGRPS.EMPTY2

 

 

 

 

 

 

 

L2

(LUNAME PERMANENT)

L3

(LUNAME LOGON

)

L4

(LUNAME PCONV

)

Figure 13. Example empty trangroups report

Group merge report

For each combined group, this report gives the constituent transactions and basic groups that went to comprise it. (This is a kind of audit trail.) It is produced only if there are no errors in the input data sets. It is very useful when establishing which basic group has caused the severe worsening of an affinity lifetime. For example, in Figure 14 on page 62, four groups were merged: three were LUNAME and PCONV, and one was LUNAME and SYSTEM. The latter caused the lifetime worsening.

Chapter 7. Running the Builder 61

Page 76 Page 78
Image 77
Page 76 Page 78
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 Cics books for Cics Transaction Server for OS/390 BibliographyCics 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 affinitiesTarget region Requesting regionRouting region Transaction affinities Benets of dynamic routingWhat does dynamic routing cost? 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 Estimating the size of the MVS data space and Vsam les Preparing to use the affinity utility programCreating the 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 Changing the options Running the DetectorChanging the state 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 statementsTrangrps DD statement Output from the ReporterCmdgrps 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 CONTEXT=plexname Running the BuilderDSPSIZE=16number Affgrps DD statement Syntax for input to the BuilderRepgrps DD statement Builder input syntax Combined affinity transaction group denitions Header statementsOutput from the Builder Combining basic affinity transaction groups Relation a Relation B Resultant relation C Group merge report Data sets processed reportEmpty transaction groups 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 Examples Reporter outputScanner output Example 2±VS Cobol Which occurs for the rst Move Move Unrecognized Transids Logon or System when Pconv expectedCobol affinities Cics Transaction Affinities Utility Guide Function code values Appendix D. DiagnosticsDetector table manager diagnostics 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