|
That is true, I forgot that QCMDEXEC basically works on the same strings-snip-
as a command line. Too many things get paged out of memory over time.
Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx
From: Vern Hamberg<vhamberg@xxxxxxxxxxx>
To: Midrange Systems Technical Discussion<midrange-l@xxxxxxxxxxxx>
Date: 10/20/2010 06:43 PM
Subject: Re: passing Call commands (with parms) from program to
program
Sent by: midrange-l-bounces@xxxxxxxxxxxx
You can still get garbage using QCMDEXC with the length correctly set.
This will happen when using QCMDEXC to do a CALL when character
parameters in the program are longer than 32. The system only guarantees
padding with blanks out to the first 32, after that you get what's in
memory - maybe the next few parameters, maybe anything.
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.