Usage Notes

• The PLAN NAME can be up to six characters in length. Use of the SUFFIX parameter in the FETCH phase permits creation of multiple Daily User Prompting Plans based on one Master Prompting Plan. This also makes it possible to duplicate (by overriding) a fetch of the same plan by setting the OVERRIDE DAILY PLAN parameter to YES on the FETCH A PLAN screen.
• Each job defined in the Master Scheduling table must contain an IN prerequisite condition in the format:

  RUN-%%PLANID

  This prerequisite condition is added during the EXEC phase only after all parameters for a specific plan are assigned in the EXEC phase. %%PLANID resolves to the PLAN NAME (and SUFFIX) designated in the FETCH phase.

  Since each plan can be ordered multiple times for the same scheduling date, it is highly recommended to distinguish between the dependencies of the jobs in the plan based on PLAN NAME. Every prerequisite condition used for inter-plan dependency must contain the string %%PLANID. It is automatically replaced by the PLANID during the FETCH phase.

• The JCL of each job must be modified as follows:

  The first AutoEdit control statement must point to an AutoEdit Parameters library and the PLANID member. The PLANID member contains the unique PLANID of the job (automatically handled by Control-M).

  Example

  %%LIBSYM CTM.PROD.SYMBOLS %%MEMSYM PLANID

  The second AutoEdit control statement must point to the Daily AutoEdit Parameters library and the member %%PLANID. Control-M automatically resolves %%PLANID to the PLAN NAME designated in the FETCH phase.

  The Daily AutoEdit Parameter library must be suffixed by a date parameter that is resolved by Control-M. Example:

  %%LIBSYM CTM.PROD.AEDI%%OMONTH.%%ODAY %%MEMSYM %%PLANID

• The %%PLANID member of each plan (in the Daily AutoEdit Parameter library) contains up to four configuration tables identified by AutoEdit variables.

  Parameters and data that are repeatedly used in a data processing environment can be defined in such a configuration table.

  A configuration table is a member of the GLOBAL library, which is referenced by the DAGLOBAL DD statement. Such a member contains a set of user-defined local variables and their assigned values that can be referenced in the JCL of individual jobs.

  An AutoEdit variable identifies such a configuration table by a statement in the form %%CONFn=config_tablename in the %%PLANID member.

  Example

  %%CONF1=INDICES
  %%CONF2=WEEKCHAR
  %%CONF3=
  %%CONF4=

  To use the configuration tables parameters procedure, insert the following AutoEdit statement in the JCL of each job:

  //* %%INCLIB CTM.PROD.PARM %%INCMEM PPF2CONF

  The PPF2CONF member uses the configuration table values specified in the %%PLANID member to select the GLOBAL autoedit members to be included in the JCL of the job. It contains the following AutoEdit code:

  %%IF *%%CONF1 NE *
  %%GLOBAL %%CONF1    
  %%ENDIF             
  %%IF *%%CONF2 NE *
  %%GLOBAL %%CONF2    
  %%ENDIF             
  %%IF *%%CONF3 NE *
  %%GLOBAL %%CONF3    
  %%ENDIF             
  %%IF *%%CONF4 NE *
  %%GLOBAL %%CONF4    
  %%ENDIF            

• The MEMLIB parameter of each job scheduling definition in the table must point to the Daily JCL library. The library name is suffixed by the AutoEdit date variables.

  Example

  CTM.PROD.JCLP%%OMONTH.%%ODAY

• Occurrence numbering:

  It is recommended that all AutoEdit parameter names of jobs in the same plan be unique. In some plans, duplicate names may be unavoidable, and more than one job may share the same AutoEdit parameter name. If the parameters are to be assigned different values, that is, used for different purposes, each parameter must be assigned a different OCCUR NO during definition of the Master Prompting Plan.

  A %%SET statement specifying the OCCUR NO. must be included in the JCL of the associated jobs as follows:

  %%SET %%OC# = 01

  When the AutoEdit parameter member is created, each AutoEdit parameter includes the OCCUR NO. as a suffix.

• Using the Parameter Prompting facility – Type 2 requires customizing the Control-M submit exit (CTMX002). This exit does the following:
  • It ensures that at the time when the job is submitted, the AutoEdit Parameters library contains the PLANID member.
  • It places in the PLANID member an AutoEdit variable definition in the form

    %%PLANID=plan_id

    in order to provide the job with a unique identity (plan_id). This is done using an OUT condition in the job scheduling definition, as described in the source code of the exit.

  For information about modifying the exit, see the CTMX2PPF member in the IOA SAMPEXIT library.