Steps to configure a TXSeries region with a particular language

IBM TXSeries for Multiplatforms supports multiple locales. Details of TXSeries supported locales can be found in the infocenter link http://publib.boulder.ibm.com/infocenter/txformp/v7r1/index.jsp?topic=/com.ibm.cics.tx.doc/concepts/c_tx_supported_locales.html

Here are the steps to configure a TXSeries region with a particular language(locale)

1) Create a new region
cicscp –v create region japreg

2) Setup region environment to work with the language.
Suppose we are configuring a region with Japanese language, we need to export the following environment variables in the regions environment file.
LANG=Ja-JP
NLSPATH=$CICSPATH/msg/Ja_JP

3) Copy the Japanese map files into regions map directory.
cp $CICSPATH/msg/Ja_JP /var/cics_regions/japreg/maps/prime

Copying the Japanese map files into regions prime folder will enable the region to pick the Japanese map files whenever we are running CICS Supplied transactions like CSTD,CEBR etc

4)Start the region
cicscp –v start region japreg StartType=cold

To check whether the region is properly configured with Japanese language, we can check for the following ‘ERZ010135I ‘ message in the console file of the region.

ERZ010135I/0362 09/15/10 23:21:12.642808969 test2 46208/0001 : CICS region 'japreg' is being started with locale categories Ja_JP Ja_JP Ja_JP Ja_JP Ja_JP Ja_JP’

Getting around starting woes

If you're doing a fresh installation of TXSeries on a machine i.e., the first time TXSeries is being installed on that machine you might hit a couple of issues.

NLSPATH or LANG isn't set

For example, when you try to start/create a region using the command :
"cicscp -v start region XYZ StartType=cold"

You are likely to see this message :
ERZ057001E/00xx: Cannot access message catalog cics.cat for message ERZ038038I
Please check if NLSPATH or LANG variable is set

This happens because the LANG environment is set to "C" by default, since there is multiple language support with TXSeries and the user has to set this variable.
Also, we need to verify if the path that contains the directory (catalog) that contains CICS messages. This is usually found in this path : /msg/ or /usr/lpp/cicssm/msg ( /opt/lpp/cicssm/msg for non AIX )

ERZ038255E : SFS_NO_SUCH_FILE_SYSTEM

Another issue that you may hit is when we try to start a region/sfs for the first time, you may see SFS_NO_SUCH_FILE_SYSTEM where even though the sfs server exists, it fails to start.
In this case, we need to stop the sfs server and do a cold start.

Stop : cicscp -v stop sfs_server sfsSeverName
Cold Start: cicscp -v start sfs_server sfsSeverName StartType=cold

(Warning : Cold starting an sfs server will erase user's files and TDQs. Never cold start an sfs server in the middle of a production environment )

More on ERZ038255E :
http://www-01.ibm.com/support/docview.wss?uid=swg21045527
http://www-01.ibm.com/support/docview.wss?uid=swg1IZ64176
http://www-01.ibm.com/support/docview.wss?uid=swg21045361

Introduction to WebServices in TXSeries

TXSeries for Multiplatforms announced the availability of in-bound web services support natively in November, 2009. The feature is provided as a support pac named CN01 (can be downloaded from here,http://www-01.ibm.com/support/docview.wss?rs=1083&uid=swg24024193). CN01 provides support for in-bound SOAP requests to be translated to program invocations in TXSeries. It allows to expose existing or new transactions as web services. There is no requirement for additional products now to be able to perform this function. Prior to this support pac, clients had to use WebSphere Application Server and CICS Transaction Gateway to be able to do this.
With this feature, TXSeries acts as a Web services provider. Transactions written in C or COBOL programming languages can be exposed as Web services. A new tool, CICS WebServices assistant is provided with this SupportPac, which helps to create Web services description language (WSDL) files from the language structure. Various commands are available for using the tool. In addition, RDz (Rational Developer for System z) provides web services assistant tool that can be used to create WSDL files. Refer to RDz documentation for more information on usage and details of applicable options for TXSeries.
Note : The WSDL files created using the Web services assistant tool are compatible with CICS TS (CICS Transaction Server for z/OS). However, TXSeries does not support all the features or options that CICS TS supports.
This SupportPac is supported for use with TXSeries 7.1 Fixpack 1. SupportPac does not work with prior versions of TXSeries.
Some important information about the support pac below,
Ability to expose CICS transactions as Web services. Does not support invocation of other Web services (outbound) from within TXSeries runtime.
Supported only on English language
Supports COMMAREA interface only. Does not support Containers & Channels.

Additional information and details available with following links ,
TXSeries web site -> http://www-01.ibm.com/software/htp/cics/txseries/
Infocenter -> http://publib.boulder.ibm.com/infocenter/txformp/v7r1/index.jsp
Podcast on Enhancing Business Flexibility using WebServices in TXSeries for Multiplatforms V7.1 can be found at the library -> http://www-01.ibm.com/software/htp/cics/txseries/library/
Developer works article : Using and configuring WebServices with TXSeries -> http://www.ibm.com/developerworks/webservices/library/ws-txseriesmulti/index.html

Introduction to TXSeries

Introduction to TXSeries
TXSeries for Multiplatforms is a distributed CICS transaction processor for mixed language applications.

IBM TXSeries for Multiplatforms V7.1 delivers simplified interoperability with IBM CICS Transaction Server, improved system resilience, problem determination, and application development tooling.
* Robust and extensible distributed transaction processing platform for deploying CICS applications written in C, C++, COBOL and PL/I.
* Widely used for integrating data and applications between distributed solutions and enterprise systems such as CICS and IMS.
* Reuse existing CICS applications and application programming skill sets in your organization consistent with corporate distributed platform policy.
* Develop, test and diagnose CICS applications using COBOL, PL/I, C, and C++ for deployment to CICS Transaction Server for z/OS.
* TXSeries for Multiplatforms V7.1 delivers significant enhancements in integration and connectivity through containers and channels and TCP/IP based interoperability between CICS regions, and further improvements to system resilience, application development and problem determination tooling, Web administration console, and installation.

Important documentation information can be found here, http://www-01.ibm.com/software/htp/cics/txseries/library/