Start Today

← Documentation

Troubleshooting

Player cannot open a remote session

  • Confirm Global Settings for CICS/MQ or IMS Connect are saved (host + channel + queue manager, or host + data store).
  • Select an operation that has descriptors (Import maps, mainframe, AtomIQ, or example).
  • For CICS, start the target transaction (for example AQ00) on the mainframe before Play.
  • For IMS, set Play start (Entry MID / Trancode) on the operation or in My Maps.
  • Only one remote session per process — Close session on HTTP 409 / busy, or wait 15 minutes for idle release.

Screens look wrong or fields misaligned

  • Re-import maps and re-OPEN Player — descriptors are not hot-reloaded.
  • For CICS, the symbolic copybook must match the BMS map (one map per BMS file).
  • For IMS, each .mfs file must contain exactly one MID and one MOD.

Import from mainframe or AtomIQ fails

  • Save Global Settings first, then Test connection. AtomIQ Test uses the stored password only.
  • JZOS Test authenticates the user; catalog and member reads run as the USS process identity.
  • Stay within 50 selected members (mainframe) or 50 MiB for an .atq upload.

AI features not working

  • Configure an AI provider with a model name and a valid API key under Global Settings.
  • For local models, select Ollama and set the custom URL (default http://localhost:11434).

Session busy, misaligned screens, import Test, and AI setup.

Read more