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.
Do More with your TXSeries - Webinar Series: TXSeries for Multiplatforms, is IBM's premiere online transaction processing environment for business critical mixed language applications. It is widely used for integrating data and applications between distributed solutions and enterprise systems. It is also used for the deployment of high-performance, distributed CICS applications written in COBOL, C / C++, and PL/I. This integrates well into mixed language, multi platform service oriented architecture (SOA) solution. With its support for... [More]
As we grow older each year, we get all the more matured, gain more experience and get closer to the friends. So is for TXSeries,
On 17th Feb 2015, TXSeries grew an version older, its now TXSeries V8.2 - With years TXSeries has improved in performance, has imbibed all the great values from its previous versions and ofcourse, works just so well with its friends (CICS TS, DB2, WebSphere MQ to name a few)...
Here the TXSeries team proudly presents the next version of TXSeries V8.2 with... [More]
This blog provides quick links to get started with TXSeries 8.1 .
TXSeries 8.1 GA Announcement letter
TXSeries 8.1 infocenter/knowledgecenter
If the above page is not accessible, try accessing through TXSeries knowledge center page:
The wait is over, TXSeries v8.1 is available for download. One of the key features of 8.1 is the ability to monitor TXSeries using IBM Tivoli monitoring infrastructure. You must be wondering, why do I need Tivoli to monitor TXSeries when the existing monitoring capabilities are working for me. Let me give you a short introduction to the IBM Tivoli Monitoring. Tivoli Monitoring is the premium, enterprise class monitoring solution from IBM. Its easy to use highly customizable portal provides all the insight into your IT infrastructure in one... [More]
PPCGWY process will give following bind errors if RPC fails to get a port to use from windows 2008 onwards.
3483 224 13/11/03-12:28:37.787442 6c1c0ca7 W connect: errno:10060
3486 224 13/11/03-12:28:43.394505 6c1c0ca7 W connect: errno:10060
From Windows 2008 onwards, Microsoft windows has increased the dynamic client port range for outgoing connections in Windows Server 2008. The new default start port is 49152, and the default end port is 65535. This is a change from the configuration of earlier versions of Windows... [More]
What is a switchload file?
The switch load file is a shared library (a DLL on Windows systems) that is loaded in the cics application server . Its purpose is to simplify the loading of the database's client shared library, and to return the pointers to the XA functions to Transaction Manager (region). It is required to define switch load file when the region is configured to use an RDBMS database (not SFS) as a resource or file manager.
What is 2-phase commit protocol?
In simple words, 2-phase commit protocol is a... [More]
On the machine where Websphere MQ server is installed , perform the following steps:
Create the WMQ queue manager
Start the queue manager
Define the channel using MQSC command
DEFINE CHANNEL(CHAN_NAME) CHLTYPE(SVRCONN) TRPTYPE(TCP) +
DESCR('Server-connection to Client_1')
You can also use default server-connection channel definition SYSTEM.DEF.SVRCONN
Start the... [More]
As SSL/TLS are developed to provide a secured communication over the internet. TXSeries7.1 onwards supports SSL/TLS over IPIC communication with the help of IBM GSKit. The blog gives an example on how to configure SSL/TLS Communication between two TXSeries regions with a self-signed certificates.
Step 1 : Configure the two regions for IPIC Communication. Let the region name be REGION1 and REGION2.
For more information visit the link ... [More]
Here are few Linux system parameters that you can tune before running TXSeries to have better performance and to avoid any frequently seen issues.
You may see a problem when you start TXSeries region with systems default stack size for threads. Default stack size may vary from system to system like, 8MB or 16MB or even more.
When region is configured with many CICS Application Server(CICSAS) processes, you may see error in the console file as follows:
ERZ041001E/0008 12/11/14... [More]
ATNI abend can happen when the connection from the remote region or client(CUC, CTG, cicsteld) gets terminated and when the transaction on the region is active.
The termination can be due to that the client getting stopped or even due to network issue. ATNI abends are after-effects of client terminations.
You can also see from the CSMT.out file that the message indicates "A client aborted",
ERZ016050W/0234 12/11/14 05:00:01.371935253 REGTEST 22169/0001 : Logical unit of... [More]
TXSeries supports various high availability solutions for uninterupted productivity. The detailed configuration steps are explained in the white paper "Preparing TXSeries systems for high availability on AIX" .
Click this link for more details. http://www-01.ibm.com/software/htp/cics/txseries/library/
The search ends here, if you were looking for extending COBOL applications to Mobile devices, Here are 2 easy solutions to this
Learn in 90secs on how to do
Solution 1 : Using IBM MobileFirst Platform ( former IBM Worklight )
Solution 2 : Using CICS Transaction Gateway (CICS TG).
Are you interested in knowing more ?? Contact us at firstname.lastname@example.org
A147 abends are very generic and can come with Microfocus cobol applications on TXSeries for various reasons.
One of the most common reason on AIX is due to non availability of free segments especially if it is used along with WMQ/DB2. See my blog Managing shared memory in TXSeries on AIX Part 1 for details about free segments in TXSeries.
To resolve it, check set LDR_ CTRL =MAX DATA =0x2 0000 000 on region's environment file and restart the... [More]
While using cicsteld server, you need to check the LANG of the inted process. You can run ps eww <PID of inetd> to know the LANG settings of inetd. If the LANG is incompatible with CICS, your transactions can fail with APCT abends.
To resolve the issue, you can try either of the following methods:
-> Restart the inetd service to reflect the new LANG setting in /etc/environment (Ex: LANG=en_US) .
-> Create the telnet_server with -l option to specify the locale as en_US as follows:
# cicscp -v... [More]