IBM OS manual Cobol affinities, Logon or System when Pconv expected, Unrecognized Transids

Page 91

Appendix C. Useful tips when analyzing Transaction Affinities Utility reports

Sometimes the report produced by the Reporter from data gathered from the Detector can contain some results that appear odd at ®rst glance. This appendix gives tips for resolving such results.

COBOL affinities

If an application program is invoked using the native CALL statement, CICS COBOL run-time code issues an EXEC CICS LOAD HOLD for the program and branches to it directly. This causes affinity only if the program is not reentrant; that is, if it modi®es itself. Otherwise, there is no affinity.

CICS COBOL run-time code writes data to a TS queue if an abnormal termination occurs. The TS queue name used is ªCEBRº plus the termid of the terminal, or blanks if there is no terminal. This does not cause affinity.

LOGON or SYSTEM when PCONV expected

When dealing with an application that is known to use TS queues within a pseudoconversation, but never beyond, there may be occurrences in the report of affinity groups that appear as LUNAME/SYSTEM or LUNAME/LOGON, instead of the expected LUNAME/PCONV.

vA SYSTEM lifetime can be explained if the installation uses a session manager that logs users off after a pre-determined quiet time. When the log off occurs in the middle of a pseudoconversation, the Transaction Affinities Utility notices that the TS queue still exists, and increases the lifetime to SYSTEM.

vA LOGON lifetime can be explained by the user switching off the terminal in the middle of a pseudoconversation and causing a VTAM® line error. This causes an error transaction to be attached internally at the terminal. The affinity utility program notices that the TS queue exists at the end of that transaction, and increases the lifetime to LOGON.

In both these circumstances the real lifetime is PCONV, because, although the TS queue exists at the end of the pseudoconversation, the data in it will never be used again. Normally the ®rst action of a new pseudoconversation is to delete the contents of all such TS queues for that terminal to ensure that everything is tidy.

Unrecognized Transids

Transids that consist of garbage data are reported in the Transaction Affinities Utility report. Such transids are not known to CICS, and most contain the same hexadecimal data. This is probably caused by a bug in an application that causes the EIB to be overwritten.

© Copyright IBM Corp. 1994, 1999

75

Page 90 Page 92
Image 91
Page 90 Page 92
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 Transaction Server for OS/390 BibliographyCics 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 affinitiesRouting region Requesting regionTarget region What does dynamic routing cost? Benets of dynamic routingTransaction affinities Global Inter-transaction affinityTransaction-system affinity Affinity relationsCics programming techniques for transaction affinity Affinity lifetimesAvoiding the effects of transaction affinity Safe programming techniquesUnsafe programming techniques Suspect programming techniquesProtecting 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 lesReport presenting the affinity data in a readable form Detector performanceReporter component Builder componentIntroducing the Transaction Affinities Utility Cics Transaction Affinities Utility Guide Creating the Vsam les Preparing to use the affinity utility programEstimating 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 Changing the state Running the DetectorChanging the options CAFF01 Displaying the Detector control screenStarting the collection of affinity data When you can start collecting affinity dataResuming the collection of affinity data Pausing the collection of affinity dataWhen you can pause affinity data collection When you can resume collecting 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 start„2… Detect affinity types „4… Last update by useridSize of dataspace Transid prexDetector errors Cics Transaction Affinities Utility Guide Caucntl DD statements Running the ReporterRequesting a report from the Reporter CAUAFF1, CAUAFF2, and CAUAFF3 DD statementsCmdgrps DD statement Output from the ReporterTrangrps DD statement System Affinity reportTrangroup „1… Incorrect affinity types„2… Affinity types reported „3… Affinities reportsLifetime RecoverableCommand AffinityTotal Transactions Producing affinity transaction group denitionsTerminal BTS TaskAfflifesystem Descaddress CWA Using the affinity reportRemove affinity relation worsening Understanding the affinitiesModifying affinity transaction groups Remove false affinitiesCompressing affinity data Shared storage Using the IBM Cross System ProductSPI commands ENQUEUEs/DEQUEUEsENQUEUE/DEQUEUE Detailed affinity analysisGetmain Shared SPI commands Cics Transaction Affinities Utility Guide DSPSIZE=16number Running the BuilderCONTEXT=plexname Repgrps DD statement Syntax for input to the BuilderAffgrps DD statement Builder input syntax Output from the Builder Header statementsCombined affinity transaction group denitions Combining basic affinity transaction groups Relation a Relation B Resultant relation C Empty transaction groups report Data sets processed 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 Scanner output Reporter outputExamples Example 2±VS Cobol Which occurs for the rst Move Move Cobol affinities Logon or System when Pconv expectedUnrecognized Transids Cics Transaction Affinities Utility Guide Detector table manager diagnostics Appendix D. DiagnosticsFunction code values Table identier values Reason code values This section Detector Cafb request queue manager diagnosticsDate formatter diagnostics Reason code valuesIndex 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