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 z/OS integration

z/OS Mainframe Job Scheduling Without Installing Anything on 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.

Request a Demo

Nothing on the host

No agent or software installed on z/OS

Talks to JES

Submits JCL through the JES FTP interface as a TSO user

Full spool output

SYSOUT and job output land in the JAMS log

What JAMS Scheduler Runs on z/OS

You paste the JCL into the job’s Source tab and set the TSO user as Execute As. Schedules, dependencies, and alerts work like any other job.

JCL jobs

z/OS

Submits the JCL stored in the job to JES and polls until it completes. JCL steps behave as they do today.

JCL jobs

z/OS

Submits the JCL stored in the job to JES and polls until it completes. JCL steps behave as they do today.

Spool output in the log

JES spool

Pulls every output file from the spool, including SYSOUT DD statements, into the JAMS log, then purges them from JES.

Spool output in the log

JES spool

Pulls every output file from the spool, including SYSOUT DD statements, into the JAMS log, then purges them from JES.

Connection retries

z/OS Max Ftp Retry, Max Status Retry

Set how many times, and how often, JAMS Scheduler retries the FTP connection or a status check when z/OS holds a job in INPUT.

Connection retries

z/OS Max Ftp Retry, Max Status Retry

Set how many times, and how often, JAMS Scheduler retries the FTP connection or a status check when z/OS holds a job in INPUT.

How JAMS Scheduler Connects to z/OS

You define a passive agent with the zOS platform type and point it at the mainframe’s host name or address. JAMS Scheduler opens an FTP connection to the JES daemon, sends the job, and watches the spool.

Jobs run as a TSO user. Its credential is encrypted in JAMS Scheduler, and RACF controls what it can do on the mainframe.

Requirements

z/OS host

Nothing installed

JAMS Server

z/OS Integration installed

TSO user ID

7 characters or fewer, with rights to submit and receive jobs

JCL job name

Execute As user plus one character, for example IBMUSERA

Read the z/OS setup guide

Mainframe Jobs in a Cross-Platform Workflow

A nightly mainframe batch can wait for a Windows file drop, run its JCL, then hand its output to an SAP job or a file transfer.

If a step abends, the spool output is already in the JAMS log, so whoever is on call can see what happened and restart the job.

z/OS FAQ

Does JAMS Scheduler install anything on the mainframe?

No. JAMS Scheduler uses a passive agent and talks to JES over FTP as a TSO user. The z/OS Integration is installed on the JAMS Server only.

How does JAMS Scheduler submit JCL?

The JCL lives in the job’s Source tab. When the job runs, JAMS Scheduler opens an FTP connection to the JES daemon, sends the job, polls the spool until it completes, then purges the output files from JES.

Can a z/OS job depend on a Windows job?

Yes. A z/OS job takes the same dependencies as any other job, so it can wait on Windows, Linux, database, or ERP jobs, and they can wait on it.

Documentation

Working with credentials

Agents in JAMS

Related integrations

IBM i

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.

File Transfer

JAMS Scheduler moves files over FTP, FTPS, SFTP, SCP, or a network copy as ordinary jobs. Transfers retry on their own, accept wildcards, start when a file arrives, and alert you when one fails or stalls.

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.

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.