Industries / Financial services

Modern COBOL development, without leaving z/OS.

For application programmers and production support. Your compilers, JES and change control stay on z/OS.

Standards
SOX · PCI DSS
Host
z/OSMF, Enterprise COBOL, JES, Db2, CICS
Workstation
GnuCOBOL, GDB, COBOL Check
Agent policy
Mainframe and finance templates
Deployment
Self-hosted, your cloud or air-gapped

What your team gets

The z/OS development loop in one IDE.

Govern features are in use today. Domain modules are pre-release; their state is listed under Tools and formats.

Edit and compileMembers compiled through your own cataloged procedures, with listings read in place.
Submit and spoolBatch jobs submitted through JES; failing steps and abends found in the spool and mapped to source.
Db2 and CICSPrecompile, BIND and CICS translation driven through z/OSMF.
Production read-onlyData sets you name, such as PROD.**, open read-only.
Workstation pathGnuCOBOL, GDB and COBOL Check for continuous integration and engineers without a host seat.
Agents inside change controlThe mainframe template lets agents edit COBOL and JCL in the repository; they never submit jobs, bind Db2 packages or delete host data sets.

Who uses it

One environment for every role on the team.

Application programmersEdit members and compile with your own procedures.
Production support analystsFind the failing step and the abend in the spool.
Db2 and CICS developersPrecompile, BIND and translate from the same environment.
New team membersA familiar editor instead of ISPF and green screens.

Tools and formats

What the Mainframe module handles, and how far each is verified.

The z/OS side runs while a z/OS connection exists. COBOL and JCL colouring is always available.

z/OSData sets and members, job submission and spool, compiles with your procedures, Db2 and CICS steps, all through z/OSMF. Nothing has run against a z/OS system yet: it is tested against a local server shaped like z/OSMF, with a verification kit for your own z/OS.z/OSMF · Zowe team configuration · Enterprise COBOL · JES · Db2 · CICS
WorkstationCompile, run, debug and test on your machine. Verified on Linux with GnuCOBOL 3.1.2, GDB 15.1 and COBOL Check 0.2.19.GnuCOBOL · GDB · COBOL Check
Source and dataCOBOL programs, copybooks and JCL, and data read through its copybook.COBOL · copybooks · JCL

Nothing is verified on Windows or macOS. Domain modules are pre-release. Nothing is verified by a customer yet, and nothing is verified on Windows. Do not rely on a capability for production work until it is verified for your tools, versions and operating system. Product names belong to their owners.

How a change moves

A person decides before anything leaves the desk.

  1. Propose
    An engineer or agent drafts a change to COBOL programs.
  2. Verify
    Your compilers and tests check it.
  3. Approve
    An upload to host data sets waits for a named approver.
  4. Record
    Change, results and approval kept together in the audit record.

Standards

Evidence for your controls. The audit opinion is your auditor's.

SOXEvidence toward SOX change control: the finance template makes payment and ledger changes and pushes to main wait for a named approver.
PCI DSSEvidence toward PCI DSS: agent reads of cardholder data and production credentials are denied and logged.

Neural Inverse provides evidence toward these standards. Certification stays with your organisation and assessor.

Talk to our team.

Neural Inverse is available by request. We work with your engineering, security and procurement teams from the first conversation.

Banking and mainframe · Neural Inverse