Transaction Program Definitions

Personal Communications and Communications Server configuration uses two naming levels to identify the remotely started program:

The 64-character name of the local program known by the partner transaction program (tp_name)
The file specification of the local program to be started (filespec)

Using two names enables flexible reconfiguration that can increase the portability of your APPC programs among workstations.

TP name: The name that a partner transaction program sends in the allocation request to the attach manager in the local workstation.
The partner transaction program and the local program must both know the transaction program name. The transaction program name is a supplied parameter for RECEIVE_ALLOCATE verbs in programs on local LUs. Partner transaction programs supply a transaction program name with APPC [MC_]ALLOCATE or [MC_]SEND_CONVERSATION verbs.
Path name: The transaction program file specification (path name) names the program to start locally. The transaction program file specification contains the executable file's drive, path, file name, and extension.
Multiple transaction program definitions can specify the same transaction program file specification. The attach manager must determine whether to run one or multiple instances of a program, so a given transaction program file specification must be configured as either queued or nonqueued in all definitions that name it. For example, if a definition that specifies MYTP.EXE is configured as "queued—attach manager started", MYTP.EXE cannot be configured as nonqueued in another transaction program definition. However, the transaction program filespec is case sensitive.