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.
There has been a recent update to the version of IBM Communication Server (SNA) supported with TXSeries v8.1 on Linux. TXSeries v8.1 now supports IBM Communication Server 220.127.116.11 on Linux. No additional fix required on TXSeries side. Here's a quick look at the table from system requirements page,
You can find the detailed system requirements on Linux here, http://www-01.ibm.com/support/docview.wss?uid=swg21656675
One common question that many TXSeries users ask is if they can transfer or migrate their region configurations across platforms. For example, users may create their applications on a Windows installation of TXSeries, for development and unit testing, and later on move to a different platform for deployment, say AIX.
With the release of the latest version, TXSeries V8.1, Linux as been added as a new supported platform. So, an existing TXSeries user looking to tryout TXSeries on Linux would want to recreate their region based on their... [More]
Configuring WLM for TXSeries may seem like a daunting task, but is actually quite simple. Once you have decided on your system design, WLM configuration can be done in a few steps. Perform the necessary region configuration and voila! - we are set to go.
To get started, first check out this blog entry. What's new with TXSeries v8.1 - WLM Samples and Verification .
Next, watch the video below, which shows you how to manually configure and run a WLM environment similar to... [More]
TXSeries v8.1 introduces a new a WLM Sample and Verification suite. The suite will automatically setup all the configuration required to setup a sample WLM environment with 1 COR (Client Owning Region) and 3 AOR (Application Owning Region) regions. It also configures sample application programs and provides a Client application to run it. All this in under a minute!
The following video will walk you through how to access and run the new WLM Sample configuration in TXSeries v8.1.
This blog provides quick links to get started with TXSeries 8.1 .
TXSeries 8.1 GA Announcement letter
TXSeries 8.1 infocenter
TXSeries 8.1 system requirements on AIX
TXSeries 8.1 system requirements on x-Linux
Do you want to avoid repeating the same cicsadd or cicsupdate commands on every region that you create? Well, if your architecture has many regions which are quite similar, you don’t really have to repeat these configurations manually for every region you create. You can clone them.
This blog will cover steps required to clone a TXSeries Region.
One way to clone you region is by using the cicsexport and cicsimport commands.
Let us suppose that you have a region ‘region1’ where you have... [More]
The Open Beta for TXSeries v8.1 has been refreshed with a new build. See: https://www.ibm.com/developerworks/community/blogs/DoMoreWithTXSeries/entry/refreshed_txseries_for_multiplatforms_v8_1_open_beta?lang=en .
You may be interested in exploring the latest features available in the beta refresh. If you are currently using TXSeries v7.1 or earlier version of TXSeries v8.1 Open Beta, then you would need migrate your configuration to latest version of TXSeries v8.1 open beta before starting to use the same.
If you are already using TXSeries, and would like to upgrade to the latest version of the product, you will be required to migrate your TXSeries configration. In this blog, we’ll concentrate on the aspects around migrating existing Regions, SFS and PPC gateways to the latest version. More specifically, this blog would cover migration to a new version on the same system .
If you are migrating to a new version on the same system, there is no need to export and then import your region configurations (i.e the use of... [More]
What is the difference between timeout in TD.stanza and XPRecvTimeout?
Both TD timeouts and XPRecvtimeout are communication related time outs applicable in an Inter System communication. The table summarizes the differences between the two.
The timeout is set in TD.stanza for a particular transaction
"XPRecvTimeout" is global to the region and applies to all the transactions in a region. It is set in RD.stanza
This is an update to the blog that I wrote earlier on ways to monitor a TXSeries system... With the monitoring features introduced in TXSeries for Multiplatforms V8.1 Open Beta I have highlighted the new updates in this blog (marked in BLUE color)...
The CICS TS for the z environment has a rich set of monitoring tools available from both IBM and the third-party vendors. Though TXSeries (CICS) is not blessed with similar offerings, I have striked this sentence as we now provide real-time monitoring support for TXSeries using Tivoli... [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]
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.
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]