|
|
|
|
|
The library containing report decollating mission definitions is referenced by DD statement DAREPMIS. This DD statement is normally included in the Control‑M User Daily job. However, if jobs ordered through the New Day procedure have decollating missions, DD statement DAREPMIS must also be included in the Control‑M New Day procedure. Add DD statement DAREPMIS wherever it may be needed, for example, to procedures/batch utilities CTMTDAY, CTMDAILY, CTMJOBPR, CTMAPI, CTMJOB, the CLIST CTMCJOBS, the Online monitor, KSLs which perform ordering functions and so on.
More than one partitioned dataset can be referenced by each DD statement DAREPMIS (in a job or CLIST). If a library is not referenced, an error message is produced and the Control‑M New Day procedure or the User Daily job skips to the next job.
If you want to use more than one library to store definitions of report decollating missions, more than one Control‑M Daily can be used. This usually corresponds with using more than one Control‑M scheduling library (for security reasons).
Example - Relevant DD Statements Only
Control-M User Daily Job 1
//USER01 EXEC CTMDAILY
//DACHK DD DISP=SHR,DSN=parm‑library‑1(date‑Control‑record‑1)
//DAJOB DD DISP=SHR,DSN=scheduling‑library‑1(table‑1)
// DD DISP=SHR,DSN=scheduling‑library‑1(table‑2)
// DD DISP=SHR,DSN=scheduling‑library‑1(table‑3)
//DAREPMIS DD DISP=SHR,DSN=report‑definitions‑library‑1
//DAAMF DD DISP=SHR,DSN=the‑Control‑D‑active‑missions‑file
Control-M User Daily Job 2
//USER02 EXEC CTMDAILY
//DACHK DD DISP=SHR,DSN=parm‑library‑2(date‑Control‑record‑2)
//DAJOB DD DISP=SHR,DSN=scheduling‑library‑2(table‑1)
// DD DISP=SHR,DSN=scheduling‑library‑2(table‑2)
//DAREPMIS DD DISP=SHR,DSN=report‑definitions‑library‑2
//DAAMF DD DISP=SHR,DSN=the‑Control‑D‑active‑missions‑file
For a full description of Control‑M New Day processing, see Control-M.
Parent Topic |