updatedef

This utility has been deprecated. It is no longer enhanced and support will be discontinued in version 9.0.22. For more information, see emdef Utility Suite Deprecation.

The updatedef utility updates specified parameter values in the following definitions in the Control‑M/EM database:

  • Job processing definitions

  • Folder definitions

  • SMART folder definitions

  • Sub Folder definitions

The selected jobs, folders, SMART folders and Sub Folders are modified according to specifications in the updatedef arguments file. For more information, see updatedef XML file rules.

updatedef modifies the characteristics of existing job processing definitions, but does not create new jobs or folders. duplicatedefjob creates new job processing definitions based on existing job processing definitions from the data center and folders.

For an example of the two validation processes see emdef Validation Service Error Message Example.

Updating Parameter Values Using the updatedef Utility

This procedure describes how to update specified parameter values in the Control‑M/EM database using the updatedef utility.

Begin

  1. Do one of the following:

    • UNIX: Log in to a Control-M/EMaccount.

    • Windows: Open a command prompt window where Control-M/EM is installed. You do not need to be in the Control-M/EM database directory.

      For Windows client installations, open a command prompt window and navigate to the <EM Instance Name>\bin directory

  2. Enter either of the following commands:

    • emdef updatedef [-USERNAME <user> [-PASSWORD <password>] | -PASSWORD_FILE <password file>] -HOST <GUI Server Name> -ARG_FILE <XML file name> [/a] [-vv 2]

    • emdef updatedef [-u <user> [-p <password>] | -pf <password file>] -s <GUI Server Name> -arg <XML file name> [/a] [-vv 2]

      For Windows you do not need to use the emdef prefix.

For details about the updatedef parameters and switches, see emdef General Parameters and emdef Switches.

updatedef XML File Rules

The following rules apply to the updatedef arguments file:

  • Only one block of criteria can be specified for updating in each arguments file. This criteria block can update many jobs or folders.

  • Text in the arguments file is case-sensitive.

  • All parameter values must be enclosed in quotation marks (for example, JOBNAME="Job1").

Multiple values can be specified for TO and FROM by using the * wildcard character. For an explanation of how wildcards function in the XML-based utilities, see Wildcards.

For instructions about preparing this file, see XML File Rules.

Most parameters of the job, folder, SMART folder or Sub Folder definitions are optional. However:

  • If you specify a parameter, the FROM subparameter is mandatory, but the TO subparameter is optional.

  • When a FROM value is specified without a TO value, the FROM value is used as a filter criterion.

  • When a TO value is included, the new value parameter is set.

SMART folder parameters are usually modified using the SMART folder criteria described in updatedef XML file parameters for SMART folders. However, you cannot use these criteria to change the name of a SMART folder.

The folder name parameter of a job processing definition cannot be modified using the job definition criteria described in updatedef XML file parameters for jobs. However, you can use the updatedef utility to change the name of a SMART folder or folder by using the criteria for folders (described in updatedef XML File Parameters for Folders) and specifying a new value for the FOLDER_NAME parameter.

Three sets of parameters can be supplied in an arguments file – one each for folders, SMART folders, and jobs. Each set of parameters is described in:

updatedef XML File Parameters for Folders

The following table lists the updatedef XML input file parameters for folders:

The first two lines of the arguments file specify the XML version, the text encoding format being used, and the location of the .dtd file.

Parameter

Description

UPDATE

Indicates the start and end of the UPDATE argument. Only criteria located between the tags are considered to be part of the argument.

FOLDER

Indicates the start and end of the folder specification. Criteria identifying the folders to be modified and indicating the types of modifications to be made are located between these tags.

FOLDER_NAME

Defines the name of the folder that the job belongs to.

FOLDER_NAME FROM="Tbl5NYC" TO="Tbl_new"

FOLDER_DSN

(z/OS only) Defines the name of the library that contains the (scheduling) folder.

