Context-Aware “Next Action” Guidance for Job Outcomes (No Additional Messages or Alerts)

Business Justification

The IBM i platform already captures comprehensive job information, including job status, job logs, and spool files. However, users must rely on experience and manual navigation to determine the appropriate next step after a job completes.

This creates unnecessary friction, particularly in batch processing environments where users must interpret outcomes and locate relevant diagnostic or output information.

Common challenges include:

• Navigating multiple commands (WRKJOB, WRKSPLF, DSPJOBLOG)

• Determining whether a job failed or completed with issues

• Identifying whether spool files or logs exist

• Slower troubleshooting due to lack of guidance

• Increased reliance on experienced users

This proposal introduces a lightweight, contextual enhancement that surfaces the next logical action directly within existing interfaces—without introducing additional system noise.

Proposed Enhancement

Introduce a context-aware “Next Action” layer within existing IBM i interfaces, including:

• 5250 sessions

• IBM i Access Client Solutions

• Navigator for i

This layer would:

• Detect job outcome (e.g., normal completion, abnormal end, messages present, spool files generated)

• Dynamically surface relevant actions

• Present options only when applicable

• Require no additional configuration

• Avoid generating messages, alerts, or notifications

Key Features

1. Context-Aware Actions

System evaluates existing job state and exposes relevant options:

• “View Job Log” (if errors or messages exist)

• “View Spool Files” (if output exists)

• “View Messages” (if message queue entries are relevant)

2. Inline Integration (No New UI Surface)

Enhancements appear within existing workflows:

• Function keys in 5250 become context-aware

• Action columns in job lists show relevant options

• Navigator/ACS surfaces actions alongside job status

3. Zero Additional System Noise

This solution is state-driven, not event-driven:

• No new messages sent to message queues

• No alerts or notifications generated

• No impact on job logging or system performance
  
  Navigator / ACS

• Contextual action buttons appear only when relevant

• No additional menus or navigation required

What This Proposal Is NOT

To be explicit:

This is not:

• A notification system

• An alerting mechanism

• An email or messaging feature

This proposal does not:

• Generate message queue entries

• Interrupt users

• Introduce additional system noise

It strictly enhances how existing system state is presented.

Business Value

1. Reduced Cognitive Load

Users no longer need to remember:

• Where job logs are located

• How to access spool files

• Which commands to use

2. Faster Troubleshooting

• Immediate access to relevant diagnostics

• Fewer navigation steps

• Reduced time to resolution

3. Improved Accessibility for New Users

• Reduces dependency on tribal knowledge

• Makes IBM i more intuitive

• Lowers onboarding friction

4. Alignment with IBM i Philosophy

• Leverages existing system architecture

• Enhances, rather than replaces, current tools

• Maintains stability and predictability

Technical Considerations (High-Level)

• Utilizes existing job metadata (status, message severity, spool file presence)

• Minimal overhead—evaluation occurs at display time

• No changes to job processing or logging mechanisms

• Backward compatible with existing workflows

Why This Matters

IBM i excels at capturing system state—but does not guide users on how to act on it.

This enhancement bridges that gap by making system state actionable in context, improving usability without compromising the platform’s core principles.

Summary

IBM i already tells users what happened.

This proposal enables it to also suggest what to do next—
without adding noise, complexity, or risk.