Universal Agent Modernization Guide

The Universal Agent facilitates automation of z/OS workloads within the Stonebranch Universal Automation Center. It enables scheduling, monitoring, and control of z/OS jobs and processes.

The agent supports standard z/OS job control language (JCL) and allows execution of TSO commands, batch jobs, and started tasks. It integrates with z/OS security systems for authentication and authorization.

The Universal Agent communicates with the Stonebranch Universal Automation Center (UAC) using a proprietary protocol over TCP/IP. This protocol ensures secure and reliable communication for job execution and status updates.

The Universal Agent supports various authentication methods, including LDAP, Kerberos, and certificate-based authentication. Access control is managed through role-based access control (RBAC) within the Stonebranch UAC.

Common commands include submitting JCL jobs, executing TSO commands, checking job status, and retrieving job output. Examples: `SUBMIT JOB(jobname)`, `EXECUTE TSO(command)`, `STATUS JOB(jobname)`, `GETOUTPUT JOB(jobname)`.

The Universal Agent exposes a REST API for programmatic interaction. API endpoints include `/jobs`, `/tasks`, and `/events`. Supported methods include GET, POST, PUT, and DELETE.

The main components are the Agent Controller, the Communication Module, and the Task Execution Engine. The Agent Controller manages overall agent operations. The Communication Module handles communication with the UAC. The Task Execution Engine executes the actual z/OS tasks.

The Universal Agent uses configuration files, typically stored in a PARMLIB dataset, to define agent parameters, communication settings, and security configurations. These files are read during agent startup.

The Universal Agent supports integration via REST APIs and a Java SDK. The REST APIs allow interaction using any language that supports HTTP requests. The Java SDK provides a native interface for Java-based applications.

By automating z/OS workloads, the Universal Agent reduces manual intervention, improves scheduling accuracy, and accelerates batch processing. This leads to increased operational efficiency and reduced costs.

The Universal Agent enables organizations to integrate z/OS workloads into their enterprise-wide automation strategy, providing a single point of control for all automation tasks. This improves visibility and control over critical business processes.

The Universal Agent helps organizations meet compliance requirements by providing detailed audit trails of all automated tasks. This ensures accountability and facilitates regulatory reporting.

The Universal Agent supports authentication methods such as LDAP, Kerberos, and X.509 certificates. These methods ensure secure access to z/OS resources.

The Universal Agent uses role-based access control (RBAC) to manage user permissions. This allows administrators to assign specific roles to users, granting them access to only the resources they need.

The Universal Agent encrypts sensitive data both in transit and at rest. Data in transit is encrypted using TLS/SSL. Data at rest, such as credentials, can be encrypted using AES-256.

The Universal Agent provides comprehensive audit logging capabilities. All actions performed by the agent, including job submissions, command executions, and security events, are logged to a secure audit trail.

The Universal Agent provides a command-line interface (CLI) and a web-based console for administrative tasks. The CLI is used for scripting and automation, while the web console provides a user-friendly interface for monitoring and management.

User management is handled through the Stonebranch Universal Automation Center (UAC). The UAC allows administrators to create and manage user accounts, assign roles, and configure access permissions.

Key configuration parameters include agent ID, communication port, security settings, and logging level. These parameters are defined in the agent's configuration file.

The Universal Agent provides extensive monitoring and logging capabilities. The agent monitors job status, resource utilization, and system health. Logs are generated for all agent activities and can be sent to a central logging server for analysis.