Mainframe Developer

Novalink Solutions LLC•West Columbia, SC

16h

About The Position

The Office of the State Treasurer is hiring a Mainframe Developer to add composite reservoir accounts (CRAs) to an existing z/OS accounting platform. CRAs pool balances from multiple subsidiary accounts into a single reservoir account and distribute balances back under defined sweep and allocation rules. The work extends a long-running legacy system, requiring analysis of lightly documented COBOL and careful integration of the new account type so that it posts, settles, accrues, reports, and reconciles consistently with existing account types. Correctness and traceability are prioritized.

Requirements

At least 5 years of Enterprise COBOL development experience in a z/OS environment.
At least 5 years of experience with NaturalOne.
At least 3 years of JCL development and production-support experience.
At least 3 years of financial/accounting systems development or support experience, including double-entry posting, balance and accrual maintenance, value dating, reconciliation, and month-end closeouts in a regulated environment.
At least 3 years of experience working with Adabas and VSAM.
At least 3 years of experience tracing undocumented logic through copybooks, call chains, and job streams.
Substantial production experience with Enterprise COBOL on z/OS, in both batch and online environments, including extending large existing programs and reading code written by others.
Experience developing, debugging, and deploying Natural applications in NaturalOne, including local development and remote z/OS projects.
Experience with Natural programs, subprograms, and maps; DDMs, descriptors and superdescriptors; and Adabas file design and performance behavior.
Experience writing and debugging JCL, procedures, GDGs, utilities, SORT, and restart/rerun handling; fluency in TSO/ISPF.
Experience with VSAM file design and access and Adabas for z/OS.
Ability to trace undocumented logic through copybooks, call chains, and job streams and clearly explain the scope and effects of a change.
Track record of carrying a specification from analysis through production implementation with limited supervision.
Clear written communication skills, including the ability to explain changes to auditors, business analysts, and developers.
A degree in computer science or a related field, or equivalent practical experience.

Nice To Haves

Experience with cash management, account pooling, sweeps, or treasury applications.
Experience with CA-7 scheduling and batch operations.
Experience with REXX, Python, or Java.
Experience integrating COBOL and Natural, or exposing mainframe functionality through z/OS Connect, IBM MQ, or REST services.
Experience with CA-7 batch-window analysis and performance tuning.
Experience with REXX or CLIST tooling, or Java or Python for data comparison and migration work.
Knowledge of notional and physical pooling, cash concentration, sweeps, and intercompany allocation.

Responsibilities

Analyze existing account master, posting, and balance-maintenance programs to determine where composite reservoir accounts must be recognized, and document findings.
Design and implement the new account type end to end, including master-file and table structures, account opening and closing, participant linkage, sweep and reverse-sweep logic, allocation and interest apportionment, and closing-balance derivation.
Modify batch COBOL programs and JCL and extend nightly and month-end cycles while keeping the batch window within agreed limits.
Add composite reservoir accounts to audit trails, exception reporting, and reconciliation controls, working with accounting stakeholders to establish evidence requirements.
Produce test data and unit and regression test packs; compare parallel-run results with current production output and investigate every difference.
Support implementation, conversion of in-scope existing accounts, and early-life production runs, including on-call coverage during the first cycles.
Prepare program documentation, data-flow notes, and runbook updates for the support team.
Take specifications from analysis through production implementation with limited supervision.
Explain changes clearly to auditors, business analysts, and developers, adapting communication to each audience.
Follow formal change control, peer review, and signed-off implementation plans for production changes.