|
|
|
|
|
Defines the name of the job processing definition and appears in the job definition and tracking displays, and enables you to identify the job, and order the job.
Additional information |
Description |
|---|---|
Usage |
Mandatory |
Length |
1-64 characters z/OS: 1-8 characters |
Case Sensitive |
Yes |
Invalid Characters |
|
Variable Name |
%%JOBNAME |
Alternate Names |
|
Computer specific information |
|
IBM i (AS/400) |
The value specified for this parameter is the actual job name to be used by IBM i (AS/400). It is part of the job submission command. NOTE: For jobs on an IBM i (AS/400) computer, the value specified for the Job Name parameter must conform to IBM i (AS/400) conventions for job names. |
The Job Name can also be displayed in the job node displayed in the Control‑M/EM window (depending upon options specified in the Display Net window). This parameter is used when ordering or forcing a job, either using the Order Job (Ignore Scheduling Criteria) parameter or when using the Order/Force windows. You can define a job without a job name in ctmcreate and ctmdefine.
Job naming standards are a must for every successful implementation of Control-M as the design phase of Control-M is predicated on solid, enforceable naming standards.While there is no set standard for job naming, a good rule-of-thumb is that all jobs start with the application moniker. Next, a few characters to describe the job’s function may be included and finally a few characters to describe the specific purpose, destination or process the job performs.
EXAMPLE: AAA – for application moniker, such as DDA, SAV, MTG, LOA
TTT – for job type, such as AFT, SAP, WIN, UNX, WJM, DBA
FFFFFFF – such as POSTING, BACKUP, DBLOAD
Well-thought naming conventions are the basis for identifying the job and its function; managing access for security, change and problem management as well as reporting. Using this job naming format, Control-M access control can be designed around the job name. Control-M security can restrict or allow access to the application based on the user’s role and responsibility.
For change management, users authorized to access DDA in a read-only mode can be defined, where as another user can be given full access to define, manage and monitor DDA jobs but not restart them and still, a third user can be given access to monitor and restart/override jobs but not update the jobs’ definitions.
Accessing/modifying the Job Name in Variable expressions: The value of the Job Name parameter can be accessed using the %%JOBNAME variable. For example, this name can be included in a message that is sent using the Notify parameter. The Job Name parameter can also be overridden when the job is ordered, for example, by using the following statement in the command line of the ctmorder utility for Control‑M/Server.
EXAMPLE:-variable %%JOBNAME newjobname
Parent Topic |