10.2.1 LANSA Communications Definitions (COMMS_DEFINITIONS)

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:

LCOADMP401         Display Communications Definitions           Communications routing table  . . . /etc/dc_pgmlib/lroute.dat              Trace file name . . . . . . . . . . /tmp/dc_pgmlib/lroute.trc              Maximum size of trace file (bytes)    640000              User queue for session jobs . . . . QUSRSYS/LCOTPJOBS        Job description for session jobs  . *LISTENER    Prefix for session jobs' name . . . TP            Line turnaround wait & retry:      Wait time (milliseconds)  . . . . 300      Number of retries . . . . . . . . 300              Object LCOA01 in library DC@PGMLIB now locked by this job.      F1=Help  F12=Cancel  F14=Messages  F21=Change

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:

• Review the details of LANSA communications definitions.

• Use the Change function key to change details of LANSA communications definitions.

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.

• It must be an absolute IFS path. That is, you must enter the path starting from the root directory ("/").

• If the IFS directory entered doesn't exist, it is created. If the routing table itself doesn't exist, it is created and initialized with default contents. If you will be creating a new directory, it is strongly recommended that you sign on using the LANSA system's owner user profile.

Trace File Name

This is the Integrated File System (IFS) path to the stream file where trace data is recorded when tracing is enabled.

• It must be an absolute IFS path. That is, you must enter the path starting from the root directory ("/").

• If the IFS directory entered doesn't exist, it is created. If the trace file itself doesn't exist, it is created during runtime when tracing is enabled. If you will be creating a new directory, it is strongly recommended that you signon using the LANSA system's owner user profile.

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:

• The nominated library must allow for user domain objects to be created in it (review the IBM i system value QALWUSRDMN).

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:

• The job description must exist before it is named here.

• The library list parameter in the job description must include the libraries where the LANSA Communications Extensions programs reside.

• The special value *LISTENER may be used. This special value specifies that sessions jobs will be submitted to the same job queue and with the same job description and library list used to submit the listener job.

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:

• 1 to 4 characters long.

• A valid IBM i name.

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.

• Wait time - the time to wait (in milliseconds) before checking if the line has been turned around.

• Number of retries - The number of times it will check for the line turnaround signal.

If left blanks the default values of 300 milliseconds and 300 retries are returned.