OS Job
- Kathleen Avery (Deactivated)
- Select Planning, Then Blank Workspace(Top left or Far right):
2. Top Left, there are options/templates. Drag “OS” to the blank workspace.
3. Right click on the folder and select properties.
4. Fill in a meaningful Folder Name – Usually the environment (UAT or PRD), followed by the Application (KFS, ETL, PSOFT, etc) followed by a meaningful name.
5. If this will be a SMART folder, select that option (Upper right).
If not, choose the order method from the Drop down.
6. Press OK.
7. Right click on the job and select properties.
8. Result: Note anything highlighted in RED is a required field.
9. In the General Tab, fill in a meaningful job name and an optional description.
10. Under the What section, choose an option.
If Script is chosen fill in the File Path and File Name.
If Command is chosen, fill in the command.
If Embedded Script is chosen, fill in the Script commands and the File Name.
In this example, I chose Command.
11. From the drop down, select a host/host Group.
12. Fill in Run As. This is the username you will use to execute the script, command or embedded script. Usually kfsctmuser (the control-M user id).
13. Fill in Parent Folder, Application, and Sub Application. The Parent Folder and Sub Application should have the same name. The Application is usually the Schedule Name. It can be left blank for a stand-alone job.
The remaining entries on this Tab can be ignored.
14. Scheduling Tab – This is where you specify when you want the job to run. Most cases a Rule-based calendar is used, since this type of calendar does not have to be reloaded for a new year. You can set the job to run at a specific time, using the Time Settings.
15. Prerequisites Tab – This is where the Job Dependencies are set up.
Select Requires user confirmation.
Fill in the In Conditions – these are the dependencies.
Ignore Control Resources.
Set Quantitative Resources - Resource Name to INITIATOR.
16. Actions Tab is used to create instructions for when a job fails or to send notifications on successful or unsuccesful completion (failures). Note that when notifying more than one person or group, the email addresses must be separated by a semi-colon.
ENDED-OK means the job ran successfully.
ENDED means the job failed.
If the job fails (NOTOK), it does not post a condition. Out conditions are needed to notify users that the job failed.
If there is going to be an Out Condition, press the blue + sign. Fill in the condition name as follows:
Jobname-ENDED-OK--%%TABLE_ID
Ex. UAT-KFS-Kathy-Test-ENDED-OK-%%TABLE_ID
Press Add.
If more Conditions, press the blue + sign again and repeat above step.
17. Notifications before job completion – If you want to notify a user or group of users before the job executes, the conditions can be entered here similar to the Out Conditions above.
Press OK.
May add additional notifications by pressing the blue + sign
18. On Do Actions – Press blue + sign
On: Select Job ended Not OK
Do: Select Add/Remove Condition from Drop down
Name: %%JOBNAME–ENDED
Date: Order Date
Sign: Add
To add additional ON Do Actions, Select Add Do button on the upper left corner
Press OK.
19. Press OK. Job is created.
20. Press Check In (Top Left) to save changes.
