Job Control

[Bhusan]

I am curious to know how the job name of a job that has only job control routine contains "::" (two colons). For example, the name of the job is Batch::XXXXXXX.

Can any one please help me as to how this name is given.

Thanks.

[chulett]

It's automatic and a remnant of the old way of doing Job Control.

Go into Director and from the Status view, pull down the 'Tools' menu. You'll see an entry for 'Batch' and then the option to create a 'New...' one. It will look just like the Job Properties tab of a 'normal' job in Designer, but won't have the GUI part. You enter the job control code here by hand and then when you click 'Ok' to close it, it will automatically compile. Whatever name you gave it when you created it will automatically have the "Batch::" prefix added to it.

[Bhusan]

It's automatic and a remnant of the old way of doing Job Control.

Go into Director and from the Status view, pull down the 'Tools' menu. You'll see an entry for 'Batch' and then the option to create a 'New...' one. It will look just like the Job Properties tab of a 'normal' job in Designer, but won't have the GUI part. You enter the job control code here by hand and then when you click 'Ok' to close it, it will automatically compile. Whatever name you gave it when you created it will automatically have the "Batch::" prefix added to it.

[datastage]

FYI, if you don't like the Batch:: or it doesn't fit your naming conventions you can still have this same Job Control code in a server job, but the canvas won't have any stages. And putting an annotation on the canvas denoting the job has job control in it is a helpful best practice.

The key difference to note is that creating it with Director with the Batch:: allows someone to be able to modify the job control through Director, and if its just in a job then you can't modify it with Director. The DataStage Operators group only has access to Director, so this is a way to give them or deny them a chance to modify job control logic.