Batch Job Documentation System
Procedures/Online Migration Procedures
Overview
When some jobs are changed, documentation must also be changed. If
documentation is changed directly, there will be a period of time when
the documentation does not match the job as it exists in the
production Panvalet library. An import/export facility is needed to
resolve the possible mismatches.
Preparation
If documentation needs to be changed, it should first be brought into
Test AIMS. This is done by using the documentation transport
application (DJT). It will delete any current
documentation in test and will import an exact copy of the
documentation as it exists at that time in production.
Changes
Changes can then be made to the documentation under Test AIMS. If
this is a new job, the job should be documented in the test
environment. Normal procedures should be used to accomplish this.
Migration
When JCL is migrated into production using the TSO Migration System, any
documentation for it in the test documentation system will be
automatically moved into production.
Alternatively, documentation may be moved into production by using the
DJT application, but in the Production AIMS
environment. This will delete the old production documentation and will
import the changed documentation as it exists in the test environment.
Cleanup
If manual migration is used, when the migration is complete, delete the
documentation from the test environment. This is done through the
DJS application. Deletion will help avoid confusion at
a later time should test and production documentation differ.
IT Applications Support
Last Modified: