3.1.4 Verify Typical Installation
When you see the message indicating that the batch job has finished, examine the resulting job log QPJOBLOG before attempting to use the LANSA system.
If there are any EPCs with the Install, they will be applied and the EPC log updated accordingly.
Once the LANSA update job has completed, check the job's spooled file for the following:
Check messages
- Filename: QPDSPMSG
- User Data: SUMMARYMSG and DETALMSG
and check for any errors.
Check for required IBM i software
- Filename: QSYSPRT
- User Data: DC@LOAD20
The final message after a successful install is:
****All selected LANSA components have successfully installed****
Regardless of whether the successful install message appears or not, retain the job log that results from the install for future reference.
You must check that LANSA_CLN has been run successfully. For details refer to Check LANSA_CLN.
If the Installation of LANSA for i completed successfully, go to LANSA License Codes.
As LANSA for the Web is installed as part of the Typical Install, you must also install the LANSA for the Editor and Administrator as applicable.
QOTHPRDOWN User Profile
If you had used QOTHPRDOWN instead QSECOFR to do the install, the QOTHPRDOWN profile might not have authority to use the command STRSBS. Because of this, the following sub systems might not start automatically:
- LISTENER
- LANSA for Integrator (if installed).
You must use a User Profile that has appropriate authority to start sub systems (STRSBS).
If you did use QOTHPRDOWN as the product owner, you must perform the steps in QOTHPRDOWN Profile not used.
Typical Installation failed
If you did not see this message:
All selected LANSA components have successfully installed
read the other messages sent to the workstation and in the job log and perform any suggested actions in full.
When reading the job log, always read it backwards, starting from the last page. If you read it from the beginning, you cannot assume that the first error you see is the cause of the problem.
For instance, most job logs will contain escape messages reporting "Object xxxxxxxxxx in lllllllll type tttttttttt not found". If you read the job log forwards and stop at this apparently fatal/severe message you will miss the actual error that caused the install to fail. In this case, this error occurs when the install software tests if an object already exists. It is not fatal and does not indicate any problem with the install.
Do not restart the installation without first checking the job log produced for messages that clearly indicate the source of the problem.