Add CICS PPT Entry (ADDCICSPPT)

Use the Add CICS Processing Program Table (ADDCICSPPT) command to add an entry to the PPT.

The Processing Program Table (PPT) defines the programs that may be invoked by the transaction identifiers held in the PCT. You need to create entries for:

All programs invoked by a local transaction id. These programs may be local or remote.
All programs that are invoked by either the EXEC CICS LINK or the EXEC CICS XCTL commands.
All BMS map sets and user spaces used on the local system.

Parameters

Keyword	Description	Choices	Notes
LIB	Library	Communications name, LIBL, CURLIB	Required, Positional 1
GROUP	Group	Communications name	Required, Positional 2
PGMID	CICS program	Communications name	Required, Positional 3
CICSMAP	BMS map set	NO, YES	Optional, Positional 4
SYSID	Remote CICS system	Communications name, *NONE	Optional, Positional 5
RMTPGMID	Remote CICS program	Communications name, *PGMID	Optional, Positional 6
PGMOBJ	Program object	Qualified object name	Optional, Positional 7
	Qualifier 1: Program object	Name
	Qualifier 2: Library	Name, LIBL, CURLIB
CICSDEBUG	CICS debug	DEBUG, NODEBUG	Optional, Positional 10
APISET	API commands	FULLAPI, DPLSUBSET	Optional, Positional 11
TRANSID	Transaction	Character value, *NONE	Optional, Positional 12
PGMSTS	Status	ENABLED, DISABLED	Optional, Positional 8
PGMLNG	Calling convention	COBOL, C	Optional, Positional 9

Top

Library (LIB)

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

*LIBL: The library list is used to locate the first OS/400 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 OS/400 library that contains the group.

Group (GROUP)

The name of the group to which this PPT 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 #.

CICS program (PGMID)

Enter the program identifier used to initiate an iSeries program object. This field is also used to identify this PPT entry.

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 #.

BMS map set (CICSMAP)

Indicates if the program identified in the PGMID field is a BMS map set or a user space.

Possible values are:

*NO: The program identifier is not a BMS map set or user space; it is an application program.
*YES: The program identifier is a BMS map set or a user space.

Remote CICS system (SYSID)

Enter the identifier of the system owning the program. The system should have a TCS entry. This field is valid only for PPT entries defining application programs, that is the CICSMAP field should contain *NO.

Possible values are:

*NONE: The program 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 CICS program (RMTPGMID)

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

Possible values are:

*PGMID: The local and remote program identifiers are the same. The local identifier will be used to access the remote program.
remote-pgm-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 #.

Program object (PGMOBJ)

Enter the name of the iSeries program object or user space object that will be utilized by the program identifier. This field is valid only for local systems, that is when the system identifier field contains *NONE.

Possible library values are:

*LIBL: The library list for the job that is associated to the CICS control region is used to locate the iSeries program object or user space object.
*CURLIB: The current library for the job that is associated to the CICS control region is used to locate the iSeries program object or user space object. If no library is specified as the current library, the QGPL library is used.
library-name: Specify the name of the library where the iSeries program object or user space object is located.

object-name: Specify the name of the iSeries program object or user space object.

CICS debug (CICSDEBUG)

Indicates whether or not the CICS-supplied transaction CEDF can be used when running an iSeries program object. This field is valid only when the CICSMAP field is referencing an application program held on the local system, that is when the CICSMAP field contains *NO and the system identifier field contains *NONE.

Possible values are:

*DEBUG: CEDF can be used with the iSeries program object.
*NODEBUG: CEDF cannot be used with the iSeries program object.

API commands (APISET)

Indicates which of the EXEC CICS commands can be executed in an application program. This field is valid only when the CICSMAP field references an application program held on the local system, that is when the CICSMAP field contains *NO and the system identifier field contains *NONE.

Note: If the program identifier starts with AEG, then this field must contain *FULLAPI.

Possible values are:

*FULLAPI: All the EXEC CICS commands can be used in application programs.
*DPLSUBSET: Only the EXEC CICS commands specified in the distributed progamming link subset can be used in application programs.

Transaction (TRANSID)

Enter the overriding transaction identifier under which the server program runs during a distributed program link. This transaction identifier should have its own PPT entry. This parameter is not valid for the local system, that is when the system identifier field contains *NONE.

Possible values are:

*NONE: There is no overriding transaction identifier to be used.
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.

Status (PGMSTS)

Indicates whether or not the program identifier can be used.

Possible values are:

*ENABLED: This program identifier can be used.
*DISABLED: This program identifier cannot be used.

Calling convention (PGMLNG)

Enter the program language convention used to call the OS/400 program object. This determines how CICS passes parameters to the program object.

*COBOL: CICS uses the CICS COBOL calling convention to invoke the OS/400 program object
*C: CICS uses the CICS C calling convention to invoke the OS/400 program object