×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Using a SBMJOB to call program with parms that exceed 32-characters in size
but less than 32 characters in non-blank data in those fields.
Turns out that if a CL uses SBMJOB to call another program, you can pass
"small" parms without issue. Passing "ABC@xxxxxxx" as an email address in
a 32 character field works. However, passing "ABC@xxxxxxx" in a 50
character fields doesn't work. The system does not guarantee the value of
the data to the right of the last non-blank character after the 32nd
character. In the 50 character field, positions 33-50 could be blank as
expected, or they could pick up garbage from memory.
Changing the sbmjob back to a interactive call makes the problem go away
(makes debugging fun).
The solution is to make it a 51 character and make the last position a
non-blank character. The called program will receive the 51 character parm
and can then strip out the first 50 character for actual processing.
I can't put my cursor on it at the moment, but yes, IBM does document this
"feature".
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
