Q. What should I see if the IBM i Listener is running?
A. You should see at least three items in the Work Active Job display when you execute the WRKACTJOB command:
Sub-system named: <pgmlib> where <pgmlib> is your LANSA Program Library.
Listener Job defined in the Job Description: LISTENER
A TP (Transaction job): TP00000001
If you do not see the sub-system or jobs, then the Listener is not executing properly.
Note: In this section, "LANLISTEN" and "TP000000nn" are used as the default names for the Sub-system name and the Transaction jobs. These are the names used by LANSA when a standard LANSA install is performed. Depending on your chosen naming convention, your Sub-system and Transaction jobs may be named differently.
Q. How do I know if the IBM i Listener port is active?
A. Use the IBM i command NETSTAT.
Select the option to Work with IPv4 connection status.
Look for Local Port 4545 (default) and check that the state is LISTEN.
Q. The Listener IBM i sub-system starts but there are no jobs.
A. If you see a LANLISTEN Sub-system started but no jobs listed in the sub-system, then select option five to Work with the Sub-system, display the job logs by selecting option 10, and look for any errors.
Also look in the QEZJOBLOG out queue for the job logs of the programs that ran and failed. Check for any authority problems.
Also check the library lists being used for the jobs. Make sure that the proper libraries such as QTEMP, QGPL and the LANSA Program Library are included - in that sequence. (QOTHPRDOWN is used in the instructions for setting up the LANLISTEN Sub-system. QOTHPRDOWN, by default, has a job description QDFTJOBD. This usually does not have DCXPGMLIB in its library list.)
Q. The Listener IBM i Sub-system starts and a job starts and then stops. There are no jobs running.
A. When you start the LANSA LISTEN Sub-system, you may see jobs start and then stop.
Look in the QEZJOBLOG for the job logs of the programs that ran and failed. These Transaction jobs will have a prefix of TP (unless you have changed the default prefix). Check for any authority problems. If no job logs are generated, you should change the jobs message logging level to LOG (4 00 *SECLVL) to get full details in the job log.
Also check the library lists being used for the jobs. Make sure that the proper libraries such as QTEMP, QGPL and the LANSA Program Library are included - in that sequence. (QOTHPRDOWN is used in the instructions for setting up the LANLISTEN Sub-system. QOTHPRDOWN by default has a job description QDFTJOBD. This usually does not have DCXPGMLIB in its library list.)
For multiple systems, ensure that there are separate names for the User Queue for Session Jobs otherwise you may receive errors such as "Message . . . . : Lock operation for object LCOTPJOBS not satisfied" in the job logs.
