Industries
Mainframe operations, industry by industry.
The z/OS estates that still run settlements, claims, prices, bookings and payments have different nights. Meridian, Hexabin Infotech's product for mainframe operations, is the same in each. What changes is which batch matters, what it depends on, and what a late one costs.
Example data from a lab estate.
What the night's batch carries
- End-of-day settlement
- Payment files
- Policy renewals
- Premium billing
- Claims batches
- Sales posting
- Prices and stock
- Replenishment orders
- Revenue accounting
- Partner settlement
- Benefit payments
- Pension runs
- Payroll
- Planning runs
- Shipping manifests
Banking and payments
Settlement and payment files that must meet their cut-offs.
What the night's batch carries in banking
End-of-day settlement, interest and fee posting, statement runs, payment files to clearing houses and regulatory extracts, while CICS keeps serving card and channel transactions.
What goes wrong in banking
A late settlement batch misses a payment cut-off, and that is seen outside the bank.
What Meridian shows in banking
- The settlement and payment-file batches named, with their cut-offs and their state in words
- The CICS regions and Db2 subsystems those batches need, live
- Abends with the restart card, and whether the cut-off can still be met
Insurance
Renewals, billing and claims batches, with evidence ready for audit.
What the night's batch carries in insurance
Policy renewals, premium billing, claims batches and actuarial and finance extracts, often on IMS and Db2 applications that have run for decades.
What goes wrong in insurance
A late renewal or billing run lands on customers and on the finance close.
What Meridian shows in insurance
- Renewal, billing and claims batches with their deadlines
- IMS and Db2 status for the jobs that need them
- Every reply and restart recorded with its evidence, for audit
Retail
Sales posting, prices and replenishment, done before stores open.
What the night's batch carries in retail
The day's sales posted, prices and stock recalculated, and replenishment orders sent to suppliers and distribution centres before stores open.
What goes wrong in retail
A late batch means the wrong prices or empty shelves in the morning.
What Meridian shows in retail
- The sales posting, pricing and replenishment batches against the store-opening deadline
- Initiators and spool on the busy nights: weekends, promotions, season ends
- Alerts you set on the jobs and abend codes that matter
Airlines and travel
Revenue accounting and partner files on fixed schedules.
What the night's batch carries in airlines and travel
Revenue accounting, loyalty, crew and partner settlement, with files exchanged with other carriers and agencies on fixed schedules.
What goes wrong in airlines and travel
A late run delays the files partners are waiting for.
What Meridian shows in airlines and travel
- Revenue accounting and partner file batches with their send times
- WTORs and abends holding the jobs, at the top of the console
- Ticket write-back, so the service desk sees what operations did
Government and public sector
Benefit, pension and payroll runs with fixed payment dates.
What the night's batch carries in government and the public sector
Benefit payments, pension runs, tax processing and payroll, on long-lived z/OS applications with fixed payment dates.
What goes wrong in government and the public sector
A late payment batch reaches citizens directly.
What Meridian shows in government and the public sector
- Payment and payroll batches against their payment dates
- Four-eyes approvals where the rules require them
- An exportable audit trail of every action
Manufacturing and logistics
Planning and dispatch batches the next shift depends on.
What the night's batch carries in manufacturing and logistics
Planning runs, order processing, shipping manifests and invoicing, in nightly and weekly cycles.
What goes wrong in manufacturing and logistics
The next shift's production and dispatch depend on these runs. A late one leaves the shift without its plan or its manifests.
What Meridian shows in manufacturing and logistics
- Planning and dispatch batches with the shift start as the deadline
- Subsystem status for the jobs that need it
- Flows that handle the routine WTORs and restarts you approve
Mainframe service providers
All of the above, for many clients at once.
What the night's batch carries at mainframe service providers
Providers run all of the above for many clients at once, with an SLA and often a credit on every batch.
What goes wrong at mainframe service providers
A late batch is a missed SLA for that client. Meridian was built for this job: one install, every client, every LPAR, each client with its own people, rules and reports.
What Meridian shows at mainframe service providers
- Every client's batches and SLAs, each screen naming the client shown
- Attainment and prediction accuracy reports per client
- Per-client rules, roles and approvals
One product
The same Meridian in every industry.
There is no special edition. Each estate names its own batches, deadlines, conditions and rules, so Meridian fits the night your business runs.
- Named batches with their deadlines and conditions, defined by your SMEs and approved by a manager.
- Runs inside your network. Your data never leaves it.
- Approvals and four-eyes per client, and every action recorded with its evidence.
- CA 7 and ServiceNow today, with CICS, IMS, Db2 and Adabas status.
Example data from a lab estate.
Is there a separate Meridian for each industry?
No. It is the same product everywhere. Each estate names its own batches, deadlines, conditions and rules, so it fits the industry without a special edition.
Does our data leave our network?
No. Meridian runs inside your network, and nothing is sent to Hexabin. That matters most in regulated industries, and it is the same for everyone.
Can approvals be required before actions?
Yes. Approvals and four-eyes can be switched on per client, and every action is recorded with what Meridian saw, who confirmed it, the time and the outcome.
Which schedulers and subsystems does Meridian support?
CA 7 and ServiceNow today, with CICS, IMS, Db2 and Adabas status. Other schedulers and ticket tools are on the roadmap. Tell us what you run.
See it on your own estate.
A ninety-day proof of concept on one LPAR, free, with our engineers on the call. After ninety days you decide on your own results.