%%PATH Autoedit variable Overrides Shell PATH

[wrclark]

It seems as though using an autoedit variable named %%PATH in a job definition causes the corresponding autoedit value to be used as the actual shell path for the job. But I can't seem to find any reference to this in the Job Parameter and Variable Reference Guide.

If you have seen this documented somewhere, would you mind sending me a link to letting me know which doc I can find this in?
Thanks!
Bill C

[wrclark]

On further review, it seems that all autoedit variables in the set tab get turned into unix environment variables in the spawned shell. That could be useful, I suppose but can also lead to some unpredictable results if one is not careful managing autoedit variable names.

[wrclark]

One clarification: We are running ControlM 6.3.01 Fix Pack 5 for Distributed Systems on Solaris/Sparc

[nicolas_mulot]

I have the same behaviour under Windows server 6.3 FixPack 5.
This sounds new to me and I didnt find any info on that enhancement in neither the base documentation nor in any fixpack release notes.

If anyone has info about when this was released - thanks
Nicolas_Mulot

[baralem]

Check the following parameter in CM Agent:

10) AutoEdit Inline. . . . . . . (Y|N): [N]

--> CONTROL-M Agent for UNIX and Microsoft Windows Administrator Guide:

AutoEdit Inline Flag that indicates whether AutoEdit variables defined in a
CONTROL-M/Server job are set as Environment variables in the
user job environment. This parameter can only be changed after
completing the installation.Valid values:
Checked - AutoEdit variables are set. Default.
Cleared - AutoEdit variables are not set.

regards
Martin

[wrclark]

Thank you, Martin. Very helpful. I should have looked in the Agent documentation but was just looking at ctlm server docs.

Bill