PCT

Use this page to create a new PCT.

If you displayed this page by clicking COPY on a previous page, the values on the previous page are used as the basis for the new PCT.

To display the currently installed definition of this resource, click ACTIVE.

To install and make this resource active, click INSTALL.

To delete this PCT, click DELETE.

To create a new PCT using the values set on this page as the basis for the new PCT, click COPY.

To create and view dump information for this PCT, click DUMP.

Name
The name for this PCT.
Description
A description of the transaction program (can be up to 60 characters).
Program Name
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. This can be up to eight characters (A-Z, 0-9, #, @, or $). The name is translated to upper case.
Remote SysID
The system ID of the remote system on which the file resides, specify the 4-character, remote system identifier (as defined in the TCT). If the program resides in the local region, leave this field blank. The name specified must be the same as that given in Name in the SysC or Sys62 definition. You must uncheck Use Catalog before you can specify a system ID for the remote system, this is because the catalog is used only for storing information about files held locally.
Remote PCT
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.
Priority
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:
  • The terminal priority
  • The transaction priority (this field)
  • The operator priority.
This sum must not be greater than 255.
Work Area
The size of the transaction program's Transaction Working Area (TWA) in bytes, in the range 0 through 32767.
Status
A status for the transaction program:
  • Enabled - The transaction program is enabled.
  • Disabled - The transaction program is disabled.
In Doubt
What is to happen 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. To use this option, files used by the transaction program must have Backward recovery checked on the FCT page.
  • 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.
3270 Screen
The screen size to be used by the transaction program. Select:
  • Default To use the default screen size (as defined in the Typeterm entry).
  • Alternate To use the alternate screen size (as defined in the Typeterm entry).
Tracing
Choose the type of tracing to be performed for the transaction program:
  • No - No tracing is performed.
  • Standard - Tracing is performed.
  • Special - Special tracing is performed.
Dynamic Route
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.
Translate to Upper Case
Check this if you want the transaction program to translate input into upper case.
Dump on ABEND
Check this to create a program dump if the transaction program abends.
Inbound
Check this to indicate that this transaction can be initiated by an inbound user action.
RLS Security
RLS (Resource Level Security), if checked Enterprise Server will check the user's authorization for all resources that the transaction accesses, for example, file access, TDQ, TSQ, LINK, DPL, START and so on.
CMD Security
CMD (Command), check this to check the authorization on all the EXEC CICS command operations, for example, EXEC CICS SET/ENABLE/DISABLE.
Cat3 Security
Cat3 (IBM Category 3) Transactions do not have security checking at all, so the transactions are allowed for everyone with no authorization calls.
Input Timeout
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.
Runaway Timeout
The maximum continuous period of time in seconds that the region will allow this transaction to run without making a CICS, EZASOKET or WebSphere MQ API call. When this time is exceeded, the transaction is abended. A value of 0 indicates that there is no timeout.
System Default
Check this to use the system wide value for Runaway Timeout rather than the PCT entry.
Deadlock Timeout
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.
System Default
Check this to use the system wide value for Deadlock Timeout rather than the PCT entry.
Transaction Threshold
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.
System Default
Check to use the system wide value for the transaction time threshold rather than the PCT entry.
Resource Keys
  • All - Check this to activate all the resource keys.
  • 1 - 24 - Check any of the boxes 1 through 24 to activate that resource key.
Security Keys
  • All - Check this to activate all the security keys.
  • 1 - 64 - Check any of the boxes 1 through 64 to activate that security key.
Parent topic: CICS - Groups