Use this page to define a new transaction or view an existing one.
Click
Apply to save your changes.
Click
Install to install and make the resource active.
Click
Delete to delete this transaction.
Click
Copy to create a new transaction. The values on the current page will be used as the basis for the values in the new transaction.
Click
Dump to create and display a dump of the transaction information.
- Name
- Specify the name of the transaction.
- Description
- Specify a description for the transaction.
- PSB Name
- Specify the name of the PSB associated with this transaction.
- Class
- Specify the message class for this transaction.
- Program Name
- Specify the name of the application program associated with this transaction.
- Schedule
- Choose whether the application program can be scheduled into more than one message processing region simultaneously:
- Parallel
- The application program can be scheduled into more than one message processing region simultaneously.
- Serial
- The application program cannot be scheduled into more than one message processing region simultaneously. This option is not
supported.
- SPA Size
- Specify the size of the conversational ScratchPad Area (SPA). The size specified must be between 16 bytes and 32767 bytes.
- SPA Truncate
- Check this field to set the truncate data option to on.
- Wait For Input
- Check this to specify that this is a wait-for-input (WFI) transaction.
- Transaction Threshold
- Specify the maximum length of time in seconds that a transaction can run before a message is logged to the console to indicate
that it has exceeded its threshold. This must be in the range 0 through 65535. A value of 0 indicates that there is no threshold.
- Use System Value
- Check this to use the system wide value for the transaction time threshold set on the IMS Control page.
- Priority
- Specify the priority assigned to this transaction (and any messages it creates) when the number of input transactions enqueued
and waiting to be processed is less than the value specified in P-Limit Count. The priority must be in the range 0 through
14. The default value is 1.
- Priority Limit
- Specify the priority assigned to this transaction (and any messages it creates) when the number of input transactions enqueued
and waiting to be processed is greater than or equal to the value specified in P-Limit Count. The priority must be in the
range 0 through 14. The default value is 1.
- Priority Limit Count
- Specify the number of input transactions enqueued and waiting to be processed that determines whether the transaction's priority
is the value specified in Priority or Priority Limit. The count must be in the range 1 through 65535. The default is 65535.
- Process Limit
- Specify how many of this transaction's messages a program can process in a single scheduling. This must be in the range 1
through 9999. The default is 9999. Specifying 9999 indicates that no limit is to be imposed.
- Process Limit Time
- Specify how many seconds a program can spend processing this transaction (or a message from it) in a single scheduling. The
number must be in the range 1 through 65535. The default is 65535. Specifying 65535 indicates that no limit is to be imposed.
- Max Segments
- Specify the maximum number of application program output segments that are allowed into the message queues for each Get Unique
(GU) call from the application program. The number must be in the range 0 through 65535. The default is 0. Specifying 0 indicates
that the number of segments is not checked at execution time.
- Deadlock Timeout
- Specify the maximum time in seconds that the message processing region will permit this transaction to wait for a resource
that has been locked by another process. A value of 0 indicates that there is no timeout.
- Enabled
- Check this field to enable the transaction program.
- To Uppercase
- Check this field to translate the input data to uppercase.
- Fast Path
- Specify the size of the EMH buffer required to run the transaction using Fast Path processing. The minimum value is 12 and
the maximum is 30720. Specifying 0 indicates that the transaction cannot be run using Fast Path processing.
- In Doubt
- Choose what happens if a transaction program using intersystem communication abends at a critical moment during syncpoint
or abend processing:
- Backout
- The effects of the transaction are backed out using ROLLBACK.
- Commit
- Any changes are committed.
- Wait
- Critical resources are locked until the session has recovered, and are then backed out or committed in step with the remote
system.
- Response Mode
- Check this to specify that, for terminals with a default of OPTIONS=TRANRESP, no additional messages are to be allowed after
this transaction is entered until this transaction sends a response message back to the terminal. Leave this option unchecked
to specify that input should not stop after this transaction is entered.
- Tracing
- Choose the type of tracing to be performed for the transaction:
- Standard
- Tracing is performed.
- Special
- Special tracing is performed.
- No
- No tracing is performed.
- Codeset
- Choose the codeset to use for this transaction:
- Default
- The transaction inherits the system bias codeset.
- ASCII
- The transaction uses ASCII.
- EBCDIC
- The transaction uses EBCDIC.
- Dump On Abend
- Check this to request a program dump if the transaction program abends.
- MFS Attributes
- Choose how attributes are defined in the transaction program:
- Default
- The program defines attributes as defined by the system bias value (which is binary, by default).
- Binary
- The program defines attributes as binary values.
- Character
- The program defines attributes as characters.
This setting only has an effect if the program is compiled using the ASCII character set; it is ignored if the program is
compiled using EBCDIC.
- MFS Null
- Specify the character to use as the NULL. You can enter the value in character form or hexadecimal form (X'nn'). The default
value is X'1A'.This setting only has an effect if the program is compiled using the ASCII character set; it is ignored if
the program is compiled using EBCDIC.
- Password Reverification Required
- If checked, every time the transaction is invoked, the password of the user that invoked it is reverified and access to it
is denied if the verification fails.