โ—† PROTOTYPE / CLICKABLE MOCKUP โ€” not published, not indexed. Use-case landing page per the SEO & Website Action Plan.
Home › Use Cases › Documentation & Modernization

Document and Understand the Business Logic in Your Nonstop Applications

Generate documentation, extract business rules, build searchable knowledge, and ask trusted AI questions before you modernize.

The problem

Modernization planning runs into the same wall every time: the business logic that matters is buried in decades-old COBOL, TAL, SCOBOL, and TACL. The people who understood it are retiring, and the documentation either does not exist or no longer matches the source.

NavigatorHow Navigator helps

Point Navigator at representative programs or the full codebase and it generates, from your actual source:

AtlasHow Atlas helps

Navigator gives you the narrative. Atlas gives you the structural reality underneath it: architectural clusters, orphan programs, shared files, dependencies, and risk areas that shape modernization sequencing.

The workflow

  1. Run Navigator across representative programs or the full codebase.
  2. Generate source-based documentation and business-rule summaries.
  3. Use Chat Navigator to fill knowledge gaps before SMEs retire.
  4. Use Atlas to identify dependencies, orphan programs, shared files, and migration risk.
  5. Build a modernization roadmap grounded in both business logic and code structure.

Example scenario

Illustrative A typical workflow, not a specific customer result.

  1. 01

    Trigger Two senior developers are retiring

    An insurer preparing to modernize a claims system on HPE Nonstop (Tandem) needs the logic captured before the people who wrote it leave.

  2. 02

    Navigator Document the codebase

    Navigator runs across several hundred COBOL and TAL programs, generating documentation and extracting the premium-calculation business rules.

  3. 03

    Chat Navigator Capture what only the experts know

    Plain-English questions about the legacy logic get answered while the experts are still available, so the knowledge is held in the system rather than in people.

  4. 04

    Atlas Map the real dependencies

    Atlas flags orphan programs and shared Enscribe files that the documentation alone would not reveal.

  5. 05

    Outcome Sequenced by dependency, not guesswork

    The team plans the migration against the codebase's actual structure instead of assumptions about it.

FAQ

What source files are required?
Your source: COBOL, TAL/pTAL, SCOBOL, TACL, and C/C++ programs, plus copybooks and file/DDL definitions where available. The more complete the source, the richer the documentation.
Can this run without sending source code to an external AI service?
Yes. On-premises deployment is available, and Navigator's Reference Tier answers from source-analysis facts without a cloud LLM.
How is Navigator different from ChatGPT, Claude, or Copilot?
General assistants answer from model memory and do not understand Nonstop semantics. Navigator answers from analysis of your actual source, grounded in COBOL/TAL/SCOBOL/TACL and Nonstop patterns like Guardian, Pathway, and Enscribe.
What outputs can be exported for audit or review?
Documentation packages, business-rule summaries, diagrams, and searchable knowledge โ€” exportable for review, audit, onboarding, and modernization planning.
Can TIC analyze COBOL, TAL, pTAL, SCOBOL, TACL, and C/C++?
Yes โ€” those are the core Nonstop languages TIC is built to analyze, along with copybooks and Enscribe file structures.