97 lines
7.2 KiB
HTML
97 lines
7.2 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="task" />
|
||
|
|
<meta name="DC.Title" content="Set up multiple scheduling environments" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajs3custom.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajsnotification.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajsdatalibrary.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzaksajsmultenv" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Set up multiple scheduling environments</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaksajsmultenv"><a name="rzaksajsmultenv"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Set up multiple scheduling environments</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<div class="section"><p>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.</p>
|
||
|
|
<p>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.</p>
|
||
|
|
<p>To
|
||
|
|
set up a multiple scheduling environment, follow these steps:</p>
|
||
|
|
</div>
|
||
|
|
<ol><li class="stepexpand"><span>Obtain a data library from a system</span> <p>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:</p>
|
||
|
|
<ul><li>Save the data library from a system and restore it onto the production
|
||
|
|
system.</li>
|
||
|
|
<li>Duplicate the data library on the current system using the Copy Library
|
||
|
|
(CPYLIB) command.</li>
|
||
|
|
<li>Mirror a data library on the test system. These systems should be running
|
||
|
|
the same version release level.</li>
|
||
|
|
</ul>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> The copied, restored, or mirrored data library uses a different
|
||
|
|
name than the original system.</div>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>Assign data libraries to users</span> <p>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.</p>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>Copy jobs from test data library to actual data library (optional)</span> <p>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.</p>
|
||
|
|
<p>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.</p>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksajs3custom.htm" title="After you have installed the Advanced Job Scheduler, you need to configure it. After you have finished this preliminary work, you are ready to begin scheduling jobs.">Set up the Advanced Job Scheduler</a></div>
|
||
|
|
<div class="previouslink"><strong>Previous topic:</strong> <a href="rzaksajsnotification.htm" title="Set up a mail server to use for e-mail notification messages. A mail server is required if you want to send e-mail notifications.">Specify a mail server to use for notification</a></div>
|
||
|
|
<div class="nextlink"><strong>Next topic:</strong> <a href="rzaksajsdatalibrary.htm" title="Specify what data library is associated with each user. A data library will contain all the objects found in the QUSRIJS library. You can have any number of data libraries.">Assign data libraries to users</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|