Host Monitor fails to start: error LII0028S
|Product/Release:||LANSA for Windows|
|Abstract:||Error LII0028S is usually caused by an outbound communications job on the host AS/400 that is still active from a previous Host Monitor session|
|Submitted By:||LANSA Technical Support|
Error message LII0028S 'Failed to start the Host Monitor at the Host. Aborting LANSA/PC Host Monitor.' indicates that an outbound communications job on the Host AS/400 is still active from a previous Host Monitor session.
Using the WRKACTJOB or WRKSBSJOB QCMN command, look for a job with the same name as the PC node name or server and the user id which was used to LOGON to LANSA/PC. There could also be a job in the QINTER subsystem with the name MON_xxxxxx (where xxxxxx is the PC node name), although this one may no longer be active. Please repeat the following steps for both the job in QCMN and the one in QINTER:
- Use option 5 to work with job.
- Use option 13 to inspect the library list.
Now, compare the library lists of the job running in QCMN and the job running in QINTER.
The most likely cause of this error is that the job description associated with the User Profile used to log on to LANSA/PC has a different library list to the one required to connect to the correct LANSA/AD Host system.
To actually resolve the problem end both jobs. Use option 4=End against both jobs. After ending these the two jobs and logging on with an appropriate user id, there should be no further problem.
Note: The LANSA administrator should ensure that ALL user ids used to run LANSA have the correct library lists to avoid starting the wrong LANSA system when there are more than one on the same AS/400.