Legops

The Legops perform actions on remote hosts such as legacy IBM Mainframe, AS/400 and more..

You can manage LegOps in the Resource Center under the Legops tab.


🎯 What is a LegOps?

A LegOps (Legacy Operations) defines:

  • The type of backend system you're connecting to
  • Connection details (host, credentials, etc.)
  • Rules for which files to retrieve (filters, patterns, etc.)

Once defined, a LegOps can be used to explore remote systems and fetch source files such as COBOL programs, or PCML wrappers.


🧭 How to Create a LegOps

  1. Go to Resource Center → Legops

  2. Click ➕ New Legops

  3. Fill in the required fields:

    • Select the Type
    • Enter a Name and optional Description
  4. Fill in Configuration

  5. Provide the Connection Properties

  6. Save the LegOps

💡

You can also test the connection and preview available files after saving.


🛠 Supported LegOps Types

TypeDescription
as_400IBM AS/400 environments
mf_rseMainframe via RSE (Remote System Explorer)
ftpGeneric FTP server

Each type has a tailored configuration experience.


🧩 LegOps Structure

1. Basic Info

  • Type: Select one of the supported backend types.
  • Name: A unique ID for this LegOps.
  • Description (optional): Notes about this connection.

2. Configuration Fields

Depending on the selected type, you’ll see different configuration fields:

Common Fields

FieldDescription
PatternFile name or dataset filter (e.g. .*PGM, UNIT*)
RecursiveIf checked, searches subfolders/datasets (where supported)

AS_400

FieldDescription
LibraryThe AS/400 library to scan

MF_RSE

FieldDescription
DatasetDataset filter, e.g. ${HLQ}.**
Auto-detect File Extension StrategyHow to determine file types (see below)
Manual File ExtensionOverride the file extension manually
File Extension Strategies (MF_RSE)
StrategyBehavior
AUTOUses server metadata or content
SERVER_BASEDUses server-side mappings
CONTENT_BASEDUses file content to infer type
NONENo detection applied

3. Connection Properties

These fields vary per backend type, but generally include:

  • host
  • port
  • user
  • password
  • encoding
  • timeout (optional)

You must fill these in correctly to fetch files or test the connection.


📁 What Happens After Creation?

Once a LegOps is created:

  • You can view it from the Legops tab in the Resource Center.
  • You can fetch files using the pattern and connection details defined.
  • The fetched files can then be used for analysis, conversion, or enrichment inside the Hub Apps.

💡 Tips & Best Practices

  • ✅ Use specific patterns to narrow file searches.
  • 🧪 Test connections to ensure your credentials and filters are correct.
  • 🧵 Use AUTO file extension detection as a starting point for MF_RSE.
  • 🔁 LegOps definitions are reusable across the platform — define once, use often.