CA Gen creates a special file to hold the transaction codes associated with executable load modules. This file is named AEENV and a copy of it resides in the models' source directory where you built your application. All load modules built as part of a block mode application or a cooperative server write their transaction codes to this file.
Each transaction code should be unique within each AEENV file. Duplicate transaction codes can cause problems during load module execution.
You can edit the AEENV file with any editor that saves files in ASCII format. The edited file cannot contain any control codes or header information unique to the editor.
Add transaction codes to the AEENV file in the following format:
tran_type tran_code lm_name user_id password database
where:
Transaction Type:
TRAN – used to invoke a load module with block mode applications.
FLOW – used to flow between load modules, with cooperative servers.
The transaction code used as the key to the load module to invoke.
The name of the executable load module file associated with the transaction code. Omit file suffix.
A user ID to access the database.
A password to access the database.
The name of the database bound to the load module.
Separate parameters with spaces and omit tabs. You must include the following parameters: tran_type, tran_code and lm_name.
You only need to specify a database when the executable load module is bound to a database. You only need a user ID and password when database access requires a user ID and password.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|