LOCO Modernization Guide

LOCO is a z/OS console automation product that allows for the automatic issuing of z/OS commands based on factors such as time of day, specific WTOs received, or even after an IPL. It can also automatically respond to WTORs, reducing manual operator intervention.

LOCO is best described as a system automation tool. It provides a framework for automating z/OS console operations, reducing the need for manual intervention and improving system efficiency.

Organizations that rely heavily on the z/OS operating system and require a high degree of automation in their console operations would find LOCO useful. This includes large enterprises in industries such as banking, finance, insurance, and government.

A company should consider using LOCO when they need to automate repetitive z/OS console commands, reduce manual operator intervention, and improve overall system efficiency. This is especially relevant in environments with a large number of z/OS systems and complex operational requirements.

Alternatives to LOCO include products like Rocket Zack, OPS/MVS, and BMC AMI Ops Automation for z/OS. These products offer similar capabilities for z/OS console automation and can be considered as replacements.

LOCO runs on the z/OS operating system and is dependent on specific z/OS subsystems for its operation. It typically runs within an LPAR on a mainframe system.

LOCO requires existing z/OS infrastructure, including the operating system itself and any necessary subsystems for console operations. It also requires a network connection for communication between components.

LOCO's architecture includes components for command processing, event monitoring, and response automation. These components communicate through internal interfaces and z/OS system services.

LOCO likely uses configuration files to define automation rules and parameters. These files would specify the conditions under which commands are issued and the responses to WTORs.

The primary business value of LOCO is the reduction of manual effort in z/OS console operations. By automating repetitive tasks and responding to system events automatically, it frees up operators to focus on more critical issues.

Without LOCO, organizations would need to rely on manual operator intervention for z/OS console operations. This can be time-consuming, error-prone, and inefficient, especially in large and complex environments.

LOCO integrates with the z/OS operating system and its subsystems. It may also integrate with other system management tools for monitoring and reporting.

LOCO's security features would likely include access control mechanisms to restrict who can define and modify automation rules. It may also integrate with z/OS security systems like RACF, ACF2, or Top Secret for authentication and authorization.

LOCO likely provides audit logging capabilities to track changes to automation rules and the execution of automated commands. This allows administrators to monitor system activity and identify potential security issues.

LOCO is typically deployed on-premise, within the z/OS environment. It requires technical expertise to implement and configure the automation rules.

Ongoing operational requirements for LOCO include monitoring the execution of automated commands, maintaining the automation rules, and troubleshooting any issues that arise. This requires skilled z/OS system programmers and operators.

Common implementation challenges for LOCO include defining the appropriate automation rules, ensuring that the automated commands are executed correctly, and managing the interactions between LOCO and other z/OS subsystems.