×
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.
*NULL is no value. Not even hex 00. The field just isn't there. Unless you've defined the field to allow nulls you'd never see a null value.
Paul Morgan
Principal Programmer Analyst
IT Supply Chain/Replenishment
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Greg Wenzloff
Sent: Tuesday, March 22, 2011 8:56 AM
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:
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
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.