Usually, a transaction definition must exist for any program you want to run. There are two ways of creating transaction definitions:
- Define them manually using Enterprise Server Monitor and Control (ESMAC)
- Use the transaction export and import utilities to extract IMS transactions from an IMS stage 1 file downloaded from the mainframe,
or from transaction file created from an
enterprise server instance, and automatically add the transactions to your
enterprise server instance. This is a two-step process.
- You export transaction definitions to a transaction file, which contains the transaction and printer definitions needed to
subsequently import into
Enterprise Server. It is a flat text file, so you can edit it to remove any definitions that are not needed for the application to run under
Enterprise Server. You can create a transaction file in one of two ways: Either export from a stage 1 file from the mainframe, or export the
transactions from a different
enterprise server instance.
- The import utility reads the transaction file created by the export utility, and adds the transaction definitions to the
IMSGEN2.DAT file in the current directory. If
IMSGEN2.DAT doesn't exist, it is created.