FID to pathname translation

Some messages, like ICH408I refer to UNIX file ID aka FID. Usually it is FID(long_hex_number). In some case human-readable form is also provided, but not always. I vaguely remain there is some utility to translate FID hex number into regular pathname like /usr/lpp/some/file Any clue? -- Rados

Re: FID to pathname translation

On Mon, 18 Nov 2024 01:12:52 +, Seymour J Metz wrote: >Is FID another name for inode? > If you read beyond the first ply in the thread, you'll see that: o he tried it; it isn't. o RACF messages explain that. > >From: Radoslaw Skorupka <0471ebeac2

Re: FID to pathname translation

W dniu 17.11.2024 o 17:05, Paul Gilmartin pisze: On Sun, 17 Nov 2024 16:35:09 +0100, Radoslaw Skorupka wrote: Some messages, like ICH408I refer to UNIX file ID aka FID. Usually it is FID(long_hex_number). In some case human-readable form is also provided, but not always. I vaguely remain there

Re: FID to pathname translation

equ...@listserv.ua.edu> Sent: Sunday, November 17, 2024 10:35 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: FID to pathname translation External Message: Use Caution Some messages, like ICH408I refer to UNIX file ID aka FID. Usually it is FID(long_hex_number). In some case human-readable form is also provide

Re: FID to pathname translation

On Sun, 17 Nov 2024 16:35:09 +0100, Radoslaw Skorupka wrote: >Some messages, like ICH408I refer to UNIX file ID aka FID. >Usually it is FID(long_hex_number). In some case human-readable form is >also provided, but not always. >I vaguely remain there is some utility to translate FID hex number into

Re: FID to pathname translation

On Sun, 17 Nov 2024 17:47:16 +0200, ITschak Mugzach wrote: >find -inum xxx? > Note that if FID is multiply linked this will return multiple answers. Not all may be relevant. If the pathname is open then unlinked there may be no answer, except a useless one from: find /dev/fd -inum xxx -- gi

Re: FID to pathname translation

On Sun, 17 Nov 2024 17:23:44 +0100, Radoslaw Skorupka wrote: > >I tried, it doesn't work. >FSUM6504 find: bad number specification in "C2D3" >I displayed the inode, it has nothing to do with 31-character long FID >hex string. > In:

Re: FID to pathname translation

On Sun, 17 Nov 2024 17:23:44 +0100, Radoslaw Skorupka wrote: >... >I tried, it doesn't work. >FSUM6504 find: bad number specification in "C2D3" >I displayed the inode, it has nothing to do with 31-character long FID >hex string. > . Submit an RCF. -- gil -

Re: FID to pathname translation

find -inum xxx? ITschak Mugzach *|** IronSphere Platform* *|* *Information Security Continuous Monitoring for z/OS, x/Linux & IBM I **| z/VM coming soon * nbsp; *|* On Sun, Nov 17, 2024 at 5:35 PM Radoslaw Skorupka < 0471ebeac275-dmarc-requ...@listserv.ua.edu> wrote: > Some messages,