Managing the ReportCenter Java Task › When the Task is Not Running

When the Task is Not Running

When the ReportCenter Java Task is not running, the following occurs:

• Viewing report output is unaffected.

  You can view reports that have run by the usual methods. Report viewing is processed by the ReportCenter control region reading the HFS files and does not involve the task.

• No reports are run.

  This applies to on demand and scheduled report runs. Report runs queued when the task was stopped are not run. They have a status of stopped or terminated.

• Services do not run.

  If the task is not active at the specified time, any service scheduled to run through a timer does not run. This includes the Scheduler service.

• Collected data is queued by data regions.

  If data cannot be sent to its destination, a data region queues the data to send later when the connection to the task recovers. To find out the queue depth, enter /DWS in the region.

  Data regions store queued ReportCenter data in the VFS VSAM file. Usually, the file can store up to 99999 hourly summary observations. Ensure that your VFS file has plenty of space in the primary extent.

Do not leave the task inactive for an extended period, unless this is unavoidable due to database outage. You do not lose data simply because the ReportCenter Java Task is down; but if it is down for too long, you lose data.