Product

IntegrationsAll integrations

Featured

Platforms

Scripting

Business apps

Data & reporting

Cloud & file transfer

Resources

Migrations

JUMP Migration ToolAutomate most of your scheduler migration

Migrate fromAll migrations

Featured

Redwood

Broadcom

SMA

IBM / HCL

Independent

Free & native tools

JUMPJUMP eligible: convert your jobs with a free Dry Run

Free trial

JAMS IBM i integration

IBM i (AS/400) Job Scheduling Across Your Whole Environment

The JAMS Agent for IBM i runs CL commands and programs on IBM i (i5/OS and OS/400) over TCP/IP, deploys from the JAMS client, and ties IBM i work to Windows, Linux, JD Edwards, and SAP jobs.

Request a Demo

Execution method

OS400

Deploys from

The Agents view in the JAMS client

Passwords

Up to 128 characters

What JAMS Scheduler Runs on IBM i

Enter CL commands in the job, one per line, with comments in /* */. Long commands can span lines that end in a space and a plus sign. Schedules, dependencies, and alerts work like any other job.

IBM i jobs

OS400

Runs IBM i and OS/400 jobs, with multiline CL commands that follow CL programming rules.

IBM i jobs

OS400

Runs IBM i and OS/400 jobs, with multiline CL commands that follow CL programming rules.

TLS

STRJAMSSSL

Turns on TLS 1.2 between JAMS Scheduler and the agent.

TLS

STRJAMSSSL

Turns on TLS 1.2 between JAMS Scheduler and the agent.

How JAMS Scheduler Connects to IBM i

The agent ships with the JAMS Scheduler and is pushed to IBM i from the Agents view. If FTP is blocked, install it by hand: create the JAMS user profile and the JAMSLIB library, restore the save file, and start the JAMS subsystem.

JAMS Scheduler connects to the agent over TCP/IP. Each JAMS user who runs IBM i jobs needs the matching IBM i access.

Requirements

Deployment

Push from the Agents view, or manual with JAMSLIB

User profile

JAMS, with *JOBCTL, plus *ALLOBJ for TLS

Encryption

TLS 1.2 with STRJAMSSSL

Library list

JAMSLIB in the user library list only

Read the IBM i agent guide

IBM i Jobs in a Cross-Platform Workflow

An IBM i batch can wait on a Windows file drop, then start a JD Edwards report or an SAP job.

For more on running IBM i work in the same schedule as everything else, read IBM i jobs don’t live on an island.

IBM i FAQ

How does JAMS Scheduler connect to IBM i?

Over TCP/IP, through the JAMS Agent for IBM i. The agent deploys from the JAMS client’s Agents view.

Can I deploy the agent if FTP is blocked?

Yes. Create the JAMS user profile and the JAMSLIB library, copy the save file over, restore it, and start the JAMS subsystem.

Can an IBM i job depend on a Windows job?

Yes. IBM i jobs take the same dependencies as any other job, in either direction.

Documentation

Agents in JAMS

Working with credentials

Related integrations

JDE

JAMS Scheduler runs JD Edwards EnterpriseOne reports on Windows or Linux, on the same schedules and dependencies as the rest of your batch. A UBE can wait for a SQL Server load to finish, then start the file transfer that ships its output.

z/OS

JAMS Scheduler submits your JCL to JES over FTP, waits for it to finish, and pulls the spool output into the job log. Nothing gets installed on the mainframe, and z/OS jobs share dependencies with Windows, Linux, and SAP work.

Windows

The JAMS Agent for Windows runs batch files, commands, executables, PowerShell, and VBScript on any Windows server, under the direction of one JAMS Scheduler. Jobs on agents keep running through a scheduler failover.

SAP

JAMS Scheduler runs SAP background jobs, BW process chains, and BusinessObjects Data Services jobs in the same workflows as your Windows, SQL Server, and Linux jobs. An SAP job can wait on a job anywhere else in your environment, or start one.