ABLE_DSN FROM="Lib1" TO="Lib2"

DATACENTER

Defines the name of the Control-M installation to which the job belongs.

A TO parameter cannot be specified for this parameter.

DATACENTER FROM="CTMNYC"

CYCLIC_TYPE

Determines the type of cyclic job.

Valid Values:

  • Interval

  • IntervalSequence

  • SpecificTimes

CYCLIC_TOLERANCE

Determines the maximum delay in minutes permitted for a late submission when selecting a specific time.

CYCLIC_INTERVAL_SEQUENCE

Defines a list of time intervals, separated by commas, of up to 4000 characters.

+30M,+2H,+1D

CYCLIC_TIMES_SEQUENCE

Defines a list of time intervals represented by hour of the day, separated by commas, of up to 4000 characters.

0800,1330,2300

updatedef XML File Parameters for Jobs

The following table lists the arguments file parameters for jobs:

The first two lines of the arguments file specify the XML version, the text encoding format being used, and the location of the .dtd file.

Parameter

Description
UPDATE

Indicates the start and end of the UPDATE argument. Only criteria that are located between the tags are considered to be part of the argument.

JOB

Indicates the start and end of each job specification. Criteria identifying the jobs to be modified and indicating the types of modifications to be made are located between these tags.

FOLDER_NAME

Defines the name of the folder where the job belongs.

This parameter cannot be modified.

FOLDER_NAME FROM="Tbl5NYC"

FOLDER_DSN

(z/OS only) Defines the name of the library that contains the (scheduling) folder.

This parameter cannot be modified.

FOLDER_DSN FROM="Lib1"

DATACENTER

Defines the name of the Control-M installation where the job belongs.

This parameter cannot be modified.

DATACENTER FROM="CTMNYC"

FOLDER_ORDER_METHOD

Optional.

This parameter cannot be modified.

FOLDER_ORDER_ METHOD FROM="Job3"

JOBNAME

Defines the name of the job processing definition.

JOBNAME FROM="Job3" TO="Job3_COPY"

FILE_NAME

Name of the file that contains the job script.

FILE_NAME FROM="File3" TO="File7"

SUB_APPLICATION

Defines the name of the group where the job belongs.

GROUP FROM="Grp_HR"

APPLICATION

Defines the name of the application where the job group belongs.

APPLICATION FROM="App3" TO="App1"

TASKTYPE

Defines the type of the job (task) to be performed by Control-M.

TASKTYPE FROM="Detached" TO="Dummy"

FROM: Mandatory.

Valid Values:

  • Job

  • Detached

  • Command

  • Dummy

  • External

  • (z/OS only) Job

  • (z/OS only) Started_Task

TO: Optional.

Valid Values: Same as FROM.

CREATED_BY

Defines the Control‑M/EM user who created the job.

This argument is used by the Control‑M/Server security mechanism and, under certain circumstances, cannot be modified. For more information, see the Security chapter and the description of the AuthorSecurity system parameter in GUI Server parameters.

EXAMPLE: CREATED_BY FROM="emuser" TO="em5"

FILE_PATH

Defines the name of the library/directory where the job script resides.

FILE_PATH FROM="File1" TO="File4"

CMDLINE

Describes the command string supplied when the job Task Type is Command.

CMDLINE FROM="C:\Format" TO="C\:CD Emnt"

HOSTID

Host name of an Agent computer or host group to which the job is submitted. Optional.

HOSTID FROM="Com3" TO="Acct4"

TO: Host name of the Agent computer where the job copy is running.

RUN_AS

Defines the owner (user ID) associated with the job. This parameter is used by the Control-M/Serversecurity mechanism.

OWNER FROM="emuser" TO="emhr"

MAXRERUN

Determines the maximum number of reruns that can be performed for the job.

MAXRERUN FROM="1" TO="3"

TIMEFROM

Determines the earliest time for submitting the job.

