Automic Workload Automation

Assuming that you renamed it using the Explorer, how did you respond to this pop-up message?

https://us.v-cdn.net/5019921/uploads/editor/61/qav6uu6usoq4.png" width="560">

Hi Pratima,

>But the jobs don't show the renamed object name ,instead the old name is still seen and no longer available.

Unfortunately that's the build-in behaviour  :\

Before you start to rename INC objekts you should search for the usage and adopt the corresponding matches manually.

Peter

I'm on V8, I have never, to my recollection, not received that pop-up when renaming an object that is used in other objects.

Peter, are you saying that this is no longer the case?

The example in my first reply is a rename of an Include object.

:INC objects are normally defined within a Script Tab. The 'Replace' functionality applies to where Objects are defined in a Parameter. Since the scripts are essentially stored as a giant String, the Replace functionality can't do a easy 'find and replace'. 

Whereas, if it's say a Login Object, it's able to find where the Login Object is defined as a parameter and replace that value.

The  purpose of Object oriented approach is also to be able to reflect the changes done.I won't be able to use the :INC object as a template for new jobs creation  if I have to manually update each one of them if we rename the INC object.

We resist renaming objects for many reasons and this issue is one of them.  Choose wisely!!  ;)

We have in excess of 150,000 objects and use Includes in virtually all of them and haven't found this restriction to be much of an impediment, just an annoyance.

When we are faced with a mass rename, our approach is to perform a "Search for use" with "Include Script" checked.   We then Export the needed objects, use the appropriate utility or text editor to change the name and then Import the modified objects.  For us this has been relatively painless and takes little effort.

Thank you Mark.

One option is to put the name of the JOBI object in an object variable in the job or script’s Variables & Prompts tab, and include the JOBI by referencing the name of the variable that contains the JOBI name. E.g.,

 :INC &MY_JOBI# 

You will then be able to change the reference to the JOBI automatically when you change the JOBI’s name. This approach makes the script a bit harder to read, but it might be worth it.

Update 2017.04.26: Variables arenotresolved in :INCLUDE statements. I opened an enhancement request for this:

Allow variables in :INCLUDE statements 

If you like the idea, please vote for it.

Michael:

On V8, the documentation states:  

Enter the complete name of the Include object. Script variables are not allowed. 

Error: U0010003 Object: 'THE_OBJECT': Include '&THE_INC' not found in object
'THE_OBJECT(1)'.

Are you (hopefully) saying that this actually works in later versions?  Please say that it is true since I have always had a desire to do this.

Michael:

On V8, the documentation states:  

Enter the complete name of the Include object. Script variables are not allowed. 

 

While it allows the object to be saved, execution results in:

Error: U0010003 Object: 'THE_OBJECT': Include '&THE_INC' not found in object
'THE_OBJECT(1)'.

Are you (hopefully) saying that this actually works in later versions?  Please say that it is true since I have always had a desire to do this.

Hi Mark,

this is still not possible (v10 SP2). The AE takes the characters after the :INC statements as a "real" object name. Replacing a script variable by its content is not implemented here.

To make this possible I guess the script interpreter has to be changed ...

Thanks Peter.  

Too bad, I'd really like to be able to selectively chose the INC at generation.   As it sits now, I am forced to do something like the following. It's not terrible, but not too elegant either.

:IF &something EQ "whatever"
: INC this
:ELSE
: INC that
: ENDIF

since v9 you can also use SWITCH to avoid nested IFs:

:set &INCNAME# = 'something'

:switch &INCNAME#
:case 'test'
: inc JOBI.TEST
:case 'prod'
: inc JOBI.PROD
:other
: print 'Invalid INC name specified'
:endswitch