<?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 Way to extract full message attributes in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/way-to-extract-full-message-attributes/m-p/4479916#M42687</link>
    <description>I am on OpenVMS 8.3 IA64.&lt;BR /&gt;&lt;BR /&gt;Is there a way to convert a .MSG file into a "normalized" form, where I can get a listing of all the messages with all of their attributes?&lt;BR /&gt;&lt;BR /&gt;I have a .MSG file which I want to print out with the code, message, severity, fao, facility, prefix, etc. Some of these parameters are set for each line, but others are set for whole blocks of lines using .SEVERITY and .FACILITY directives.&lt;BR /&gt;&lt;BR /&gt;Is there an easy way to convert this into a form where nothing is set by directive, but intead is made explicit on each line. I am open to using MESSAGE, UNMESSAGE, Perl, or even writing a program and calling LIB$SIGNAL on every condition... It just has to be some process where message file goes in and list of all messages with attributes comes out.&lt;BR /&gt;&lt;BR /&gt;Thanks.</description>
    <pubDate>Fri, 14 Aug 2009 18:26:33 GMT</pubDate>
    <dc:creator>Maxy2</dc:creator>
    <dc:date>2009-08-14T18:26:33Z</dc:date>
    <item>
      <title>Way to extract full message attributes</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/way-to-extract-full-message-attributes/m-p/4479916#M42687</link>
      <description>I am on OpenVMS 8.3 IA64.&lt;BR /&gt;&lt;BR /&gt;Is there a way to convert a .MSG file into a "normalized" form, where I can get a listing of all the messages with all of their attributes?&lt;BR /&gt;&lt;BR /&gt;I have a .MSG file which I want to print out with the code, message, severity, fao, facility, prefix, etc. Some of these parameters are set for each line, but others are set for whole blocks of lines using .SEVERITY and .FACILITY directives.&lt;BR /&gt;&lt;BR /&gt;Is there an easy way to convert this into a form where nothing is set by directive, but intead is made explicit on each line. I am open to using MESSAGE, UNMESSAGE, Perl, or even writing a program and calling LIB$SIGNAL on every condition... It just has to be some process where message file goes in and list of all messages with attributes comes out.&lt;BR /&gt;&lt;BR /&gt;Thanks.</description>
      <pubDate>Fri, 14 Aug 2009 18:26:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/way-to-extract-full-message-attributes/m-p/4479916#M42687</guid>
      <dc:creator>Maxy2</dc:creator>
      <dc:date>2009-08-14T18:26:33Z</dc:date>
    </item>
    <item>
      <title>Re: Way to extract full message attributes</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/way-to-extract-full-message-attributes/m-p/4479917#M42688</link>
      <description>Writing your own parser?  Why? &lt;BR /&gt;&lt;BR /&gt;Why not build the message library and access the resulting message definitions normally; use the MESSAGE definition module as it was originally intended?  &lt;BR /&gt;&lt;BR /&gt;If you're looking to include messages in an application, then look to use the (undocumented) MESSAGE /SDL and the SDL tool.  Details are here:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://labs.hoffmanlabs.com/node/588" target="_blank"&gt;http://labs.hoffmanlabs.com/node/588&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://labs.hoffmanlabs.com/node/585" target="_blank"&gt;http://labs.hoffmanlabs.com/node/585&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 14 Aug 2009 20:56:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/way-to-extract-full-message-attributes/m-p/4479917#M42688</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2009-08-14T20:56:39Z</dc:date>
    </item>
    <item>
      <title>Re: Way to extract full message attributes</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/way-to-extract-full-message-attributes/m-p/4479918#M42689</link>
      <description>message/list produces a listing, which includes the full message text and code. That's not exactly what you are asking for, but it may help. Search it for ".facility" and use the last four (hex) digits of the  facility code to extract all messages with their code.&lt;BR /&gt;&lt;BR /&gt;If you want this to have your literals defined in any programming language, you are better off with the SDL output and the SDL tool.&lt;BR /&gt;&lt;BR /&gt;But you can easily construct your literals or '#define's out of the message object. For Alpha and C just use something like:&lt;BR /&gt;&lt;BR /&gt;$! p1 message file (without type .msg)&lt;BR /&gt;$! p2 facility name&lt;BR /&gt;$! results in 'p1.h&lt;BR /&gt;$&lt;BR /&gt;$ message/object=tmp 'p1.MSG&lt;BR /&gt;$ analyze/obj/out=x.tmp tmp&lt;BR /&gt;$ search x.tmp symbol:,value/out=y.tmp&lt;BR /&gt;$ search y.tmp """''p2'"/wind=(1,0)/out=z.tmp&lt;BR /&gt;$ open/read in z.tmp&lt;BR /&gt;$ open/write out 'p1.h&lt;BR /&gt;$ loop:&lt;BR /&gt;$ read/end=done in line1&lt;BR /&gt;$ read in line2&lt;BR /&gt;$ line1= line1- "value:"- "%X'00000000"- "'"&lt;BR /&gt;$ line2= line2- "symbol:"- """"- """"&lt;BR /&gt;$ write out "#define ", f$edit(line2,"collapse"), " 0x", f$edit(line1,"collapse")&lt;BR /&gt;$ goto loop&lt;BR /&gt;$ done:&lt;BR /&gt;$ close in&lt;BR /&gt;$ close out&lt;BR /&gt;$ del tmp.obj;*, x.tmp;*, y.tmp;*, z.tmp;*&lt;BR /&gt;</description>
      <pubDate>Mon, 17 Aug 2009 07:05:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/way-to-extract-full-message-attributes/m-p/4479918#M42689</guid>
      <dc:creator>H.Becker</dc:creator>
      <dc:date>2009-08-17T07:05:07Z</dc:date>
    </item>
  </channel>
</rss>

