Legops
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
-
Go to Resource Center → Legops
-
Click ➕ New Legops
-
Fill in the required fields:
- Select the Type
- Enter a Name and optional Description
-
Fill in Configuration
-
Provide the Connection Properties
-
Save the LegOps
💡 You can also test the connection and preview available files after saving.
🛠 Supported LegOps Types
| Type | Description |
|---|---|
as_400 | IBM AS/400 environments |
mf_rse | Mainframe via RSE (Remote System Explorer) |
ftp | Generic 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
| Field | Description |
|---|---|
| Pattern | File name or dataset filter (e.g. .*PGM, UNIT*) |
| Recursive | If checked, searches subfolders/datasets (where supported) |
AS_400
| Field | Description |
|---|---|
| Library | The AS/400 library to scan |
MF_RSE
| Field | Description |
|---|---|
| Dataset | Dataset filter, e.g. ${HLQ}.** |
| Auto-detect File Extension Strategy | How to determine file types (see below) |
| Manual File Extension | Override the file extension manually |
File Extension Strategies (MF_RSE)
| Strategy | Behavior |
|---|---|
AUTO | Uses server metadata or content |
SERVER_BASED | Uses server-side mappings |
CONTENT_BASED | Uses file content to infer type |
NONE | No detection applied |
3. Connection Properties
These fields vary per backend type, but generally include:
hostportuserpasswordencodingtimeout(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
AUTOfile extension detection as a starting point for MF_RSE. - 🔁 LegOps definitions are reusable across the platform — define once, use often.
The document outlines the functionalities of different Legops types, including creating legops instances, configuring properties, connecting to remote hosts, and running specific actions such as creating and testing connections, fetching data, and executing commands for as400, ftp, and mf-rse servers.