Previous Topic: Defining Source NamesNext Topic: Batch Packaging


Assigning Transaction Codes

For certain operating system and teleprocessing monitor combinations, other generated code needs to be named. You can add transaction codes to a load module and then assign them to the packaged procedure steps during packaging. If you do not, the Construction Client adds and assigns transaction codes for you during load module generation.

If you want the application user to have a meaningful transaction code with which to invoke certain procedure steps, assign your own clear screen transaction codes to them.

The Construction Client displays a window for entry of the transaction code and source member name information. The fields contained in the window depend on the environment and configuration options you specify. See the following table:

Environment and Configuration Options

Information Required by Panel

No display (all environments)

Source member name
Dialog flow transaction code

Display, z/OS with IMS MFS

Source member name
Screen member name
Clear transaction code
Dialog flow transaction code
MID, MOD, and FMT member names

Display (other environments)

Source member name
Screen member name
Clear screen transaction code
Dialog flow transaction code, if procedure is flowed to