10.2.3 LANSA Communications Extensions Facility Tracing Records (COMMS_FACILITY_TRACE)

Configuration item COMMS_FACILITY_TRACE allows the creation, change and deletion of LANSA Communications Extensions Facility Tracing Records. These records are used to set tracing and logging options for each facility or module. When the listener job starts, it enables the tracing options specified by these records or those specified on the listener record.

Select configuration item COMMS_FACILITY_TRACE from the COMMS_EXTENSIONS group to review Communications Facility Tracing Records. The screen presented looks something like this:


  LCOADMP405        Work with Comms Facility Tracing Records


   Type options, press Enter.

   2=Review/Change        4=Delete


    Sel   Facility                                            Tracing  

    __    CPIC MANAGER                                        Partial  

    __    IPC MODULE                                          Partial  







   Object /etc/dc_pgmlib/lroute.dat now locked by this job.

   F1=Help  F6=Add/Create  F12=Cancel  F14=Messages



This screen lists all the facilities (modules) for which tracing records have been created. To the right of the facility name is a summary value of the tracing flag settings.

Note: Facility tracing records are entirely optional. If they are defined, the normal settings should be with all flags unchecked (that is, no tracing and no logging). Tracing should only be set on when asked by your product vendor to assist in troubleshooting.

Working from this screen you can, by entering one of the options beside a list entry, perform these actions:

2=Review/Change: Display the tracing and logging details for the facility tracing record. From the screen displayed, press the Change function key to enable the fields to be amended.

4=Delete: Delete the facility tracing record on which this option is entered.

Pressing the Add/Create function key will present the Add Facility Tracing screen which allows the addition of a new facility tracing record.


  LCOADMP414               Add Facility Tracing Record


   Facility (Module) . . . . . . . . . ______________________________  




  Tracing Options

   Errors . . . . . . . _ External IPC calls . _  IPC data . . . . . . _

   Debug listener . . . _ Calls to CPIC  . . . _  Internal IPC calls . _ 

   CPIC data  . . . . . _ System info  . . . . _  Cryptographic info . _ 


  Logging Options           

   Connect in . . . . . _ Connect out  . . . . _  





  F1=Help  F12=Cancel  F14=Messages



These input options are required on the Add Facility Tracing Record screen:

Facility (Module)

The facility or module for which the tracing and logging options are specified. It must be one of these values:

Tracing Options

Check (enter any non-blank character) beside the events or actions which require tracing:


Traces error information. This consists of errors which may be considered "normal" during communications as well as any "fatal" errors encountered. "Fatal" error messages are also written to the IBM i job log.

System Info

Traces basic information at the system software level such as version negotiation.

Debug Listener

Traces the events in the listener job.


Trace data sent and received at the point where LANSA Communications Extensions APIs are called.

IPC Data

Trace data sent and received at the point where the Inter Process Communications (IPC) interface (for example, TCP/IP sockets) is called.

External IPC Calls

Trace calls to the IBM i communications interface (for example, TCP/IP sockets APIs).

Internal IPC Calls

Trace calls made to the Inter Process Communications (IPC) interface (for example, the Sockets IPC Module).

Calls to CPIC

Trace API (CPIC) calls to the LANSA Communications Extensions CPIC Manager.

Cryptographic Info

Trace cryptographic information

Logging Options

Enables the recording of normal events which need tracking. On the IBM i, messages are sent to the job's external message queue and will be listed in the job log. Check (enter any non-blank character) beside the event(s) which require logging:

Connect In

Record details of incoming connection requests.

Connect Out

Reserved for future use.