× 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.


  • Subject: Re: Internally described files with null data
  • From: "Simon Coulter" <shc@xxxxxxxxxxxxxxxxx>
  • Date: Thu, 14 Jan 99 21:11:49 +1100

Hello David,

I am guessing that your friend is trying to create a file editor.  The only way 
I know of to handle generic 
program-described files is with C.  I am not certain but I am fairly sure that 
C can handle null-capable 
program-described files.  Of course, the actual file must be externally 
described otherwise it couldn't have 
null fields.  The only difficulty is dynamically handling the null-byte map.

Regards,
Simon Coulter.

//--------------------------------------------------------------
// FlyByNight Software         AS/400 Technical Specialists
// Eclipse the competition - run your business on an IBM AS/400.
// Phone: +61 3 9419 0175      Mobile: +61 0411 091 400
// Fax:   +61 3 9419 0175      mailto: shc@flybynight.com.au
// 
// Windoze should not be open at Warp speed.
//--- forwarded letter -------------------------------------------------------
> X-Mailer: Internet Mail Service (5.5.1960.3)
> Date: Wed, 13 Jan 99 10:31:55 -0600
> From: "David Gibbs" <David.Gibbs@IL.US.MKS.com>
> To: "'Midrange Mailing List'" <MIDRANGE-L@midrange.com>
> Reply-To: MIDRANGE-L@midrange.com
> Cc: "Bob Crafer" <Bob.Crafer@IL.US.MKS.com>,
>     "Brian Anderson" <Brian.Anderson@IL.US.MKS.com>
> Subject: Internally described files with null data

> 
> Folks:
> 
> An associate of mine is trying to do some strange stuff with internally
> described files... and he's running into problems with NULL data in a
> field.
> 
> Basicly, we're trying to extract data from a file that is internally
> described... but when we encounter null data in a field (either alpha or
> date) we get "Message . . . . :      CPF5029   Data mapping error on
> member CVRGCOMP [...] error code 19.  19 -- An unexpected null field was
> found."
> 
> We're defining a bunch of "I" specs for the maximum file size and then
> extracting the field information based on a DSPFFD output.
> 
> Apparently the ALWNULL parameter on CRTBNDRPG only applies to externally
> described files.
> 
> Any suggestions on how to deal with this error?
> 
> Thanks!
> 
> David

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.