TIMEFROM FROM="1430" TO="1450"

TIMETO

Determines the latest time for submitting the job.

TIMETO FROM="1600" TO="1620"

DUE_OUT

Determines the time expected for the job to finish.

DUE_OUT FROM="1500" TO="1530"

PRIORITY

Indicates Control-M job priority.

PRIORITY FROM="AA" TO="1A"

CRITICAL

Indicates whether the job is a critical-path job in Control-M.

CRITICAL FROM="0" TO="1"

FROM: Mandatory.

Valid Values:

  • 0: No

  • 1: Yes

Default: 0

TO: Optional.

Valid Values:

  • 0: No

  • 1: Yes

Default: 0

CYCLIC

Indicates whether the job runs at regular intervals.

CYCLIC FROM="0" TO="1"

FROM: Mandatory.

Valid Values:

  • 0: No

  • 1: Yes

Default: 0

TO: Optional.

Valid Values:

  • 0: No

  • 1: Yes

Default: 0

CONFIRM

Indicates that the job must be manually confirmed by the Control‑M/EM user before it runs.

CONFIRM FROM="0" TO="1"

FROM: Mandatory.

Valid Values:

  • 0: No

  • 1: Yes

Default: 0

TO: Optional.

Valid Values:

  • 0: No

  • 1: Yes

Default: 0

AUTOARCH

Determines whether SYSDATA is to be archived.

AUTOARCH FROM=0" TO="1"

FROM: Mandatory.

Valid Values:

  • 0: No

  • 1: Yes

Default: 0

TO: Optional.

Valid Values:

  • 0: No

  • 1: Yes

Default: 0

INTERVAL

Determines the time in minutes to wait between reruns of a job or between cyclic runs of a job.

INTERVAL FROM="3" TO="4"

OVERRIDE_PATH

Defines the name of an alternate job script library/directory.

OVERRIDE PATH FROM="lib3" TO="lib4"

MAXWAIT

Determines the number of extra days after the original scheduling date that the job is allowed to remain in the Active Jobs database awaiting execution.

MAXWAIT FROM="4" TO="3"

DESCRIPTION

Describes the job.

DESCRIPTION FROM="data backup from 120399" TO="data backup from 021400"

DOCMEM

Defines the name of the file containing job documentation.

DOCMEM FROM="mem4" TO="Mem67"

DOCLIB

Defines the name of a library or directory containing the job documentation file.

DOCLIB FROM="AcctFiles" TO="HRFiles"

DAYS

Determines the days of the month to order the job.

DAYS FROM="ALL" TO="159"

DAYS_AND_OR

Indicates the relationship between specified Days values and Weekdays values.

DAYS_AND_OR FROM="AND" TO="OR"

WEEKDAYS

Determines the days of the week to order the job.

WEEKDAYS FROM="1,2,4" TO="ALL"

DATE

Specifies dates to order the job. mmdd format.

DATE FROM="0312" TO="0319"

DAYSCAL

Identifies a user-defined calendar.

DAYSCAL FROM="shipping" TO="receiving"

WEEKSCAL

Defines the name of a calendar to be used to validate specified weekdays to order the job.

WEEKSCAL FROM="w5" TO="w6"

CONFCAL

Specifies a calendar that is used to validate all specified days and dates to schedule the job.

CONFCAL FROM="cal99" TO="cal00"

RETRO

Indicates whether the job is scheduled for possible execution after its original scheduling date (odate) has passed.

RETRO FROM="0" TO="1"

FROM: Mandatory.

Valid Values:

  • 0: No

  • 1: Yes

Default: 0

TO: Optional.

Valid Values:

  • 0: No

  • 1: Yes

Default: 0

SHIFT

Describes how to shift the scheduling date of the job.

SHIFT FROM="PREVDAY" TO="NEXTDAY"

FROM: Mandatory.

