Re: AW: AW: Handling null-capable fields with program-described file--reading externally described using program defined layout

Hi Birgitta,

Thanks -- it was a good idea, but unfortunately it had the same result.

The question is, why is this mapping taking place? The program doesn't have any individual fields for it to map into, so does it read the record into a buffer, then do the mapping based on the external definitions of the file into some intermediate space, then copy the resulting mapped record to the single program-described input field in my program? Seems like a lot of extra work for nothing, except of course it's concerned about the null fields. But then I would expect the ALWNULL(*INPUTONLY) to have worked, so there must be something else going on.

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

BirgittaHauser wrote:

Hi,

Yet an other idea:
What if your create an external described physical file with a single null
capable field.
Add this physical file as external described data structure in your program
and read your data into this 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: Sunday, August 12, 2007 22:42
An: Midrange Systems Technical Discussion
Betreff: Re: AW: Handling null-capable fields with program-described
file--reading externally described using program defined layout


Thanks Chuck. Good thought, but it didn't work. I tried with with the first file I could think of and it didn't work, but then I realized that file had no null values (and no null-capable fields) so I tried it with the file that's actually causing the problem, but sad to say it didn't work. One of these days I'll get around to using the C apis...

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

CRPence wrote:

I was just thinking [I have not tried this, nor the originally given
scenario], what about adding any externally described file to the F-Specs [and maybe also add a user open which is never performed]? Just possibly, the compiler ignores the request to override the database file open option because there are no externally described files declared, versus more likely, that the specific open is declared as being program described.

Regards, Chuck