Meet VERIFIn: JCL Validation Built Into Your Workflow
If you've spent any time submitting jobs on z/OS, you know the routine. You write the JCL, submit it, wait, and find out something's wrong only after JES has already rejected it or worse, run it. A missing DD statement. A duplicate parameter. A dataset you don't have access to. Seemingly small mistakes, but they cost time, and on a busy system they cost more than that.
VERIFIn was purpose built to close that gap. It validates your JCL before submission, checking syntax, parameters, and permissions, so you find out about problems on your own terms. Instead of a rejected job and a scramble to figure out why, you get clear feedback on every failure up front, before you ever submit. Fix it, submit, and move on.
VERIFIn isn't tied to one interface. It runs in ISPF, through batch, over USS, via REST API, and through the Zowe CLI. Whether you're in a terminal session or working through a more traditional interface, the validation logic is the same, and the results are just as trustworthy.
That flexibility has been the point from the start. Mainframe teams don't all work the same way, and a validation tool that only fits one workflow isn't much of a tool.
With this release, that same validation is available directly inside VS Code. VERIFIn's checks become part of your editor, not a separate step you have to remember to run. Write your JCL, get validation feedback in the same window, and catch the same syntax errors, parameter issues, and access problems before you ever leave your editor. When VERIFIn provides an error message, you can click it for further details and guidance on how to fix the issue.
For teams already living in VS Code for other parts of their workflow, this means one less context switch. You don't have to jump to ISPF or a terminal just to confirm your JCL is clean. The validation comes to you.
Whether you're working from ISPF, the CLI, or VS Code, the underlying philosophy doesn't change: no more finding out something's wrong after the fact. Write your JCL, let VERIFIn check it, fix what needs fixing, and submit with confidence. The interface is just the entry point. The value is knowing your job will run the way you expect it to, the first time.
VS Code integration is just the start, we have a plan to open the door for VERIFIn to integrate into your AI workflows, with more to share soon.
JCL Validation, Right Where You Write It
If you're modernizing your tooling and wondering whether VERIFIn is right for you, reach out, and let's talk about how many of your failed submissions never needed to happen.
Reach out to kaili.andre@21cs.com or visit 21cs.com. Let's set up time to show you what this looks like running on your own system.
Kaili Andre is z/OS Product Manager at 21CS