Valid Values:

  • IGNOREJOB

  • PREVDAY

  • NEXTDAY

  • NOCONFCAL

TO:

Valid Values: Same as FROM.

SHIFTNUM

Determines the number of days to shift the scheduling date of the job.

SHIFTNUM FROM="-10" TO="5"

MAXDAYS

Determines the maximum number of days to retain the SYSDATA archive dataset for jobs that ended NOTOK. Subparameter of AUTOARCH.

MAXDAYS FROM="07" TO="14"

MAXRUNS

Determines the maximum number of job runs to retain the SYSDATA archive dataset for jobs that ended NOTOK. Subparameter of AUTOARCH.

MAXRUNS FROM="100" TO="250"

RERUNMEM

Defines the name of the JCL member to use when the job is automatically rerun. 1 - 8 characters.

RERUNMEM FROM="Mem45" TO="Mem7"

RETEN_DAYS

(z/OS only) Determines the number of days to retain the job in the History Jobs file.

RETEN_DAYS FROM="5" TO="7"

RETEN_GEN

(z/OS only) Determines the maximum number of generations of the job to keep in the History Jobs file.

RETEN_GEN FROM="3" TO="4"

TASK_CLASS

TASK_CLASS FROM="Distribution" TO="Decollation"

PREV_DAY

PREV_DAY FROM="N" TO="Y"

FROM: Mandatory.

Valid Values:

  • Y

  • N

TO: Optional

Valid Values:

  • Y

  • N

IND_CYCLIC

Indicates whether the interval between further runs of a cyclic job is counted from the start or the end of the previous job run.

IND_CYCLIC FROM="Y" TO="N"

FROM: Mandatory.

Valid Values:

  • START

  • END

TO: Optional

Valid Values:

  • START

  • END

RULE_BASED_CALENDAR_RELATIONSHIP

Describes the relationship (AND|OR) between the specified Rule-Based Calendar and the basic scheduling criteria of the job.

RULE_BASED_CALENDAR_RELATIONSHIP FROM="AND" TO="OR"

FROM: Mandatory.

Valid Values:

  • AND

  • OR

TO: Optional

Valid Values:

  • AND

  • OR

TAG_RELATIONSHIP

Describes the relationship (AND|OR) between the specified Schedule Tag criteria and the basic scheduling criteria of the job. This parameter is only relevant for jobs in a SMART folder. This parameter is for backward compatibility.

TAG_RELATIONSHIP FROM="AND" TO="OR"

FROM: Mandatory.

Valid Values:

  • AND

  • OR

TO: Optional.

Valid Values:

  • AND

  • OR

SYSDB

Determines whether one or multiple data sets are used to catalogue sysdata.

SYSDB FROM="1" TO="0"

FROM: Mandatory.

Valid Values:

  • AND

  • OR

TO: Optional.

Valid Values:

  • AND

  • OR

PDSNAME

Defines the name of a partitioned dataset (PDS) to be checked for free space.

PDSNAME FROM="Lib_3" TO="Lib_5"

MINIMUM

Defines the name of a partitioned dataset (PDS) to be checked for free space.

PDSNAME FROM="Lib_3" TO="Lib_5"

CATEGORY

Defines the name of a Control-D report decollating mission category that must be scheduled under Control-D when the job is scheduled under Control-M.

CATEGORY FROM="*" TO="DAILY"

PREVENTNC2

(z/OS only) Performs dataset clean up before the original job run.

PREVENTNC2 FROM="1" TO="0"

FROM: Mandatory.

Valid Values:

  • 0

  • 1

Default: 0

TO: Optional.

Valid Values:

  • 0

  • 1

Default: 0

JAN, FEB, MAR,

APR, MAY, JUN,

JUL, AUG, SEP,

OCT, NOV, DEC

Determines the months when the job runs.

JAN FROM="0" TO="1"

FROM: Mandatory.

Valid Values:

  • 0

  • 1

Default: 0

