IBM OS manual Builder input syntax

Page 73

9. If a line comment contains the characters HEADER anywhere in it, it is not

 

 

 

treated as a comment and is parsed like any ordinary line in case it is a

 

 

 

HEADER statement. Otherwise comment lines are thrown away.

 

10.

The only valid values for AFFINITY are GLOBAL, LUNAME, USERID, and

 

 

BAPPL. NONE is not allowed.

 

 

11. Keywords and values (including surrounding brackets) must not be split across

 

 

 

input lines.

 

 

12. Nested brackets are not allowed within values.

 

 

13. The Builder is case sensitive. This applies to both keywords and their values

 

 

 

(keywords must be in upper case).

 

 

Any syntax error causes an error message to be issued. Logic errors are also

 

 

possible; for example, CREATE DTRINGRP before CREATE TRANGRP can cause

 

 

error messages to be issued.

 

 

Any such errors do not cause the Builder to terminate immediately, but normally

 

 

cause a skip to either the next keyword or the next statement, depending on the

 

 

error. The Builder terminates with return code of 8 when EOF is ®nally reached. An

 

 

error report lists all errors encountered. For each error, the line containing the error

 

 

is output, plus up to four preceding lines for the same statement to put the error in

 

 

context, plus the error message.

input_statement

=

{create_statement

 

 

remove_statement

 

 

header_statement

 

 

context_statement

 

 

comment}

create_statement

=

CREATE

 

 

 

{create_trangrp

 

 

create_dtringrp}

 

 

;

 

create_trangrp

=

TRANGRP

 

 

 

NAME

(trangroup)

 

 

AFFINITY

({GLOBALLUNAMEUSERID})

 

 

AFFLIFE

({PERMANENTSYSTEMLOGONSIGNONPCONV})

 

 

[DESC

(string)]

 

 

[MATCH

({LUNAMEUSERID})]

 

 

[STATE

({ACTIVEDORMANT})]

create_dtringrp

=

DTRINGRP

 

 

 

TRANGRP (trangroup)

 

 

TRANID

(tranid)

remove_statement =

REMOVE

 

 

 

TRANGRP

 

 

 

NAME

(trangroup)

 

 

;

 

context_statement = CONTEXT

 

 

 

[plexname]

 

 

;

 

header_statement =

HEADER

 

 

 

[APPLID

(applid)]

 

 

[SAVEDATE (date)]

 

 

[SAVETIME (time)]

 

 

;

 

comment

=

©*©

 

 

 

[string

 

 

header_statement]

Figure 10. Builder input syntax

Chapter 7. Running the Builder 57

Page 72 Page 74
Image 73
Page 72 Page 74
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 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 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 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 statementsCmdgrps DD statement Output from the ReporterTrangrps 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 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 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