Configuration item COMMS_DEFINITIONS stores the basic definitions used by LANSA Communications Extensions for the listener and session jobs.
Select configuration item COMMS_DEFINITIONS to review LANSA communications definitions:
This screen displays the basic definitions required to use LANSA Communications Extensions. LANSA provides default values which can be left unchanged.
Using this display you can:
Communications Routing Table
This is the Integrated File System (IFS) path to the stream file where the listener and facility tracing definition records are stored.
Trace File Name
This is the Integrated File System (IFS) path to the stream file where trace data is recorded when tracing is enabled.
If left blank, the default value of /tmp/subdir/lroute.trc is used, where subdir is based on the name of the communications configuration object library.
Maximum Size of Trace File
Used to limit the amount of tracing data written to the tracing file. Once this limit is reached, no more tracing data is written to the file. The default size is 0, which means the size limit is the maximum size for the file allowed by the operating system.
User Queue for Session Jobs
The qualified name (library/user queue) of the IBM i user queue used by the prestarted session jobs to make themselves available to the listener job. It must satisfy these requirements:
If left blank the default value of QUSRSYS/LCOTPJOBS is returned.
Job Description for Session Jobs
The qualified name (library/job description) of the IBM i job description used by the listener job to submit session jobs. The job description named here allows the user to specify the job queue (and therefore the subsystem) where session jobs will run. It must satisfy these requirements:
If left blank the default value of *LISTENER is returned.
Prefix for Session Jobs' Names
The prefix used to start session jobs' names. Its purpose is to make it easier to identify session jobs in the system. The session job name is completed by appending a numeric sequential number (for example, TP00000001). The prefix must satisfy these requirements by being:
If left blank the default value of "TP" is returned.
Line Turnaround Wait & Retry
LANSA communication jobs are conversation oriented, in which the local and remote programs take turns to send and receive data. Before one side can send data, the other side must "turn the line around". If one side attempts to send data when it is in "receive state", it will get a state-check exception. This may also occur if the receiving side has already received all the data it expected and is ready to send, but it hasn't got yet the line turnaround signal, due to a slow communications link or due to one side,(either the remote or local program) being comparatively slower than the other side.
Use these "wait & retry" values to reduce the number of state check exceptions due to delays in the line turnaround signal.
If left blanks the default values of 300 milliseconds and 300 retries are returned.