Hi Jon,

Thanks anyway. I needed the create/change file date times. At the end I did some search in the QSYSINC.

For now it is working ok.

Frans.

-----Oorspronkelijk bericht-----
Van: COBOL400-L [mailto:cobol400-l-bounces@xxxxxxxxxxxx] Namens Jon Paris
Verzonden: donderdag 11 augustus 2016 23:40
Aan: Cobol400-L@Midrange. Com
Onderwerp: Re: [COBOL400-L] using stat64 function...

It looks OK Frans - well down as far as alloc-size anyway. After that it doesn’t match what I have - but that appears to be mostly because there are a bunch of reserved and other fields beyond that that I haven’t needed.

Mine from that point on is:

objtype Pic X(12).
codepage Pic 9(4) Binary.
reserved Pic x(62).
ino_gen_id Pic 9(9) Binary.

I’d also compile with the *NOSTDTRUNC option to ensure that all binary fields are used to full capacity.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Feb 3, 2016, at 8:46 AM, Vries, Frans de <FdVries@xxxxxxxxxxxxxxx> wrote:

Hi All,

I'm trying to use the stat64() unix API in a ILE COBOL program it works fine but the structure of the output buffer has not the layout of documentation available!

Does any one has any experience using this API? The structure I'm using now is:

03 Stat-Buffer.
1 1 05 File-Mode PIC 9(009) BINARY.
2 5 05 File-Serial-Nr PIC 9(009) BINARY.
3 9 05 Nr-Links PIC 9(004) BINARY.
11 05 filler PIC X(002).
4 13 05 UID PIC 9(009) BINARY.
5 17 05 GIG PIC 9(009) BINARY.
6 21 05 Stat-Size PIC S9(009) BINARY.
7 25 05 Access-Time PIC S9(009) BINARY.
8 29 05 Modification-Time PIC S9(009) BINARY.
9 33 05 Status-CHG-Time PIC S9(009) BINARY.
10 37 05 File-System-ID PIC S9(009) BINARY.
11 41 05 Block-Size PIC 9(009) BINARY.
12 45 05 Alloc-Size PIC 9(009) BINARY.
13 49 05 Code-Page PIC 9(009) BINARY.
14 53 05 Alloc-Size-2 PIC 9(009) BINARY.
15 57 05 filler PIC X(004).
16 61 05 Object-Type PIC X(010).
15 51 05 filler PIC X(001).
18 05 Stat-codepage PIC 9(004) BINARY.
18 05 Stat-CCSID PIC 9(004) BINARY.
19 05 St-rdev PIC 9(009) BINARY.
20 05 St-nlink32 PIC 9(009) BINARY.
19 05 St-rdev64 PIC 9(016) BINARY.
20 05 St-dev64 PIC 9(016) BINARY.
21 05 St-vfs PIC 9(009) BINARY.
22 05 St-reserverd PIC X(032).
23 05 St-ino-gen-id PIC 9(009) BINARY.
24 05 st-filler PIC X(100).

Thanks in advance,

Met vriendelijke groet,

Frans de Vries.
============================================================
F. de Vries | Detailresult Groep N.V. | Leeghwaterweg 11 - 1951 NA Velsen-Noord | Postbus 86 - 1940 AB Beverwijk
Bedrijfsondersteunende systemen & Rapportage | Detailresult ICT | tel: +31 (0)251-279220 |
www.Dirk.nl<http://www.dirk.nl/> I www.Dekamarkt.nl<http://www.dekamarkt.nl/> I www.Detailresult.nl<http://www.detailresult.nl/> I e-mail: fdvries@xxxxxxxxxxxxxxx<mailto:fdvries@xxxxxxxxxxxxxxx>


************************DISCLAIMER*******************************
De informatie in dit bericht is vertrouwelijk. Het is daarom niet toegestaan dat u deze informatie openbaar maakt, vermenigvuldigt of verspreidt, tenzij de verzender aangeeft dat dit wel is toegestaan. Als dit e-mailbericht niet voor u bestemd is, vragen wij u vriendelijk maar dringend om het bericht en kopieen daarvan te vernietigen. Dit bericht is gecontroleerd op bekende virussen. Helaas kunnen wij niet garanderen dat het bericht dat u ontvangt volledig en tijdig verzonden is, of tijdig ontvangen wordt en vrij is van virussen of aantasting door derden.
**********************************************************************
--
This is the COBOL Programming on the IBM i (AS/400 and iSeries) (COBOL400-L) mailing list
To post a message email: COBOL400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/cobol400-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.