4.1.8 Verify the Upgrade
During the upgrade, any EPCs supplied with the install will be automatically applied.
You may wish to use the IBM i command CHGMSGQ to change the nominated <message queue> to DLVRY(*BREAK) to receive any messages from the submitted job. For example:
CHGMSGQ DSP02 DLVRY(*BREAK)
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@LOAD25
The final message after a successful install is:
****All selected LANSA components have successfully installed****
Retain the job log that results from the install for future reference regardless of whether the install message appears or not.
Refer also to Verify Integrator Upgrade if appropriate.
Once the LANSA upgrade batch job has been completed and if Initialization options have been selected, make sure the job LANSA_CLN is released. For details of LANSA_CLN, refer to Check LANSA_CLN.
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 can use a User Profile that has appropriate authority to start sub systems (STRSBS).
If you did not not use QOTHPRDOWN as the product owner, you must perform the steps in QOTHPRDOWN Profile not used.
Upgrade failure
If you do not see the message:
All selected LANSA components have successfully installed****
Read the job log that results from the upgrade to determine the reason for the upgrade's failure. When reading the job log, always read it backwards from the end. 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 a very early escape message reporting PROGRAM MESSAGE QUEUE QCL 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 upgrade to fail. In this case, this error occurs on the job log when the upgrade software tests which IBM command requester program is controlling it, QCL or QCMD. It is not fatal and does not indicate any type of problem with the upgrade.
Restarting an upgrade
Under no circumstances should you restart the upgrade without first checking the job log produced for messages that clearly indicate whether you can restart it or not. You must follow the recovery/restart procedures that are printed at the end of the upgrade job log.