Hello Vern,
Am 01.06.2021 um 20:57 schrieb Vern Hamberg <vhamberg@xxxxxxxxxxxxxxx>:
Every library object gets an extension that is the object type when pointed to using path naming. I suspect you already know all that, but you did ask, right? :)
I did ask, but maybe my question was a bit ambiguous. I know that (and how) QSYS.LIB filesystem is mapped to a classical directory structure.
My main question was: How (and if) are these QSYS.LIB objects *contents* — being record oriented by nature — translated to the stream oriented world outside by NetServer, or FTP?
I once tried to do a binary only FTP transfer of a database file member but the local result was a 0 Byte file, on V4. […] Testing with 7.2, I get a file. Converting that from EBCDIC to ASCII shows actual database content. Duh!
Okay, nevermind. :-) Then I also understand that it should be possible to rewrite those emulated file, however IBM i would cope with wrong record lengths.
Apparently IBM did implement some means to access QSYS.LIB via stream interfaces. For whatever reason. I'm not *that* curious to invest more time in testing. :-)
I stand corrected. In a way. :-)
:wq! PoC
As an Amazon Associate we earn from qualifying purchases.
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.