Memorized Transactions screen

Memorized Transaction screen

How to Get There

Click the Memorized Transactions tab on the navigation pane on the left side of the Insite window.

What it Does

The Memorized Transactions screen enables you to maintain memorized transactions. To create a Memorized Transaction, you can select the Memorize button on the View Transaction screen.

Options

Selection, sorting, filtering, deleting, and navigation features on this screen are described in Using the Web Browser Interface.

Click a memorized transaction to open the Edit Memorized Transaction screen where you can view and edit a memorized transaction.

Field Descriptions

Server > Function

A Server in Exit Point Manager is a controlled entry point into your system. These entry points are determined and defined by IBM. Exit Point Manager has assigned easy-to-remember names to these controlled entry points.

A Function, or Server Function, in Exit Point Manager represents a class of operations that a given Server may perform. For example, the *SIGNON Server classifies its operations as those pertaining to changing passwords, generating authentication tokens, and retrieving sign-on information. Exit Point Manager has assigned easy-to-remember names to these Functions, such as CHGPWD, GENAUTTKN and RETRIEVE.

Status

This is the status of the Memorized Transaction, listed directly under the Server and Function. Possible values are:

*ACTIVE Exit Point Manager will attempt to match this transaction during rule enforcement. Memorized Transactions that are changed to *ACTIVE will have a matching User or Location rule changed to the corresponding action; *ALLOW to *MEMOS400, *REJECT to *MEMREJECT, or *SWITCH to *MEMSWITCH.

*INACTIVE Exit Point Manager will not attempt to match this transaction during rule enforcement. Memorized Transactions that are changed to *INACTIVE will have the matching User or Location rule changed (if there are no other Memorized Transactions for that rule) to the corresponding action; *MEMOS400 to *ALLOW, *MEMREJECT to *REJECT, or *MEMSWITCH to *SWITCH.

User /Location

User represents the identity of the person initiating a transaction as a user profile. The special value *PUBLIC, when used on a rule, means that the rule applies to any User lacking a specific rule. when used as a subset or selection parameter, *PUBLIC means to select all such rules for display or printing. This displays the User to which this Memorized Transaction applies. If blank, then this is for a specific Location. If the value is *PUBLIC, the transaction applies to all users.

Location represents the source of a transaction. Location can hold an IP Address, an IP Address Group or the name of an SNA Communications Device. The special value *ALL, when used on a rule, means that the rule applies to any rule means that the rule applies to any Location lacking a specific rule. when used as a subset or selection parameter, *ALL generally means to select all such rules for display or printing. This displays the Location to which this Memorized Transaction applies. If blank, then this is for a specific User. If the value is *ALL, the transaction applies to all Users.

ASP Group

This is the name of an ASP Group. It is used in rule evaluation to determine if an object referenced in a transaction is the one specified on the object entries for this list.

Possible values are:

  • *SYSBAS The Object List entries refer to those objects in *SYSBAS.
  • *ALL The Object List entries refer to those objects in any namespace.
Authority

Authority represents the action to be taken when a rule is found that matches the data present on a transaction. This field may hold one of these values:

*USER Current user authority is used.
*OS40O Exit Point Manager will use normal operating system authority for the user.
*REJECT Exit Point Manager will reject requests.
*SWITCHExit Point Manager will use the authority of the switch profile for the transaction. A switch profile entry is required.
*MEMUSR Memorized Transactions (MTR) are checked for authority first. If no MTR authority is encountered, Exit Point Manager will use the authority of the current user.
*MEMOS400 Memorized Transactions (MTR) are checked for authority first. If no MTR authority is encountered, Exit Point Manager will use normal operating system authority for the user.
*MEMREJECT Memorized Transactions (MTR) are checked for authority first. If no MTR authority is encountered, Exit Point Manager will reject requests for the specified user.
*MEMSWITCH Memorized Transactions (MTR) are checked for authority first. If no MTR authority is encountered, Exit Point Manager will use the authority of the switch profile for the specified user. A switch profile entry is required.
*MEMOBJ Memorized Transactions (MTR) are checked for authority first. If no MTR authority is encountered, Exit Point Manager will check any objects used in the transactions for authorities defined by Object Rules.
*SERVER Exit Point Manager will use the authority defined for the Server.
*SRVFCN Exit Point Manager will use the authority defined for the Server Function.

 

Related Topics