Where allowed to run:
|
Parameters Examples Error messages |
Use the Change CICS Program Control Table (CHGCICSPCT) command to change an entry in the PCT.
The Program Control Table (PCT) contains a definition for each transaction that may be run from this system. Each local transaction must be linked with a program which is defined in the Program Processing Table (PPT). Each remote transaction should have an associated remote system identifier which is defined in the Terminal Control Table (System Entry) (TCS).
Top |
Keyword | Description | Choices | Notes |
---|---|---|---|
LIB | Library | Communications name, *LIBL, *CURLIB | Required, Positional 1 |
GROUP | Group | Communications name | Required, Positional 2 |
TRANSID | Transaction | Character value | Required, Positional 3 |
SYSID | Remote CICS system | Communications name, *SAME, *NONE | Optional, Positional 4 |
RMTTRANSID | Remote transaction | Character value, *SAME, *TRANSID | Optional, Positional 5 |
PGMID | CICS program | Communications name, *SAME | Optional, Positional 6 |
TRANSTS | Status | *SAME, *ENABLED, *DISABLED | Optional, Positional 7 |
PURGE | Can be purged while executing | *SAME, *YES, *NO | Optional, Positional 8 |
WAITTIME | Maximum deadlock wait time | 0-7000, *SAME | Optional, Positional 9 |
IDLETIME | Maximum device I/O wait time | 0-7000, *SAME | Optional, Positional 10 |
DUMP | Dump when Abend | *SAME, *YES, *NO | Optional, Positional 11 |
TWASIZE | Transaction work area size | 0-32767, *SAME | Optional, Positional 12 |
SCRNSZE | Screen size used | *SAME, *DFT, *ALT | Optional, Positional 13 |
LCLQUEUE | Local system queuing | *SAME, *YES, *NO | Optional, Positional 14 |
UCTRN | Auto upper case translation | *SAME, *NO, *YES | Optional, Positional 15 |
Top |
Enter the name of the OS/400 library that contains the group. Possible values are:
Top |
Enter the name of the group to which the PCT entry to be changed belongs.
Top |
Enter the transaction identifier of the PCT entry to be changed.
When there is not enough space to enter the apostrophes, then enter an ampersand (&) in the first character position to get an extended field size that allows for the entry of additional characters. Blanks are accepted but, when the entry is defined to a control region, anything after the blank is ignored. For example, 'ab g' will be treated as 'ab' in the control region.
Hexadecimal characters should be enclosed in apostrophes and preceded by an uppercase X, for example X'A1A2A3A4'. Any hexadecimal value will be accepted, but, if the value is not a printable character, the entry will be rejected when it is defined to a control region.
Top |
Enter the name of the remote system that owns the transaction.
Possible values are:
Top |
Enter the identifier by which the transaction is known on the remote system. This field is not valid for the local system, that is when the system identifier field contains *NONE.
Possible values are:
When there is not enough space to enter the apostrophes, then enter an ampersand (&) in the first character position to get an extended field size that allows for the entry of additional characters. Blanks are accepted but, when the entry is defined to a control region, anything after the blank is ignored. For example, 'ab g' will be treated as 'ab' in the control region.
Hexadecimal characters should be enclosed in apostrophes and preceded by an uppercase X, for example X'A1A2A3A4'. Any hexadecimal value will be accepted, but, if the value is not a printable character, the entry will be rejected when it is defined to a control region.
Top |
Enter that name of the program to be started by this transaction identifier. This program should have a PPT entry. This field is valid only for the local system, that is when the system identifier field contains *NONE.
Possible values are:
Top |
Indicates whether or not the transaction may be used.
Possible values are:
Top |
Indicates whether or not the transaction may be purged.
Possible values are:
Top |
Enter the amount of time in seconds that the transaction can be in a dead lock state. The format is mmss
Possible values are:
Top |
Enter the amount of time in seconds that the transaction waits for terminal input or output. The format is mmss.
Possible values are:
Top |
Indicates whether or not a transaction dump is taken when the transaction terminates abnormally. This field is valid only for the local system, that is when the system identifier field contains *NONE.
Possible values are:
Top |
Enter the size of the associated Transaction Work Area (TWA). This field is valid only for the local system, that is when the system identifier field contains *NONE.
Possible values are:
Top |
Indicates whether the default or the alternate screen size associated with the terminal to be used to run the transaction.
Possible values are:
Top |
Indicates whether or not queuing on the local system is to be performed.
Possible values are:
Top |
Indicates whether the terminal input to this transaction is to be translated to uppercase at any terminal on which this transaction is run.
Possible UCTRN values are:
Top |
Top |
Top |