|
Excellent. This works beautifully. I was unaware of that fact about parameters, but it makes sense, when you consider that programs you call can change the values in the called parameters, and the actual copy is changed (passed by reference, I believe is the term.) I have since realized, that since I am using the qualified parameter to send to an API (QUSLMBR, parm 3), there is no need to parse out the file and library name, I can simply pass the parm to the API. But when I use the SrcFile variable as a parm to this API, I get a 'Severe error while addressing parameter list.' error. I assume this is because I am passing a pointer to storage my job doesn't own? I guess I will have to break down and simply pass the parm to a DS, then pass the DS to the API. 'Severe' sure sounds menacing... ;-) -- "Enter any 11-digit prime number to continue..."
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.