Mainframe SCM · Ingest
PYD ENTERPRISES and Broadcom Endevor
Ingest exported Endevor element libraries (COBOL, copybooks, JCL, PROCs and BMS maps) with their environment, system, subsystem, type and stage metadata intact.
Broadcom Endevor
Mainframe SCM
1{2 "codePage": "IBM-1047",3 "authoritativeStage": "PROD/2",4 "elements": [5 { "element": "LNACCR02", "type": "COBOL", "system": "LOANS", "subsystem": "ACCRUAL", "stage": "PROD/2", "file": "cobol/LNACCR02.cbl" },6 { "element": "LNREC", "type": "COPY", "system": "LOANS", "subsystem": "COMMON", "stage": "PROD/2", "file": "copy/LNREC.cpy" },7 { "element": "LNDLY01", "type": "JCL", "system": "LOANS", "subsystem": "BATCH", "stage": "PROD/2", "file": "jcl/LNDLY01.jcl" }8 ],9 "copyConcatenation": ["copy/LOANS", "copy/SHARED", "copy/VENDOR"]10}
Why Endevor metadata matters to the parser
On many z/OS shops the authoritative copy of a program is not a PDS member but an Endevor element, identified by environment, system, subsystem, type and stage. The same program name can exist at several stages at once: a fix in TEST, the production version in PROD, an emergency change somewhere in between. Scan the wrong one and every rule PYD ENTERPRISES extracts describes code that is not running.
PYD ENTERPRISES therefore ingests Endevor content as an export plus a manifest rather than as a flat pile of members. The manifest tells the parser, for each element, its type (COBOL, COPY, JCL, PROC, BMS, ASM), its location in the Endevor inventory and the stage it came from. When an element exists at several stages, the scan policy picks one explicitly (usually the highest production stage) and records the choice.
Getting elements out of Endevor
PYD ENTERPRISES does not connect to Endevor or to the mainframe. Your Endevor administrator uses the retrieval or batch reporting facilities your site already runs to copy the selected elements to datasets or to z/OS UNIX files, and then transfers them to the PYD ENTERPRISES ingest volume over your approved file transfer route.
- Transfer in text mode with the right code page (for example IBM-037 or IBM-1047 to UTF-8), or transfer binary and let PYD ENTERPRISES convert using the code page you declare. Do not mix the two in one export.
- Keep columns 1 to 6 and 73 to 80 intact: PYD ENTERPRISES uses sequence numbers to keep line references stable against the listings your mainframe team already uses.
- Export the copybook libraries in the same concatenation order as the compile step, because a COPY member resolves to the first library that contains it. Endevor processor groups usually define that order; give PYD ENTERPRISES the same list.
What PYD ENTERPRISES builds from it
With elements and manifest in place, PYD ENTERPRISES expands every COPY statement (including nested copybooks and COPY REPLACING), parses CICS commands and BMS mapsets, reads JCL and cataloged PROCs with symbolic substitution, and links programs to the VSAM clusters and DB2 tables they touch. The resulting dependency graph shows Endevor system and subsystem as grouping, so a mainframe lead sees the inventory in the vocabulary they already use. Every extracted rule records element name, type, system, subsystem and stage alongside line numbers.
FAQ
Broadcom Endevor questions.
Does PYD ENTERPRISES need a connection to the mainframe or to Endevor?
No. It works from exported files and a manifest that your team produces with existing procedures. Nothing runs on z/OS and no mainframe credentials are shared.
What happens when the same element exists at several stages?
The scan policy chooses one, normally the highest production stage, and records that choice in every artifact. Other stages can be scanned separately and compared rule by rule.
Can PYD ENTERPRISES handle copybooks that are generated or vendor-supplied?
Yes, if they are included in the export. Missing copybooks are reported as unresolved COPY statements with the referencing programs, so the gap is visible before rules are extracted.
RELATED INTEGRATIONS
GitHubMirror GitHub or GitHub Enterprise Server repositories inside your VPC, scan a pinned commit, and return specifications to a review repository as pull requests.
GitLabClone self-managed GitLab projects inside your network, run PYD ENTERPRISES as a CI job on your own runners, and publish specs back as merge requests.
BitbucketIngest legacy repositories from Bitbucket Data Center or Bitbucket Cloud with read-only credentials, and return specification bundles as pull requests for review.
Azure DevOpsScan Azure Repos Git repositories and TFVC snapshots from Azure DevOps Server or Services, run scans from self-hosted pipeline agents, and export specs as pull requests.See the Broadcom Endevor flow on your own code.
Run PYD ENTERPRISES on 100,000 lines of COBOL or Java in your private VPC and review OpenAPI specs and DMN tables tomorrow.