Does CA View or CA Deliver have an IVP (Installation Validation Procedure)?
Article ID: 71943
Updated On:
Products
Deliver
View
Issue/Introduction
Are there IVPs (Installation Validation Procedures) to verify if CA View or CA Deliver installations and started tasks are working?
Environment
CA View - All Releases
CA Deliver - All Releases
CA Deliver - All Releases
Resolution
CA View and CA Deliver do not have IVPs available, to validate their installations,because there could never be a generic, unique, pre-composed environment that could be guaranteed against any conflict with something else that might be in a client system.
With that, the below is presented with a WARNING that the user of the procedures should be aware of what parameters and other settings are being used in any currently-existing systems, so that no parameters are set in a similar manner, which could possible cause conflicts.
Here are recommended basic procedures that can be used for testing CA View:
. Modify SARSTC task, with its own unique set of SARINIT parameters.
. Start the SARSTC task using "/S sarstc,OPT=STOPBU".
. Run a report job, matching SARINIT CLSL/DEST/FORM settings for sysout.
. Run a View backup using "/F sarstc,NEW".
. Modify a CLIST, for access to the database.
. Access the database.
. Navigate Primary and Sysout Selection List panels.
Here are recommended basic procedures that can be used for testing CA Deliver:
. Note: The below is done with the existence of a related CA View database.
. Modify RMOSTC task, with its own unique set of RMOPARMS parameters.
. Start the RMOSTC task using "/S rmostc".
. Modify a CLIST, for access to the database.
. Access the database.
. Navigate Primary panel for Job, Report, and Distribution ID panels.
. Define a Job, a Report (of that Job), and a Distribution ID
. Run 2 report jobs:
. . One, matching RMOPARMS JOBCLSL and SYSCLSL (pre-spool processing)
. . Two, matching RMOPARMS NETCLSL/NETDEST/NETFORM (post-spool processing)
. Look in CA View to see if the reports processed through Deliver are in the database.
Note: The above are the basic functions of the products, as much of the rest of the products are utilities.
With that, the below is presented with a WARNING that the user of the procedures should be aware of what parameters and other settings are being used in any currently-existing systems, so that no parameters are set in a similar manner, which could possible cause conflicts.
Here are recommended basic procedures that can be used for testing CA View:
. Modify SARSTC task, with its own unique set of SARINIT parameters.
. Start the SARSTC task using "/S sarstc,OPT=STOPBU".
. Run a report job, matching SARINIT CLSL/DEST/FORM settings for sysout.
. Run a View backup using "/F sarstc,NEW".
. Modify a CLIST, for access to the database.
. Access the database.
. Navigate Primary and Sysout Selection List panels.
Here are recommended basic procedures that can be used for testing CA Deliver:
. Note: The below is done with the existence of a related CA View database.
. Modify RMOSTC task, with its own unique set of RMOPARMS parameters.
. Start the RMOSTC task using "/S rmostc".
. Modify a CLIST, for access to the database.
. Access the database.
. Navigate Primary panel for Job, Report, and Distribution ID panels.
. Define a Job, a Report (of that Job), and a Distribution ID
. Run 2 report jobs:
. . One, matching RMOPARMS JOBCLSL and SYSCLSL (pre-spool processing)
. . Two, matching RMOPARMS NETCLSL/NETDEST/NETFORM (post-spool processing)
. Look in CA View to see if the reports processed through Deliver are in the database.
Note: The above are the basic functions of the products, as much of the rest of the products are utilities.
Feedback
Yes
No
Powered by
