AutoSys JIL Viewer

Visualise, edit, and export AutoSys JIL job definitions as an interactive dependency graph inside VS Code.

Features

Interactive Graph Visualisation

Open any .asy diagram file and see your AutoSys jobs rendered as a live, zoomable dependency graph. BOX jobs appear as resizable framed containers; child jobs are laid out inside them automatically.

Job Types Supported

Properties Panel

Click any job on the graph to open a full property editor. Edit all job attributes — name, type, schedule, conditions, ownership, resources, and more — and save changes directly back to the .asy file.

JIL Export

Export diagrams to AutoSys JIL format (.JIL). Generates one file per diagram per environment, resolving environment-specific placeholders such as ${env.owner}, ${env.machine}, and ${env.group}.

Reverse-Engineer JIL → Diagram

Right-click any .JIL file in the Explorer and choose Reverse Engineer to .asy File to automatically generate a diagram from an existing JIL definition.

Logic Gate Wiring

Connect jobs with AND / OR / NOT logic gates to model complex dependency conditions visually, then export them as AutoSys condition: expressions.

Flexible Job Naming

Configure naming patterns per job type for JIL export using tokens like ${application.name}, ${jobSubType.prefix}, ${environment.code}, and more.

Getting Started

1. Install the extension from the VS Code Marketplace.
2. Create a new .asy file via File → New File → AutoSys JIL File (.asy).
3. Add jobs from the palette on the right, drag them to arrange, and connect them with dependency arrows.
4. Click a job to edit its properties in the AutoSys panel.
5. Click Generate JIL to export to AutoSys JIL format.

Configuration

All settings are under the autosys namespace in VS Code settings.

Applications & Environments

Define your applications and their per-environment values. Any field you add (e.g. group, permission) is available in job fields as ${env.<fieldName>}.

"autosys.applications": [
  {
    "name": "MY_APP",
    "environments": [
      {
        "name": "PROD",
        "owner": "svc_prod",
        "runAsUser": "svc_prod",
        "machine": "prod-server-01",
        "code": "P",
        "group": "PROD_GRP"
      },
      {
        "name": "DEV",
        "owner": "svc_dev",
        "runAsUser": "svc_dev",
        "machine": "dev-server-01",
        "code": "D",
        "group": "DEV_GRP"
      }
    ]
  }
]

Job Naming Patterns

Customise the exported job name per job type using pattern tokens:

"autosys.jobNamingPatterns": {
  "default": "${application.name}_${jobSubType.prefix}_${job.name}_${job.type}_${environment.code}",
  "BOX": "${application.name}_${job.name}_BOX_${environment.code}"
}

Available tokens: ${application.name}, ${jobSubType.prefix}, ${jobSubType.name}, ${job.name}, ${job.type}, ${jobType.prefix}, ${environment.name}, ${environment.code}

Job Sub-Types

"autosys.jobSubTypes": [
  { "name": "DAILY",   "prefix": "D" },
  { "name": "WEEKLY",  "prefix": "W" },
  { "name": "MONTHLY", "prefix": "M" }
]

Environment Placeholder Resolution

In any job field, use ${env.<key>} to substitute a value from the matched environment at export time:

File Format

AutoSys diagram files use the .asy extension and are stored as XML. They can be version-controlled alongside your other configuration files.

License

This extension is the property of Nihadi Technologies LLC. A 30-day free trial with full features is included upon installation — no credit card required. After the trial period, a valid commercial license must be purchased to continue use.

• 📄 To view the full license agreement inside VS Code, open the Command Palette (Ctrl+Shift+P) and run AutoSys: View License Agreement
• To purchase or manage your subscription, use the Command Palette: AutoSys: Subscribe / Upgrade
• To view the license inside VS Code, use the Command Palette: AutoSys: View License Agreement

AutoSys® and AutoSys Workload Automation® are trademarks of Broadcom Inc. Nihadi Technologies LLC is not affiliated with or endorsed by Broadcom Inc.