Note: The postings on this site solely reflect the personal views of each author and do not necessarily represent the views, positions, strategies or opinions of IBM or IBM management. IBM reserves the right to remove content deemed inappropriate.
Have you been an avid user of Web Administration Console in TXSeries? Then, be ready for a pleasant surprise when you move to a version newer than TXSeries for Multiplatforms V7.1.
The TXSeries Administration Console (Let me call it TAC keep it short) is a Java EE web application, which is deployed on to a web application server. Since its introduction in TXSeries for Multiplatforms version 6.1, till TXSeries for Multiplatforms V7.1, it was using Light Weight Infrastructure (pet named LWI) as its web server. Now this is replaced with... [More]
In the earlier blog on “ Securing your XA Password ” , you saw the steps that need to be followed to create a secure password for your XA connections. This blog just adds to the previous post by showing a picture of how the XAD entries look with existing plain text passwords and newly modified secure XA password.
An existing XAD entry with plain text password could look something like this ,
Observe the XAOpen... [More]
Well, if you have been using TXSeries for Multiplatforms (TXSeries), one of the difficult problems that you would have come across is to debug transaction error scenarios that span across multiple regions. Co-relating critical data for a transaction or a task across all the involved regions is always important while debugging such scenarios. In most situations, a TXSeries setup involves multi-region setup that are all connected using inter system communication facilities (DPL, TR etc). So, if you imagine a typical setup, 3 TXSeries regions are... [More]
AppProbe (Application Probe) facility which is introduced in the TXSereis for Multiplatforms V7.1, is a very useful tool to monitor and debug application's memory usage and helps in detecting memory leaks within the application.
The tool can be used to monitor your applications based on transaction names, program names or the programming language. Using this facility, you can monitor the memory usage in process heap (for tracking memory blocks allocated through standard functions such as malloc/calloc) and TaskPrivate pool (for tracking... [More]
TXSeries for Multiplatforms v8.1 Open Beta has introduced CKTI (Task Initiation) that spawns a task in TXSeries upon receiving a WebSphere MQ trigger. This improves upon existing conventional methods in that it brings enhanced integration with better control and management for handling trigger conditions.
The way it works is, CKTI starts a CICS transaction when a WebSphere MQ trigger message is read. When a message is put onto an application message queue, a trigger is generated by WebSphere MQ upon meeting trigger... [More]
CICS region uses a default file manager SFS (Structured File Server) to store system and user files and queues. An SFS server is a recoverable server that manages access to data that is stored in record-oriented files. It provides transactional integrity and flexible storage management. SFS server uses two logical volumes.
SFS Data Volume - To write/store recoverable data
SFS Log Volume... [More]
IBM COBOL for AIX provides integrated CICS translator option for compiling the CICS COBOL Programs (-qcics). If the programs are developed using the IBM Rational Developer for Power Systems (RDp), using the integrated translator option for the COBOL compiler, the break points can be added to the EXEC CICS statements directly.
If you use TXSeries supplied cicstcl tool to compile the IBM COBOL program, first it converts .ccp files to .cbl files (translating or pre-processing CICS statements) and then it compiles .cbl files with cob2_r... [More]
Have you ever faced a situation where you are left with a hung CICS region and not able to connect to it to see what's going on?. This situation arises as all the CICSAS application server processes are busy running user transaction and there is no freely available application server process to run CICS supplied transactions such as CEMT, CSTD, etc,... We require a free CICSAS application server process to connect to the CICS region as well as that would run CCIN or CHAT CICS supplied transactions.
Similarly for administration... [More]
In TXSeries environment, a transaction runs in a cicsas process. The number of ungrouped transactions (Transactions where TClass is None) that can be run in parallel in a TXSeries region is controlled by the MaxServer attribute in Region Definition(RD) Stanza. The number of application servers available for taking new transaction work at any point in time is controlled by the MinServer attribute in RD Stanza.
CST3 transaction can be used to monitor and... [More]
One of the key feature of TXSeries for Multiplatforms V8.1 Open Beta is its ability to store XA passwords in secure format in the XAD stanza.
XA complaint resource managers are configured with TXSeries where resource manager specific details such as resource name, userid, password, etc,. are stored in the configuration file known as XAD stanza. XA password is part of 'XAOpen' attribute defined in the XAD stanza that contains the credentials for accessing a resource manager. In the previous versions of TXSeries the XA password... [More]
You can easily collect the TXSeries MustGather documents for hang condition of a region and U-abends through cicsservice tool.
The following command can be run when the region is non-responsive state:
/usr/lpp/cics/utils/cicsservice/cicsservice -r niktest -D /tmp -o HANG
The command will collect all the documents required to be collected for a region in hang state for further investigation. Stop and restart the region after the command completes.
TXSeries allow users to classify the transaction and control the number of simultaneous or parallel execution of transactions belonging to a group. For example, in a CICS region shared between HR and finance team in an organization, the applications of both the teams can be classified into different groups and the number of maximum parallel executions of the transactions of different groups can be controlled.
As of TXSeries 7.1, the grouping of transactions can be achieved by using TCLASS. The number of TClass that can be... [More]
This blog covers the basics of shared memory segments used by TXSeries on AIX and increasing the shared memory available to applications using LDR_CTRL=MAXDATA settings.
TXSeries is a 32-bit product and works based on 32 bit virtual memory model of AIX. The total virtual address space of a CICS application server process (cicsas) is restricted to 4GB. In 32-bit AIX memory model, the address space is divided into 16 segments with each occupying 256 MB memory (256MB *16=4GB). The addressable memory segments are from 0... [More]
Servers configured with multiple IP addresses is a very common setup in many production and test systems. The blog covers the method improve the performance of the region by restricting the RPC addresses getting registered .
TXSeries region , SFS and ppc gateway register its RPC interface with sarpcd process whenever it comes up. By default, sarpcd registers on all the available IP addresses configured in the machine and also on all protocols (udp, tcp and cipc). When the number of cicsas configured on the machine... [More]
There are a lot of useful and productive features in TXSeries v8.1 Open Beta.
One of the key capability is the integration with the Tivoli monitoring infrastructure. The TXSeries monitoring
agent allows you to take control of your entire TXSeries deployment from a single Tivoli Enterprise Portal.
You can use the following three basic views to get started
Log Views: Lets you view and sort the current console log file
Status Views: Gives you status of all the TXSeries servers including the sarpc daemon
Detailed views:... [More]