Add CICS PCT Entry (ADDCICSPCT)

Where allowed to run:

Batch job (*BATCH)
Interactive job (*INTERACT)
Batch program (*BPGM)
Interactive program (*IPGM)
Batch REXX procedure (*BREXX)
Interactive REXX procedure (*IREXX)
Using QCMDEXEC, QCAEXEC, or QCAPCMD API (*EXEC)

Threadsafe: No

Parameters
Examples
Error messages

Use the Add CICS Program Control Table (ADDCICSPCT) command to add an entry to 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).

Parameters

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, *NONE	Optional, Positional 4
RMTTRANSID	Remote transaction	Character value, *TRANSID	Optional, Positional 5
PGMID	CICS program	Communications name	Optional, Positional 6
TRANSTS	Status	ENABLED, DISABLED	Optional, Positional 7
PURGE	Can be purged while executing	YES, NO	Optional, Positional 8
WAITTIME	Maximum deadlock wait time	0-7000, 0	Optional, Positional 9
IDLETIME	Maximum device I/O wait time	0-7000, 0	Optional, Positional 10
DUMP	Dump when Abend	YES, NO	Optional, Positional 11
TWASIZE	Transaction work area size	0-32767, 0	Optional, Positional 12
SCRNSZE	Screen size used	DFT, ALT	Optional, Positional 13
LCLQUEUE	Local system queuing	YES, NO	Optional, Positional 14
UCTRN	Auto upper case translation	NO, YES	Optional, Positional 15

Library (LIB)

Enter the name of the library that contains the group. Possible values are:

*LIBL: The library list is used to locate the first library that contains the group.
*CURLIB: The current library contains the group. If no current library is specified, the QGPL library is used.
library-name: The name of the library that contains the group.

Group (GROUP)

Enter the name of the group to which this PCT entry is to be added.

group-name: The group name may have a maximum length of 10 characters. The first character must be alphabetic, or one of the special characters, $, @, or #. The remaining characters can be alphanumeric or one of the special characters, $, @, or #.

Transaction (TRANSID)

Enter the transaction identifier used to start a program defined in the processing program table. This name is also used to identify this PCT entry.

transaction-identifier: The transaction identifier may have a maximum length of 4 characters. Any characters on the keyboard can be entered, but lowercase letters and special characters should be enclosed in apostrophes.
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.

Remote CICS system (SYSID)

For a remote transaction, enter the identifier of the system owning the transaction. The system should have a TCS entry.

Possible values are:

*NONE: The transaction is held on the local system.
system-identifier: The system identifier may have a maximum length of 4 characters. The first character must be alphabetic, or one of the special characters, $, @, or #. The remaining characters can be alphanumeric or one of the special characters, $, @, or #.

Remote transaction (RMTTRANSID)

Enter the identifier by which the transaction is known on the remote system. This field is not valid for a local system, that is when the system identifier field contains *NONE.

Possible values are:

*TRANSID: The local and remote transaction identifiers are the same. The contents of the transaction identifier field in this PCT entry will be used.
remote-transaction-identifier: The remote transaction identifier may have a maximum length of 4 characters. Any characters on the keyboard can be entered, but lowercase letters and special characters should be enclosed in apostrophes.
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.

CICS program (PGMID)

Enter the identifier of the program to be started when the transaction is used. The program should be defined in the PPT. This field is only valid for local transactions, that is when the system identifier field contains *NONE.

program-identifier: The program identifier may have a maximum length of 8 characters. The first character must be alphabetic, or one of the special characters, $, @, or #. The remaining characters can be alphanumeric or one of the special characters, $, @, or #.

Status (TRANSTS)

Indicates whether or not the transaction can be used.

Possible values are:

*ENABLED: The transaction can be used.
*DISABLED: The transaction cannot be used.

Can be purged while executing (PURGE)

Indicates whether or not the transaction may be purged.

Possible values are:

*YES: The transaction may be purged.
*NO: The transaction may not be purged.

Maximum deadlock wait time (WAITTIME)

Enter the amount of time in seconds that the transaction can be in a dead lock state. The format is mmss.

Possible values are:

0: The transaction can be in a dead lock state for an unlimited amount of time.
dead-lock-timeout: Enter a number in the range 0 7000 (70 minutes).

Maximum device I/O wait time (IDLETIME)

Enter the amount of time in seconds that the transaction may wait for terminal input or output. The format is mmss.

Possible values are:

0: The transaction may wait for unlimited amount of time for terminal input or output.
read-timeout: A number in the range 0 through 7000 (70 minutes).

Dump when Abend (DUMP)

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:

*YES: A transaction dump will be taken on abnormal termination of the transaction.
*NO: A transaction dump will not be taken on abnormal termination on the transaction.

Transaction work area size (TWASIZE)

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:

0: There is no TWA associated with the transaction.
twa-size: A number in the range 0 through 32767.

Screen size used (SCRNSZE)

Indicates whether the default or the alternate screen size is to be used for the terminal running this transaction.

Possible values are:

*DFT: The default screen size is to be used.
*ALT: The alternate screen size is to be used.

Local system queuing (LCLQUEUE)

Indicates whether or not queuing on the local system is to be performed.

Possible values are:

*YES: Local system queuing is to be performed.
*NO: Local system queuing is not to be performed.

Auto upper case translation (UCTRN)

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:

*NO: Specifies that terminal input uppercase translation is dependent upon the UCTRN setting in effect in the Terminal Control Table for each individual terminal.
*YES: Specifies that data entered in lowercase from any terminal is to be translated to uppercase before being passed to this transaction.

Examples

None

Error messages

Unknown