Phased modernization

The mapper has no fields until the steps are connected

I am mapping the new process to the host program and the expression inputs are empty. Is the asset missing?

Run the VSAM batch load once, not as a permanent service

We have the .odz pack for this process. Do we run it once from the CLI or leave the batch service up?

We cannot delete a shared business model that this process still uses

I tried to delete a business model from the spec and it was blocked. Is that a bug?

RSE, JT400, CoreIQ, or a file upload for this one process?

We only need the programs for one process. Which import should we use?

Can the new process and the host path share one contract?

Channels want one contract whether the process still runs on CICS or on the new service. Can we do that?

Generate the Reverse API client from Hub or from an OpenAPI file?

We can generate the COBOL client from a Hub method or by uploading OpenAPI. Which one should we use for this process?

Which CoreIQ APIs stay up until the old path is retired?

We are replacing one claims process. Which host APIs should stay in place so the rest of the application keeps running?

Turn one IMS segment layout into a SQL table for the new process

This process only needs two IMS segments. How do we get SQL tables without migrating the whole database?

The API integration points wizard shows yesterday's AtomIQ tree

We re-imported operations and the API integration points wizard still shows the old tree. Does it call AtomIQ live?

We found the programs. How do we know they are one process?

Search found thirty programs that mention claims. How do we tell whether that is one business process or three?

The process we are not rewriting is still a 3270 conversation

One process is becoming a service. The process next to it is still a 3270 conversation we will keep for now. How do channels call that one?

The generated Reverse API client compiles, then the host sees the wrong characters

We generated a COBOL client for the new HTTP API. The call works and the text fields are garbled. Where do we look?

We enabled CDC and someone still wants the new service to update the KSDS

Dataset CDC is on. Does that mean the new service can also update the same VSAM file CICS updates?

Create the SQL table from the CoreIQ layout, not from JDBC metadata

We generated a CREATE TABLE from JDBC and the packed fields came out wrong. What should the column types follow?

Build the spec from an AtomIQ export when the live link is down

The AtomIQ workspace link is down and we still need a spec for this one process. Is there a path that does not call AtomIQ live?

Nobody documented the operation. How do we regress it before cutover?

The process we want to peel off was never specified. How do we know the new service matches what the host does today?

Keep an inbound API up while we rewrite a single process

Digital channels already call this CICS transaction. We are replacing only one process behind it. How do callers keep working?

The COBOL program has to call the new HTTP service

The new claims service is HTTP. The nightly COBOL job still has to call it. How does the host program reach it?

CICS still updates the VSAM file the new service also writes

We peeled off one process, but CICS still updates the same KSDS. Can the new service write it too?

Move only the tables this process needs, not the whole VSAM file

The new service needs a handful of columns from a VSAM file. Do we migrate the file, or leave it and copy a slice?

When do we freeze the spec before generating the new service?

We are still editing the process spec and someone already generated artifacts. What should have been frozen first?

Four thousand COBOL programs. Where do we start if we modernize one process?

We have about four thousand COBOL programs. Leadership wants one business process modernized, not a rewrite. Where do we actually start?