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



     Jim,
     
     Just to set the record straight, fixed length records are 
     "traditionally" used on the as/400, but varying length records are 
     certainly doable on os400. RPGIV handles varying length fields and 
     record formats pretty well, though even RPG400 had minimal support 
     for varying length fields/formats.


______________________________ Reply Separator
_________________________________
Subject: Re: Unix API read()
Author:  "Jim Langston" <SMTP:jimlangston@conexfreight.com> at EXCHANGE
Date:    12/26/00 11:49 AM


It seems from the data that it is being padded *before* the 
OD 25.  So each record would be a different length.
     
DB2 files all have records of the same length.  There are no 
variable length records (don't take that as an absolute, as I'm 
sure someone could come up with a SQL file that has variable 
length records).
     
Try creating the record length on the read function to longer 
than the records are.  That is, if you are expecting 176 length 
records, actually ask the unix read function to read 255 length
records.  The end of the record should be padded with spaces (x40) 
or maybe nulls (x00).
     
I think the error is probably coming from you specifying 176 length 
records, and since the record is longer than 176 the call is complaining 
that it didn't read the entire records, which it didn't.
     
Regards,
     
Jim Langston
     
Phil Groschwitz wrote:
>
> Do you mean it pads within the record in order to
> align the data with the prior record?  Or pads after 
> the crlf?  How does edtf display these two hex
> examples exactly the same when one has fewer blanks 
> before the crlf than the other?
>
> Thanks for your help.  I want to be able to read in 
> this file and parse it but this is causing trouble! 
>
> Thanks,
>
> Phil
>
> --- Rolf Mittag <rm@r-m-e-d-v.de> wrote:
> > I think Notepad and EdtF are simply padding the 
> > records which have
> > different lengths with blanks. The EBCDIC "0D" and 
> > "25" stand for
> > carriage return = end of line = end of record. I 
> > marked them with "^"
> > (caret).
> >
> > Rolf
> >
> > C1F0F1F2 F0F1F1F6 F0F0F440 F3F4F0F4   :A012 0116 004 
> >  3404:
> > F6F04040 4040F1F1 61F2F161 C1F04040   :60     11 
> > /21/ A0  :
> > 40F0F1F0 F0F1F0F1 F0404040 40404040   : 010 0101 0 
> >      :
> > 40404040 40404040 40404040 40F0F0F0   : 
> >   000:
> > F0F0F0F0 F0F0F0F0 F9F34BF1 F2404040   :0000 0000 
> > 93.1 2   :
> > 40404040 40404040 40404040 404040F0   : 
> >     0:
> > F0F0F0F0 F0F0F0F8 4BF0F040 40404040   :0000 0008 .00 
> >      :
> > 40404040 40404040 40404040 40404040   : 
> >      :
> > 40404040 40404040 40404040 40404040   : 
> >      :
> > 40404040 40404040 40404040 40404040   : 
> >      :
> > 0D254040 40404040 40404040 40404040   :
> > 40404040 40404040 40404040 40404040    ^^ 
> >         = CR CR
> > 40404040 40404040
> >
> >
> >
> > C1F0F1F2 F0F1F1F6 F0F0F440 F3F4F0F4   :A012 0116 004 
> >  3404:
> > F6F04040 4040F1F1 61F2F461 C1F04040   :60     11 
> > /24/ A0  :
> > 40F0F1F0 F0F1F0F1 F0404040 40404040   : 010 0101 0 
> >      :
> > 4040F0F0 F0F0F0F0 F0F0F0F0 F0F9F34B   :  00 0000 
> > 0000 093.:
> > F1F24040 40404040 40404040 40404040   :12 
> >      :
> > 40404040 F0F0F0F0 F0F0F0F0 F84BF0F0   :     0000 
> > 0000 8.00:
> > 40404040 40404040 40404040 40404040   : 
> >      :
> > 40404040 40404040 40404040 40404040   : 
> >      :
> > 40404040 40404040 40404040 40404040   : 
> >      :
> > 40404040 400D2540 40404040 40404040   : 
> >      :
> > 40404040 40404040 40404040 40404040          ^^ 
> >        = CR CR
> > 40404040 40404040 40404040 40404040 
> > 40404040 40404040
> >
> > Dipl.Inf.(FH) Rolf P Mittag
> > IBM Partner In Development
> > Leipziger Str. 50
> > D-69214 Eppelheim
> > eMl: rm@r-m-e-d-v.de
> > Fon: +49 (6221) 76 78 60
> > Fax: +49 (6221) 76 80 26
> >
> > +---
> > | This is the RPG/400 Mailing List!
> > | To submit a new message, send your mail to 
> > RPG400-L@midrange.com.
> > | To subscribe to this list send email to 
> > RPG400-L-SUB@midrange.com.
> > | To unsubscribe from this list send email to 
> > RPG400-L-UNSUB@midrange.com.
> > | Questions should be directed to the list 
> > owner/operator: david@midrange.com
> > +---
>
> __________________________________________________ 
> Do You Yahoo!?
> Yahoo! Shopping - Thousands of Stores. Millions of Products. 
> http://shopping.yahoo.com/
> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com. 
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com 
> +---
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com. 
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com 
+---
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-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.