1. Identify and resume suspended processes
Key Points
- Access Process Details page to view process state
- Processes can be suspended manually or automatically (e.g., breakpoints, errors)
- Resume operation restores process execution from suspension point
- Suspend/Resume buttons appear on Process Details operations bar
- Requires appropriate administrative authority
Detailed Notes
Why Processes Become Suspended
Process suspension and resumption are critical process management capabilities in InterSystems IRIS. Processes may become suspended for various reasons including manual suspension by administrators, hitting debug breakpoints, encountering specific error conditions, or resource limitations.
Identifying Suspended Processes
To identify suspended processes, navigate to the Processes page (System Operations > Processes) where you can view all active processes and their current states. The State column indicates each process's execution state - common states include running, suspended, waiting for lock, and various I/O wait states. To examine a specific process in detail, click the Details link in that process's row, which displays the Process Details page. This page shows comprehensive information including the process ID (PID), current user, namespace, execution state, lock information, memory usage, CPU time, and currently executing routine.
Resuming a Suspended Process
If a process is suspended and you have appropriate authority to manage it, Suspend and Resume buttons appear on the operations bar at the top of the Process Details page. Clicking Resume attempts to restart the suspended process from its suspension point. This operation is particularly useful when debugging applications, recovering from temporary resource contention, or addressing processes stuck waiting for external resources.
Security Requirements
Process management requires the appropriate security privileges - typically %Admin_Operate or equivalent roles. The ability to identify and resume processes is essential for maintaining system availability and troubleshooting operational issues.
Documentation References
2. Stop processes
Key Points
- Two termination methods: normal Terminate and Terminate with
Error - Accessed through Process Details page operations bar
- Use caution: termination interrupts active work and may cause data inconsistency
- Critical for resolving hung or runaway processes
- Should verify process activity before terminating
Detailed Notes
Termination Methods
Process termination is a powerful administrative function that forcibly stops running processes. InterSystems IRIS provides two termination methods, each accessible through the Process Details page. Normal Terminate attempts a graceful shutdown of the process, allowing it to clean up resources where possible. Terminate with
How to Terminate a Process
To terminate a process, navigate to System Operations > Processes, click Details for the target process, and then click either Terminate or Terminate with
Caution and Pre-Termination Checks
Process termination should be exercised with caution because forcibly stopping a process can result in incomplete transactions, unreleased locks, orphaned temporary data, and potential data inconsistency. Before terminating a process, examine its details carefully: review what routine it's executing, check if it's in a transaction (In Transaction field), examine its lock holdings, and verify it's not performing critical system operations.
Common Termination Scenarios
Common scenarios requiring process termination include hung processes stuck waiting for resources that won't be released, runaway processes consuming excessive CPU or memory, processes holding locks that are blocking other critical operations, and misbehaving user sessions. After terminating a process, monitor the system to ensure locks are released and verify no data corruption occurred. The ability to terminate processes is restricted to users with appropriate administrative privileges. Process termination is a last-resort troubleshooting technique - always try less invasive approaches first, such as identifying and resolving the root cause of process issues.
Documentation References
3. Manage batch and scheduled jobs via Task Manager
Key Points
- Accessible at System Operations > Task Manager
- Create tasks using Task Scheduler Wizard
- Schedule types: Daily, Weekly, Monthly, On-demand, After another task
- Configure task priority, user context, and email notifications
- Task Manager polls every 60 seconds for tasks to run
Detailed Notes
Accessing Task Manager
The Task Manager is InterSystems IRIS's integrated job scheduling system for managing batch and scheduled operations. Access the Task Manager through the Management Portal at System Operations > Task Manager.
Creating a New Task
Creating a new scheduled task involves using the Task Scheduler Wizard, which guides you through configuration. First, specify task properties: task name, description, namespace, task type (from predefined types like IntegrityCheck, FullDBList, PurgeAudit, etc.), and task-specific parameters. Task priority can be set to Normal, Low, or High, affecting execution order when multiple tasks are ready. The "Run task as this user" setting determines the security context - each task consumes a license unit based on this username. You can configure output file location, error handling behavior (suspend on error or reschedule), and restart behavior (whether tasks missed during system downtime should run immediately or reschedule). For mirrored environments, specify which mirror member types should execute the task. Email notification settings allow you to receive completion or error notifications if Task Manager email is configured.
Scheduling Options
The second wizard page defines the schedule: Daily (every N days), Weekly (specific days of week), Monthly (specific day of month), Monthly by day (e.g., first Monday), After another task completes, or On-demand (manual execution only). For time-based schedules, specify start date, end date, and either single execution time or recurring execution at intervals. The Task Manager polls every 60 seconds, so "Perform Action Now" tasks may experience up to 60-second delays.
Predefined and Custom Tasks
InterSystems provides numerous predefined system tasks that run by default, handling operations like backup purging, error log cleanup, journal switching, and integrity checking. You can also define custom task types using the %SYS.Task.Definition API for organization-specific automation needs.
Documentation References
4. Configure resource limits for scheduled tasks
Key Points
- Task priority controls execution order (High, Normal, Low)
- Mirror member restrictions control where tasks run
- Task expiration prevents stale executions
- License unit consumption per task based on user context
- Resource scheduling prevents system overload
Detailed Notes
Task Priority
Resource management for scheduled tasks is critical for maintaining system performance and stability while ensuring important batch operations complete successfully. Task Manager provides several mechanisms for controlling resource utilization. Task priority (High, Normal, or Low) determines execution order when multiple tasks are ready to run simultaneously - high-priority tasks execute before lower-priority ones. This prioritization ensures critical operations like backups or integrity checks take precedence over less time-sensitive tasks like log purging.
Mirroring Considerations
For mirrored configurations, the "How should task run for Mirror" setting controls resource distribution across mirror members. Options include running only on the primary failover member, only on backup and async members, or all mirror members. This prevents duplicate executions while ensuring tasks run on appropriate system roles. During failover transitions, the Task Manager suspends task execution until member status stabilizes.
License and Error Handling
Task expiration behavior (configured via "Changing Task Expiration Behavior") controls whether missed tasks expire or queue for execution - this prevents accumulation of stale tasks after extended outages. Each task consumes a license unit based on the configured username, so consider license capacity when planning task schedules. The "Suspend task on error" setting determines whether failing tasks keep retrying (potentially consuming resources repeatedly) or suspend for manual investigation.
Best Practices for Scheduling
Resource considerations also extend to scheduling patterns: avoid scheduling multiple resource-intensive tasks (backups, integrity checks, database reorganizations) simultaneously; InterSystems explicitly recommends running only one database reorganization operation system-wide at any time. Email notification configuration (completion and error emails) enables monitoring without continuous manual checking. For production systems, implement comprehensive task scheduling strategy: stagger intensive operations, leverage off-peak hours for heavy workloads, monitor task history for failures and performance trends, and maintain documentation of critical task dependencies.
Documentation References
Exam Preparation Summary
Critical Concepts to Master:
- Process States: Understand different process states (running, suspended, waiting)
- Process Identification: Know how to find process details via Management Portal
- Termination Methods: Understand difference between Terminate and Terminate with
- Task Scheduling: Master task creation via Task Scheduler Wizard
- Task Types: Recognize predefined task types (IntegrityCheck, FullDBList, PurgeAudit, etc.)
- Mirror Task Behavior: Understand how tasks execute in mirrored environments
Common Exam Scenarios:
- Identifying and resolving suspended or hung processes
- Determining appropriate termination method for stuck processes
- Creating scheduled tasks for maintenance operations
- Configuring task priorities and resource constraints
- Troubleshooting tasks that don't run as expected
- Managing tasks in mirrored configurations
Hands-On Practice Recommendations:
- Navigate Process Details page and examine process information
- Practice suspending and resuming processes
- Create and schedule tasks using Task Scheduler Wizard
- Configure task priorities and execution parameters
- Review Task Schedule page to monitor task history
- Test task execution in different mirror member scenarios
- Broadcast messages to terminals using Management Portal
- Examine process variables for debugging purposes