AW: Handling null-capable fields with program-described file--readingexternally described using program defined layout

Hi,

Have you already tried to use embedded SQL?
And fetch the complete row into a long character field and move it after
into the internally described data structure?

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Peter Dow (ML)
Gesendet: Wednesday, August 15, 2007 00:20
An: Midrange Systems Technical Discussion
Betreff: Re: Handling null-capable fields with program-described
file--readingexternally described using program defined layout


Thanks Barbara! Well, rather than consider this a bug or a feature, I'm
considering it an opportunity to learn about the C APIs. Thanks to all
who responded!!

*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
pdow@xxxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxxx> /

Barbara Morris wrote:

Peter Dow (ML) wrote:

You said "The current behaviour may seem like a bug for an
application
that wants to behave like DSPPFM; but it is a feature for an application
that was never intended to work if a record had a null-valued field."
My feeling is that the application that wants an error when a null value
is encountered can just use ALWNULL(*NO); the application that wants to
behave like DSPPFM (mine!) should be able to specify ALWNULL(*INPUTONLY).

Was Chuck Pence's explanation of what's going on correct? Is it just
that the open for a program-described file is not requesting
ALWNULL(*INPUTONLY) for that file?

Peter, I personally agree that ALWNULL(*INPUTONLY) _should_ have also
applied to program described files; I don't know why it was restricted
to externally-described files. But since it didn't apply to pgm-desc
files when *YES was first introduced in V2R1 or when *INPUTONLY (= *YES)
was introduced in V3R7(?), it can't start applying to them now. Some
new syntax would have to be added that would make alwnull apply to
program described files.

Yes, Chuck's explanation was correct.