| 
 | 
I am using a bit of code I probably got from someone on this list quite
some time ago.  It reads the directories in the IFS and reports back on
size.  Evidently I've reached the limit of a 4B 0 field.  The file is
bigger than a gig.  And, while yes, we should address that issue, I want to
get the list program working.  Here are some lines of code:
DStatStruc        DS           128
d  fill1                  1     20
D* Size                  21     24B 0
d  size                  45     48b 0
d  FileType              49     53
d  fill4                 76    127
DpStatStruc       S               *   Inz(%Addr(StatStruc))
...
c                   eval      boxsize = size
...
 *
 * Get file information
 *
c                   eval      Dir#File = %Subst(StreamDir:1:Leny - 1)
c                                      + %Subst(FileNam:1:Len)
c                                      + X'00'
C                   Eval      RC = Stat(pDir#File:pStatStruc)
...
c                   eval      boxsize = size
...
MCH1210 - The target for a numeric operation is too small to hold the
result (C G D F)
'D'
BOXSIZE               PACKED(12,0)         000007864320.
                      VALUE IN HEX         '0000007864320F'X
BOXSIZE must be from previous file.
SIZE                BIN(9,0)             078984704.       '40500000'X
1 is truncated from the beginning of SIZE.
How could I change 'size' without messing up the data structure?
Rob Berendt
==================
Remember the Cole!
+---
| 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 mailing list archive is Copyright 1997-2025 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.