Use this page to view and, if you have the required permissions, to edit the PCT pct_name.
The title bar gives the name (pct_name) of the PCT you are editing and the resource group (group_name) it belongs to.
Click Apply to save changes you make to the page then refresh the page. This button is displayed only if you have permission to edit the group in which the PCT resides.
Click this to display the CICS Group page group_name.
Shows the name for this PCT.
Specify a description of the transaction program (can be up to 60 characters).
For local programs only, specify the name of the application program to be run when this transaction is invoked. Leave this field blank if you enter a value in the remote system ID field.
Can be up to eight characters (A-Z, 0-9, #, @, or $). The name is translated to upper case.
Specify the size of the transaction program's Transaction Working Area (TWA) in bytes, in the range 0 through 32767.
Specify the system ID of the remote system. The name specified must be the same as that given in Name in the SysC or Sys62 definition.
Specify the transaction ID of the transaction program on the remote system. You must specify Remote SysID before you can specify a transaction ID.
Can be up to four alphanumeric characters, the first of which must be a letter. Do not use the letter C as the first character; transaction IDs beginning with C are reserved for use by MSS.
Choose a status for the transaction program:
Choose what is to happen if a transaction program using intersystem communication abends at a critical moment during syncpoint or abend processing:
Check this if you want the transaction program to translate input into upper case
Choose the type of tracing to be performed for the transaction program:
Check this to have the program status (local or remote) determined dynamically at user invocation time. If this is unchecked, the program status is made local or remote according to the value of System ID.
Use these check boxes to control the way in which resource authorization checks are performed. If they are not checked, the only check performed will be to confirm that the user has authority to run the transaction. If you check RLS (Resource Level Security), Enterprise Server will check the user's authorization for all resources that the transaction accesses (e.g. file access, TDQ, TSQ, LINK, DPL, START and so on). Checking CMD(for Command) will check the authorization on all the EXEC CICS command operations (e.g. EXEC CICS SET/ENABLE/DISABLE).
Note that IBM Category 3 Transactions do not have security checking at all, so the transactions are allowed for everyone with no authorization calls.
Specify the transaction priority of the transaction program in the range 0 through 255, where 255 is the highest priority.
The priority of a transaction is the sum of:
This sum must not be greater than 255.
Check this to create a program dump if the transaction program abends.
Specify the screen size to be used by the transaction program. Select:
Check this to indicate that this transaction can be initiated by an inbound user action.
Specify the maximum time in seconds allowed for operator response to an explicit CICS RECEIVE, WEB OPEN, WEB SEND, WEB RECEIVE, or WEB CONVERSE command before this transaction is abended. A value of 0 indicates that there is no timeout, and the system will wait indefinitely for a response.
Check Use System Value to use the system wide value for Input Timeout (as shown on the ESMAC Control screen) rather than the PCT entry.
Specify the maximum continuous period of time in seconds that the region will allow this transaction to run without making a CICS, EZASOKET or MQSeries API call. When this time is exceeded, the transaction is abended. A value of 0 indicates that there is no timeout.
Check Use System Value to use the system wide value for Runaway Timeout (as shown on the ESMAC Control screen) rather than the PCT entry.
Specify the maximum time in seconds that the 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.
Check Use System Value to use the system wide value for Deadlock Timeout (as shown on the ESMAC Control screen) rather than the PCT entry.
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. A value of 0 indicates that there is no threshold.
Check Use System Value to use the system wide value for the transaction time threshold (as shown on the ESMAC Control screen) rather than the PCT entry.
Choose a setting to apply to the resource keys:
Check any of the boxes 1 through 24 to activate that resource key.
Choose a setting to apply to the security keys:
Check any of the boxes 1 through 64 to activate that security key.
Click Display to display the currently installed definition of this resource.
Click Install to install (make active) this resource.
Click this to delete this PCT. You see this button only if you have editing permissions for the group to which the PCT belongs.
Click this to create a new PCT, using the values set on this page as the basis for the new PCT.
Click this to create and view dump information for this PCT.