<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Common Accountng File in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897790#M68227</link>
    <description>Thanks for all the help guys.</description>
    <pubDate>Mon, 09 May 2005 08:56:53 GMT</pubDate>
    <dc:creator>VMS Support</dc:creator>
    <dc:date>2005-05-09T08:56:53Z</dc:date>
    <item>
      <title>Common Accountng File</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897775#M68212</link>
      <description>I have a cluster with two system disk (Hetrogenous). The accountng.dat (Was it version &amp;lt;=3 that limited file names to 9 characters ?) is currently located in the default location. I would like to make one common accounting file, on a shared disk of course. The disk being mounted via a call in sylogicals. I used to have some code to handle this. But this was about 8 years ago !&lt;BR /&gt;&lt;BR /&gt;I know some of the process ...&lt;BR /&gt;Define logical ACCOUNTNG&lt;BR /&gt;$SET ACC/NEW - pick up new common file.&lt;BR /&gt;However its the process for forcing each node in the cluster to use the same file after a single node has issued the $SET ACC/NEW to rollover the file. This node will use the new file ..but other nodes will use the old version.&lt;BR /&gt;&lt;BR /&gt;Any contributions welcome.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Kevin Raven (London UK)</description>
      <pubDate>Fri, 22 Apr 2005 04:27:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897775#M68212</guid>
      <dc:creator>VMS Support</dc:creator>
      <dc:date>2005-04-22T04:27:55Z</dc:date>
    </item>
    <item>
      <title>Re: Common Accountng File</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897776#M68213</link>
      <description>Kevin, &lt;BR /&gt;&lt;BR /&gt;you are already sooo close!&lt;BR /&gt;&lt;BR /&gt;Just issue $SET ACC/NEW from each node (or by SYSMAN) will do the trick.&lt;BR /&gt;&lt;BR /&gt;However, we do it a little differently.&lt;BR /&gt;We also have the common environment.&lt;BR /&gt;But our logical ACCOUNTNG (do not forget /EXEC !) is to &lt;NODENAME&gt;_ACCOUNTNG.DAT in that environment.&lt;BR /&gt;Every day at 3 seconds after midnight we do SET ACCO/NEW on each node, and rename the old files from .DAT to .&lt;DATE&gt;&lt;BR /&gt;Noe we still have all acco info available on a per node/per day basis.&lt;BR /&gt;And... we have a logical ACCNT as &lt;LOCATION&gt;:*_ACCOUNTNG.DAT.&lt;BR /&gt;&lt;BR /&gt;For normal use, ACCO ACCNT &lt;WHATEVER&gt; instead of ACCO ACCOUNTNG gives clusterwide info, but every so often it can be quite usefull to nail a process down to a specific node.&lt;BR /&gt;&lt;BR /&gt;FWIW.&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe &lt;BR /&gt;&lt;/WHATEVER&gt;&lt;/LOCATION&gt;&lt;/DATE&gt;&lt;/NODENAME&gt;</description>
      <pubDate>Fri, 22 Apr 2005 04:50:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897776#M68213</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2005-04-22T04:50:27Z</dc:date>
    </item>
    <item>
      <title>Re: Common Accountng File</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897777#M68214</link>
      <description>Will just a SET ACC/NEW on both nodes work?&lt;BR /&gt;&lt;BR /&gt;Example of what I want and end up with :-(&lt;BR /&gt;&lt;BR /&gt;Node ALPHA1 and ALPHA2&lt;BR /&gt;Disk dsa1: - Mounted on both nodes&lt;BR /&gt;&lt;BR /&gt;On both nodes (ALPHA1 and ALPHA2)&lt;BR /&gt;$DEF/SYS/EXEC ACCOUNTG DSA1:[TEST]COMMON_ACC.DAT&lt;BR /&gt;&lt;BR /&gt;On ALPHA1 &lt;BR /&gt;$Set acc/new &lt;BR /&gt;Now uses DSA1:[TEST]COMMON_ACC.DAT;1&lt;BR /&gt;Version 1 &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;On ALPHA2 &lt;BR /&gt;$Set acc/new &lt;BR /&gt;Now uses DSA1:[TEST]COMMON_ACC.DAT;2&lt;BR /&gt;Version 2&lt;BR /&gt;&lt;BR /&gt;What I would like is both using one version of file.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 22 Apr 2005 04:59:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897777#M68214</guid>
      <dc:creator>VMS Support</dc:creator>
      <dc:date>2005-04-22T04:59:27Z</dc:date>
    </item>
    <item>
      <title>Re: Common Accountng File</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897778#M68215</link>
      <description>Hi Kevin,&lt;BR /&gt;&lt;BR /&gt;Why you want common accounting file? &lt;BR /&gt;&lt;BR /&gt;Put the node specific accounting file in commom disk/directory (as Jan suggested) and I guess that will sever the purpose of moving the file off system disk. &lt;BR /&gt;&lt;BR /&gt;Thanks &amp;amp; regards,&lt;BR /&gt;Lokesh</description>
      <pubDate>Fri, 22 Apr 2005 05:08:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897778#M68215</guid>
      <dc:creator>Lokesh_2</dc:creator>
      <dc:date>2005-04-22T05:08:19Z</dc:date>
    </item>
    <item>
      <title>Re: Common Accountng File</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897779#M68216</link>
      <description>sorry for the typo, replace "sever" with "serve" in my previous post.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Lokesh&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 22 Apr 2005 05:10:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897779#M68216</guid>
      <dc:creator>Lokesh_2</dc:creator>
      <dc:date>2005-04-22T05:10:55Z</dc:date>
    </item>
    <item>
      <title>Re: Common Accountng File</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897780#M68217</link>
      <description>We run a regular security routine (Command file) that gerenerates reports from the accountng.dat file. Just trying to tidy things up by having one shared copy of the file. At the moment we run the command file twice (one on each node). System disk only mounted on node booted from it, all other disks shared (mounted/cluster).&lt;BR /&gt;Of course I could have two copies of accounting file in common area (One per node) and have one command file that runs once , but reads from both files.&lt;BR /&gt;I'm sure several years ago ..in my Digital days , based in London/Newbury/Reading , we had a shared accountng.dat file on our ALL-IN-1 clusters. Distant memory now. Left Compaq 5 years ago ...in fact to the day almost.</description>
      <pubDate>Fri, 22 Apr 2005 05:34:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897780#M68217</guid>
      <dc:creator>VMS Support</dc:creator>
      <dc:date>2005-04-22T05:34:08Z</dc:date>
    </item>
    <item>
      <title>Re: Common Accountng File</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897781#M68218</link>
      <description>Hi Kevin,&lt;BR /&gt;&lt;BR /&gt;Accounting utility accepts multiple input files, so that you can use multiple accounting files to generate a single report.&lt;BR /&gt;&lt;BR /&gt;for exam&lt;BR /&gt;&lt;BR /&gt;$ACCOUN  ACCOUNTING_NODEA.DAT,ACCOUNTING_NODEB.DAT&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Thanks &amp;amp; regards,&lt;BR /&gt;Lokesh</description>
      <pubDate>Fri, 22 Apr 2005 05:49:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897781#M68218</guid>
      <dc:creator>Lokesh_2</dc:creator>
      <dc:date>2005-04-22T05:49:47Z</dc:date>
    </item>
    <item>
      <title>Re: Common Accountng File</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897782#M68219</link>
      <description>Re Lokesh:&lt;BR /&gt;&lt;BR /&gt;... which is exactly what we do!&lt;BR /&gt;And also on a daily basis, and rather extensive.&lt;BR /&gt;(one of our applics does the tracing by writing USER records to the accountng file for every query and avery mutation, which are mined for legal reporting).&lt;BR /&gt;Only defference: we us a single logical name that wildcards the multiple files.&lt;BR /&gt;&lt;BR /&gt;I never tried a single multinode accountng file; could it be you remember the single ACCO command, but might it have had a multifile input specification?&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe&lt;BR /&gt;</description>
      <pubDate>Fri, 22 Apr 2005 06:36:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897782#M68219</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2005-04-22T06:36:51Z</dc:date>
    </item>
    <item>
      <title>Re: Common Accountng File</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897783#M68220</link>
      <description>Kevin,&lt;BR /&gt;&lt;BR /&gt;I don't think this will work. It looks like JOB_CONTROL opens the ACCOUNTNG.DAT file:&lt;BR /&gt;&lt;BR /&gt;FAC:            01      PUT&lt;BR /&gt;SHR:            42      SHRGET,UPI&lt;BR /&gt;&lt;BR /&gt;which would probably NOT allow multiple shared writers.&lt;BR /&gt;&lt;BR /&gt;If you don't want to change your existing procedure and not add multiple accounting file names, you may be able to append the files and use the resulting file for your reports.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Fri, 22 Apr 2005 07:37:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897783#M68220</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-04-22T07:37:40Z</dc:date>
    </item>
    <item>
      <title>Re: Common Accountng File</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897784#M68221</link>
      <description>&lt;WHICH would="" probably="" not="" allow="" multiple="" shared="" writers.=""&gt;&lt;BR /&gt;&lt;BR /&gt;Obviously!&lt;BR /&gt;&lt;BR /&gt;Accounting is done on a node-by-node basis. It contains clues on usage of THAT node. No way to tamper the data (Don't trust system managers - and system programmers even less :D)&lt;BR /&gt;&lt;BR /&gt;SET ACC/NEW will create a new file FOR THAT NODE, so you'll have to change your algorithm, using a file per node (can be on a  common disk) and name each file in the ACC command analyzing them into one output file.&lt;BR /&gt;&lt;BR /&gt;&lt;/WHICH&gt;</description>
      <pubDate>Mon, 25 Apr 2005 08:18:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897784#M68221</guid>
      <dc:creator>Willem Grooters</dc:creator>
      <dc:date>2005-04-25T08:18:39Z</dc:date>
    </item>
    <item>
      <title>Re: Common Accountng File</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897785#M68222</link>
      <description>Note that the node name is not in the accounting report. So, you loose info if everything was in 1 file. If it is possible.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Mon, 25 Apr 2005 08:35:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897785#M68222</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2005-04-25T08:35:45Z</dc:date>
    </item>
    <item>
      <title>Re: Common Accountng File</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897786#M68223</link>
      <description>Volker, Wim,&lt;BR /&gt;&lt;BR /&gt;combining your entries, you loose the node-info upon appending!&lt;BR /&gt;Note, that the first 3 (hex) digits of the PID specify a VMS instance (well, for completeness, the third digit can then be even or odd)&lt;BR /&gt;So, you can identify processes from a single boot from a node. And if you have a batch queue that contains the nodename (as I understand most of us have), than you can find the nodename even afterwards...&lt;BR /&gt;&lt;BR /&gt;hth,&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe</description>
      <pubDate>Mon, 25 Apr 2005 09:38:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897786#M68223</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2005-04-25T09:38:58Z</dc:date>
    </item>
    <item>
      <title>Re: Common Accountng File</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897787#M68224</link>
      <description>The only way I can think of to do what you want is to redirect accountng to a mailbox, or decnet task controlled by a process which just combines its inputs from different nodes. A spooled device to a symbiont process to do the same thing might also work.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 25 Apr 2005 11:20:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897787#M68224</guid>
      <dc:creator>Tom O'Toole</dc:creator>
      <dc:date>2005-04-25T11:20:21Z</dc:date>
    </item>
    <item>
      <title>Re: Common Accountng File</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897788#M68225</link>
      <description>To build on Lokesh's idea:&lt;BR /&gt;$ACCOUN -ACCOUNTING_NODEA.DAT,ACCOUNTING_NODEB.DAT/binary/out=common_accounting.dat&lt;BR /&gt;&lt;BR /&gt;Then run the accounting report on the file common_accounting.dat</description>
      <pubDate>Mon, 25 Apr 2005 12:51:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897788#M68225</guid>
      <dc:creator>Steve Nimr</dc:creator>
      <dc:date>2005-04-25T12:51:54Z</dc:date>
    </item>
    <item>
      <title>Re: Common Accountng File</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897789#M68226</link>
      <description>Steve,&lt;BR /&gt;&lt;BR /&gt;back to the same issue: you merged the files, but lost the node info.&lt;BR /&gt;&lt;BR /&gt;Just defining a searchlist for your input files gives you the same compactness, but leaves your node-specificity (like indicated above)&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have on eon me.&lt;BR /&gt;&lt;BR /&gt;jpe</description>
      <pubDate>Mon, 25 Apr 2005 15:52:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897789#M68226</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2005-04-25T15:52:18Z</dc:date>
    </item>
    <item>
      <title>Re: Common Accountng File</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897790#M68227</link>
      <description>Thanks for all the help guys.</description>
      <pubDate>Mon, 09 May 2005 08:56:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/common-accountng-file/m-p/4897790#M68227</guid>
      <dc:creator>VMS Support</dc:creator>
      <dc:date>2005-05-09T08:56:53Z</dc:date>
    </item>
  </channel>
</rss>

