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.
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... [More]
Below are the quick reference of the environment variables that you need to be aware of when using the DB2 VSAM Transparency Layer:
Specifies whether CICS can perform "dirty reads" from a DB2 database -- that is, whether images of database rows that are locked for update can be read by CICS. To enable dirty reads, set the value of this environment variable to 1. This tunable is disabled by default.
This variable holds a numreic value that represents... [More]
Below are some of the behavior differences that you should be aware when moving files across SFS to DB2 using the DB2 VSAM Transparency support in TXSeries.
1) When CICS applications browsing the files using STARTBR FILE / DATASET APIs, while performing READNEXT FILE / DATASET API operation CICS will return ENDFILE condition even though the FILE / DATASET contains records. This condition occurs when TXSeries region is configured with DB2 V9.5 or above as File Manager and the database created with default locale. The locale configured with... [More]
If your applications contains "EXEC CICS STARTBR" API and found application taking more time for execution, you can try rebinding the TXSeries supplied DB2 packages with "REOPT ALWAYS" as follows.
1) Connect to DB2 database
2) Rebind the CICS packages:
Go to /usr/lpp/cics/etc directory
Run the following command to rebind the CICS package with option REOPT ALWAYS/
# db2 bind @cics101.bndlst REOPT ALWAYS
# db2 bind @cics102.bndlst REOPT ALWAYS... [More]
TXSeries for Multiplatforms offers a sandbox on SoftLayer that allows you to quickly and easily evaluate your applications on TXSeries.
Here are a couple of videos that take you through the steps of provisioning the evaluation edition of TXSeries for Multiplatforms V8.1 onto Linux instances deployed on SoftLayer.
The first demo video gives instructions to provision a new Linux server on SoftLayer, with TXSeries 8.1 installed and configured on it.
We know TXSeries V8.1 trial on Linux can be deployed on IBM SoftLayer public cloud. If you have not yet tried, you can start with Evaluate TXSeries V8.1 on SoftLayer
Now it is time to try IBM DB2 with TXSeries V8.1 on SoftLayer. Here are details for you to know how this can be done.
IBM DB2 provides a no charge community edition of DB2 server called “DB2 Express C” and 90 days trial edition of DB2 Server. You can get more information on DB2 at... [More]
Here is a quick reference guide for you to configure TXSeries with DB2 in XA environment. To aid this, TXSeries provides, “Cheese sample”, This sample consists of a table which contains different types of cheeses and the number of ordered quantity for each cheese. You can use the transaction “UXA1” to query the number of cheeses of particular type that have been ordered and update the same number if required. Follow the below steps to do the same.
1. CREATE THE CHEESE TABLE
The SQL command file... [More]
How do I resolve when cicswlmstat shows Host-Unreachable message ?
If cicswlmstat shows Host-Unreachable message, you can look for the following:
Check whether the machine is reachable or not, by pinging the machine IP address.
# ping <Remote Machine IP Address>
Sometimes even though remote machine ( where AORs and COR(s) are running ) is up and running and CTG Client is connected to region, cicswlmstat shows Host-Unreachable message. Check if the udp4+echo... [More]
Usually TranMonitorInterval is used to set the timeout for a transaction. TranMonitorInterval in combinaiton with TranMonitorAction specifies, what action should be taken if particular transaction goes out of time.
Force Purge the transaction
If TranMoniotrAction for a transaction is set to purge and the transaction take more time than the value specified by TranMonitorInterval, then the transaction will be force purged.
Step 1: Create a region
So, you’ve now read that TXSeries for Multiplatforms V8.1 Trial is now available on cloud, in the previous blog . Here are some more details for you to understand what this means.
TXSeries V8.1 trial on Linux can now be deployed using the IBM SoftLayer public cloud.
SoftLayer, provides cloud infrastructure as a service from a host of data centers across the globe. To simply put, SoftLayer is a hosting provider. It gives you an quick and easy way to deploy operating system instances –... [More]
TXSeries now offers a 90 day free trial offering for TXSeries for Multiplatforms V8.1 which is available on Linux on x86 and AIX platforms.
In addition,TXSeries for Multiplatforms now offers a trial sandbox on cloud using IBM SoftLayer, that allows a fast and easy evaluation of your applications with TXSeries. Trial Sandbox on SoftLayer eliminates the need for you to procure a hardware instance and then setup infrastructure on your own, which more often is a multiple week effort.
Download the Trial >... [More]
As you know, TXSeries for Multiplatforms supports external authentication mechanism, by supporting external data stores like Active Directory, RACF server, etc. through an LDAP client. In fact, for most of the business solutions, external authentication is the preferred mechanism.
Here is an IBM developerWorks article on how to customize TXSeries External authentication to work with Active Directory: Customizing TXSeries CICS external authentication, Part 1: Windows Active Directory
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... [More]
Mobility is the most demanded IT capability today. With steeply increasing business users depending on Mobile devices to finish a task on the fly, rather than have to login to a computer .
Now, Enterprises in the sectors like Banking, Transportation, Telecom etc have been in the business for long time. Their business applications/logic was written in COBOL/C/C++ or PL/I, and as technology grew they will have to enable their customers access these applications to make a transaction(in case of a bank), Book tickets(in case of a... [More]
I was articulating for one of our customers on how they could invoke an external application or a command from an on-line CICS transaction running in TXSeries and also to invoke a CICS transaction from an external application (The external application are also referred to as batch application).
The immediate options that comes to mind is the usage of CICS Transaction Gateway that provides an ECI interface for invoking CICS transaction from an external application. However it would not help for invoking an external... [More]