Start Today

← Documentation

OL Code

OL Code Documentation

OL Code is a browser-based workspace for exploring, editing, compiling, and modernizing legacy applications. Use Getting Started to connect to your mainframe or IBM i environment and open the workspace.

Explore and edit legacy source

Use the Explorer to browse datasets and members, open files in the editor, and manage source in your workspace. In checkbox selection mode, you can download selected members as a ZIP file.

Search members and content

When using OL Code through MCP:

  • Use member-name search for a narrow lookup. A query value is treated as a member-name pattern.
  • Use content search only with a specific PDS/dataset. This keeps scans scoped to that dataset instead of performing an HLQ-wide content search.
  • You can use regex matching independently for member names and content, choose case-sensitive content matching, and set a result limit (50 by default).
  • Select a content-search result to open the member at its matching line. If the member is already open, OL Code moves the cursor to that line.

Screen maps

OL Code parses and displays both CICS BMS and IMS MFS screen maps.

  • BMS parsing identifies map sets, sections, fields, screen size, positions, attributes, colors, highlighting, and input/output/label field types.
  • MFS parsing identifies the device format, fields, screen size, message count, cursor position, and PF-key definitions.

Use these views to understand terminal-screen layouts while working with the corresponding legacy source.

Upload members in bulk

Use the bulk-upload dialog to upload multiple members into a selected dataset. OL Code processes uploads sequentially in batches of five members and shows a per-member success or failure status.

  • If a batch fails, OL Code reports the failure for every member in that batch and stops the remaining batches.
  • The summary notification shows the total uploaded and failed members.
  • A completely successful upload closes the dialog; partial failures remain visible so you can review and retry them.

Compile and run jobs

When you compile or submit a mainframe job, OL Code allows time for the submission and polls job status until completion.

  • A job that is still active is not treated as a compilation failure merely because an initial wait period elapsed.
  • While a job is running, OL Code shows its job name and ID and opens the job-files view.
  • A job is complete when it reaches a terminal status such as OUTPUT, COMPLETED, FAILED, ABEND, or CANCELLED.
  • Successful return codes include CC 0000 and completion codes from CC 0000 through CC 0007.

Hub integration

Administrators configure Hub access in Admin > Settings.

  1. Enter the Hub URL and Hub API key.
  2. Select Test Connection to validate the current values without saving them.
  3. Resolve any reported connection or authorization error, then select Save Settings.

If Allow Custom Hub is enabled:

  • In the standalone Explorer, use Hub Settings in the header to set browser-local Hub overrides.
  • In SSO-enabled deployments, use the account Settings page instead.

Generated IBM i (AS/400) Hub members retain an uppercase extension, for example GETPETBY.CBL or OLAPICPY.CPY. Generated mainframe members omit the extension.

Retired capability: OL Code no longer provides Create Baseline / Analyze from the Explorer toolbar. The associated Planner baseline workflow and endpoints have been removed.

Help navigation

Use the in-product Help navigation for task-based guidance on Git workflows, AI assistance, compilation, Hub integration, RPC conversion, reverse API clients, dependency baselines, and administration.

Read more