TO: Optional.

Valid Values:

  • 0

  • 1

Default: 0

OPTION

Describes the job output handling options.

OPTION FROM="Copy" TO="Release"

FROM: Mandatory.

Valid Values:

  • Release

  • Delete

  • Copy

  • Move

  • File

  • NewDest

  • ChangeClass

TO: Optional.

Valid Values: Same as FROM.

PAR

Holds certain OPTION values that require that you supply additional information, such as Release, NewDest.

PAR FROM="mem3log" TO="mem5log"

FROM

Limits the OUTPUT handling operation to OUTPUTs from the specified class.

FROM FROM="1" TO="2"

ADJUST_COND

Indicates whether to ignore prerequisite conditions normally set by predecessor jobs if the relevant predecessor jobs are not scheduled. This parameter is only relevant for jobs in a SMART folder.

Valid Values:

  • 0: Do not ignore.

  • 1: Ignore relevant prerequisite conditions

    Default: 0

ADJUST_COND FROM="1" TO="0"

APPL_TYPE

Defines the external application, such as SAP or Oracle, where the external application job runs. Mandatory for external application jobs. Up to 10 characters.

APPL_TYPE FROM="SAP" TO="OracleApps"

APPL_VER

Defines the version of the external application, such as SAP or Oracle, where the external application job runs. Mandatory for external application jobs. Up to 10 characters.

APPL_VER FROM="4.5" TO="4.6"

APPL_FORM

Defines a predefined set of external application parameters that are displayed in the Job Properties team. Mandatory for external application jobs. Up to 30 characters.

APPL_FORM FROM="Default SAP 4.6" TO="Default SAP 4.5"

CM_VER

Defines the version of the external Application Add-on, such as SAP or Oracle, that is installed in the Control-M installation. Mandatory for external application jobs. Up to 10 characters.

CM_VER FROM="6.1.00" TO="6.1.01"

MULTY_Agent

Broadcasts job submission details to all Agents in a specified Host Group.

MULTY_Agent FROM="N" TO="Y"

FROM: Mandatory.

Valid Values:

  • Y: run as a multi-Agent job.

  • N: do not run as a multi-Agent job.

Default: N

ACTIVE_FROM

(z/OS only) Indicates the start of a period of time during which the job or SMART folder can be ordered.

Date Format: YYYYMMDD

ACTIVE_FROM FROM="20080315" TO="20080601"

ACTIVE_TILL

(z/OS only) End of a period of time during which the job or SMART folder can be ordered

Date Format: YYYYMMDD

ACTIVE_TILL FROM="20080315" TO="20080601"

TIMEZONE

Determines the global time zone used to calculate the interval for time-related conditions.

Default: GMT

TIMEZONE FROM="EST" TO="GMT"

CREATION_USER

Defines the name of the user that created the job.

CREATION_USER FROM="emuser" TO="em1"

CREATION_DATE

Determines the date that the job was created.

CREATION_DATE FROM="1212" TO="2012"

CREATION_TIME

Determines the time that the job was created.

CREATION_TIME FROM="1230" TO="1430"

CHANGE_USERID

Name of the user that last modified the job.

CHANGE_USERID FROM="emuser" TO="emacct"

CHANGE_DATE

Determines the date that the job was last modified.

CHANGE_DATE FROM="1204" TO="1304"

CHANGE_TIME

Determines the time that the job was last modified.

CHANGE_TIME FROM="1650" TO="1700"

updatedef XML File Parameters for SMART Folders

The following table lists the arguments file parameters for SMART folders:

The first two lines of the arguments file specify the XML version, the text encoding format being used, and the location of the .dtd file.

Parameter Description

UPDATE

Indicates the start and end of the UPDATE argument. Only criteria located between the tags are considered to be part of the argument.

SMART_FOLDER

