×
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.
hi John,
syscmd="CALL SSYSNDMSG PARM('SPBAHCNCL - Retrieving file: $i\$')"
system $syscmd
My guess is that this SSYSNDMSG program is corrupting memory. Keep in
mind the way parameters to a CL program work... if the CL program has
this parameter defined (for example) as *CHAR 200, then you need to make
sure that the string you pass to the program is at least 200 characters
long. If it's not, then you'd better hope that the programmer who wrote
SSYSNDMSG knew that he was going to be interfaced with a QShell script,
and understood how to handle it properly.
Otherwise he might've done something like "hey! I got garbage in my
parameter. No problem... I'll translate teh garbage to blanks". The
problem is, the garbage didn't actually BELONG to the parameter, it was
part of something else in memory. When he blanked it out, he chagned
that memory, messing up other variables and/or code in job that's
unrelated to his CL program. And therefore... MCH3601 (which is
about the best possible result you can get from that sort of corruption)
Try removing the call to SSYSNDMSG and see if you still get the error.
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
