Enhancement Request: Instead of having Maximum Runtime set at runtime of an object, to allow a temporary increase in MRT to be set during execution of the object.

[Gerry Jandeska]

Enhancement Request:  Instead of having Maximum Runtime set at runtime, to allow a temporary increase in MRT to be set during execution of an object.

 That would be useful in the following scenario:

Let's say the Operators are monitoring an object with a 6 hour Maximum Runtime, and the MRT has been exceeded.  But the Operator's shift is ending.  So, the Operators want to hand off monitoring of the object to off-shore Operators, and to temporarily extend the MRT by 2 hours, without changing the original 6-hour MRT value.   This is while the object is executing.  Also, we would expect that another MRT alert would be generated if the additional 2 hours has been exceeded.

------------------------------
Gerry Jandeska
Lead Scheduling Systems Engineer
AEA. Core Technology Services
CME Group
20 South Wacker Drive
Chicago, Illinois 60606
------------------------------

[Carsten Schmitz]

For Enhancement Requests ​to have any chance at all, they need to be entered into the "Ideation":

https://community.broadcom.com/ideation/allideas

No guarantees that it will be picked up by Automic from there, but as a plain thread it is highly likely to not be tracked by Automic nor, consequently, implemented.

[Gerry Jandeska]

Thanks.  Will do.

------------------------------
Gerry Jandeska
Lead Scheduling Systems Engineer
AEA. Core Technology Services
CME Group
20 South Wacker Drive
Chicago, Illinois 60606
------------------------------

[Gary Chismar]

Set the MRT (give it a value of something that would be obvious) and Save.  Afterwards, export the object to file.  Look for the value and the XML tag that goes with it.  With that information, you should be able to set that value at runtime (as long as you have compile at runtime checked)..  For example, We use a RA FTP Agent for file transfers.  The default is to erase the file from the source once the file has been transferred.  There are about 3 - 4 vendors that do not allow this to happen.  So, I checked the Erase after transfer checkbox; saved, and then exported the object as a file.  I then unchecked it and did the same.  Compared the two and found that the tag that holds that value is named prompt_0_eraseSource.  So now, we have a pre-process script that runs and if a flag is set to not delete the file then we do a:
:PUTT_ATT prompt_0_erseSource = 'False'.  Otherwise the checked box stays.  You should be able to do something similar.

------------------------------
Cheers,

Gary Chismar
Manager, Automic, PeopleSoft HCM/FI
Florida State University
Florida
------------------------------