sharas, There is no mandatory order while stopping components, but common sense will tell you to stop operational processes first (gateway, gui server etc..), then the configuration agent, then the configuration server, then the naming service, then the database. Do not stop the operational componen...

Samarth_Vyom, It actually looks like ctmfw doesnt like AutoEdit as part of the rule syntax. I made a small test which consists in dynamically tailor the rule text. I wrote a rule skeleton based on your model, then a script which tailors the rule and calls ctmfw. The skeleton looks like this: # Globa...

dograv, The mentionned error must be a typing error. When using your rule as is, we got a syntax error like: ctmfw: command line 'ON_FILEWATCH c:\tmp\xyz.txt CREATE '(arg#=3). id=1. Unknown keyword 'ELSE' in line 6 of the input file: C:\IOALIBS\ctmecs\batch\file_watcher\MSbatch\dograv.rul. After hav...

dograv, Simply looking at the Example 1 supplied page 160 of the "CONTROL-M/Server for UNIX and Microsoft Windows Administrator Guide" version 6.3.0, it seems your first END_ON is spurious. The sequence supplied in the example is: ON_FILEWATCH..DO..ELSE..DO..END_ON ..while the one you supplied is: O...

kambiante, I have no opportunity to test your case. Did you set the "Bourne Shell Flags" to "n" using the ctmagcfg utility ? If so, I cannot help you any further and, as mentionned previously, it seems that controlm does not siupport other shels than the 4 listed in the agent admin guide Cheers Nico...

sharonc,x This is true. Unfortunately, controlm for distributed does not allow combination of several ON arguments. Hence there is no possibility to select the desired situation (NOTOK and RERUNCOUNT) with basic Steps parameters. Maybe you could try to DOShout to program the %%RUNCOUNT when NOTOK. T...

sharonc, Yes depending on your controlm version, In the PostProc tab of your job, starting from version 6.3.xx and upper, you can specify something else than COMPSTAT. For example (refer the the “controlm parm & variable guide” for complete explanations), you can specify ON RERUNNO, which "Upon term...

LordOfAfford, Let's consider daily JobA which triggers weekly JobB which triggers daily JobC, which is more or less you example (simpler). Put them all in a scheduling group, with 2 tags ("daily" - all days and "fridays" - once a week). Under normal conditions (except on friday), your schedule will ...

kambiante, Refer to "Specifying the shell type" in the "control-m administrator guide" (V6.4.xx) or "control-m agent for Unix and Microsoft Windows administrator guide", if you use V6.3.xx. According to the information specified here, it looks like controlm expects YOU to specify either /bin/sh, ksh...

cobus1234

As written previously, since no one else on this forum seem to ever have experienced your problem, and since I do not have additional idea, the best at that stage is to open a case near BMC.

Sorry for being helpless

Nicolas Mulot

LordOfAfford, Why do you spend time and energy trying to implement what control-m can do automatically. As stated in an other post on this forum, refer to: 1°) Adjust condition: which you specify in the Scheduling Group definition 2°) CTM_GROUP_ADJUST_DUMMY: which you specify in the config.dat of th...

cobus1234, The fact that your jobs execute in the proper order confirms that this is a display problem, only linked to EM and not to the server. Those conditions which are not displayed as links should have a common characteristic. Please check either condition names or job environment. Since your E...

cobus1234, Si it doesnt seem to be exactly the same problem I experienced. Still, and even if you dont USE global conditions, make sure there is no definition in the global condition tab in EM GUI. I still think the problem is just a display problem: I understand you went back to 6.1.03 because this...

cobus1234,

I checked on my 6.3.0 and the same problem appears.
If you are using global conditions, please forward the global conditions definition matrix

Nicolas Mulot

cobus1234,

Do you see no link at all or only some of them are missing?
Do you use or specify Global Condition definitions ?

Please reply, for your problem might relate to a bug I found and reported to BMC while upgrading straight from 6.1.03 to 6.4.0

Cheers
Nicolas Mulot