Defining Autotasks
You define each autotask with a separate AUTOTASK statement, specifying a task code and the time at which the autotask is invoked. When the AUTOTASK statement is successfully submitted to the system generation compiler, the compiler cross-references the autotask with its corresponding task in the data dictionary. At runtime, the DC/UCF system executes multiple autotasks in the order in which they are defined.
Note: The AUTOTASK statement should not be confused with the LTERM statement AUTOTASK parameter, which defines a task to be initiated automatically when a logical terminal is enabled. For more information about the LTERM statement, see LTERM Statement.
Startup Autotasks
The system attaches startup autotasks after initialization is complete. A startup autotask can preempt execution of other user tasks or can execute concurrently with user tasks. For more information about special considerations for startup autotasks, see the AUTOTASK syntax description.
Shutdown Autotasks
The system attaches shutdown autotasks during a planned shutdown (that is, in response to a SHUTDOWN command) after all other user tasks are terminated.
The ABEND/NOABEND Parameter
Before defining a startup autotask as PREEMPT ABEND, you should thoroughly test the task to ensure that it runs normally. Otherwise, if the startup autotask abends, the system will abend. The suggested specification is PREEMPT NOABEND.
|
Copyright © 2014 CA.
All rights reserved.
|
|