<?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: Patch ACRTL V200 for OpenVMS 7.3-2 in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/patch-acrtl-v200-for-openvms-7-3-2/m-p/4946778#M73213</link>
    <description>Hi Kevin,&lt;BR /&gt;&lt;BR /&gt;I'm fairly sure I had a similar sounding problem with VMS731_ACRTL, where the solution was to increase (significantly (try x2 x4)) BYTLM for the account applying the update.&lt;BR /&gt;&lt;BR /&gt;From SDA what channels did the product install have open ? (syslib:starlet.olb?)&lt;BR /&gt;&lt;BR /&gt;Kind Regards&lt;BR /&gt;John.</description>
    <pubDate>Wed, 14 Dec 2005 09:57:56 GMT</pubDate>
    <dc:creator>John Abbott_2</dc:creator>
    <dc:date>2005-12-14T09:57:56Z</dc:date>
    <item>
      <title>Patch ACRTL V200 for OpenVMS 7.3-2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/patch-acrtl-v200-for-openvms-7-3-2/m-p/4946777#M73212</link>
      <description>I have built a test bed server with a simple OpenVMS 7.3-2 system disk and no other products.&lt;BR /&gt;I have been applying patches over the last three months. This is a pure and simple test the patch system.&lt;BR /&gt;Tried to apply the ACRTL V200 patch today and it hung.&lt;BR /&gt;It got as far as 90% completed and then appeared to hang.&lt;BR /&gt;Did a $Moni proc/topc - 100% cpu process.&lt;BR /&gt;Did a show proc/cont on this and it was running Librarian.exe.&lt;BR /&gt;This completed after approx 30 minutes.&lt;BR /&gt;However the Product install never came back to the $ prompt to say finished. Left it for Approx 30 minutes and then killed it via a control Y.&lt;BR /&gt;Anyone else had issues with this patch ?&lt;BR /&gt;&lt;BR /&gt;                         Process PCSI$52                      13:40:37&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;    State               COM                 Working set               1876&lt;BR /&gt;&lt;BR /&gt;    Cur/base priority   4/4                 Virtual pages            12300&lt;BR /&gt;&lt;BR /&gt;    Current PC          809066E8            CPU time         0 00:06:36.13&lt;BR /&gt;&lt;BR /&gt;    Current PSL         0000001B            Direct I/O              235315&lt;BR /&gt;&lt;BR /&gt;    Current user SP     7AE6B400            Buffered I/O             10411&lt;BR /&gt;&lt;BR /&gt;    PID                 00000123            Page faults             131288&lt;BR /&gt;&lt;BR /&gt;    UIC                 [SYSTEM]            Event flags           C0000003&lt;BR /&gt;                                                                  80000000&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;    DSA99:[SYS0.SYSCOMMON.][SYSEXE]LIBRARIAN.EXE&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;$ product install VMS732_ACRTL/save_recov/recover&lt;BR /&gt; &lt;BR /&gt;   1 - DEC AXPVMS VMS732_ACRTL V2.0        Patch (maintenance update)&lt;BR /&gt;   2 - DEC AXPVMS VMS732_ACRTL V1.0        Patch (maintenance update)&lt;BR /&gt;   3 - All products listed above&lt;BR /&gt;   4 - Exit&lt;BR /&gt; &lt;BR /&gt;Choose one or more items from the menu separated by commas: 1&lt;BR /&gt; &lt;BR /&gt;The following product has been selected:&lt;BR /&gt;    DEC AXPVMS VMS732_ACRTL V2.0           Patch (maintenance update)&lt;BR /&gt; &lt;BR /&gt;Do you want to continue? [YES] &lt;BR /&gt; &lt;BR /&gt;Configuration phase starting ...&lt;BR /&gt; &lt;BR /&gt;You will be asked to choose options, if any, for each selected product and for&lt;BR /&gt;any products that may be installed to satisfy software dependency requirements.&lt;BR /&gt; &lt;BR /&gt;DEC AXPVMS VMS732_ACRTL V2.0: OpenVMS V7.3-2 ACRTL V2.0&lt;BR /&gt;&lt;BR /&gt;Recovery data will be saved which will allow you to un-install&lt;BR /&gt;this kit.  In the past, kit installations provided some level&lt;BR /&gt;of recovery capability by renaming all replaced files to&lt;BR /&gt;file_name.ext_OLD.  If you wish, you can continue to do this.&lt;BR /&gt;&lt;BR /&gt;Note that this will triple the disk space required for&lt;BR /&gt;this kit - one for the installed files, once for the saved&lt;BR /&gt;recovery data and once for the file_name.ext_OLD files.&lt;BR /&gt;&lt;BR /&gt;Do you wish to have replaced files renamed&lt;BR /&gt;to file_name.ext_OLD [NO] ?: yes&lt;BR /&gt;&lt;BR /&gt;_OLD files will be saved&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;* This product does not have any configuration options.&lt;BR /&gt; &lt;BR /&gt;    &amp;lt;&amp;lt; System Disk Backup &amp;gt;&amp;gt;&lt;BR /&gt; &lt;BR /&gt;    &lt;BR /&gt;    This kit will make functional changes to your system.&lt;BR /&gt;    Before installing this kit you should make a backup&lt;BR /&gt;    copy of your system disk.  If you do not make a copy&lt;BR /&gt;    of your system disk you will not be able to restore&lt;BR /&gt;    your system to a pre-kit installation state.&lt;BR /&gt;    &lt;BR /&gt; &lt;BR /&gt;    Do you want to continue? [YES] &lt;BR /&gt; &lt;BR /&gt;    Installing this patch kit requires a reboot.&lt;BR /&gt; &lt;BR /&gt;    &lt;BR /&gt;    Hewlett Packard strongly recommends that you reboot your&lt;BR /&gt;    system immediately after installation  of  this kit.  The&lt;BR /&gt;    images in this kit will not fully take effect until the&lt;BR /&gt;    system is rebooted.  However, if you do not re-boot&lt;BR /&gt;    immediately after kit installation, the system may become&lt;BR /&gt;    unstable and may not function as expected.&lt;BR /&gt;    &lt;BR /&gt;    If you have other nodes in your VMS cluster, they must also&lt;BR /&gt;    be rebooted in order to make use of the new image(s).  If it&lt;BR /&gt;    is not possible or convenient to reboot the entire cluster&lt;BR /&gt;    at this time, a rolling re-boot (kit installation and reboot&lt;BR /&gt;    on one node at a time) may be performed.&lt;BR /&gt;    &lt;BR /&gt; &lt;BR /&gt;    Do you want to continue? [YES] &lt;BR /&gt; &lt;BR /&gt;Execution phase starting ...&lt;BR /&gt;&lt;BR /&gt;The following product will be installed to destination:&lt;BR /&gt;    DEC AXPVMS VMS732_ACRTL V2.0           DISK$ALPHASYS:[VMS$COMMON.]&lt;BR /&gt; &lt;BR /&gt;Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%&lt;BR /&gt;TST731::_RTA1: 12:29:15 PCSI$MAIN CPU=00:00:39.22 PF=1049 IO=18532 MEM=1088&lt;BR /&gt;TST731::_RTA1: 12:29:21 PCSI$MAIN CPU=00:00:39.24 PF=1049 IO=18533 MEM=1088&lt;BR /&gt;TST731::_RTA1: 12:29:24 PCSI$MAIN CPU=00:00:39.24 PF=1049 IO=18534 MEM=1088&lt;BR /&gt;TST731::_RTA1: 12:29:26 PCSI$MAIN CPU=00:00:39.24 PF=1049 IO=18535 MEM=1088&lt;BR /&gt;TST731::_RTA1: 12:29:27 PCSI$MAIN CPU=00:00:39.24 PF=1049 IO=18536 MEM=1088&lt;BR /&gt;TST731::_RTA1: 12:46:23 PCSI$MAIN CPU=00:00:39.25 PF=1049 IO=18537 MEM=1088&lt;BR /&gt;TST731::_RTA1: 13:09:12 PCSI$MAIN CPU=00:00:52.23 PF=1070 IO=21015 MEM=1110&lt;BR /&gt;TST731::_RTA1: 13:09:13 PCSI$MAIN CPU=00:00:52.23 PF=1070 IO=21016 MEM=1110&lt;BR /&gt;TST731::_RTA1: 13:13:25 PCSI$MAIN CPU=00:00:52.23 PF=1070 IO=21017 MEM=1110&lt;BR /&gt;TST731::_RTA1: 13:14:22 PCSI$MAIN CPU=00:00:52.23 PF=1070 IO=21018 MEM=1110&lt;BR /&gt;TST731::_RTA1: 13:15:28 PCSI$MAIN CPU=00:00:52.23 PF=1070 IO=21019 MEM=1110&lt;BR /&gt; Interrupt &lt;BR /&gt;&lt;BR /&gt;%PCSIUI-W-CONTROLY, Ctrl/Y or Ctrl/C has been detected&lt;BR /&gt; &lt;BR /&gt;    * This operation is executing in recovery mode.  Therefore, before exiting&lt;BR /&gt;    * a best effort attempt will be made to restore the files, directories,&lt;BR /&gt;    * libraries, etc. on your system to their state prior to the start of the&lt;BR /&gt;    * operation.  However, it is possible that execution of installation command&lt;BR /&gt;    * procedures from the kit may have modified the system environment in ways&lt;BR /&gt;    * that cannot be reversed automatically.  (The software installation utility&lt;BR /&gt;    * cannot track what product specific procedures do.)  For this reason, you&lt;BR /&gt;    * may want to reconsider your action.  To cancel your abort request and&lt;BR /&gt;    * thereby resume the operation, answer YES to the following question.&lt;BR /&gt; &lt;BR /&gt;Do you want to continue? [YES] &lt;BR /&gt; &lt;BR /&gt;TST731::_RTA1: 13:30:19 PCSI$MAIN CPU=00:00:52.23 PF=1070 IO=21036 MEM=1110&lt;BR /&gt;TST731::_RTA1: 13:30:21 PCSI$MAIN CPU=00:00:52.24 PF=1070 IO=21037 MEM=1110&lt;BR /&gt; Interrupt &lt;BR /&gt;&lt;BR /&gt;%PCSIUI-W-CONTROLY, Ctrl/Y or Ctrl/C has been detected&lt;BR /&gt; &lt;BR /&gt;    * This operation is executing in recovery mode.  Therefore, before exiting&lt;BR /&gt;    * a best effort attempt will be made to restore the files, directories,&lt;BR /&gt;    * libraries, etc. on your system to their state prior to the start of the&lt;BR /&gt;    * operation.  However, it is possible that execution of installation command&lt;BR /&gt;    * procedures from the kit may have modified the system environment in ways&lt;BR /&gt;    * that cannot be reversed automatically.  (The software installation utility&lt;BR /&gt;    * cannot track what product specific procedures do.)  For this reason, you&lt;BR /&gt;    * may want to reconsider your action.  To cancel your abort request and&lt;BR /&gt;    * thereby resume the operation, answer YES to the following question.&lt;BR /&gt; &lt;BR /&gt;Do you want to continue? [YES] &lt;BR /&gt; Interrupt &lt;BR /&gt;Are you repeating ^Y to abort the remote session on node 11073? N&lt;BR /&gt;%PCSIUI-E-INVALKEY, invalid key&lt;BR /&gt; &lt;BR /&gt;Do you want to continue? [YES] no&lt;BR /&gt; &lt;BR /&gt;%PCSIUI-W-CONTROLY, Ctrl/Y or Ctrl/C has been detected&lt;BR /&gt; &lt;BR /&gt;    * You have already requested termination of this operation.  Termination is&lt;BR /&gt;    * either in progress or the utility is trying to complete processing of the&lt;BR /&gt;    * current object before an orderly shutdown can begin.  It is recommended&lt;BR /&gt;    * that you wait for the PRODUCT command to finish its activity by answering&lt;BR /&gt;    * YES to the following question.  However, if the process is hung or you&lt;BR /&gt;    * want to force image exit now, then answer NO to the following question.&lt;BR /&gt; &lt;BR /&gt;Do you want to continue? [YES] no&lt;BR /&gt; &lt;BR /&gt;%PCSIUI-I-USERABORT, operation terminated by user request&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;The Alpha server is a very low spec.&lt;BR /&gt;&lt;BR /&gt;$ sh cpu&lt;BR /&gt;&lt;BR /&gt;System: TST731, AlphaServer 400 4/233&lt;BR /&gt;&lt;BR /&gt;CPU ownership sets:&lt;BR /&gt;   Active               0&lt;BR /&gt;   Configure            0&lt;BR /&gt;&lt;BR /&gt;CPU state sets:&lt;BR /&gt;   Potential            0&lt;BR /&gt;   Autostart            0,1&lt;BR /&gt;   Powered Down         None&lt;BR /&gt;   Not Present          1&lt;BR /&gt;   Failover             None&lt;BR /&gt;$ show mem/phy&lt;BR /&gt;              System Memory Resources on 14-DEC-2005 13:43:35.82&lt;BR /&gt;&lt;BR /&gt;Physical Memory Usage (pages):     Total        Free      In Use    Modified&lt;BR /&gt;  Main Memory (256.00MB)           32768        7613       24380         775&lt;BR /&gt;&lt;BR /&gt;Write Bitmap (WBM) Memory Summary&lt;BR /&gt;  Local bitmap count:     0     Local bitmap memory usage (bytes)       0.00&lt;BR /&gt;  Master bitmap count:    0     Master bitmap memory usage (bytes)      0.00&lt;BR /&gt;&lt;BR /&gt;Of the physical pages in use, 3960 pages are permanently allocated to OpenVMS.&lt;BR /&gt;$ &lt;BR /&gt;&lt;BR /&gt;$ product show hist&lt;BR /&gt;----------------------------------- ----------- ----------- --------------------&lt;BR /&gt;PRODUCT                             KIT TYPE    OPERATION   DATE AND TIME&lt;BR /&gt;----------------------------------- ----------- ----------- --------------------&lt;BR /&gt;DEC AXPVMS VMS732_ACRTL V2.0        Patch       Install     14-DEC-2005 13:00:26&lt;BR /&gt;DEC AXPVMS VMS732_RTPAD V1.0        Patch       Install     16-NOV-2005 15:58:38&lt;BR /&gt;DEC AXPVMS VMS732_DDTM V1.0         Patch       Install     02-NOV-2005 12:17:56&lt;BR /&gt;DEC AXPVMS VMS732_MUP V1.0          Patch       Install     02-NOV-2005 09:59:27&lt;BR /&gt;DEC AXPVMS VMS732_UPDATE V5.0       Patch       Install     02-NOV-2005 09:58:17&lt;BR /&gt;DEC AXPVMS VMS732_MUP V1.0          Patch       Install     31-OCT-2005 16:44:56&lt;BR /&gt;DEC AXPVMS VMS732_UAF V1.0          Patch       Install     21-OCT-2005 17:26:27&lt;BR /&gt;DEC AXPVMS DNVOSIMUP01 V7.3-2       Patch       Install     12-OCT-2005 13:13:07&lt;BR /&gt;DEC AXPVMS DNVOSIECO01 V7.3-2       Patch       Install     12-OCT-2005 13:11:03&lt;BR /&gt;DEC AXPVMS VMS732_MQ V3.0           Patch       Install     03-OCT-2005 16:08:48&lt;BR /&gt;DEC AXPVMS VMS732_JOBCTL V2.0       Patch       Install     03-OCT-2005 16:07:05&lt;BR /&gt;DEC AXPVMS VMS732_MANAGE V4.0       Patch       Install     03-OCT-2005 16:05:42&lt;BR /&gt;DEC AXPVMS VMS732_IPC V2.0          Patch       Install     03-OCT-2005 15:59:12&lt;BR /&gt;DEC AXPVMS VMS732_F11X V4.0         Patch       Install     03-OCT-2005 15:57:12&lt;BR /&gt;DEC AXPVMS VMS732_SYS V8.0          Patch       Install     03-OCT-2005 15:02:34&lt;BR /&gt;DEC AXPVMS VMS732_SHADOWING V5.0    Patch       Install     05-SEP-2005 16:31:24&lt;BR /&gt;DEC AXPVMS VMS732_SYSLOA V3.0       Patch       Install     01-SEP-2005 12:50:40&lt;BR /&gt;DEC AXPVMS VMS732_LAN V4.0          Patch       Install     01-SEP-2005 12:49:10&lt;BR /&gt;DEC AXPVMS VMS732_AUDSRV V2.0       Patch       Install     12-AUG-2005 12:59:23&lt;BR /&gt;DEC AXPVMS VMS732_BACKUP V4.0       Patch       Install     12-AUG-2005 12:59:23&lt;BR /&gt;DEC AXPVMS VMS732_FIBRE_SCSI V7.0   Patch       Install     12-AUG-2005 12:59:23&lt;BR /&gt;DEC AXPVMS VMS732_MQ V2.0           Patch       Install     12-AUG-2005 12:59:23&lt;BR /&gt;DEC AXPVMS VMS732_DRIVER V2.0       Patch       Install     21-JUL-2005 15:09:03&lt;BR /&gt;DEC AXPVMS VMS732_LAN V3.0          Patch       Install     21-JUL-2005 15:09:03&lt;BR /&gt;DEC AXPVMS VMS732_MANAGE V3.0       Patch       Install     21-JUL-2005 15:09:03&lt;BR /&gt;DEC AXPVMS VMS732_PCSI V1.0         Patch       Install     21-JUL-2005 15:09:03&lt;BR /&gt;DEC AXPVMS VMS732_SHADOWING V4.0    Patch       Install     21-JUL-2005 15:09:03&lt;BR /&gt;DEC AXPVMS VMS732_SYS V7.0          Patch       Install     21-JUL-2005 15:09:03&lt;BR /&gt;DEC AXPVMS VMS732_VERIFY V1.0       Patch       Install     21-JUL-2005 15:09:03&lt;BR /&gt;DEC AXPVMS VMS732_DCL V3.0          Patch       Install     21-JUL-2005 14:56:02&lt;BR /&gt;DEC AXPVMS VMS732_ACRTL V1.0        Patch       Install     21-JUL-2005 14:16:03&lt;BR /&gt;DEC AXPVMS VMS732_UPDATE V4.0       Patch       Install     21-JUL-2005 09:41:14&lt;BR /&gt;DEC AXPVMS VMS732_PCSI V1.0         Patch       Install     21-JUL-2005 09:35:41&lt;BR /&gt;CPQ AXPVMS CSWB V1.4                Full LP     Install     02-APR-2004 14:21:06&lt;BR /&gt;CPQ AXPVMS GTK V1.2-10              Full LP     Install     02-APR-2004 14:21:06&lt;BR /&gt;CPQ AXPVMS OPL V1.0-0A7             Full LP     Install     02-APR-2004 14:21:06&lt;BR /&gt;DEC AXPVMS TCPIP_ECO V5.4-151       Patch       Install     02-APR-2004 11:30:39&lt;BR /&gt;DEC AXPVMS VMS732_F11X V1.0         Patch       Install     02-APR-2004 11:11:11&lt;BR /&gt;DEC AXPVMS VMS732_LAN V1.0          Patch       Install     02-APR-2004 10:56:53&lt;BR /&gt;DEC AXPVMS VMS732_FIBRE_SCSI V2.0   Patch       Install     02-APR-2004 10:46:45&lt;BR /&gt;DEC AXPVMS VMS732_SYS V2.0          Patch       Install     02-APR-2004 10:42:50&lt;BR /&gt;DEC AXPVMS VMS732_DCL V1.0          Patch       Install     02-APR-2004 10:33:41&lt;BR /&gt;DEC AXPVMS VMS732_RPC V1.0          Patch       Install     02-APR-2004 10:05:22&lt;BR /&gt;DEC AXPVMS VMS732_GRAPHICS V2.0     Patch       Install     02-APR-2004 09:58:39&lt;BR /&gt;DEC AXPVMS VMS732_UPDATE V1.0       Patch       Install     02-APR-2004 09:50:34&lt;BR /&gt;DEC AXPVMS VMS732_PCSI V1.0         Patch       Install     02-APR-2004 09:43:15&lt;BR /&gt;DEC AXPVMS DECNET_OSI V7.3-2        Full LP     Install     02-DEC-2003 10:07:07&lt;BR /&gt;CPQ AXPVMS CDSA V2.0-109            Full LP     Install     02-DEC-2003 09:49:32&lt;BR /&gt;DEC AXPVMS DWMOTIF V1.3-1           Full LP     Install     02-DEC-2003 09:49:32&lt;BR /&gt;DEC AXPVMS OPENVMS V7.3-2           Platform    Install     02-DEC-2003 09:49:32&lt;BR /&gt;DEC AXPVMS TCPIP V5.4-15            Full LP     Install     02-DEC-2003 09:49:32&lt;BR /&gt;DEC AXPVMS VMS V7.3-2               Oper System Install     02-DEC-2003 09:49:32&lt;BR /&gt;HP AXPVMS KERBEROS V2.0-6           Full LP     Install     02-DEC-2003 09:49:32&lt;BR /&gt;----------------------------------- ----------- ----------- --------------------&lt;BR /&gt; &lt;BR /&gt;53 items found&lt;BR /&gt;$ &lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Kevin Raven&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 14 Dec 2005 08:44:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/patch-acrtl-v200-for-openvms-7-3-2/m-p/4946777#M73212</guid>
      <dc:creator>VMS Support</dc:creator>
      <dc:date>2005-12-14T08:44:26Z</dc:date>
    </item>
    <item>
      <title>Re: Patch ACRTL V200 for OpenVMS 7.3-2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/patch-acrtl-v200-for-openvms-7-3-2/m-p/4946778#M73213</link>
      <description>Hi Kevin,&lt;BR /&gt;&lt;BR /&gt;I'm fairly sure I had a similar sounding problem with VMS731_ACRTL, where the solution was to increase (significantly (try x2 x4)) BYTLM for the account applying the update.&lt;BR /&gt;&lt;BR /&gt;From SDA what channels did the product install have open ? (syslib:starlet.olb?)&lt;BR /&gt;&lt;BR /&gt;Kind Regards&lt;BR /&gt;John.</description>
      <pubDate>Wed, 14 Dec 2005 09:57:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/patch-acrtl-v200-for-openvms-7-3-2/m-p/4946778#M73213</guid>
      <dc:creator>John Abbott_2</dc:creator>
      <dc:date>2005-12-14T09:57:56Z</dc:date>
    </item>
    <item>
      <title>Re: Patch ACRTL V200 for OpenVMS 7.3-2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/patch-acrtl-v200-for-openvms-7-3-2/m-p/4946779#M73214</link>
      <description>John,&lt;BR /&gt;      Thanks for the reply. I have increased bytlm from 64K to 200K and I'm rerunning the install. It has been running now for 25 minutes and is chugging away using librarian.exe ..lots of Direct I/O and CPU being clocked. Will see what happens with the CLI product install session when the librarian sub process exits.&lt;BR /&gt;&lt;BR /&gt;And have a look at channels at the stalled CLI process if it does not complete.&lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;Kevin</description>
      <pubDate>Wed, 14 Dec 2005 10:56:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/patch-acrtl-v200-for-openvms-7-3-2/m-p/4946779#M73214</guid>
      <dc:creator>VMS Support</dc:creator>
      <dc:date>2005-12-14T10:56:19Z</dc:date>
    </item>
    <item>
      <title>Re: Patch ACRTL V200 for OpenVMS 7.3-2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/patch-acrtl-v200-for-openvms-7-3-2/m-p/4946780#M73215</link>
      <description>Worked....&lt;BR /&gt;&lt;BR /&gt;After 35 minutes ...The installed finished.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Kevin</description>
      <pubDate>Wed, 14 Dec 2005 11:14:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/patch-acrtl-v200-for-openvms-7-3-2/m-p/4946780#M73215</guid>
      <dc:creator>VMS Support</dc:creator>
      <dc:date>2005-12-14T11:14:47Z</dc:date>
    </item>
    <item>
      <title>Re: Patch ACRTL V200 for OpenVMS 7.3-2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/patch-acrtl-v200-for-openvms-7-3-2/m-p/4946781#M73216</link>
      <description>Thanks for the solution.&lt;BR /&gt;&lt;BR /&gt;Now fixed and patch is in.</description>
      <pubDate>Wed, 14 Dec 2005 11:15:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/patch-acrtl-v200-for-openvms-7-3-2/m-p/4946781#M73216</guid>
      <dc:creator>VMS Support</dc:creator>
      <dc:date>2005-12-14T11:15:39Z</dc:date>
    </item>
  </channel>
</rss>

