Installation Jobs

The ChangeMan ZMF install process is accomplished by a sequence of batch jobs.

The first job in the sequence is initiated by the Scheduler defined in the package

Installation Instructions. The rest of the jobs in the sequence are automatically submitted to the internal reader by the preceding job or by ChangeMan ZMF when successful completion of a preceding job is recorded in the package master.

When you attempt to restart an install process for a package in limbo, you must choose which job to restart and you must know whether or not to submit that job in the development environment or on a ChangeMan ZMF production environment that runs at a remote site.

The following table describes ChangeMan ZMF installation jobs. The table indicates where each job runs. If you do not have remote production environments, a subset of these jobs is used to install your packages.

DEVELOPMENT CENTER		REMOTE SITE
Job	Action	Job	Action
10	● Package is audited and/or frozen. ● Jobs are created in X.&node. ● Package is approved. ● Job 10 is submitted to initiate the distribution. ● CMNBATCH transaction 10 says distribution initiated and status is changed to DIS. ● Vehicle is asked to submit job 11 at remote site.
11	Staging libraries are sent to remote site.	10	● Staging libraries are received including QSAM package master. ● Job 11 is submitted.
		11	● CMNBATCH transaction 11 overlays package records (on the package master) with QSAM package master. ● Proper node record is time stamped; status is DIS. ● Job 14 is submitted. (Only if IEBCOPY is not used.)
		14	Job 14 requests vehicle to submit 15 at DEV site.
		17	Job 17 is submitted if external (not internal) scheduler is used.
		18	Job 18 requests vehicle to submit 19 at DEV site.
15	Job 15 is submitted. (Only if IEBCOPY is used.)
15	CMNBATCH transaction 15 stamps acknowledgment of distribution.
19	Notification to the user specified in the Notify user field that distribution failed.
		21	Perform Db2 bind for production installation. (INSTALL IN PROD = YES).
		20	Job 20 is submitted to check if package was previously installed. If not, package begins installation.
		20	CMNBATCH transaction 20 changes package status to INS.
		20	Job 24 is submitted. (Only if IEBCOPY is not used.)
		20t	If Temporary, Job 20t runs to install members into temporary libraries.
		24	Requests vehicle to submit 25 at DEV site.
		28	Requests vehicle to submit 29 at DEV site.
25	CMNBATCH transaction 25 changes package status to INS.
29	Notification to the user specified in the Notify user field that installation failed.
25	If Permanent, Job 30 is submitted.
		30	Job 30 is submitted if system environment is ALL.
30	CMNBATCH transaction 30 changes package status to BAS and ripples the baseline.
30	Delete members from promotion libraries based on promotion level and library type.
		31	If temporary, Job 31 runs to delete members from temporary libraries.
		31t	CMNBATCH transaction 31 changes package status to TCC (Temporary Change Cycled) and date/time stamps. Submit job 35.
		32	Performs Db2 bind for production installation (INSTALL IN PROD = NO).
		34t	Requests vehicle to submit 35t at DEV site.
35t	Package status updated to TCC and date/time stamped when all remote sites have been cycled.
		38t	Requests vehicle to submit 39t at DEV site.
39t	Notification to the user specified in the Notify user field that the package cycle failed.		CASE: A permanent change must be backed out. ● Operator makes human decision to back out (full) particular package. ● Operator enters backout reasons on panel. ● ChangeMan ZMF instance copies package to same flat file that was sent from development center. ● Job 50 is submitted.
		49	Job 21 runs the Db2 bind for production backout (INSTALL IN PROD = YES).
		50	● Backs out the change by copying back from BKUP libraries. ● Changes package status to BAK. ● Job 54 is submitted if IEBCOPY is used; else job 51 is submitted.
		50	If system environment is ALL, job 55 is submitted.
		51	Job 51 transmits a QSAM package master to the development center and requests a vehicle to submit job 54.
54	● Reads flat package and transmits reasons. ● Updates backout reasons into correct package.
55	Job 55 is submitted to reverse ripple the baseline if all remote sites are backed out.
55	● Status is changed to BAK. ● * node record is date and time stamped.
		56	Job 32 runs the Db2 bind for production backout (INSTALL IN PROD = NO).
		58	Job 58 requests vehicle to submit 59 at DEV site.
59	Notification to the user specified in the Notify user field that package backout failed.
		64	Job 64 requests vehicle to submit 65 at DEV site. ● Package is audited and/or frozen. ● Jobs are created in X.&node. ● Package is approved. ● Job 10 is submitted to initiate the distribution.

...