Introduction › Using a Test Database

Using a Test Database

We recommend that you use a test database and run CA Deliver as a separate task when you are following the procedures in this guide. This precaution protects you from inadvertently changing or losing data in your production database and prevents problems in your production environment.

Before setting up a unique, separate test system, you must do the following:

• Define a separate and unique database for your system.
• Assign a unique and separate identifier to your system.

  Use the SYSID initialization parameter, which is a single letter, number, or national character ($, #, @), to define the identifier of a system.

• Assign a unique and separate combination of network input attributes to your system if it is used for network input.

  You must specify unique values for initialization parameters NETCLSL, NETDEST, and NETFORM).

• Assign a unique and separate combination of bundle holding copy attributes (BNDLCLS and BNDLDEST) to your system if it is to use the JES spool to retain bundle-holding copies.
• Create and maintain a unique and separate started task procedure and set of initialization parameters for your separate and unique system.