|
"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 08/05/2016command processing program.
12:31:48 PM:
This has to be a command line thing. I wonder if I need to createwhole
the
command in a variable and then use QCMDEXEC to execute it. Any ideas?
Normally, there isn't an issue between command use from a
command line vs. command use from a CL program. As long as the
command can be prompted without errors in either environment then the
editor will format it correctly in the CL program source for
compilation and subsequent execution. The issue comes when calling a
CL program without using a command interface.
The reason is that the command-line processor (in either
environment) has to make some assumptions about literals used as
parameters in the CALL parameter list. Those assumptions are (1) that
string literals will be blank-padded to a minimum length of 32
characters or a maximum length equal to the actual length of the
string literal, (2) that numeric literals are always formatted as *DEC
15 5, and (3) floating-point literals must be formatted using
floating-point syntax. The processor for a command interface doesn't
have that issue because the command contains all the data type
definition information required to correctly format the interface to the
transmission.
So, that said, I presume you can prompt the "failing" command
in your CL source and the editor reformats the results as needed and
without errors? If so, then it is the command processing program
associated with the command interface, itself, that is failing to
handle the parameters appropriately in an *IPGM or *BPGM environment.
Sincerely,
Dave Clark
--
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300
Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331
**********************************************************************
*********************** This email message and any attachments is for
use only by the named
addressee(s) and may contain confidential, privileged and/or
proprietary information. If you have received this message in error,
please immediately notify the sender and delete and destroy the
message and all copies. All unauthorized direct or indirect use or
disclosure of this message is strictly prohibited. No right to
confidentiality or privilege is waived or lost by any error in
--
**********************************************************************
***********************
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
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
