<?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: File Monitoring Service in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/file-monitoring-service/m-p/4901717#M32130</link>
    <description>A simple (but not very elegant) solution is just have a DIR/FTP in a loop and check the status. This is of course not useful, if you have to check very often...&lt;BR /&gt;&lt;BR /&gt;regards Kalle</description>
    <pubDate>Fri, 13 May 2005 00:20:43 GMT</pubDate>
    <dc:creator>Karl Rohwedder</dc:creator>
    <dc:date>2005-05-13T00:20:43Z</dc:date>
    <item>
      <title>File Monitoring Service</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/file-monitoring-service/m-p/4901716#M32129</link>
      <description>I'm trying to monitor the existence of a flat file resident on a Unix server from a VMS machine.  Currently have a NFS mount giving visibility to the Unix box, but need to develop a VMS (detached?) service to watch for the appearance of the files on the Unix box so they can processed into a database on the VMS machine.  I'm not a VMS programmer, so I'm looking for suggestions for available system services, library routines, freeware, etc... to help.  Any suggestion ?????</description>
      <pubDate>Thu, 12 May 2005 11:39:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/file-monitoring-service/m-p/4901716#M32129</guid>
      <dc:creator>Robert Cermack</dc:creator>
      <dc:date>2005-05-12T11:39:21Z</dc:date>
    </item>
    <item>
      <title>Re: File Monitoring Service</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/file-monitoring-service/m-p/4901717#M32130</link>
      <description>A simple (but not very elegant) solution is just have a DIR/FTP in a loop and check the status. This is of course not useful, if you have to check very often...&lt;BR /&gt;&lt;BR /&gt;regards Kalle</description>
      <pubDate>Fri, 13 May 2005 00:20:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/file-monitoring-service/m-p/4901717#M32130</guid>
      <dc:creator>Karl Rohwedder</dc:creator>
      <dc:date>2005-05-13T00:20:43Z</dc:date>
    </item>
    <item>
      <title>Re: File Monitoring Service</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/file-monitoring-service/m-p/4901718#M32131</link>
      <description>Robert,&lt;BR /&gt;&lt;BR /&gt;if I understand your references to 'NFS mount' correctly, you have the directory on the Unix box mounted via NFS from the OpenVMS system, so you could see the file from OpenVMS system with a $ DIRECTORY command ?&lt;BR /&gt;&lt;BR /&gt;If so, you could use a simple DCL procedure using F$SEARCH to 'wait' for the appearance of the file and then start processing it:&lt;BR /&gt;&lt;BR /&gt;$loop:&lt;BR /&gt;$ file = F$SEARCH("X.X")&lt;BR /&gt;$ IF file .nes. "" THEN $ GOTO process_file&lt;BR /&gt;$ WAIT 0:0:5&lt;BR /&gt;$ GOTO loop&lt;BR /&gt;$!&lt;BR /&gt;$process_file:&lt;BR /&gt;$ SHOW SYMB file&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Fri, 13 May 2005 01:02:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/file-monitoring-service/m-p/4901718#M32131</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-05-13T01:02:49Z</dc:date>
    </item>
    <item>
      <title>Re: File Monitoring Service</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/file-monitoring-service/m-p/4901719#M32132</link>
      <description>Robert,&lt;BR /&gt;&lt;BR /&gt;I agree with Volker that this is the simplier way. You could submit such procedure in a batch queue to get a "detached" process (I put detached in quotes because this is not a real detached process).&lt;BR /&gt;&lt;BR /&gt;If you want to go on the hard way, there is the VMS documentation:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/doc/os82_index.html" target="_blank"&gt;http://h71000.www7.hp.com/doc/os82_index.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;For system services:&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/doc/82FINAL/4527/4527PRO.HTML" target="_blank"&gt;http://h71000.www7.hp.com/doc/82FINAL/4527/4527PRO.HTML&lt;/A&gt;&lt;BR /&gt;for library routines:&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/doc/82final/5932/5932PRO.HTML" target="_blank"&gt;http://h71000.www7.hp.com/doc/82final/5932/5932PRO.HTML&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;probably you will need RMS:&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/doc/73final/6027/6027PRO.HTML" target="_blank"&gt;http://h71000.www7.hp.com/doc/73final/6027/6027PRO.HTML&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;For the freeware look at:&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/openvms/freeware/index.html" target="_blank"&gt;http://h71000.www7.hp.com/openvms/freeware/index.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Bojan</description>
      <pubDate>Fri, 13 May 2005 01:25:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/file-monitoring-service/m-p/4901719#M32132</guid>
      <dc:creator>Bojan Nemec</dc:creator>
      <dc:date>2005-05-13T01:25:42Z</dc:date>
    </item>
    <item>
      <title>Re: File Monitoring Service</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/file-monitoring-service/m-p/4901720#M32133</link>
      <description>Robert,&lt;BR /&gt;&lt;BR /&gt;A slight variation on Volker's procedure...&lt;BR /&gt;Depending on the size of the file, it may exist&lt;BR /&gt;but still be in the process of being written.&lt;BR /&gt;Try opening it for write access, if it fails&lt;BR /&gt;go back to waiting.&lt;BR /&gt;&lt;BR /&gt;$loop:&lt;BR /&gt;$ file = F$SEARCH("X.X")&lt;BR /&gt;$ IF file .nes. "" THEN $ GOTO process_file&lt;BR /&gt;$wait_a_bit:&lt;BR /&gt;$ WAIT 0:0:5&lt;BR /&gt;$ GOTO loop&lt;BR /&gt;$!&lt;BR /&gt;$process_file:&lt;BR /&gt;$ close/nolog channel&lt;BR /&gt;$ open/read/write/error=wait_a_bit channel 'file'&lt;BR /&gt;$ close/nolog channel&lt;BR /&gt;$ SHOW SYMB file&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Dave</description>
      <pubDate>Fri, 13 May 2005 01:37:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/file-monitoring-service/m-p/4901720#M32133</guid>
      <dc:creator>David B Sneddon</dc:creator>
      <dc:date>2005-05-13T01:37:03Z</dc:date>
    </item>
    <item>
      <title>Re: File Monitoring Service</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/file-monitoring-service/m-p/4901721#M32134</link>
      <description>Robert,&lt;BR /&gt;&lt;BR /&gt;I agree with David that you should check for the file being closed already.&lt;BR /&gt;However, I do not fully trust in NOT being able to write to a _UNIX_ file while it is open. Also, the chance exists that _YOUR_ test-OPEN interferes with the writing app.&lt;BR /&gt;&lt;BR /&gt;Can you have/get any control over the applic that _WRITES_ the file?&lt;BR /&gt;My usual approach is to have the generating applic rename the file after closing.&lt;BR /&gt;Then checking for the renamed file results in a found file being fullt available for you.&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>Fri, 13 May 2005 04:06:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/file-monitoring-service/m-p/4901721#M32134</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2005-05-13T04:06:23Z</dc:date>
    </item>
    <item>
      <title>Re: File Monitoring Service</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/file-monitoring-service/m-p/4901722#M32135</link>
      <description>Thanks to all for your responses.  I'll probably work with the DCL (F$SEARCH) batch routine option first and investigate the more robust RMS solution later.</description>
      <pubDate>Fri, 13 May 2005 09:01:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/file-monitoring-service/m-p/4901722#M32135</guid>
      <dc:creator>Robert Cermack</dc:creator>
      <dc:date>2005-05-13T09:01:05Z</dc:date>
    </item>
    <item>
      <title>Re: File Monitoring Service</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/file-monitoring-service/m-p/4901723#M32136</link>
      <description>Closed.  Thanks again.</description>
      <pubDate>Fri, 13 May 2005 09:03:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/file-monitoring-service/m-p/4901723#M32136</guid>
      <dc:creator>Robert Cermack</dc:creator>
      <dc:date>2005-05-13T09:03:13Z</dc:date>
    </item>
  </channel>
</rss>

