Application level variables

All questions about Control-M jobs definitions
Post Reply
User avatar
littlepeoplemusic
Nouveau
Nouveau
Posts: 1
Joined: 18 Aug 2011 12:00

Application level variables

Post by littlepeoplemusic » 18 Aug 2011 5:39

Hi

Been looking through documentation for information about variable scope. Our current system seems to run using a number of Global variables which is not ideal for our purposes. I understand how to define Group Schedule level and Job level variables. But can variables be defined at the application level?

The 'Control-m Job Parameter and variable ref guide' alludes this i think, but i'm unsure on how you'd set these up:

Application-specific job parameters may not be specified in
AutoEdit variable values. The names of application-specific
job parameters are prefixed by two percent signs, the
application’s abbreviation and a hyphen (%%SAPR3- for
SAP, %%OAP- for Oracle, and so on).


I could work with group level variables, but would prove clunky compared to variables whose scope are within an application.

ANyone have any insight on this?

Any help would be appreciated?

Best regards,
Laurent

processing

Post by processing » 18 Mar 2012 11:24

I think the Application in the text extract you provide refers to a Control-M Module, not the 'Application' category that can be set in a Control-M job definition.

Late reply, I know... but better late than never, right?

PS: I could be wrong, haven't tested it.

Post Reply