Host connections are shared, and CoreIQ endpoints are picked from a list

Connections to a host now live on their own page and are created once, then reused by every application. Each has a reach — direct JDBC, or through OL CoreIQ — and an engine that is discovered rather than typed: a JDBC connection reports its own engine when you test it, and a CoreIQ connection takes its engine from the endpoint you pick, whether that is DB2 for z/OS, DB2 for i, IMS DL/I or VSAM datasets.

A new CoreIQ connection starts from the gateway configured in Global Settings, so its URL and default host are already filled in and the host list loads straight away. It then lists every data endpoint that host carries and lets you tick several at once, so a mainframe serving DB2, IMS and VSAM becomes three connections without retyping the URL, the host or the login three times.

One mainframe user is typed once and inherited by AtomIQ, CoreIQ and every connection unless a connection overrides it, and the Identity card names exactly what reads it and what overrides it. Connection ids can still be typed by hand when CoreIQ is unreachable, and the connection table shows reach, credentials and how many applications depend on each row before you open it.