Batch Job Documentation System

Usage/Documentation Import

Problem

The production Batch Job Documentation System should always be operational and should always reflect a job's status as it is in the production environment. Two factors can affect this goal.

When the SPX D.8 option is used, it will close the documentation files for 5-10 minutes as new documentation is extracted and placed in the appropriate files.
If a job is being changed by the programming staff in such a manner that the documentation for the job will change, then changes to the documentation must be coordinated with the migration of the program and JCL changes.

Method

To accommodate the needs of (1) above, use of the SPX D.8 option will only place documentation in test files available under Test AIMS.

To accommodate (2) above, documentation should be changed under Test AIMS.

Normally documentation will exist only in the production environment. An import facility (AIMS application DJT) exists to transfer documentation between Test AIMS and Production AIMS.

Before changing documentation, the documentation should be imported from the production environment into the test environment. Changes should then be made in the test environment.

When programs and JCL are migrated into production, the documentation must also be migrated. This is an automatic process with the TSO Migration SYstem. When JCL is migrated, any documentation for it in the test documentation system is automatically migrated into production.

Operation

Operation is the same as selecting a job through the Job Selection screen. The DJT application will display a job selection screen. Select the items to be migrated/transfer and press "enter". The migration will then take place.

When migrating, if the job was previously documented in the destination location, it will first be deleted before the migration takes place.

If jobs to be migrated span across selection screens, repeat the migration process on each relevant screen.

IT Applications Support

Last Modified: