Editing the environment file

Editing the environment file

Use the Administration Console to edit the environment file.
After editing the environment file, stop/re-start the CICS region (i.e Testreg1) using COLD start type to activate your changes.

1. Select the CICS Region (i.e Testreg1).
2. Click Environment.
3. Add a line (i.e PATH=C:\Program Files\IBM\SDP\bin).
4. Click the Save button when done.

Error Messages

cicsas.exe - Unable to Locate Component

When you see this error message, it indicates that TXSeries cannot find the COBOL runtime files.
Specifically, TXSeries cannot find the file iwzrlibm.dll.

File iwzrlibm.dll is in C:\Program Files\IBM\SDP\bin which is where Rational Developer for System Z is installed.

To make this file (iwzrlibm.dll) visible to TXSeries, you have add the line PATH=C:\Program Files\IBM\SDP\bin to the Environment file.

When you click OK, the error message (ERZ014016E) shown below is displayed.

ERZ014016E

Transaction 'transId', Abend 'abendCode', at 'termId'.

1. Explanation
   The transaction 'transId' running at the terminal where this message is displayed was abnormally terminated with code 'abendCode'. If the transaction is not associated with a terminal then '????' is substituted for 'termId'.
2. System action
   The transaction 'transId' is abnormally terminated.
3. User response
   'abendCode' is the abnormal termination code that caused the transaction to be terminated. If the code is not one used for abnormal terminations initiated by CICS then it is a user code generated by an EXEC CICS ABEND ABCODE ('abendCode'). Correct the problem and resubmit the transaction. If the transaction was abended A147 while it was being debugged via CEDF the debug terminal can remain locked; use CEMT commands to put the debug terminal out of service and reacquire it.
4. Destination
   console.msg and the terminal that invoked the transaction.

ERZ031003W

Invalid transaction identifier 'transId' - please resubmit

1. Explanation:
   The transaction 'transId' is not known on the remote system.
2. System action:
   CICS continues.
3. User response:
   Verify that the transaction name you have entered is correct, and that it is available on the system you are transaction routing to.
4. Destination:
   The user's screen.

Transaction Definition

Transaction Definition

Transaction Definitions (TD) define all the transactions that CICS® can process in a region. CICS requires this definition to verify incoming requests to start transactions, and to supply information about a transaction. Each entry in the TD contains control information that CICS uses to identify and run a transaction. You can define remote and local transactions in the TD.

Configuring a Transaction Definition using the TXSeries Administration Console

To create, modify, or delete a Transaction Definition using the TXSeries Administration Console, complete the following:

1. Expand Testreg1 and select Transaction
   
2. Select Transactions tab and click Add.
   
3. Fill in the following.
   - Transaction Name - TZON- Right click Transaction/Program list
   
4. Click the Select  Option  and click Add
5. The First program name is automatically filled-in (i.e TIMEZONE).
   Click Submit.
   
6. The Transaction Definition TZON is added.
   
   
7. Cold start the CICS region (Testreg1)
   Everytime you add resources to the CICS region, you MUST stop and stop the region.  Otherwise, the new resources will not become available.
   
   Stop the region and re-start the region using Cold Start Type.
   

Program Definition

Program Definitions

The Program Definitions (PD) identify the application programs, map sets, and tables that are required in a CICS® region, including those supplied by CICS. You can define remote and local programs in the PD

Configuring a Program Definition using the TXSeries Administration Console

To add, modify, or delete a Program Definition using the TXSeries Administration Console, do the following:

1. Expand Testreg1 and select Program
   
2. Select Programs tab and click Add.
   
3. Fill in the following and click Submit.
   - Program Name - TIMEZONE- Activate resource at cold start? Yes
   - Resource description - Program Definition
   - Etc...
   
4. Program definition is successful.
   
5. Cold start the CICS region (Testreg1)
   Everytime you add resources to the CICS region, you MUST stop and stop the region.  Otherwise, the new resources will not become available.
   
   Stop the region and re-start the region using Cold Start Type.
   

References

TXSeries 7.1 Overview

Installation environment

1. Windows XP 32 bit with Service pack 3
2. Lenovo Thinkpad W530 (Stand-alone, not part of a network)
3. Installer must have Administrator authorization

References

1. IBM Information Center
2. TXSeries 7.1 Infocenter
3. Topics on Version 7 of IBM Rational Developer for System z and IBM WebSphere Developer for System z
4. http://www-01.ibm.com/support/knowledgecenter/SSAL2T_8.2.0/com.ibm.cics.tx.doc/ic-homepage.html
5. TXSeries 8.2 Infocenter
6. System requirements for IBM TXSeries for Multiplatforms V8.2 on Microsoft Windows

Create CICS Region

Create CICS Region

Before creating a CICS Region, you should do the following:

1. Set up LWI Service for administrative tasks on Windows
2. Install Microsoft Loopback adapter

Creating a CICS Region

1. Click Start\All Programs\...\IBM TXSeries Administration tool
2. In the Login window, enter User Name (i.e Charles) and Password with Administrator privileges.  click Login. The user Name should belong to Administrators and cicsgroup.
   
   
   
3. In the TXSeries Administration Console, click Regions and click Create.
   
   
4. In the Region -> New Window, enter Name (i.e Testreg1), leave Group ID blank, and select Use SFS (File Management) and click Submit.
   
5. The CICS region and default SFS server are created.
   

Testing the setup

Make sure that you re-start the CICS region before testing the setup you did above.

1. From the Windows® Start menu, select All Programs > IBM > TXSeries for Multiplatforms V7.1 > Start Local Terminal. The CICSTERM - CICS server selection window opens.
2. Select the correct CICS server for your CICS region and click OK
   
3. When the CICS terminal starts, type: CEMT (all capitalized) and press Ctrl, which is the 3270 terminal Return key 
4. If the transaction runs properly, the CICS terminal screen will show something like the following: