speculation about interfacing REST API from rexx
Moderator: mickeydusaor
- Pablo-Fuentes
- New Member
- Posts: 1
- Joined: Wed Dec 03, 2025 3:08 pm
speculation about interfacing REST API from rexx
Integrating modern REST APIs into mainframe workflows can significantly enhance agility, but many still hesitate due to perceived complexity. Is it truly that difficult to bridge legacy COBOL or REXX with cloud-native services? Could making REST calls from REXX be the key to unlocking a new era of mainframe adaptability and real-time data access?
- Anuj Dhawan
- Founder
- Posts: 2838
- Joined: Sun Apr 21, 2013 7:40 pm
- Location: Mumbai, India
- Contact:
Re: speculation about interfacing REST API from rexx
Welcome to the forum Pablo-Fuentes, great to have you here!
It’s a great question — and in many cases, the perceived complexity is actually larger than the real effort involved. COBOL and REXX already have mature ways to invoke REST services today, whether through the z/OS Client Web Enablement Toolkit, Unix System Services (like using curl), or API-gateway–driven integration layers.The real difficulty isn’t making the REST call itself — that part is usually straightforward. The bigger challenges tend to be around TLS/cert management, JSON handling, timeouts, retries, and ensuring everything aligns with enterprise security and performance standards.Once those guardrails are in place, REST-enabling legacy workflows becomes just another I/O pattern, and it opens the door to real-time integrations and much more adaptive mainframe workflows.
It’s a great question — and in many cases, the perceived complexity is actually larger than the real effort involved. COBOL and REXX already have mature ways to invoke REST services today, whether through the z/OS Client Web Enablement Toolkit, Unix System Services (like using curl), or API-gateway–driven integration layers.The real difficulty isn’t making the REST call itself — that part is usually straightforward. The bigger challenges tend to be around TLS/cert management, JSON handling, timeouts, retries, and ensuring everything aligns with enterprise security and performance standards.Once those guardrails are in place, REST-enabling legacy workflows becomes just another I/O pattern, and it opens the door to real-time integrations and much more adaptive mainframe workflows.
Thanks,
Anuj
Disclaimer: My comments on this website are my own and do not represent the opinions or suggestions of any other person or business entity, in any way.
Anuj
Disclaimer: My comments on this website are my own and do not represent the opinions or suggestions of any other person or business entity, in any way.
Create an account or sign in to join the discussion
You need to be a member in order to post a reply
Create an account
Not a member? register to join our community
Members can start their own topics & subscribe to topics
It’s free and only takes a minute