|
> I understand the issue when passing literals. But in situations like the > one I had today where a CL program was submitting itself with all > parameters being declared valiables we shouldn't have to "work around" > anything just because 1 or more of them is greater than 32 bytes. Programs pass data back and forth by receiving pointers (memory addresses) of the data that you specify in a parameter. However, when you do a SBMJOB, the new job can't have a pointer to the data, since it's a different job. Therefore, a command line is created containing the program to execute in the new job, and new memory is allocated, etc, when the new job starts. I'm not trying to solve the problem here, just explain why it happens.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.