How do we set up a separate area for testing changes to processors?

book

Article ID: 49102

calendar_today

Updated On:

Products

CA Bind Analyzer for DB2 for z/OS CA Detector CA SQL-Ease for DB2 for z/OS CA Sysview Performance Management Option for DB2 for z/OS CA Database Detector for DB2 for z/OS CA Plan Analyzer for DB2 for z/OS CA Subsystem Analyzer for DB2 for z/OS CA PanAudit Plus CA Easytrieve Report Generator CA PAN/SQL CA Endevor Software Change Manager (SCM) CA Endevor Software Change Manager - Natural Integration (SCM) CA Endevor Software Change Manager - ECLIPSE Plugin (SCM) CA Endevor Software Change Manager - Enterprise Workbench (SCM) CA 2E

Issue/Introduction

When upgrading Endevor or implementing Endevor, many customers ask how to test changes to their processors. The recommendation from the Endevor Team is to implement a separate system and processor load library for testing new processors and maintenance. Having a separate test area for processors ensures that changes to the processors will not interfere with your production work. Make sure that you have a separate system and processor load library available for testing the new processors and maintenance to your existing processors.

The test system is typically defined in the production environment which is where we normally where the Endevor Admin system is defined. This test system should have the stage 1 and stage 2 processor load libraries defined in that order while all production systems only have the stage2 processor load library defined. This allows the Endevor Administrator to test the processors from stage 1 loadlib without affected the production system. When testing has been completed, the processor could then be moved to the stage2 processor loadlib so it can be picked up by the product systems.

Environment

Release:
Component: C21E