Defines the name of the SMART folder.

  • This parameter cannot be modified.

  • At least one of the following folder parameters must be included in the input file:

    • DATACENTER

    • FOLDER_NAME

    • FOLDER_DSN

FOLDER_NAME FROM="Tbl42"

FOLDER_NAME

Defines the name of the Control-M installation to which the job belongs.

  • A TO subparameter cannot be specified for this parameter.

  • At least one of the following folder parameters must be included in the input file:

    • DATACENTER

    • FOLDER_NAME

    • FOLDER_DSN

EXAMPLE: DATACENTER FROM="CTMNYC"

DATACENTER

Defines the name of the Control-M installation to which the job belongs.

  • A TO subparameter cannot be specified for this parameter.

  • At least one of the following folder parameters must be included in the input file:

    • DATACENTER

    • FOLDER_NAME

    • FOLDER_DSN

DATACENTER FROM="CTMNYC"

FOLDER_DSN

(z/OS only)Defines the name of the library that contains the SMART folder.

  • A TO subparameter cannot be specified for this parameter.

  • At least one of the following folder parameters must be included in the input file:

    • DATACENTER

    • FOLDER_NAME

    • FOLDER_DSN

FOLDER_DSN FROM="CTMNYC"

FOLDER_ORDER_ METHOD

A TO subparameter cannot be specified for this parameter.

FOLDER_ORDER_ METHOD FROM="CTMNYC"

SUB_APPLICATION

Defines the name of the group to which the SMART folder belongs. Used as a descriptive name for related folders.

GROUP FROM="Grp_HR" TO="Grp_ACCT"

USED_BY

USED_BY FROM="fff" TO="ffg"

USED_BY_CODE

USED_BY_CODE FROM="C***" TO="D***"

MODIFIED

MODIFIED FROM="1101" TO="1102"

LAST_UPLOAD

Determines the date of the last folder upload.

LAST_UPLOAD FROM="1101" TO="1102"

CHECKSUM

CHECKSUM FROM="Y" TO="N"

FOLDER_ID

Defines the name of the folder where the job belongs.

FOLDER_ID FROM="Tbl001" TO="Tbl002"

REAL_FOLDERID

REAL_FOLDERID FROM="43556" TO="43557"

JOBNAME

Defines the name of the job processing definition.

JOBNAME FROM="Job3"

FILE_NAME

Defines the name of the file that contains the job script. Optional.

FILE_NAME FROM="File3" TO="File7"

APPLICATION

Defines the name of the application to which the job’s group belongs. Used as a descriptive name for related jobs.

APPLICATION FROM="App3""

RUN_AS

Defines the owner (user ID) associated with the job. This parameter is used by the Control-M/Server security mechanism.

OWNER FROM="emuser" TO="emhr"

ADJUST_COND

Indicates whether to ignore prerequisite conditions normally set by predecessor jobs if the relevant predecessor jobs are not scheduled.

Valid Values:

  • 0: Do not ignore.

  • 1: Ignore relevant prerequisite conditions

Default: 0

ADJUST_COND FROM="1" TO="2"

CONFIRM

Indicates whether the job must be manually confirmed by the Control‑M/EM user before it runs.

CONFIRM FROM="0" TO="1"

FROM: Mandatory.

Valid Values:

  • 0

  • 1

Default: 0

TO: Optional.

Valid Values:

  • 0

  • 1

Default: 0

PRIORITY

Indicates Control-M job priority. Two-character alphanumeric from 00 to ZZ.

PRIORITY FROM="AA" TO="BB"

TIMEFROM

Indicates the earliest time for submitting the SMART folder. Format: HHMM.

TIMEFROM FROM="1430" TO="1450"

TIMETO

Indicates the latest time for submitting the SMART folder. Format: HHMM

TIMETO FROM="1430" TO="1450"

DUE_OUT

Determines the time that the job is expected to finish.

DUE_OUT FROM="1500" TO="1750"

DOCMEM

Defines the name of the file containing job documentation.

