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.
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 standard to maintain... [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 Improved Performance and... [More]
On the machine where Websphere MQ server is installed , perform the following steps: Create the WMQ queue manager crtmqm <Queue-manager> Start the queue manager strmqm <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 listener process runmqlsr -m <Queue-manager> -t tcp -p <Port-number> & On 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. Stack size 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 00:04:25.907155000 REGTEST ... [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 work for transaction... [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). Happy Watching Are you interested in knowing more ?? Contact us at email@example.com
A147 abends are very generic and can come with Microfocus cobol applications on TXSeries for various reasons. Reason 1: 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 region to check if the issue... [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) . or -> Create the telnet_server with -l option to specify the locale as en_US as follows: # cicscp -v create telnet_server TRY1 -l en_US... [More]
In TXSeries 7.1, it is a common practice to administer the TXSeries using sudo utility. From TXSeries 8.1, sudo is no longer required to administer TXSeries as any user can be configured as CICS administrator. See here for details on TXSeries 8.1 administration through non root users here . I have summarized some of the common issues that are seen when using sudo. 1. sudo does not seem to pass NLSPATH set on the settings. When you run any command, you may see ERZ057001E/0224: Cannot access message catalog cics.cat for... [More]
Are you moving your TXSeries to Linux? This FAQ summarizes the common initial issues that you may encounter due to various setting specific issues and quick ways to resolve them. 1. I installed TXSeries. However,could not run any command. Even cicscp fails ? This happens usually when TXSeries is installed in a 64-bit Linux. For TXSeries to work, ensure you have installed libstdc++-4.4.7-4.el6.i686.rpm ncurses-libs-5.7-3.20090208.el6.i686.rpm and glibc-devel-2.12-1.80.el6.i686.rpm They are not... [More]
Are you changing the hostname and IP of the machine where TXSeries is running? If yes, check out the following document " Impact of hostname changes on TXSeries "that provides steps to be followed for doing so.
If you feel your transaction is looping or not responding, what will be the possible cause and how I will collect the documents to analyze the problem? A first step would be to see if the transaction is looping due to the CICS application issue. To confirm this one could take a EI trace (EXEC INTERFACE) by performing the below commands: CECI TRACE ON CECI TRACE EI ON CEMT SET AUXTRACE ON The trace needs to be turned ON just for few seconds and can be turned OFF subsequently with the below commands: CECI TRACE OFF CECI TRACE EI OFF CEMT SET... [More]