×
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.
On 10/07/2004, at 8:41 AM, Buck Calabro wrote:
The help says that ALWNULL works with externally described files. I
don't see any equivalent for program described files...
There isn't. How could there be? A program-described file is one big
field. How would the database know that the 12 bytes at offset 103 is
really a null-capable field? How could it set the null-byte map
correctly?
Because the null-byte map uses 1 byte per field in the file (and is set
to 0 for not null and 1 for null) there would only be 1 null indicator
reflecting the state for the entire record (since a record in a
program-described file is a single field).
The file you are reading must be externally-described because you
cannot create a program-described file with null-capability. You have
to use DDS to define null-capability and all DDS defined files are
externally-described by definition.
Do you just want to process an externally-described file with nulls AS
IF it were program-described? If so why? What are you trying to
achieve? There is probably an alternative that will work if you can
explain what you want to do.
You could do this by creating your own UFCB and building the null maps
yourself but you're probably looking for something easier.
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software AS/400 Technical Specialists
http://www.flybynight.com.au/
Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\
Fax: +61 3 9419 0175 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
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