DOCMEM FROM="mem4" TO="Mem67"

DOCLIB

Defines the name of a library or directory containing the job documentation file.

DOCLIB FROM="AcctFiles" TO="HRFiles"

DESCRIPTION

Describes the job in free text.

DESCRIPTION FROM="backup jobs from 120399" TO="backup jobs from 021400"

CREATED_BY

Defines the Control‑M/EM user who created the job.

CREATED_BY FROM="emuser" TO="emadmin"

The New Day Procedure compares the Author and Owner for each job to check if the job’s user has authorization to submit the job. Control-M/EM security levels determine who can edit the Author value (any user or administrators only). For more information, see the Security chapter and the description of the AuthorSecurity system parameter in GUI Server parameters.

CREATION_USER

Defines the name of the user that created the job.

CREATION_USER FROM="emuser" TO="em1"

CREATION_DATE

Determines the date that the SMART folder was created. Format: DDMM.

CREATION_DATE FROM="1212" TO="2012"

CREATION_TIME

Determines the time that the SMART folder was created. Format: HHMM.

CREATION_TIME FROM="1230" TO="1430"

CHANGE_USERID

Defines the name of the user that last modified the SMART folder.

CHANGE_USERID FROM="emuser" TO="emadmin"

Modify SMART_FOLDER Parameter XML File Example

From the updatedef XML file, in the TEST data center, the SMART folder name FOLDER UNIXJobs is changed to FOLDER TandemJobs.

Copy 
<UPDATE>
<SMART_FOLDER>
<DATACENTER FROM="TEST"/>
<FOLDER FROM="UNIXJobs" TO="TandemJobs"/>
</SMART_FOLDER>
</UPDATE>

Modify Folder Name Parameter XML File Example

From the updatedef XML file, in the TEST data center, for jobs with FOLDER_ID 12202, the folder name is changed from Tbl_1 to Tbl_2.

Copy 
<UPDATE>
<FOLDER>
<DATACENTER FROM="TEST"/>
<FOLDER_ID FROM="12202"/>
<FOLDER_NAME FROM="Tbl_1" TO="Tbl_2"/>
</FOLDER>
</UPDATE>

Modify the Sub-folder Parameter XML File Example

In the updatedef XML file:

Copy 
<UPDATE>
<SUB_FOLDER>
<FOLDER_NAME FROM="Ref1"/>
<DATACENTER FROM="*"/>
<JOBNAME FROM="SubRef1" TO="SubRef1Updated"/>
</SUB_FOLDER>
</UPDATE>

Modify the Job Name of a Job XML File Example

In the updatedef XML file:

