Repository navigation
Job:zOS:SLAManagement #122
Description
In the AAPI when exporting SLA Management jobs defined to a ZOS based Control-M Server, then the type is Job:zOS:SLAMangagement instead of JobSLAManagement which is used for distributed Servers.
ctm-python-client needs support for Job:zOS:SLAManagement. See json example below...
"ZJ_1": {
"Type": "Job:zOS:SLAManagement",
"ServiceName": "JFI-TEST",
"JobRunsDeviationsTolerance": "3",
"CreatedBy": "jofink",
"RunAs": "RDWJXF",
"Application": "JFI-FNC",
"Archiving": {
"ArchiveSysData": true,
"AutoArchive": true
},
"CompleteBy": {
"Time": "12:00",
"Days": "0"
}
Activity
jfink5 commentedon Mar 27, 2025
There is an additional parameter required. OverridePath=DUMMY. The parameter name comes from a regular zos job, but not in SLA Management. There is no place in Web Client to specify this. However without it then the zos SLA Job will fail because the zos server can't find the jobname in the table(s). I suppose using DUMMY tells it to ignore looking for JCL. In fact if you try to create one of these in the 21.300 Web Client, then it gets left off and it causes problems. The only way I could get it to work was coding this into the json prior to deployment.
"ZJ_1": {
"Type": "Job:zOS:SLAManagement",
"OverridePath": "DUMMY",
...
}