ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Performance implications of using Datacom SUBTASK_AUTO MUF Startup Option

book

Article ID: 186158

calendar_today

Updated On:

Products

Datacom Datacom/DB Datacom/AD

Issue/Introduction

We would like to use the MUF startup option SUBTASK_AUTO 3600,STATUS and want to know the cost of this automated process.

Are there any thoughts about using this to repeat console commands or to repeat Modify commands?

Environment

Release : 15.1

Component : CA DATACOM/DB
Component : CA DATACOM/AD

Resolution

Using SUBTASK_AUTO has a very low cost. By using a subtask to cycle through the commands, there is very little overhead, and this likely uses fewer resources than setting up a scheduled job to run every hour and issuing a STATUS console command or running some other process that wakes up every hour to issue the command.

Additional Information

For more information about the SUBTASK_AUTO setting, please review the Datacom/DB Database and System Administration documentation for the SUBTASK_AUTO startup option.

As always, please contact Broadcom support for Datacom if you have further questions.