Version 8.2.1	SEARCH   INDEX   CONTENTS   |   PDF PAGE   PDF BOOKS   |   HOME   UP   PREV   NEXT

This section describes how to copy ET data into the ATM transaction manager's recovery file.

• ET Data Location and ET Data Migration Requirements

• ET Data Migration Checklist

• Running the ET Data Copy Program

• Error Return Codes

ET Data Location and ET Data Migration Requirements

When Adabas Transaction Manager is in use, the location of ET data is determined by the runtime parameter TMETDATA:

• The setting TMETDATA=ATM indicates that ET data is always stored in and read from the ATM transaction manager's recovery file without regard to the Database ID indicated by the Adabas command.

• The setting TMETDATA=TARGETS indicates that ET data is stored during the commit process in all changed databases that are running with DTP=RM. ET data is always read from the database specified in the Adabas command.

If the setting TMETDATA=TARGETS is used, no special action is required to set up ET data in the correct locations before using ATM.

If the setting TMETDATA=ATM is used, it may be necessary to transfer existing ET data from application databases into the ATM transaction manager's recovery file.

If an application that uses ET data is capable of starting from an initial state where no ET data is stored, it can be run with ATM without migrating ET data into the transaction manager's recovery file.

If, on the other hand, the current ET data contents of the application are required whenever the application is executed, the application’s current ET data must be migrated into the ATM transaction manager's recovery file. A utility program is provided in the ATM load library to perform the necessary migration. Usage of this utility program is described in the following sections.

ET Data Migration Checklist

The following checklist outlines the required steps in the ET data migration procedure:

1. Identify the ETIDs whose ET data needs to be migrated.

2. Identify the database(s) in which the ET data is currently stored.

3. For each database identified in step 2, use Adabas Online System to delete ET data for any ETIDs that were not identified in step 1.

4. For each database identified in step 2, run job ATMETDAT providing suitable parameter input. See the following section for further information on running this job.

Running the ET Data Copy Program

The sample job member ATMETDAT, which is located in the ATM JOBS install library, can be used to run the copy ET data program, ATMPETD. Before executing this job, modify the ADARUN parameters, dataset names, and file allocation statements according to the requirements of your installation. The ADARUN SVC parameter should specify the SVC number that is used by the target and source databases that the utility will process.

Before you can run ATMETDAT, you must link it with ADAUSER from your current Adabas load library.

This utility must execute in a batch job which does not use ATM services. That is, it must execute using an Adabas link module which has no Adabas System Coordinator stub bound to it, or else it must execute under client controls which specify ATM OFF.

ATMETDAT writes a report of the processing it has carried out. The report is written to TMETOUT, and consists of fixed-length, 121-byte records.

Execution of ATMETDAT is governed by parameters read from the TMETIN input. The input file must consist of 80-byte records. Each input record must either contain a comment, indicated by an asterisk (*) in the first position, or else it must contain a valid parameter statement, beginning in the first position. Valid parameter statements have the following form:

parameter=value

Valid parameters and their permitted values are described below.

FROM: ET data source

Possible values:

TO: ET data target

Possible values:

REPL: Replacement option

Possible values:

LIST: Report requirements

Possible values:

Example Parameter Input

ET data will be read from the checkpoint file of database 135 and stored in the ET data file of Transaction Manager 20535. If any ETID has ET data in both database 135 and TM 20535, the ET data from database 135 will replace the existing data in the ET data file of TM 20535. Details of all processed ET data will appear in the report.

FROM=DB135
TO=TM20535  
REPL=Y
LIST=Y      

Error Return Codes

On successful completion, ATMPETD will terminate with a return code of zero. Any other return code indicates an error, and in some cases will be accompanied by an ATM159 error message, which will give details of the cause of failure.

Possible return codes are as follows.

www.softwareag.com

Copyright © 2011 Software AG, Darmstadt, Germany.

SEARCH   INDEX   CONTENTS   |   PDF PAGE   PDF BOOKS   |   HOME   UP   PREV   NEXT