Hi Guys
I want to write a batch job that executes the Universe command LIST.READU
(Before/After job routine ExecTCL LIST.READU)
What I need to know is how to read the output from this command. Is it stored in some internal file?
Thanks
Output from LIST.READU
Moderators: chulett, rschirm, roy
The LIST.READU command output is generated from values found in the system at the time the command is run. The command is actually a UNIX command, so you can also call it straight from UNIX/Windoze as program in `/.dshome`/bin/list_readu.
Now to the contents - they are not all that interesting to those who don't play with the UniVerse engine. What sort of information are you trying to glean from this output? The state of the R/W and table locks as well as internal process IDs are, for the most part, not all that interesting.
The basic command shows
the LIST.READU EVERY shows even more locking information. If you are really curious the UniVerse documentation does go into detail on this.
Now to the contents - they are not all that interesting to those who don't play with the UniVerse engine. What sort of information are you trying to glean from this output? The state of the R/W and table locks as well as internal process IDs are, for the most part, not all that interesting.
The basic command shows
which are UNIX physical device, Inode and Netnode numbers for the file/record lock in question, the Userno is DS internal, lmode is the lock mode, pic is the UNIX process id and login id is the username. The Item is the record key under lock.Device.... Inode.... Netnode Userno Lmode Pid Login Id Item-ID.............
the LIST.READU EVERY shows even more locking information. If you are really curious the UniVerse documentation does go into detail on this.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
ewartpm,
that is about the only viable use for "LIST.READU EVERY" that I can think of :D I would use the "EVERY" as you get more detailed information, especially if you have several users utilizing the same login-id and want to find out from which PC they are coming.
that is about the only viable use for "LIST.READU EVERY" that I can think of :D I would use the "EVERY" as you get more detailed information, especially if you have several users utilizing the same login-id and want to find out from which PC they are coming.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>