Yep, there's always a solution.
I had an issue once where I couldn't get the parms right to pass to QSH so I stuffed them in the environment. Worked like a charm!
I remember how happy I was when we got the option to use CD instead of RQSDTA.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jim Oberholtzer
Sent: Monday, October 18, 2021 8:38 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [EXTERNAL] Re: Passing a parameter to a CLLE program in SBMJOB
IBM provided the solution long ago, a command. Clearly there are
architectural reasons IBM has so they have not changed the parameter
behavior in CL. They've had plenty of opportunity to, but have chosen not
to.
Don't like commands, fine, create a user space and stuff the parameter in
there, then grab it from the target program. Don't like user spaces, OK,
data queue, or data areas, or even a single record file. I'm sure others
will come up with more alternatives, maybe one you'll like. All have
positives/negatives but to complain that IBM has not changed a behavior you
don't agree with is not going to help.
Have you put in an RFE on this? IBM uses RFEs as a primary tool to decide
what enhancements to make.
Understanding the why is 90% of the solution.
--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
On Mon, Oct 18, 2021 at 9:57 AM Gerald Magnuson <gmagqcy.midrange@xxxxxxxxx>
wrote:
btw, every time this question comes up ( in over 35 years on the
platform). I steam with contempt for IBM for allowing this to continue.
midrange.com
