Hand - Manual operation

Enhanced Definition

In the context of mainframe operations, "hand" or "manual operation" refers to any task or process that requires direct human intervention, typically by a system operator, rather than being fully automated by software. It involves an operator physically performing an action or responding to system prompts via the operator console.

Key Characteristics

- Human Intervention Required: Tasks are not fully automated and necessitate a human operator to initiate, monitor, or complete them.
- Operator Console Interaction: Often involves responding to system messages, issuing commands (e.g., VARY, START, STOP), or entering replies via the z/OS operator console.
- Physical Media Handling: Can include tasks like mounting physical tape volumes, loading printer forms, or swapping removable disk packs.
- Slower and Potentially Error-Prone: Manual steps are inherently slower than automated processes and carry a higher risk of human error, especially during high-pressure situations.
- Used for Exceptions or Non-Standard Procedures: Frequently employed for system startups (IPL), shutdowns, recovery procedures, or handling unexpected conditions that automation cannot resolve.

Use Cases

- Mounting Tape Volumes: An operator receives a message like IEA000I 858,TAPE,SCRATCH,VOL=001234 and physically mounts the specified tape reel onto a tape drive.
- Responding to System Messages: Replying to WTOR (Write To Operator with Reply) messages, such as *01 IEE100A SPECIFY SYSTEM PARAMETERS, during an IPL or for specific application requests.
- Initiating System Shutdown or IPL: Manually issuing Z NET,QUIESCE or SHUTDOWN commands, or performing the physical IPL sequence on the Hardware Management Console (HMC).
- Manual Recovery Procedures: Executing specific, documented steps to recover a failed subsystem (e.g., CICS, DB2) when automated recovery mechanisms are insufficient.
- Hardware Maintenance: Physically replacing components, checking status lights, or performing other hands-on tasks on mainframe hardware.

Related Concepts

Manual operations stand in direct contrast to System Automation tools (e.g., SA z/OS, OPC/TWSz), which aim to eliminate human intervention by automating routine tasks, error recovery, and system monitoring. They are closely tied to the Operator Console, which is the primary interface for human interaction with z/OS, and JCL, where parameters like MSGCLASS or HOLD can influence when and how an operator might need to intervene. An IPL (Initial Program Load) is a prime example of a process that historically involves significant manual steps.

Best Practices:

Automate Whenever Possible: Prioritize the automation of repetitive, time-critical, or error-prone tasks using System Automation software to reduce reliance on manual operations.
Thorough Documentation: Maintain clear, concise, and up-to-date runbooks and procedures for all manual operations, including screenshots and expected outcomes.
Operator Training and Certification: Ensure that operators are well-trained, understand the implications of their actions, and are certified for critical manual procedures.
Implement Change Control: Apply strict change management processes to any manual changes made to the system, ensuring proper authorization and rollback plans.
Minimize Critical Path Manual Steps: Design systems and processes to avoid manual intervention during critical production paths to enhance availability and performance.