JCL → Jenkins pipeline mapping

[Aakash Kochar]

As part of my current work, I happened to run into a scenario where Representing JCL steps as CI/CD stages—what patterns worked? Thanks in advance for any pointers.

[Anuj Dhawan]

If I have understood the question correctly, are you trying to use CI/CD to execute regular application batch JCL, or is this JCL performing build, deployment or automated testing activities?CI/CD is suitable for the latter - for example, compile/link-edit, DB2 bind, deployment and regression-test jobs. Regular production batch processing should generally remain under a workload scheduler such as Control-M or TWS. Therefore, mapping every JCL step directly to a CI/CD stage may not be the right approach without understanding the actual use case.

[hollow_rowan69]

Anuj's split between build deploy test JCL and production batch is the distinction that keeps CI/CD from becoming a second scheduler. Compile, link-edit, bind and regression jobs map cleanly to Jenkins stages; nightly application batch that already runs under Control-M or TWS usually should stay there, with Jenkins only triggering or reporting. A practical pattern is one pipeline per application artifact that submits the build JCL, archives listings, and fails the stage on nonzero return codes, while production calendars remain outside the pipeline. Trying to mirror every production step as a Jenkins stage tends to duplicate scheduling logic without adding safety.