APAR status
Closed as documentation error.
Error description
. IBM no longer supports version 1.2 of webtop. But the Proviso documentation that deals with Proviso/webtop integration has not been updated. The integration scripts have not been updated as well. . Following is a feed back oof the customer who succeeded to work around these issue. He integrated Proviso 441 within webtop 2.1: ------------ ... Please find my answers to your questions below: 1. You had to add the required columns instead of building the entire alerts.status schema: . How did you achieve that ? I logged into the object server machine as root, then ran $OMNIHOME/bin/nco_sql. . Which exact columns did you add ? provisoSubElementIndex provisoThresholdType provisoViolationTime provisoSubElementGrpIndex . On which exact database table ? alerts.status . Which exact commands did you use (on your system) ? alter table alerts.status add column provisoSubElementIndex int; go alter table alerts.status add column provisoThresholdType int; go alter table alerts.status add column provisoViolationTime int; go alter table alerts.status add column provisoSubElementGrpIndex int; go 2. You noticed that some of the documents/scripts are still up to date, while some others need to be updated: . You mentioned that the following are up to date: quallaby.cfg, quallaby.cgi, mttrapd.rules and trapdQuallabyWEBTOP.rules . You did mentioned that the following need to be updated: NCOMS.sql (to reflect later versions of the ObjectServer schemas Object Server version 3.6) , NetCoolProviso-NetcoolWebtopIntegrationGuide-41.pdf (review the doc to reflect the operations with webtop 2.1, for example: update screenshots and some text). The WebtopIntegrationGuide is also missing instructions to chmod chmod quallaby.cgi to +X so it can be executed by Webtop. As for the other changes, it's pretty easy to compare the screenshots (Webtop 1.2) from the guide with the actual screens from Webtop 2.1. Also, I'd recommend placing the "alter table" nco_sql commands inside a wrapper script that first checked for the existence of these columns before attempting to add them or otherwise handles the scenario where the columns already exist. Here's the object server error when attempting to add a duplicate column: a> alter table alerts.status add column provisoSubElementGrpIndex int; b> go ERROR=Object exists on line 1 of statement 'alter table alerts.status add column provisoSubElementGrpIndex int;...', at or near 'provisoSubElementGrpIndex' ------------------------------
Local fix
Problem summary
Will include this in subsequent documentation
Problem conclusion
Docs will be updated
Temporary fix
Comments
APAR Information
APAR number
IZ21268
Reported component name
NC/PROVISO DATA
Reported component ID
5724P59DV
Reported release
441
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-04-29
Closed date
2008-05-05
Last modified date
2008-05-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCFPZJ","label":"DataView"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"441","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
05 May 2008