Setting up multiple scheduling environments

 

You can set up scheduling environments on the same system. By doing this, the original data library can act as the active data library and the copied data library can be used for testing. Thus you have two scheduling environments, one for testing and one that is the actual. In addition, the test data library can serve as a backup if there is a system failure on the original system. This feature gives you added protection if you create an error in the original data library because you have a backup copy of the data library.

There are several reasons why you might want to set up multiple scheduling environments. You might want to have a production version and a test version of the product running at the same time. This type of environment allows you to test various job schedules before actually using them in the data library on the production system. Or you might have a system that is the backup for one or more other systems in which you can use a data-mirroring product to replicate the Advanced Job Scheduler data library (QUSRIJS) from the source system into a library named differently. In this case, the data library is active until there is a problem with the source system.

A scheduling environment is a duplicate of the QUSRIJS library except with different data. For instance you can have another data library named QUSRIJSTST with all the objects as QUSRIJS. Each are considered data libraries.

To set up a multiple scheduling environment, follow these steps:

1. Obtain a data library from a system

   To create a data library, you need to obtain a data library from a system. The following are three ways that you can obtain a data library from the system:

   • Save the data library from a system and restore it onto the production system.

   • Duplicate the data library on the current system using the Copy Library (CPYLIB) command.

   • Mirror a data library on the test system. These systems should be running the same version release level.

   The copied, restored, or mirrored data library uses a different name than the original system.

2. Assign data libraries to users

   After you obtain a test data library, add the data library to the Advanced Job Scheduler's properties and assign users to the data library. Therefore, when a user uses the Advanced Job Scheduler, the changes that the user makes are stored in the data library assigned to the user.

3. Copy jobs from test data library to actual data library (optional)

   If you are using a data library for testing purposes, you might want to copy the jobs from the test data library to the actual data library in use. You only need to do this if you restored or copied a data library in step 1 and you have jobs that you want to move to the actual data library in use. You do not need to do this if you mirrored a data library from the actual system to a test system.

   To copy jobs from one system's data library to another, use the Copy Job using Job Scheduler (CPYJOBJS) command. For more information about the specific parameters for this command, see the online help.

 

Parent topic:

Setting up the Advanced Job Scheduler

Previous topic: Specifying a mail server to use for notification

Next topic: Assigning data libraries to users