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.
When ever a CICS API used in CICS application executed in the CICS region, the runtime returns the status of the execution as RESP codes to the application. Runtime returns primary and secondary RESP codes for any CICS API execution. These primary response code RESP and secondary response code RESP2 will help to debug and identify the root cause for the API failure. These RESP codes vary based on the CICS API. Its always a best practice to log/handle all the prossible RESP codes for every CICS API used in the application at applciation level.... [More]
WMQ is the message oriented middle ware, where the independent and non-concurrent applications can communicate with each other over the network. WMQ has Queue manager as its primary component for communication with outside network through client connection or binding. The Blog will elaborate the WMQ client and WMQ server configuration on different machine (LINUX,AIX or Windows) and setting up TXseries with WTC. After which, the TXSeries sample applications can communicate with WMQ Queue manger setup on different machine. Before... [More]
You can setup CTG JCA in local mode for enabling WebSphere application server to TXSeries communication. The following simple steps enable you to achieve the same. 1. Read the prerequisites for running the CTG JCA adaptor. See this link for details http://www-01.ibm.com/support/knowledgecenter/SSZHFX_9.1.0/configuring/topics/jca_ivp_prereq.html 2. Deploy and configure JCA Adaptor. You can use the IVT example described in CTG... [More]
Performance has always been a differentiating factor between middleware products. We understand this and TXSeries V8.2 has a major focus on performance. Some performance improvements have been done in core areas so that these improvements will benefit all types of workloads. I will explain the performance improvements that have been done in TXSeries V8.2 and the types of workloads that can benefit from those performance improvements in the detail below. Improvements for Micro Focus COBOL applications One of the major performance... [More]
Here is the details on how each TXSeries version compares , No doubt the latest and greatest version is TXSeries V8.2, which folds in it all the value adds from the earlier releases. Also V6.1 and V6.2 are already End of Support (EOS) and V7.1 would be EOS in Sept 2016.
In TXSeries 8.2, you can control the way stack is taken for a region processes on AIX. The stacks through showProcInfo are now taken using procstack instead of dbx by default . This has following advantages: The procstack process directly fetches the stack by OS using the information from /proc file system. So, it does not stop execution of the existing process. Taking stack through procstack is faster than dbx. So showProcInfo execution will be faster . procstack is installed by default on AIX whereas dbx needs to be... [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]
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]
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
Do you know that TXSeries 8.1 now provides a broader and high simplified way for timing out the transactions? With TXSeries 8.1, you can simply timeout a transaction if it runs beyond the time you specify. This is achieved through a TranMonitorInterval (in seconds) parameter introduced in Transaction definition(TD.stanza) of the region. After the timeout variable is set for a transaction, you can define the action that has to be taken on the timeout through TranMonitorAction in TD.stanza. Now what happens to the other timeout in... [More]
If you are in a phase of upgrading your network from IPv4 to IPv6, you must be wondering if are there any considerations for migrating TXSeries regions? One of the very important consideration is, do you still need connectivity to an IPv4 network? This is valid scenario if some of your clients (telnet, web, etc.) and other systems (such as CICS-TS) are still on IPv4 network. In this case, you need to identity the regions that need cross interaction and migrate them on to a dual stack box (a box that can talk to both IPv4 and IPv6 network). A... [More]
In today’s world when security is becoming a major concern for the enterprises, no wonder many enterprises have security policies which mandate the passwords to be greater than 8 characters. Till now this was restricted in TXSeries. But TXSeries V8.1 comes up with an exciting feature which supports greater than 8 characters for better compliance of security policies. TXSeries long password feature allows you to specify passwords up to 100 characters now. Its very easy to use and all the PASSWORD APIs support this feature. Longer... [More]
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 existing... [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 the setup done... [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.