Search BMC.com
Search

Share: |


Promotion of Jobs Across Multiple Environments

When multiple environments (production, QA, test, etc) exist and are of the same release level (another best practice!) you can use the Find and Update functionality to make changes and then save to a portable file (drf or xml).   You can access Find and Update in Control-M/Desktop from the Edit menu.  Here is a screen shot showing just some of the powerful string match and update capabilities available with Find and Update. 

fau.jpg

 

After you have made changes you can save the resulting definitions to a drf or xml file and load that file into a different Control-M environment.  If you regularly make the same updates (like changing various fields from test to prod or dev to qa) enter them one time then save those values in the Presets pulldown.  The next time you need to make identical updates (or similar ones) you can load the previously saved preset.  This could save you a lot of time and reduce the chance of typos.  Another option would be to use the exportdefjob command to export job data to an xml file which can then be modified and import into another Control-M environment using the defjob command.  Using the latter method allows you to perform the promotion in a scripted fashion if you so choose.

 

Return Code/Sysout Text String Checking

In the Steps tab of a job in the JEF you can code jobs to take some automated action based upon the return code the job returns or the appearance of text strings in the sysout file of a job.  Some of the actions available are to: mark a job as ok or notok, generate a shout, send an email, open a Remedy ticket or force in a recovery job. To set this up based upon return codes enter the following on the steps tab of the job:

On Statement   Stmt=*                            Code=COMPSTAT=4

Do OK

The above example marks a job that ends with a completion status of 4 to be OK (successful) as opposed to the default behavior in this case which would have marked the job NOTOK (failed). 

Note: Check the OSCOMPSTAT value in the log to determine the completion status of the job.

 

To set this up based upon a string in the sysout file enter:

On Statement   Stmt=*                            Code=*ERROR*

Do NOTOK

The above example marks a job that ends with the text string ERROR somewhere in the sysout file to NOTOK (failed) regardless of the job’s return code.

 

Steps.jpg

Filter Blog

By date:
By tag:
It's amazing what I.T. was meant to be.