LU02773 did not not apply successfully for 14.0 Web Viewer
search cancel

LU02773 did not not apply successfully for 14.0 Web Viewer

book

Article ID: 239243

calendar_today

Updated On:

Products

Output Management Web Viewer

Issue/Introduction

What was the exact issue with the maintenance rollout? We researched and found the below. Please check the details & let us know where things went wrong.

The Web Viewer log has the below error:
CAHVS0500E Unable to read J2Z service data: DRIB

Also when a user tries to access a report, they see the message "Failed to read J2Z service data" in web viewer site

The SMPE APPLY Job has the HOLD DATA below for the above error:
================================================================

The updated CVDELOAD load library must be used by your application      
server at the same time the updated web-viewer.war/web-viewer.ear file  
is deployed to your application server.                                 
                                                                        
The updated CVDELOAD load library is not compatible with prior          
web-viewer.war/web-viewer.ear builds.  Using the updated CVDELOAD load  
library with a prior build causes the following error when a user tries 
to open a report:                                                       
                                                                        
    CAHVS0300E Service module CAHVGetReportInformation INIT failed with 
               J2ZException There is no param with the name 'data'      
                                                                        
The updated web-viewer.war/web-viewer.ear file is not compatible with   
prior CVDELOAD load library levels.  Using the updated                  
web-viewer.war/web-viewer.ear file with a prior CVDELOAD load library   
level causes the following error when a user tries to open a report:    
                                                                        
    (toast) Failed to read J2Z service data          

----------------------------------------

The rollout order we followed is 

1) Removed the CVDELOAD from LLA  
*********************************************************************************
05:37:06.06 Q617972  00000290  F LLA,UPDATE=A1
*********************************************************************************

2) Removed the CVDELOAD from Linklist
*********************************************************************************
05:38:23.72 Q617972  00000290  SET PROG=X5
05:38:23.75          00000290  IEE252I MEMBER PROGX5   FOUND IN SYS1.GHP1.PARMLI
05:38:23.75 Q617972  00000090  CSV500I LNKLST SET LNKLST06 HAS BEEN DEFINED
05:38:23.87 Q617972  00000090  CSV501I DATA SET SYS3.CAI.CAILIB 345
                 345 00000090  HAS BEEN DELETED FROM LNKLST SET LNKLST06
*********************************************************************************

3) Renamed the CVDELOAD DSN to a backup name
4) Renamed the Maintenance applied CVDELOAD to Runtime DSN name

5) Added CVDELOAD to Linklist
*********************************************************************************
05:57:44.83 Q617972  00000290  SET PROG=X6
05:57:44.87          00000290  IEE252I MEMBER PROGX6   FOUND IN SYS1.GHP1.PARMLI
05:57:44.87 Q617972  00000090  CSV500I LNKLST SET LNKLST10 HAS BEEN DEFINED
05:57:45.11          00000094  IEF196I IEF237I C004 ALLOCATED TO SYS00177
05:57:45.11          00000094  IEF196I IEF285I   SYS3.CAI.CAILIB
05:57:45.11          00000094  IEF196I IEF285I   VOL SER NOS= ZOSRB1.
05:57:45.11 Q617972  00000090  CSV501I DATA SET SYS3.CAI.CAILIB 818
                 818 00000090  HAS BEEN ADDED TO LNKLST SET LNKLST10
*********************************************************************************

6) Added the CVDELOAD to LLA
*********************************************************************************
05:59:01.69 Q617972  00000290  F LLA,UPDATE=A1
*********************************************************************************

7) Ran the job to deploy the WAR file, however it is failed. By overlooking the failure our team started the STCs
*********************************************************************************
06:10:04.24 STC01099 00000290  S CAHVTOMX
06:10:04.24 STC01099 00000290  S CAHVHS2
*********************************************************************************

Then figured out that the brought down the started tasks & ran the job to deployed the WAR file successfully.
After that again we started the STCs however the order in which they started were first CAHVTOMX & then CAHVHS2

Still the users were unable to see reports & got the error Failed to read J2Z service data 

What caused the issue? Is the order of the started tasks matter here or was something not done right while doing the CVDELOAD rename? Need this resolved so we can apply the same maintenance in production.

Environment

Release : 14.0

Component : Output Management Web Viewer

Cause

 Incorrect modules in the SATSTC loadlib

Resolution

Why the load library used by the STC pointed to an older version depended on the customer environment and actions... They confirmed they didn't have the correct module by following the steplib from the STC, and looking for module CAHVGREI and in it for "eyecatcher" CAHVGREI CCAFE00  ~RMID(...) ... where the correct one for LU02773 should look like: CAHVGREI CCAFE00  ~RMID(LU02773)~ 20210712 14.15 - It did not look that way. When the correct modules for LU02773 were in SATSTC loadlib, the maintenance applied successfully.

Additional Information

The Web Viewer log had the below error:

CAHVS0500E Unable to read J2Z service data: DRIB

Also when the user tried to access the report received the message "Failed to read J2Z service data" in webviewer site.

And for the 2nd part of the holddata for LU02773:

The updated web-viewer.war/web-viewer.ear file is not compatible with prior CVDELOAD load library levels. Using the updated web-viewer.war/web-viewer.ear file with a prior CVDELOAD load library level caused the following error when a user tried to open a report:

    (toast) Failed to read J2Z service data                         

    (log) CAHVS0500E Unable to read J2Z service data: DRIB

These appear to be an exact match. This message is an indication that the CVDELOAD picked up by the server did not have the maintenance applied. Verify that the CVDELOAD has the maintenance applied – Verify the CVDELOAD library for your test.

The correct start-up order is:
-          Start the H2 server
-          Start the Web Viewer application server

The correct shut-down order is:
-          Stop the Web Viewer application server
-          Stop the H2 server