Copy 
<UPDATE>
<JOB>
<FOLDER_NAME FROM="SGMPM1"/>
<!-- <FOLDER_DSN FROM=""/> -->
<DATACENTER FROM="snow"/>
<JOBNAME FROM="cnn*" TO="bbc*"/>
<!-- <FILE_NAME FROM="Job2"/>-->
<!-- <SUBAPPLICATION FROM=""/> -->
<!-- <APPLICATION FROM=""/> -->
<!-- <TASKTYPE FROM=""/> -->
<!-- <CREATED_BY FROM=""/> -->
<!-- <MEMLIB FROM=""/> -->
<!-- <CMDLINE FROM="*end" TO="THE END *"/>-->
<!-- <HOSTID FROM=""/> -->
<!-- <RUN_AS FROM=""/> -->
<!-- <MAXRERUN FROM=""/> -->
<!-- <TIMEFROM FROM=""/> -->
<!-- <TIMETO FROM=""/> -->
<!-- <DUE_OUT FROM=""/> -->
<!-- <PRIORITY FROM=""/> -->
<!-- <CRITICAL FROM=""/> -->
<!-- <CYCLIC FROM=""/> -->
<!-- <CONFIRM FROM=""/> -->
<!-- <AUTOARCH FROM=""/> -->
<!-- <INTERVAL FROM=""/> -->
<!-- <OVERRIDE_PATH FROM=""/> -->
<!-- <MAXWAIT FROM=""/> -->
<!-- <DESCRIPTION FROM=""/> -->
<!-- <DOCMEM FROM="docmem"/> -->
<!-- <DOCLIB FROM="doclib"/>-->
<!-- <DAYS FROM=""/> -->
<!-- <DAYS_AND_OR FROM=""/> -->
<!-- <WEEKDAYS FROM=""/> -->
<!-- <DATE FROM=""/> -->
<!-- <DAYSCAL FROM=""/> -->
<!-- <WEEKSCAL FROM=""/> -->
<!-- <CONFCAL FROM=""/> -->
<!-- <RETRO FROM=""/> -->
<!-- <SHIFT FROM=""/> -->
<!-- <SHIFTNUM FROM=""/> -->
<!-- <MAXDAYS FROM=""/> -->
<!-- <MAXRUNS FROM=""/> -->
<!-- <RERUNMEM FROM=""/> -->
<!-- <RETEN_DAYS FROM=""/> -->
<!-- <RETEN_GEN FROM=""/> -->
<!-- <TASK_CLASS FROM=""/> -->
<!-- <PREV_DAY FROM=""/> -->
<!-- <IND_CYCLIC FROM=""/> -->
<!-- <RULE_BASED_CALENDAR_RELATIONSHIP FROM=""/> -->
<!-- <SYSDB FROM=""/> -->
<!-- <PDSNAME FROM=""/> -->
<!-- <MINIMUM FROM=""/> -->
<!-- <CATEGORY FROM=""/> -->
<!-- <PREVENTNCT2 FROM=""/> -->
<!-- <JAN FROM=""/> -->
<!-- <FEB FROM=""/> -->
<!-- <MAR FROM=""/> -->
<!-- <APR FROM=""/> -->
<!-- <MAY FROM=""/> -->
<!-- <JUN FROM=""/> -->
<!-- <JUL FROM=""/> -->
<!-- <AUG FROM=""/> -->
<!-- <SEP FROM=""/> -->
<!-- <OCT FROM=""/> -->
<!-- <NOV FROM=""/> -->
<!-- <DEC FROM=""/> -->
<!-- <OPTION FROM=""/> -->
<!-- <PAR FROM=""/> -->
<!-- <FROM FROM=""/> -->
<!-- <ADJUST_COND FROM=""/> -->
<!-- <JOBS_IN_GROUP FROM=""/> -->
<!-- <LARGE_SIZE FROM=""/> -->
<!-- <CREATION_USER FROM=""/> -->
<!-- <CREATION_DATE FROM=""/> -->
<!-- <CREATION_TIME FROM=""/> -->
<!-- <CHANGE_USERID FROM=""/> -->
<!-- <CHANGE_DATE FROM=""/> -->
<!-- <CHANGE_TIME FROM=""/> -->
<!-- <JOB_RELEASE FROM=""/> -->
<!-- <JOB_VERSION FROM=""/> -->
<!-- <FOLDER_ORDER_ METHOD FROM=""/> -->
<!-- <SCHEDULING_ENVIRONMENT FROM=""/> -->
<!-- <SYSTEM_AFFINITY FROM=""/> -->
<!-- <REQUEST_NJE_HOST FROM=""/> -->
<!-- <APPL_TYPE FROM=""/> -->
<!-- <APPL_VER FROM=""/> -->
<!-- <APPL_FORM FROM=""/> -->
<!-- <CM_VER FROM=""/> -->
<!-- <MULTY_Agent FROM=""/> -->
<!-- <ACTIVE_FROM FROM=""/> -->
<!-- <ACTIVE_TILL FROM=""/> -->
<!-- <TIMEZONE FROM=""/> -->
</JOB>
</UPDATE>