Authorisation problem 6.31:
-
LordOfAfford
-
nicolas_mulot
- Nouveau
- Posts: 149
- Joined: 07 Jan 2010 12:00
Tabpgr,
You say that « Authorising a jobuser to run on one agent is not a problem ».
Please detail the table updates you’ve done to achieve that.
I didnt find no possibility to control execution of a job. Does that mean that you control the order of the job using user/owner/nodegrp combination?
I ran some tests where I inserted a nodeid in the Scheduling Group definition (CMS_JOBDEF).
The Scheduling Group, once ordered, keeps that information on the AJF. Unfortunately, this can be done only by a direct SQL request against the CMS_JOBDEF table, and I have no idea of the side effects.
I tried to set that information using more standard ways: coding NODEID in an xml definition, and running a control-m/EM deftable works OK, but the NODEID is eliminated from the SG definition without any warning nor error message. Another way was to create the Scheduling Group directly in the control-m server base using a ctmgrpdef utility. In that case, we get an error message and the Scheduling Group is not created.
Cheers
Nicolas_Mulot
You say that « Authorising a jobuser to run on one agent is not a problem ».
Please detail the table updates you’ve done to achieve that.
I didnt find no possibility to control execution of a job. Does that mean that you control the order of the job using user/owner/nodegrp combination?
I ran some tests where I inserted a nodeid in the Scheduling Group definition (CMS_JOBDEF).
The Scheduling Group, once ordered, keeps that information on the AJF. Unfortunately, this can be done only by a direct SQL request against the CMS_JOBDEF table, and I have no idea of the side effects.
I tried to set that information using more standard ways: coding NODEID in an xml definition, and running a control-m/EM deftable works OK, but the NODEID is eliminated from the SG definition without any warning nor error message. Another way was to create the Scheduling Group directly in the control-m server base using a ctmgrpdef utility. In that case, we get an error message and the Scheduling Group is not created.
Cheers
Nicolas_Mulot