ibm/ibm-z-zos

The helpful and handy location for finding and sharing z/OS files, which are not included in the product.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 23 minutes ago
Added to GitGenius on August 16th, 2026
Created on July 17th, 2017
Open Issues & Pull Requests: 16 (+0)
GitHub issues: Enabled
Number of forks: 217
Total Stargazers: 462 (+0)
Total Subscribers: 115 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 8.9 days
Mean response time: 8.9 days
90th percentile: 8.9 days
Tracked items: 1

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 429 days
Stale 30+ days: 5
Stale 90+ days: 5

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

IBM Z zOS is a repository of sample programs and resources for the z/OS operating system community.

The repository addresses the need for tools and educational materials that extend z/OS capabilities beyond what ships with the product itself. It organizes downloadable resources across functional domains including system management facilities, automation, container platforms, health checks, security, performance analysis, and workflow management. The materials span multiple z/OS release levels and include educational modules, sample code, and utility tools written primarily in REXX.

Organizations running z/OS systems should consider this repository when seeking community-contributed tools for specific operational tasks such as performance monitoring, system configuration, security administration, or capacity planning. The collection is particularly useful for teams evaluating z/OS capabilities, migrating workloads, or automating routine administrative functions. The repository explicitly carries no warranty and receives no formal IBM support, making it suitable for non-production exploration or as a starting point for internal tool development rather than as a replacement for supported IBM products.

Development activity shows consistent engagement with the community through an open issue and pull request process. The project maintains organized categorization of materials by functional area and release level, reflecting ongoing curation of contributed resources. Contributors are invited to participate in development and share improvements, with feedback directed to a dedicated contact address or through GitHub issues.