If this CPYF statement is in a CL program could you use a *CHAR field
&BLANKS?
On the other hand, what is wrong with a spaces-constant ' '?
So what if there is no special-value '*BLANKS' to work with? Either of the
two previous solutions should work, it's coding-semantics to say that ' '
or
&BLANKS is not good programming. I don't believe there will be a measurable
performance issue between them.
Jeff Bull
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Greg Wenzloff
Sent: 22 March 2011 12:56
To: midrange-l@xxxxxxxxxxxx
Subject: CPYF and *NULL .....
I had a CPYF statement in a CLP that compiled without error but got a
syntax error when it ran:
CPYF FROMFILE(BLRATEP) TOFILE(BECKTFR/BLRATEP) +
MBROPT(*ADD) INCREL((*IF BLSDT *GT 0) +
(*AND BLWHS *NE *BLANKS))
The error said that value of the second test use not valid.
I looked into the reference manual and found that *BLANKS was not
addressed but that *NULL was.
I switched out *BLANKS for *NULL and recompiled the program.
Now I'm thinking this decision was wrong and I should just use a string
like " ".
To me *null is a hex 00.
Blanks are hex 40.
Any suggestions on how to phrase BLWHS *NE *BLANKS?
I should know this but brain not functioning well today,
Greg
--
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.
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.894 / Virus Database: 271.1.1/3520 - Release Date: 03/21/11
19:35:00
midrange.com
