Connect/USS
z/OS
Learn more about features
z/OS Batch · USS Integration
Zero
File
Staging
GnuPG
Native
PGP
cURL
SFTP & Secure
Transfer
Direct
Data
Streaming
z/OS
Native
Platform
High-Performance Streaming Between z/OS Batch and USS.
Included With Your Connect/USS License
Connect/USS, like every Connect/MP component, includes MCP API access for JES, FILE, and 3270 — for your own scripts and agents — plus the chat-only Web Workspace, at no additional cost. Connect/AI is a separate add-on that unlocks agentic execution: workspace tool use and native batch inference invoked from JCL.
High-Performance Data Streaming
- Simplifies batch pipelines by eliminating extra commands and file handling steps
- Reduces latency and overhead compared to file-oriented processing
- Integrates cleanly with JCL and production workflows — no USS expertise required
- Improves security and efficiency by minimizing data at rest
Cost-Saving z/OS PGP Encryption
Connect/USS optimizes PGP processing in z/OS batch with a high-level JCL abstraction and direct piping into USS GnuPG — no file staging, no scripting. Encrypted output is delivered to z/OS datasets, USS files, FTP targets, or email destinations, eliminating the complexity of traditional approaches. Read the white paper ›
Streamlined Secure File Transfers
Connect/USS streams z/OS files directly into cURL transfers (SFTP, FTPS), eliminating the need for intermediate file staging. Workflows are simplified and secure, enabling automation-ready file movement directly from z/OS batch jobs.
Not All Data Access Patterns Are Equal
Explore the performance trade-offs and architectural implications of streaming versus file-based approaches when reading z/OS datasets from Unix System Services. Read the white paper ›
Resources
Connect/MP › Connect/USS
Features
Key Features
Direct Execution of USS CLI Processes from Batch
Shell commands, scripts & binaries from JCL
Invoke shell commands, scripts, binaries, or cryptographic utilities in USS directly from JCL steps—with simplified parameter and environment setup. Eliminates the need for file-oriented invocation patterns, enabling more direct and efficient batch-to-USS integration.
True STDIN/STDOUT Streaming (No File-Based Handling)
Datasets stream via STDIN and STDOUT
Stream z/OS datasets directly into USS processes via STDIN and out via STDOUT—without exposing datasets as USS files or requiring intermediate file handling. Avoids file-based access patterns, reducing complexity, latency, and operational overhead.
Built-in PGP Integration with GnuPG
z/OS batch to GnuPG via native streaming
Out-of-the-box PGP processing that bridges z/OS batch and IBM-ported GnuPG using standard JCL declaratives and native streaming. Eliminates temporary clear-text files and file-based workflows, improving both security and operational efficiency.
Seamless Batch ↔ USS Application Integration
Stream-based z/OS dataset to USS app flow
Directly connect z/OS datasets with USS applications through stream-based data flow, with transparent handling of format considerations where required. Removes the need to manage dataset-to-file mappings or filesystem paths, simplifying integration.
Integrated Monitoring and Error Handling
Unified job logs across both environments
Unified job logs capture USS process output, errors, and return codes—providing clear visibility into execution without requiring separate file inspection or tracing across environments.
Security and Authorization Consistency
z/OS SAF controls across batch and USS
Leverages z/OS SAF/SAF controls across batch and USS boundaries, ensuring proper dataset and process-level access. Avoids the additional security considerations introduced by filesystem-based access models, such as mounts and path permissions.
Performance-Optimized Execution
Low-overhead streaming, reduced latency and I/O
Low-overhead streaming reduces latency, CPU, and I/O compared to file-oriented processing. By eliminating filesystem layers and intermediate steps, Connect/USS delivers more predictable, high-throughput performance.
Simplified Operations (No Filesystem Dependencies)
No mappings, mounts, or USS file management
Operate without requiring dataset-to-file mappings, mounts, or USS file management. Reduces setup complexity and ongoing operational risk associated with file-based approaches.
Suite Integration
Pairs with Connect/ZIP, Hybrid, and Web
Complements other Connect/MP components (Connect/ZIP, Connect/Hybrid, Connect/Web) to support end-to-end modernization workflows.
Value of Streaming Execution
Connect/USS's stream-first architecture delivers clear advantages over file-based approaches:
Reduce Resource Consumption
Fewer temp files, less I/O and disk usage
Eliminates temporary files, reduces I/O operations, and minimizes disk usage—especially for large datasets and high-volume processing.
Simplify Batch Pipelines
Cleaner, more maintainable JCL
Removes file handling steps, dataset-to-path mappings, and extra commands—resulting in cleaner, more maintainable JCL.
Improve Performance and Throughput
Continuous data flow without filesystem overhead
Enables efficient, continuous data flow between applications without filesystem overhead—ideal for transformation, encryption, filtering, and integration workflows.
Enhance Security
Less data at rest, no intermediate file exposure
Minimizes data at rest and avoids intermediate file exposure, reducing risk compared to file-based handling models.
Reduce Operational Complexity
No filesystem setup, mounts, or path management
Avoids filesystem setup, mounts, and path management—lowering the burden on operations teams and reducing configuration errors.
Accelerate Modernization
Add modern USS tools to existing batch workflows
Easily incorporate modern USS-based tools (e.g., scripting, cryptography, DevOps utilities, AI/ML tooling) into existing batch workflows—without redesigning around file-based access patterns.
Ideal Use Cases
Connect/USS is especially effective for:
- High-volume batch pipelines requiring USS integration
- Secure file exchange and API-driven transfers (e.g., cURL, SFTP)
- PGP encryption/decryption workflows
- ETL-style data transformation and validation
- Report generation and downstream system integration
Prerequisite