The Compare Job Schedule Entries command may be used to compare the
values of job schedule entries from two different systems or from a
previously captured version from the same system. The CVTJOBSCDE TAA
command must be used to capture the information.
To perform a comparison, you must have unique job names assigned for
the job schedule entries. See the later discussion on 'Unique job
names'.
Assume you want to compare the job schedule entries from two
different systems. On the local system, the CVTJOBSCDE command would
be used such as:
CVTJOBSCDE JOB(*ALL) OUTLIB(LIB1)
The JOBSCDP file would be output to LIB1 with the information for all
of the job schedule entries.
On the remote system, the CVTJOBSCDE command would be used such as:
CVTJOBSCDE JOB(*ALL) OUTLIB(LIB2)
LIB2 would then be transferred to the local system and a comparison
made:
CMPJOBSCDE JOB(*ALL) FROMLIB(LIB1) TOLIB(LIB2)
A listing would be output which describes any differences found.
Only the important details are compared such as the command to be
run, when it is requested, the job description used, etc.
Information such as the last time the job ran and the status of the
job queue are not compared.
The records in the From file are read and the job name is used as the
key to access the corresponding job name in the To file. Each
important value is compared.
By default only those job schedule entries that differ will be
listed. If any difference exists, one line will appear with the job
name, entry number, and text description. For each value that
differs, the From and To values are listed.
If no corresponding entry exists, the job name is flagged.
When all records have been read from the From file, the To file is
read sequentially and the job name is used as a key to access the
corresponding job in the From file. If no such job exists in the
From file, the job name is flagged.
Comparing versions from the same system
---------------------------------------
CMPJOBSCDE may be used to compare two different versions of the
CVTJOBSCDE outfile. This allows you to determine where changes have
occurred on a single system.
You may use a unique library each time CVTJOBSCDE is run or use a
unique member when specifying CVTJOBSCDE. For example, you could use
the same JOBSCDP file in a library with a member name describing the
date the command was output such as:
CVTJOBSCDE JOB(*ALL) OUTLIB(xxx) OUTMBR(*DATE)
This will create a member with a name Mcyymmdd.
When CMPJOBSCDE is needed, specify the FROMMBR and TOMBR parameters
to be compared such as:
CMPJOBSCDE JOB(*ALL) FROMLIB(xxx) TOLIB(xxx)
FROMMBR(*FIRST) TOMBR(*LAST)
Unique job names
----------------
The job scheduler support allows you to have multiple entries using
the same name. The entries are differentiated by an 'entry number'
which is assigned consecutively for any job entry added. For
example, if the last entry number assigned was 00119, the next number
will be 00120 regardless of which job name is used.
Because the same job name may exist with different entry numbers from
different systems, there is no way to match the entries other than by
job name.
If duplicate job names exist on the same system, the duplicates are
flagged to inform you that no comparison can be made.
Recovery if format differences exist
------------------------------------
CMPJOBSCDE ensures that the formats of the From and To file match the
current format of TAAJBSBP (CVTJOBSCDE model file) for the current
release. If not, an escape message will be issued.
If this occurs, you may make a comparison by using CVTJOBSCDE on the
current release to create an outfile. Then replace the data with
your old format version using CPYF and specifying FMTOPT(*MAP).
If a new important parameter is added that has a non-blank default,
this will probably result in many differences being flagged.
CMPJOBSCDE escape messages you can monitor for
----------------------------------------------
None. Escape messages from based on functions will be re-sent.
Command parameters *CMD
------------------
JOB The job schedule job name to be compared. The
default is *ALL for all job schedule entries. A
specific name or a generic name may be entered.
FROMLIB The library containing the JOBSCDP file that was
output by the CVTJOBSCDE command. This identifies
the 'From file' to be compared.
TOLIB The library containing the JOBSCDP file that was
output by the CVTJOBSCDE command. This identifies
the 'To file' to be compared.
FROMMBR The member of the 'From file' to be compared. The
default is *FIRST. A specific member or *LAST may
be entered.
TOMBR The member of the 'To file' to be compared. The
default is *FIRST. A specific member or *LAST may
be entered.
DIFFONLY Whether to list at least one line for each job
schedule entry or only those with differences.
The default is *YES meaning only those job schedule
entries that have differences will appear in the
listing.
*NO may be specified to list all job schedule
entries found in the From file.
Restrictions
------------
Unique job names are required in order for a proper comparison to be
made.
Prerequisites
-------------
The following TAA Tools must be on your system:
CHKGENERC Check generic
CVTJOBSCDE Convert job schedule entries
DUPTAADBF Duplicate TAA data base file
RTVFMT Retrieve format
RTVSYSVAL3 Retrieve system value 3
SNDCOMPMSG Send completion message
SNDESCINF Send escape information
SNDESCMSG Send escape message
Implementation
--------------
None, the tool is ready to use.
Objects used by the tool
------------------------
Object Type Attribute Src member Src file
------ ---- --------- ---------- ----------
CMPJOBSCDE *CMD TAAJBSG QATTCMD
TAAJBSGC *PGM CLP TAAJBSGC QATTCL
TAAJBSGR *PGM RPG TAAJBSGR QATTRPG
|
