The provided code does not specify a device, so how can you select a device even if you know it? It doesn't seem to be changing devices....
-----Original Message----- From: John Hester <[email protected]> To: U2 Users List <[email protected]> Sent: Fri, Mar 16, 2012 4:41 pm Subject: Re: [U2] Turn a device and inode into file name It works fine if you have multiple devices because you can only run it gainst one account and one device at a time. "ls -i" doesn't span irectory hierarchies or devices. You do at least have to know what evice the file in question is on, but if you don't know that there's no ool that will reliably work for you. -John -----Original Message----- rom: [email protected] mailto:[email protected]] On Behalf Of Wjhonson ent: Friday, March 16, 2012 3:43 PM o: [email protected] ubject: Re: [U2] Turn a device and inode into file name This only works if you have a single device, since the inode is not nique cross-device, only unique on a device -----Original Message----- rom: John Hester <[email protected]> o: U2 Users List <[email protected]> ent: Fri, Mar 16, 2012 3:25 pm ubject: Re: [U2] Turn a device and inode into file name have a utility named FLIST.READU that replaces the inode from the andard LIST.READU output with the file name. It uses "ls -i", so it's mited to files in the account you run the command from, though. Works ne for us because all of our users work out of the same account. This the relevant part of the code: INODE.NO = TRIM(READU.ARRAY<I,3>) EXECUTE 'SH -c "ls -i | grep ':INODE.NO:'"', OUT > FILENAME IF FILENAME<1,1,1> # '' THEN FILENAME = FIELD(TRIM(FILENAME<1,1,1>),' ',2) 'L#8' t's also pretty resource intensive because it re-lists the entire count for every inode. Probably not much of an issue if your hardware fairly new. John ----Original Message----- om: [email protected] ailto:[email protected]] On Behalf Of Wjhonson nt: Friday, March 16, 2012 12:24 PM : [email protected] bject: [U2] Turn a device and inode into file name nyone have an easy way to do this? the past I've run a batch routine to just query each and every niverse ile for it's inode and device and build a table of these Every week.... ems like a great amount of overkill to me. u could also mod the CREATE-FILE command to sniff it and make an xref try but .... ny suggestions? is is NOT for the case where you know the file and want to find the ode and device It's for the case where you know the inode and device nly) and want to find the file. _____________________________________________ -Users mailing list [email protected] tp://listserver.u2ug.org/mailman/listinfo/u2-users _____________________________________________ -Users mailing list [email protected] tp://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ 2-Users mailing list [email protected] ttp://listserver.u2ug.org/mailman/listinfo/u2-users ______________________________________________ 2-Users mailing list [email protected] ttp://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
