[med-svn] [fis-gtm] 01/01: There is no need to carry changelogs of never released versions
Andreas Tille
tille at debian.org
Sat Nov 23 21:48:36 UTC 2013
This is an automated email from the git hooks/post-receive script.
tille pushed a commit to branch master
in repository fis-gtm.
commit 997958279bc936d57a4844886c647481b63b2973
Author: Andreas Tille <tille at debian.org>
Date: Sat Nov 23 22:43:39 2013 +0100
There is no need to carry changelogs of never released versions
---
.../upstream-files/GTM_V5.5-000_Release_Notes.html | 1263 --------------------
1 file changed, 1263 deletions(-)
diff --git a/debian/upstream-files/GTM_V5.5-000_Release_Notes.html b/debian/upstream-files/GTM_V5.5-000_Release_Notes.html
deleted file mode 100644
index 658f463..0000000
--- a/debian/upstream-files/GTM_V5.5-000_Release_Notes.html
+++ /dev/null
@@ -1,1263 +0,0 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>GT.M V5.5-000 Release Notes</title><link rel="stylesheet" href="gtm.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><meta name="description" content="Contact Information GT.M Group Fidelity Information Services, Inc. 2 West Liberty Boulevard, Suite 300 Malvern, PA 19355 United States of America GT.M Support for customers: +1 (610) 578-4226 gtmsupport at fisglobal. [...]
- <p>
-</p><div class="address"><p>GT.M�Group�<br>
-Fidelity�Information�Services,�Inc.�<br>
-<span class="street">2�West�Liberty�Boulevard,�Suite�300</span>�<br>
-<span class="city">Malvern,�</span><span class="state">PA�</span><span class="postcode">19355</span><br>
-<span class="country">United�States�of�America</span></p></div><p>
-</p>
- </td><td>
- <p>
-</p><div class="address"><p><br>
-<span class="phone">GT.M�Support�for�customers:�+1�(610)�578-4226�</span>�<br>
-<span class="phone">gtmsupport at fisglobal.com</span>�<br>
-<span class="phone">Switchboard:�+1�(610)�296-8877</span><br>
-<span class="otheraddr">Website:�<a class="ulink" href="http://fis-gtm.com" target="_top">http://fis-gtm.com</a></span>�<br>
-</p></div><p>
-</p>
- </td></tr></tbody></table></div><p>
-</p></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#conventions">Conventions</a></span></dt><dt><span class="sect1"><a href="#id1384260">Release Overview</a></span></dt><dd><dl><dt><span class="sect2"><a href="#platforms"> Platforms</a></span></dt><dt><span class="sect2"><a href="#manage64"> Migrating to 64-bit platforms</a></span></dt><dt><span class="sect2"><a href="#id1384968">Recompile</a></span></dt><dt><span class="s [...]
- <p>Pre V5.5-000 </p>
- </th><th>
- <p>Pre V5.5-000 qualifier</p>
- </th><th>
- <p>V5.5-000 </p>
- </th><th>
- <p>V5.5-000 qualifier </p>
- </th></tr></thead><tbody><tr><td>
- <p>originating instance or primary instance </p>
- </td><td>
- <p>-rootprimary</p>
- </td><td>
- <p>originating instance or originating primary instance. </p>
- <p>Within the context of a replication connection between two instances, an originating instance is referred to as source instance or source side. For example, in an �B<-A->C replication configuration, A is the source instance for B and C. </p>
- </td><td>
- <p>-updok (recommended)</p>
- <p>-rootprimary (still accepted)</p>
- </td></tr><tr><td>
- <p>replicating instance (or secondary instance) and propagating instance </p>
- </td><td>
- <p>N/A for replicating instance or secondary instance. </p>
- <p>-propagateprimary for propagating instance </p>
- </td><td>
- <p>replicating instance. </p>
- <p>Within the context of a replication connection between two instances, a replicating instance that receives updates from a source instance is referred to as receiving instance or receiver side. For example, in an B<-A->C replication configuration, both B and C can be referred to as a receiving instance. </p>
- </td><td>
- <p>-updnotok </p>
- </td></tr><tr><td>
- <p>N/A</p>
- </td><td>
- <p>N/A</p>
- </td><td>
- <p>supplementary instance. </p>
- <p>For example, in an A->P->Q replication configuration, P is the supplementary instance. Both A and P are originating instances. </p>
- </td><td>
- <p>-updok</p>
- </td></tr></tbody></table></div></div><div class="sect1" title="Release Overview"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1384260"></a>Release Overview</h2></div></div></div><p>V5.5-000 provides a new type of replication, described in more detail in the <a class="ulink" href="http://tinco.pair.com/bhaskar/gtm/doc/articles/GTM_Supplementary_Instance.html" target="_top">Supplementary Instance Technical Bulletin</a>. With Supplementary Ins [...]
- <p class="bold">Platform</p>
- </th><th>
- <p class="bold">Supported Versions</p>
- </th><th>
- <p class="bold">Notes</p>
- </th></tr></thead><tbody><tr><td>
- <p>Hewlett-Packard Integrity IA64 HP-UX</p>
- </td><td>
- <p>11V3 (11.31)</p>
- </td><td>
- <p>-</p>
- </td></tr><tr><td>
- <p>IA64 GNU/Linux - Red Hat Enterprise Linux</p>
- </td><td>
- <p>Red Hat Enterprise Linux 5.6</p>
- </td><td>
- <p>GT.M should also run on recent releases of other major Linux distributions with a contemporary 2.6 Linux kernel, glibc (version 2.5-24 or later) and ncurses (version 5.5-24 or later). FIS has verified that GT.M passes comprehensive testing on RHEL 5.x on machines that have single cells (no more than 8 CPUs). Multi-cell machines are not considered suitable for production use until they are certified.</p>
- <p>Although this platform remains at present fully supported, the announcement that it will not be supported by Red Hat Enterprise Linux 6 makes it likely that future GT.M releases will not be supported on this platform.</p>
- <p>Please contact your FIS account manager if you need GT.M on this platform.</p>
- </td></tr><tr><td>
- <p>Hewlett-Packard PA-RISC HP-UX</p>
- </td><td>
- <p>11.11</p>
- </td><td>
- <p>GT.M supports UTF-8 mode and M mode on this platform subject to the following:</p>
- <div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Problems with HP-UX 11.11 prevent FIS from testing 4 byte UTF-8 characters. FIS understands that the issue is resolved in HP-UX 11.31. At this time, GT.M is still untested and not formally supported on HP-UX 11.31; however, we are not aware of anything that would prevent this GT.M release from working correctly on that newer version.</p></li></ul></div>
- <p>Running GT.M on HP-UX 11i requires that patch PHKL_28475 be applied to the system. This patch fixes a problem with the lseek64() C library call that GT.M uses. A system without this patch gives fairly consistent database errors of varying types, structural damage, and in general does not work correctly for any but the most simplistic usage. The swlist -p command (executed as root) can be used to determine if this patch has been applied. Since recent "BATCH" and "GOLDEN [...]
- <p>GT.M does not support database encryption on this platform.</p>
- <p>GT.M does not support the Memory Mapped (MM) Access Method on this platform.</p>
- <p>Although this platform remains at present fully supported with respect to bug fixes, owing to its looming sunset by HP, new functionality is supported on this platform only for FIS' convenience. It is likely that future GT.M releases will not be supported on this platform.</p>
- <p>Please contact your FIS account manager if you need GT.M on this platform.</p>
- </td></tr><tr><td>
- <p>Hewlett-Packard Alpha/AXP Tru64 UNIX</p>
- </td><td>
- <p>5.1B</p>
- </td><td>
- <p>GT.M supports M mode but not UTF-8 mode on this platform. GT.M does not support database encryption on this platform.</p>
- <p>Although this platform remains at present fully supported with respect to bug fixes, owing to its looming sunset by HP, new functionality is supported on this platform only for FIS' convenience. It is likely that future GT.M releases will not be supported on this platform.</p>
- <p>Please contact your FIS account manager if you need GT.M on this platform.</p>
- </td></tr><tr><td>
- <p>Hewlett-Packard Alpha/AXP OpenVMS</p>
- </td><td>
- <p>7.3-1 / 7.3-2 / 8.2 / 8.3</p>
- </td><td>
- <p>GT.M supports M mode but not UTF-8 mode on this platform. GT.M does not support several recent enhancements on this platform, including but not limited to database encryption, on-line backup, multi-site replication, PIPE devices and triggers.</p>
- <p>If you need to work with external calls written in C with Version 6.x of the C compiler on Alpha OpenVMS, then you must carefully review all the provided kits for that product and apply them appropriately.</p>
- <p>Although this platform remains at present fully supported with respect to bug fixes, owing to its looming sunset by HP, new functionality is supported on this platform only for FIS' convenience. Future GT.M releases may not be supported on this platform. Regardless of ongoing plans for support of the OpenVMS platform itself, the next GT.M release will likely no longer support OpenVMS 7.x. Please contact your FIS account manager if you need ongoing support for GT.M on t [...]
- </td></tr><tr><td>
- <p>IBM System p AIX</p>
- </td><td>
- <p>6.1, 7.1</p>
- </td><td>
- <p>Since GT.M processes are 64-bit, FIS expects 64-bit AIX configurations to be preferable.</p>
- <p>While GT.M supports both UTF-8 mode and M mode on this platform, there are problems with the AIX ICU utilities that prevent FIS from testing 4-byte UTF-8 characters as comprehensively on this platform as we do on others.</p>
- <p>Running GT.M on AIX 7.1 requires APAR IZ87564, a fix for the POW() function, to be applied. To verify that this fix has been installed, execute <code class="code">instfix -ik IZ87564. </code></p>
- </td></tr><tr><td>
- <p>GNU/Linux on IBM System z</p>
- </td><td>
- <p>SuSE Linux Enterprise Server 10.3 and 11 or later</p>
- </td><td>
- <p>GT.M support starts at SuSE Linux Enterprise Server 10 Service Pack 3. On SuSE Linux Enterprise Server 11 or later,
- we require the installation of the SuSE provided libelf0-0.8.10-37.10, or later, package. Future GT.M releases are likely to no longer support SLES 10 and to support only SLES 11.</p>
- <p>Please contact your FIS account manager if you need GT.M on this platform.</p>
- </td></tr><tr><td>
- <p>IBM System z z/OS</p>
- </td><td>
- <p>V1R11</p>
- </td><td>
- <p>Please contact your FIS account manager if you need GT.M on this platform.</p>
- </td></tr><tr><td>
- <p>Sun SPARC Solaris</p>
- </td><td>
- <p>10 (Update 6 and above)</p>
- </td><td>
- <p>The deprecated DAL calls operate in M mode but not in UTF-8 mode. Please refer to the Integrating External Routines chapter in the Programmer's Guide for appropriate alternatives.</p>
- </td></tr><tr><td>
- <p>x86_64 GNU/Linux</p>
- </td><td>
- <p>Red Hat Enterprise Linux 5.6; Ubuntu 8.04 LTS through 10.10; SuSE Linux Enterprise Server 11</p>
- </td><td>
- <p>To run 64-bit GT.M processes requires both a 64-bit kernel as well as 64-bit hardware.</p>
- <p>GT.M should also run on recent releases of other major Linux distributions with a contemporary 2.6 Linux kernel, glibc (version 2.5-24 or later) and ncurses (version 5.5 or later).</p>
- <p>To install GT.M with Unicode (UTF-8) support on RHEL 5.4, in response to the installation question <code class="code">Should an ICU version other than the default be used? (y or n)</code> please respond <code class="code">y</code> and then specify the ICU version (for example, respond 3.6) to the subsequent prompt <code class="code">Enter ICU version (ICU version 3.6 or later required. Enter as <major-</code><code class="code">ver>.<minor-ver>):</code></p>
- <p>Future GT.M releases may no longer support Red Hat Enterprise Linux 5.x. Please contact your FIS account manager if you need ongoing support for GT.M on RHEL 5.x. We anticipate support for RHEL 6 in the future.</p>
- </td></tr><tr><td>
- <p>x86 GNU/Linux</p>
- </td><td>
- <p>Red Hat Enterprise Linux 5.5</p>
- </td><td>
- <p>This 32-bit version of GT.M runs on either 32- or 64-bit x86 platforms; we expect the X86_64 GNU/Linux version of GT.M to be preferable on 64-bit hardware.</p>
- <p>GT.M should also run on recent releases of other major Linux distributions with a contemporary 2.6 Linux kernel, glibc (version 2.5-49 or later) and ncurses (version 5.5-24 or later). The minimum CPU must have the instruction set of a 686 (Pentium Pro) or equivalent.</p>
- <p>Future GT.M releases may no longer support Red Hat Enterprise Linux 5.x. Please contact your FIS account manager if you need ongoing support for GT.M on RHEL 5.x. We anticipate support for RHEL 6 in the future.</p>
- </td></tr></tbody></table></div><div class="sect3" title="Platform support lifecycle"><div class="titlepage"><div><div><h4 class="title"><a name="platform_lifecycle"></a>Platform support lifecycle</h4></div></div></div><p>FIS usually supports new operating system versions six months after stable releases are available and we usually support each version for a two year window. GT.M releases are also normally supported for two years after release. While FIS will attempt to pr [...]
- <p class="bold">Parameter type</p>
- </th><th>
- <p class="bold">32-Bit</p>
- </th><th>
- <p class="bold">64-bit</p>
- </th><th>
- <p class="bold">Remarks</p>
- </th></tr></thead><tbody><tr><td>
- <p>gtm_long_t</p>
- </td><td>
- <p>4-byte (32-bit)</p>
- </td><td>
- <p>8-byte (64-bit)</p>
- </td><td>
- <p>gtm_long_t is much the same as the C language long type, except on Tru64 UNIX, where GT.M remains a 32-bit application.</p>
- </td></tr><tr><td>
- <p>gtm_ulong_t</p>
- </td><td>
- <p>4-byte</p>
- </td><td>
- <p>8-byte</p>
- </td><td>
- <p>gtm_ulong_t is much the same as the C language unsigned long type.</p>
- </td></tr><tr><td>
- <p>gtm_int_t</p>
- </td><td>
- <p>4-byte</p>
- </td><td>
- <p>4-byte</p>
- </td><td>
- <p>gtm_int_t has 32-bit length on all platforms.</p>
- </td></tr><tr><td>
- <p>gtm_uint_t</p>
- </td><td>
- <p>4-byte</p>
- </td><td>
- <p>4-byte</p>
- </td><td>
- <p>gtm_uint_t has 32-bit length on all platforms</p>
- </td></tr></tbody></table></div><div class="caution" title="Caution" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Caution"><tr><td rowspan="2" align="center" valign="top" width="12pt"><img alt="[Caution]" src="images/caution.jpg"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>If your interface uses gtm_long_t or gtm_ulong_t types but your interface code uses int or signed int types, failure to revise the types so they [...]
- <p class="bold">Parameter type</p>
- </th><th>
- <p class="bold">32-Bit</p>
- </th><th>
- <p class="bold">64-bit</p>
- </th><th>
- <p class="bold">Remarks</p>
- </th></tr></thead><tbody><tr><td>
- <p>gtm_descriptor in gtm_descript.h</p>
- </td><td>
- <p>4-byte</p>
- </td><td>
- <p>8-byte</p>
- </td><td>
- <p>Although it is only the address within these types that changes, the structures may grow by up to 8 bytes as a result of compiler padding to meet platform alignment requirements.</p>
- </td></tr></tbody></table></div><div class="important" title="Important" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Important"><tr><td rowspan="2" align="center" valign="top" width="12pt"><img alt="[Important]" src="images/important.jpg"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>Assuming other aspects of their code are 64-bit capable, collation routines should require only recompilation. </p></td></tr></table></d [...]
- <p class="bold">Parameter type</p>
- </th><th>
- <p class="bold">32-Bit</p>
- </th><th>
- <p class="bold">64-bit</p>
- </th><th>
- <p class="bold">Remarks</p>
- </th></tr></thead><tbody><tr><td>
- <p>gtm_string_t type in gtmxc_types.h</p>
- </td><td>
- <p>4-byte</p>
- </td><td>
- <p>8-byte</p>
- </td><td>
- <p>Although it is only the address within these types that changes, the structures may grow by up to 8 bytes as a result of compiler padding to meet platform alignment requirements.</p>
- </td></tr></tbody></table></div><div class="important" title="Important" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Important"><tr><td rowspan="2" align="center" valign="top" width="12pt"><img alt="[Important]" src="images/important.jpg"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>Assuming other aspects of their code are 64-bit capable, environment translation routines should require only recompilation.</p></td></t [...]
- <em class="replaceable"><code>pid_of_gtmsecshr</code></em>.</p></li></ul></div><div class="caution" title="Caution" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Caution"><tr><td rowspan="2" align="center" valign="top" width="12pt"><img alt="[Caution]" src="images/caution.jpg"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>Never replace the binary image on disk of any executable file while it is in use by an active process. It may lead [...]
- to work properly but fail to recognize function key sequences or position the cursor properly in response to escape sequences from GT.M. GT.M itself does not have any knowledge of specific terminal control characteristics. Therefore, it is important to specify the right terminfo entry to let GT.M communicate correctly with the terminal. You may need to add new terminfo entries depending on your specific platform and implementation. The terminal (emulator) vendor may also be able to help [...]
-cursor_left(cub1), cursor_right(cuf1), cursor_up(cuu1), eat_newline_glitch(xenl),
-key_backspace(kbs), key_dc(kdch1),key_down(kcud1), key_left(kcub1), key_right(kcuf1), key_up(kcuu1),
-key_insert(kich1), keypad_local(rmkx),keypad_xmit(smkx), lines(lines).</pre></li></ul></div><p>GT.M sends keypad_xmit before terminal reads for direct mode and READs (other than READ *) if EDITING is enabled. GT.M sends keypad_local after these terminal reads.</p></div><div class="sect2" title="Installing Compression Libraries"><div class="titlepage"><div><div><h3 class="title"><a name="id1386087"></a>Installing Compression Libraries</h3></div></div></div><p>If you plan to use the option [...]
- <p><span class="bold"><strong>Id</strong></span></p>
- </th><th>
- <p><span class="bold"><strong>Prior Id</strong></span></p>
- </th><th>
- <p><span class="bold"><strong>Category</strong></span></p>
- </th><th>
- <p><span class="bold"><strong>Summary</strong></span></p>
- </th></tr></thead><tbody><tr><td>
- <p><a class="link" href="#GTM-2296">GTM-2296</a></p>
- </td><td>
- <p>C9905-001114</p>
- </td><td>
- <p>Utilities</p>
- </td><td>
- <p>Improved DSE FIND -SIBLING functionality.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-3873">GTM-3873</a></p>
- </td><td>
- <p>C9B09-001740</p>
- </td><td>
- <p>MUPIP</p>
- </td><td>
- <p>New -TRUNCATE qualifier for MUPIP REORG in UNIX.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-4033">GTM-4033</a></p>
- </td><td>
- <p>C9B12-001841</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>TROLLBACK to a $TLEVEL other than zero (0) leaves $REFERENCE empty which is the same behavior as a full TROLLBACK to 0=$TEVEL.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-4202">GTM-4202</a></p>
- </td><td>
- <p>C9C03-001934</p>
- </td><td>
- <p>MUPIP</p>
- </td><td>
- <p>Correction to NOREPLCTDREG error message context in UNIX.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-4337">GTM-4337</a></p>
- </td><td>
- <p>C9C05-002005</p>
- </td><td>
- <p>DB</p>
- </td><td>
- <p>UNIX gtm_db_startup_max_wait environment variable to control waiting on resource conflicts.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-5797">GTM-5797</a>�<span class="inlinemediaobject"><img src="images/chkmrkg.png" alt="Documented"></span></p>
- </td><td>
- <p>S9F12-002581</p>
- </td><td>
- <p>MUPIP</p>
- </td><td>
- <p>New -REGION qualifier for MUPIP REORG operations.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-5996">GTM-5996</a></p>
- </td><td>
- <p>C9H04-002848</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>Interrupted GT.M HANG commands account for the time spent handling the interrupt when the hang resumes.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-5997">GTM-5997</a></p>
- </td><td>
- <p>C9H04-002849</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>Interrupted timed GT.M LOCK commands account for the time spent waiting before the interrupt when the LOCK resumes its wait.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6185">GTM-6185</a></p>
- </td><td>
- <p>S9I05-002991</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>GT.M evaluates command postconditionals for invalid commands at runtime before generating an INVCMD error.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6224">GTM-6224</a></p>
- </td><td>
- <p>S9I08-002697</p>
- </td><td>
- <p>Utilities</p>
- </td><td>
- <p>Improved the setting of Journaling attributes with GDE.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6228">GTM-6228</a></p>
- </td><td>
- <p>C9I08-003014</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>GT.M properly manages stack frames when fielding CTRAP interrupts from the console.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6306">GTM-6306</a></p>
- </td><td>
- <p>C9I12-003062</p>
- </td><td>
- <p>DB</p>
- </td><td>
- <p>UNIX MUPIP JOURNAL -ROLLBACK -ONLINE capability and associated primarily operational changes.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6340">GTM-6340</a></p>
- </td><td>
- <p>C9J02-003091</p>
- </td><td>
- <p>MUPIP</p>
- </td><td>
- <p>Supplementary Instances and operational changes primarily to replication.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6736">GTM-6736</a></p>
- </td><td>
- <p>S9L01-002801, C9J03-003101</p>
- </td><td>
- <p>MUPIP</p>
- </td><td>
- <p>New JNLNOREPL error for the Source Server and PREVJNLLINKSET message to the operator log.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6449">GTM-6449</a></p>
- </td><td>
- <p>S9J08-002739</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p><CTRL-D> at the GT.M Direct Mode prompt on an empty line terminates GT.M and returns control to the shell in UNIX.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6569">GTM-6569</a></p>
- </td><td>
- <p>C9K03-003250</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>In UNIX, GT.M defers MUPIP STOP for a time window during which a process should not be terminated.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6614">GTM-6614</a></p>
- </td><td>
- <p>C9K05-003274</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>In UNIX, GT.M ignores SIGINT (control-C) if $PRINCIPAL is not a terminal.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6622">GTM-6622</a></p>
- </td><td>
- <p>S9K06-002778</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>GT.M better handles some error processing cases.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6650">GTM-6650</a></p>
- </td><td>
- <p>C9K07-003295</p>
- </td><td>
- <p>MUPIP</p>
- </td><td>
- <p>A Receiver Server started with the -UPDATERESYNC qualifier starts every connection handshake (with a Source Server) during its own lifetime with that characteristic.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6664">GTM-6664</a></p>
- </td><td>
- <p>C9K08-003307</p>
- </td><td>
- <p>Utilities</p>
- </td><td>
- <p>Enhancements for configure, gtmprofile, and gtminstall scripts in UNIX.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6711">GTM-6711</a></p>
- </td><td>
- <p>C9K10-003334</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>When returning from code invoked by MUPIP
- INTRPT (clearing $ZININTERRPT), GT.M implicitly clears any error(s) detected while 1=$ZININTERRUPT and sends a JIUNHNDINT error notification to the operator log.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6719">GTM-6719</a></p>
- </td><td>
- <p>C9K11-003340</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>Improved management of internal timers in UNIX.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6725">GTM-6725</a></p>
- </td><td>
- <p>C9K12-003344</p>
- </td><td>
- <p>MUPIP</p>
- </td><td>
- <p>Improved handling of database migration from V4 format.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6738">GTM-6738</a></p>
- </td><td>
- <p>C9L01-003352</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>New %RANDSTR string generator utility function.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6759">GTM-6759</a></p>
- </td><td>
- <p>S9L03-002806</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>Improved handing of TPTIMEOUT interrupts.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6771">GTM-6771</a></p>
- </td><td>
- <p>C9L03-003376</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>In UNIX, ZMESSAGE treats any non-GT.M error as a trappable or fatal event.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6811">GTM-6811</a></p>
- </td><td>
- <p>C9L05-003414</p>
- </td><td>
- <p>DB</p>
- </td><td>
- <p>Improved ftok algorithm for shared resources on UNIX.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6813">GTM-6813</a></p>
- </td><td>
- <p>C9L05-003416</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>Change to actuallist-formallist handling mostly affecting DO</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6819">GTM-6819</a></p>
- </td><td>
- <p>S9L06-002815</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>New gtm_trace_gbl_name environment variable and M-profiling enhancements.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6826">GTM-6826</a>�<span class="inlinemediaobject"><img src="images/chkmrkg.png" alt="Documented"></span></p>
- </td><td>
- <p>S9L06-002819</p>
- </td><td>
- <p>MUPIP</p>
- </td><td>
- <p>GT.M no longer requires that an external filter treat its output as a transaction in UNIX.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6834">GTM-6834</a></p>
- </td><td>
- <p>C9L06-003421</p>
- </td><td>
- <p>MUPIP</p>
- </td><td>
- <p>MUPIP RECOVER -BACKWARD restricts processing that identifies broken transactions to the most recent journal file(s).</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6836">GTM-6836</a></p>
- </td><td>
- <p>C9L06-003423</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>Improved SOCKET device handling of WRITE /LISTEN and WRITE /WAIT.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6841">GTM-6841</a></p>
- </td><td>
- <p>C9L06-003428</p>
- </td><td>
- <p>MUPIP</p>
- </td><td>
- <p>The Source Server no longer hangs while waiting for a REPL_CMP_SOLVE message in UNIX.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6845">GTM-6845</a></p>
- </td><td>
- <p>C9L06-003432</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>The GT.M parser now appropriately recognizes the end of the last source line in a routine.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6849">GTM-6849</a></p>
- </td><td>
- <p>S9L07-002821</p>
- </td><td>
- <p>Utilities</p>
- </td><td>
- <p>Corrected typographical errors in three messages.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6851">GTM-6851</a></p>
- </td><td>
- <p>S9L07-002822</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>Improved error handling for $ZDATE().</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6854">GTM-6854</a></p>
- </td><td>
- <p>S9L07-002823</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>With VIEW "FULL_BOOLEAN", GT.M now evaluates functions with side effects - extrinsic functions ($$), external functions ($&) and $INCREMENT() in left-to-right order.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6856">GTM-6856</a></p>
- </td><td>
- <p>S9L07-002824</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>GT.M correctly compiles expressions like if a<$$x(b-c) when specifying FULL_BOOLEAN.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6860">GTM-6860</a></p>
- </td><td>
- <p>C9L07-003439</p>
- </td><td>
- <p>Utilities</p>
- </td><td>
- <p>DSE DUMP -FILE -ALL output prints journal record types in hexadecimal.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6896">GTM-6896</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUPIP</p>
- </td><td>
- <p>Fixes to UNIX cross-endian replication.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6898">GTM-6898</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUPIP</p>
- </td><td>
- <p>Improved replication of duplicate KILLs.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6935">GTM-6935</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>MERGE no longer gives an error when the source and destination variables are identical.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6939">GTM-6939</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>Utilities</p>
- </td><td>
- <p>%RO no longer strips trailing spaces or program text starting with a quoted semi-colon</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6953">GTM-6953</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>DB</p>
- </td><td>
- <p>Database encryption reference plug-in improvements in UNIX.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6957">GTM-6957</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>$ZTRNLNM() recognizes all the documented keywords including all the OpenVMS keywords.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6958">GTM-6958</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUPIP</p>
- </td><td>
- <p>MUPIP INTEG and MUPIP JOURNAL -ROLLBACK (or -RECOVER) now operate successfully on database files larger than 1TB.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6994">GTM-6994</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>64-bit GT.M (all except HP Alpha (OpenVMS and Tru64), HP PA-RISC (HP-UX), and 32-bit x86 (Linux)) now passes 64-bit long and ulong values between C and M though the call-out and call-in interfaces.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-6996">GTM-6996</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>ZSHOW "D" that includes one or more SOCKET devices no longer causes memory leak.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7002">GTM-7002</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>Fixes for INDEPENDENT and RENAME device parameters for the PIPE device in UNIX.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7004">GTM-7004</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUPIP</p>
- </td><td>
- <p>Closed tiny hole in MUPIP FREEZE.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7005">GTM-7005</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>Utilities</p>
- </td><td>
- <p>More meaningful GDE error messages for encryption and MM access method set.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7007">GTM-7007</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>Corrected handling of subscripted FOR control variables in XECUTE strings.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7008">GTM-7008</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>Fix for XECUTE "DO @x" where x doesn't specify an actuallist.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7016">GTM-7016</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUPIP</p>
- </td><td>
- <p>New -STDIN qualifier for MUPIP LOAD in UNIX.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7018">GTM-7018</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>Duplicate SET optimization now the default.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7020">GTM-7020</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>DB</p>
- </td><td>
- <p>UNIX trigger updates don't get spurious TRIGDEFBAD errors.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7021">GTM-7021</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>Utilities</p>
- </td><td>
- <p>Cleaner operation and organization of the UNIX installation kit.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7027">GTM-7027</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>Utilities</p>
- </td><td>
- <p>LKE now issues NOLOCKMATCH when a non-existing lock is searched with SHOW or attempted to be released with CLEAR.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7029">GTM-7029</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>Utilities</p>
- </td><td>
- <p>GT.M build successful on Ubuntu 11.10 with GCC 4.6.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7034">GTM-7034</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUPIP</p>
- </td><td>
- <p>MUPIP JOURNAL RECOVER (or ROLLBACK) -BACKWARD now processes multi-region broken TP transactions appropriately.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7073">GTM-7073</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>Utilities</p>
- </td><td>
- <p>Improved LKE message when no matching LOCK found.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7077">GTM-7077</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUPIP</p>
- </td><td>
- <p>MUPIP EXTRACT -FORMAT=BIN now handles database blocks of maximum size.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7078">GTM-7078</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>New GTMASSERT2 message to produce more information about a failing condition.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7079">GTM-7079</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUPIP</p>
- </td><td>
- <p>MUPIP JOURNAL -SHOW=ALL output now shows counts of all Record Types correctly up to 1 billion.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7082">GTM-7082</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUPIP</p>
- </td><td>
-<p>In UNIX, -extract="-stdout" writes to standard output (stdout) instead of writing to a file named -stdout.</p>
-
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7110">GTM-7110</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>Utilities</p>
- </td><td>
- <p>In UNIX, GT.M utilities now give a CLIERR error when an equal-sign (=) follows a qualifier without an immediately following value.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7122">GTM-7122</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>DB</p>
- </td><td>
- <p>GT.M handles journal file switches for some complex permissions patterns.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7123">GTM-7123</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>DEVOPENFAIL for a deficient PIPE device specification</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7158">GTM-7158</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>DB</p>
- </td><td>
- <p>MUPIP TRIGGER, $ZTRIGGER() and ZTRIGGER now operate correctly on a read-only database in UNIX.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7176">GTM-7176</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>Improved error handling for ZBREAK and ZPRINT().</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7179">GTM-7179</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>Report global gets from MERGE in database counters displayed with ZSHOW "G".</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7185">GTM-7185</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>FOR evaluates a termination value specified with a subscripted local variable at loop initiation.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7188">GTM-7188</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>Error messages report the address of an event in hexadecimal in UNIX.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7196">GTM-7196</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>M-profiling corrections.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7206">GTM-7206</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>Resolved an interaction between ZGOTO 0:entryref and triggers in UNIX.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7210">GTM-7210</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>Better context for OpenVMS UNDEF error messages.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7214">GTM-7214</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>LOCK management avoids a possible problem.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7215">GTM-7215</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>Change to ZQUIT_ANYWAY behavior</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7224">GTM-7224</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>Utilities</p>
- </td><td>
- <p>The GT.M distribution kit now includes a README.txt file.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7228">GTM-7228</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>The LOCK (and ZALLOCATE and ZDEALLOCATE) commands manage LOCK resource names more efficiently in LOCK_SPACE.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7230">GTM-7230</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUPIP</p>
- </td><td>
- <p>Update Process and journal recover/rollback correctly handle NULL journal record type.</p>
- </td></tr><tr><td>
- <p><a class="link" href="#GTM-7234">GTM-7234</a></p>
- </td><td>
- <p>--</p>
- </td><td>
- <p>MUMPS</p>
- </td><td>
- <p>Improved parameter passing with nested JOB'd processes in UNIX.</p>
- </td></tr></tbody></table></div></div></div><div class="sect1" title="M-Database Access"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id1386025"></a>M-Database Access</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><a name="GTM-4337"></a>GT.M components use the $gtm_db_startup_max_wait environment variable to determine how long to wait for a resolution of any resource conflict wh [...]
-As in prior versions, if there is a character at the cursor when you enter <CTRL-D> in direct mode, GT.M erases it; if there are characters on the line but the character position is at the end of the line, GT.M ignores <CTRL-D>. Note: to delete the prior character on the line, use the key defined in your TERMINFO as key_backspace. [UNIX] (GTM-6449)</p></li><li class="listitem"><p><a name="GTM-6569"></a>There are a few very small and infrequent windows in GT.M code (expected t [...]
-processing was not handled: 150379874,jobintr2+4^jobintr,
-%%GTM-E-ERRWZINTR, Error while processing $ZINTERRUPT
--GTM-E-LABELMISSING, Label referenced but not defined:
-nonexistantrtn -- generated from 0x00007FEFD25B831A.</pre><p>Prior versions followed the basic error handling pattern of re-throwing the most recent unhandled error at each level as long as $ECODE is not equal to the empty string. [UNIX] (GTM-6711)</p></li><li class="listitem"><p><a name="GTM-6719"></a>GT.M now provides better management of timed events by deferring their processing during certain brief sections of code. Previously, GT.M could not keep timers alive while preventing vario [...]
-If DO or a $$ that does not specify an actuallist invokes a label with a formallist, the missing parameters are undefined in the called routine. As a result, a GT.M process no longer issues ACTLSTEXP and FMLLSTPRESENT errors, regardless of the arguments passed and parameters expected. WARNING: If DO or $$ specifies a routine but no label using an actuallist, then whether that routine's top label has a formallist or not, the actuallist applies to it directly, whereas before the actuallist [...]
-line 490 for expression (TPRESTART_STATE_NORMAL == tprestart_state)
-%GTM-F-GTMASSERT2, GT.M V5.5-000 Linux x86 - Assert failed /usr/library/V994/src/gds_rundown.c
-line 543 for expression (NULL != csa->wbuf_dqd)</pre><p>GTMASSERT and GTMASSERT2 indicate GT.M has detected a condition that seems to violate a design assumption and should be reported to your GT.M support channel. Prior versions did not provide the additional diagnostic information reported by GTMASSERT2. (GTM-7078)</p></li><li class="listitem"><p><a name="GTM-7176"></a>ZBREAK and ZPRINT() now issue errors when invoked with an indirect routine name that evaluates to the empty string [...]
- <p>Type</p>
- </th><th>
- <p>V5.4-002B</p>
- </th><th>
- <p>V5.5-000</p>
- </th></tr></thead><tbody><tr><td colspan="3">
- <p>Journal extract format (Plain)</p>
- </td></tr><tr><td>
- <p>Header Label</p>
- </td><td>
- <p>GDSJEX05</p>
- </td><td>
- <p>GDSJEX06</p>
- </td></tr><tr><td>
- <p>NULL</p>
- </td><td>
- <p>00\time\tnum\pid\clntpid\jsnum</p>
- </td><td>
- <p>00\time\tnum\pid\clntpid\jsnum\<span class="bold"><strong>strm_num\strm_seq</strong></span></p>
- </td></tr><tr><td>
- <p>KILL</p>
- </td><td>
- <p>04\time\tnum\pid\clntpid\token_seq\updnum\nodeflags\node</p>
- </td><td>
- <p>04\time\tnum\pid\clntpid\token_seq\<span class="bold"><strong>strm_num\strm_seq</strong></span>\updnum\<span class="emphasis"><em>nodeflags</em></span>\node</p>
- </td></tr><tr><td>
- <p>SET</p>
- </td><td>
- <p>05\time\tnum\pid\clntpid\token_seq\updnum\nodeflags\node=sarg</p>
- </td><td>
- <p>05\time\tnum\pid\clntpid\token_seq\<span class="bold"><strong>strm_num\strm_seq</strong></span>\updnum\<span class="emphasis"><em>nodeflags</em></span>\node=sarg</p>
- </td></tr><tr><td>
- <p>TSTART</p>
- </td><td>
- <p>08\time\tnum\pid\clntpid\token_seq</p>
- </td><td>
- <p>08\time\tnum\pid\clntpid\token_seq\<span class="bold"><strong>strm_num\strm_seq</strong></span></p>
- </td></tr><tr><td>
- <p>TCOM</p>
- </td><td>
- <p>09\time\tnum\pid\clntpid\token_seq\partners\tid</p>
- </td><td>
- <p>09\time\tnum\pid\clntpid\token_seq\<span class="bold"><strong>strm_num\strm_seq</strong></span>\partners\tid</p>
- </td></tr><tr><td>
- <p>ZKILL</p>
- </td><td>
- <p>10\time\tnum\pid\clntpid\token_seq\updnum\nodeflags\node</p>
- </td><td>
- <p>10\time\tnum\pid\clntpid\token_seq\<span class="bold"><strong>strm_num\strm_seq</strong></span>\updnum\<span class="emphasis"><em>nodeflags</em></span>\node</p>
- </td></tr><tr><td>
- <p>ZTWORM</p>
- </td><td>
- <p>11\time\tnum\pid\clntpid\token_seq\updnum\ztwormhole</p>
- </td><td>
- <p>11\time\tnum\pid\clntpid\token_seq\<span class="bold"><strong>strm_num\strm_seq</strong></span>\updnum\ztwormhole</p>
- </td></tr><tr><td>
- <p>ZTRIG</p>
- </td><td>
- <p>12\time\tnum\pid\clntpid\token_seq\updnum\nodeflags\node</p>
- </td><td>
- <p>12\time\tnum\pid\clntpid\token_seq\<span class="bold"><strong>strm_num\strm_seq</strong></span>\updnum\<span class="emphasis"><em>nodeflags</em></span>\node</p>
- </td></tr><tr><td colspan="3">
- <p>Journal extract format (Detail)</p>
- </td></tr><tr><td>
- <p>Header Label</p>
- </td><td>
- <p>GDSJDX05</p>
- </td><td>
- <p>GDSJDX06</p>
- </td></tr><tr><td>
- <p>KILL</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\updnum\nodeflags\node</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\<span class="bold"><strong>strm_num\strm_seq</strong></span>\updnum\<span class="emphasis"><em>nodeflags</em></span>\node</p>
- </td></tr><tr><td>
- <p>SET</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\updnum\nodeflags\node=sarg</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\<span class="bold"><strong>strm_num\strm_seq</strong></span>\updnum\<span class="emphasis"><em>nodeflags</em></span>\node=sarg</p>
- </td></tr><tr><td>
- <p>TKILL</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\updnum\nodeflags\node</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\<span class="bold"><strong>strm_num\strm_seq</strong></span>\updnum\<span class="emphasis"><em>nodeflags</em></span>\node</p>
- </td></tr><tr><td>
- <p>UKILL</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\updnum\nodeflags\node</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\<span class="bold"><strong>strm_num\strm_seq</strong></span>\updnum\<span class="emphasis"><em>nodeflags</em></span>\node</p>
- </td></tr><tr><td>
- <p>TSET</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\updnum\nodeflags\node=sarg</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\<span class="bold"><strong>strm_num\strm_seq</strong></span>\updnum\<span class="emphasis"><em>nodeflags</em></span>\node=sarg</p>
- </td></tr><tr><td>
- <p>USET</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\updnum\nodeflags\node=sarg</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\<span class="bold"><strong>strm_</strong></span><span class="bold"><strong>num\strm_seq</strong></span>\updnum\<span class="emphasis"><em>nodeflags</em></span>\node=sarg</p>
- </td></tr><tr><td>
- <p>FSET</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\updnum\nodeflags\node=sarg</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\<span class="bold"><strong>strm_num\strm_seq</strong></span>\updnum\<span class="emphasis"><em>nodeflags</em></span>\node=sarg</p>
- </td></tr><tr><td>
- <p>GSET</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\updnum\nodeflags\node=sarg</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\<span class="bold"><strong>strm_num\strm_seq</strong></span>\updnum\<span class="emphasis"><em>nodeflags</em></span>\node=sarg</p>
- </td></tr><tr><td>
- <p>FKILL</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\updnum\nodeflags\node</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\<span class="bold"><strong>strm_num\strm_seq</strong></span>\updnum\<span class="emphasis"><em>nodeflags</em></span>\node</p>
- </td></tr><tr><td>
- <p>GKILL</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\updnum\nodeflags\node</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\<span class="bold"><strong>strm_</strong></span><span class="bold"><strong>num\strm_seq</strong></span>\updnum\<span class="emphasis"><em>nodeflags</em></span>\node</p>
- </td></tr><tr><td>
- <p>TSTART</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\<span class="bold"><strong>strm_</strong></span><span class="bold"><strong>num\strm_seq</strong></span></p>
- </td></tr><tr><td>
- <p>TCOM</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\partners\tid</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\<span class="bold"><strong>strm_num\strm_seq</strong></span>\partners\tid</p>
- </td></tr><tr><td>
- <p>ZKILL</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\updnum\nodeflags\node</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\<span class="bold"><strong>strm_num\strm_seq</strong></span>\updnum\<span class="emphasis"><em>nodeflags</em></span>\node</p>
- </td></tr><tr><td>
- <p>TZKILL</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\updnum\nodeflags\node</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\<span class="bold"><strong>strm_num\strm_seq</strong></span>\updnum\<span class="emphasis"><em>nodeflags</em></span>\node</p>
- </td></tr><tr><td>
- <p>UZKILL</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\updnum\nodeflags\node</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\<span class="bold"><strong>strm_num\strm_seq\</strong></span>updnum\<span class="emphasis"><em>nodeflags</em></span>\node</p>
- </td></tr><tr><td>
- <p>EPOC</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\jsnum\blks_to_upgrd\free_blocks\total_blks</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\jsnum\blks_to_upgrd\free_blocks\total_blks\<span class="bold"><strong>fully_upgraded[\strm_num\strm_seq]...</strong></span></p>
- </td></tr><tr><td>
- <p>ZTWORM</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\updnum\ztwormhole</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\<span class="bold"><strong>strm_num\strm_seq</strong></span>\updnum\ztwormhole</p>
- </td></tr><tr><td>
- <p>NULL</p>
- </td><td>
- <p>time\tnum\pid\clntpid\jsnum</p>
- </td><td>
- <p>time\tnum\pid\clntpid\jsnum\<span class="bold"><strong>strm_num\strm_seq</strong></span></p>
- </td></tr><tr><td>
- <p>ZTRIG</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\updnum\nodeflags\node</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\<span class="bold"><strong>strm_num\strm_seq</strong></span>\updnum\<span class="emphasis"><em>nodeflags</em></span>\node</p>
- </td></tr><tr><td>
- <p>TZTWORM</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\updnum\ztwormhole</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\<span class="bold"><strong>strm_num\strm_seq</strong></span>\updnum\ztwormhole</p>
- </td></tr><tr><td>
- <p>UZTWORM</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\updnum\ztwormhole</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\<span class="bold"><strong>strm_</strong></span><span class="bold"><strong>num\strm_seq</strong></span>\updnum\ztwormhole</p>
- </td></tr><tr><td>
- <p>TZTRIG</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\updnum\nodeflags\node</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\<span class="bold"><strong>strm_</strong></span><span class="bold"><strong>num\strm_seq</strong></span>\updnum\<span class="emphasis"><em>nodeflags</em></span>\node</p>
- </td></tr><tr><td>
- <p>UZTRIG</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\updnum\nodeflags\node</p>
- </td><td>
- <p>time\tnum\chksum\pid\clntpid\token_seq\<span class="bold"><strong>strm_num\strm_seq</strong></span>\updnum\<span class="emphasis"><em>nodeflags</em></span>\node</p>
- </td></tr></tbody></table></div><p>Legend (additions in <span class="bold"><strong>bold</strong></span> and changes in <span class="emphasis"><em>italics</em></span>):</p><div class="informaltable"><table border="1"><colgroup><col><col></colgroup><tbody><tr><td>
- <p>strm_num</p>
- </td><td>
- <p>If replication is true and this update originated in a non-supplementary instance but was replicated to and updated a supplementary instance, this number is a non-zero value anywhere from 1 to 15 (both inclusive) indicating the non-supplementary stream number. In all other cases, this stream # value is 0. In case of an EPOCH record, anywhere from 0 to 16 such "strm_num" numbers might be displayed depending on how many sources of supplementary instance replication have [...]
- </td></tr><tr><td>
- <p>strm_seq</p>
- </td><td>
- <p>If replication is true and this update originated in a non-supplementary instance but was replicated to and updated a supplementary instance, this is the journal sequence number of the update on the originating non-supplementary instance. If replication is true and this update originated in a supplementary instance, this is the journal sequence number of the update on the originating supplementary instance. In all other cases, this stream sequence number is 0. Note tha [...]
- </td></tr><tr><td>
- <p><span class="emphasis"><em>nodeflags</em></span></p>
- </td><td>
- <p>Decimal number interpreted as a binary mask.. Currently only 5 bits are used.</p>
- <div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>00001 (1) => update journaled but NOT replicated (For example, update inside a trigger)</p></li><li class="listitem"><p>00010 (2) => update to a global that had at least one trigger defined, even if no trigger matched this update</p></li><li class="listitem"><p>00100 (4) => $ZTWORMHOLE holds the empty string ("") at the time of this update or was not referenced during this upda [...]
- <p>Combinations of the above bits would mean each of the individual bit characteristics. For example, 00011 => update within a trigger context, and to a global with at least one trigger defined. For example, 00011 => update inside a trigger and to a global with at least one trigger defined. Certain bit combinations are impossible. For example, 01001 since GT.M replicates any update that does not invoke triggers.</p>
- </td></tr><tr><td>
- <p>fully_upgraded</p>
- </td><td>
- <p>1 if the db was fully upgraded (indicated by a dse dump -file -all) at the time of writing the EPOCH</p>
- </td></tr></tbody></table></div></div><div class="sect2" title="Shared Resource Authorization Permissions"><div class="titlepage"><div><div><h3 class="title"><a name="shrd_res_exc"></a>Shared Resource Authorization Permissions</h3></div></div></div><p>GT.M uses several types of shared resources to implement concurrent access to databases. The first GT.M process to open a database file creates IPC resources (semaphores and shared memory) required for concurrent use by other [...]
- group memberships of the creating process' user</p></li></ul></div><p>The following table describes how these factors are combined to determine the permissions to use:</p><div class="informaltable"><table border="0" width="70%"><colgroup><col align="center"><col align="center"><col align="center"><col align="center"><col align="center"><col align="center"></colgroup><thead><tr><th align="center">Database File Permissions</th><th align="center">Opening process is owner of database file?< [...]
- <span class="emphasis"><em>Group of Resource</em></span>
- </th><th colspan="2" align="center">
- <span class="emphasis"><em>IPC Permissions</em></span>
- </th><th colspan="2" align="center">
- <span class="emphasis"><em>File Permissions</em></span>
- </th></tr></thead><tbody><tr><td align="center">-r*-r*-r*-</td><td align="center">-</td><td align="center">-</td><td align="center">Y</td><td align="center">-</td><td align="center">-</td></tr><tr><td colspan="2" align="center">
- <span class="emphasis"><em>Group of database file</em></span>
- </td><td colspan="2" align="center">
- <span class="emphasis"><em>-rw-rw-rw</em></span>
- </td><td colspan="2" align="center">
- <span class="emphasis"><em>-r*-r*-r*</em></span>
- </td></tr><tr bgcolor="#E3E3E3"><td align="center">-rw-rw-r*</td><td align="center">-</td><td align="center">-</td><td align="center">N</td><td align="center">-</td><td align="center">-</td></tr><tr bgcolor="#E3E3E3"><td colspan="2" align="center">
- <span class="emphasis"><em>Current group of process</em></span>
- </td><td colspan="2" align="center">
- <span class="emphasis"><em>-rw-rw-rw</em></span>
- </td><td colspan="2" align="center">
- <span class="emphasis"><em>-rw-rw-rw</em></span>
- </td></tr><tr><td align="center">-rw-rw-rw</td><td align="center">-</td><td align="center">-</td><td align="center">N</td><td align="center">-</td><td align="center">-</td></tr><tr><td colspan="2" align="center">
- <span class="emphasis"><em>Current group of process</em></span>
- </td><td colspan="2" align="center">
- <span class="emphasis"><em>-rw-rw-rw</em></span>
- </td><td colspan="2" align="center">
- <span class="emphasis"><em>-rw-rw-rw</em></span>
- </td></tr><tr bgcolor="#E3E3E3"><td align="center">-rw-rw-rw</td><td align="center">Y</td><td align="center">Y</td><td align="center">-</td><td align="center">-</td><td align="center">-</td></tr><tr bgcolor="#E3E3E3"><td colspan="2" align="center">
- <span class="emphasis"><em>Group of database file</em></span>
- </td><td colspan="2" align="center">
- <span class="emphasis"><em>-rw-rw-rw</em></span>
- </td><td colspan="2" align="center">
- <span class="emphasis"><em>-r*-r*----</em></span>
- </td></tr><tr><td align="center">-r*-r*----</td><td align="center">Y</td><td align="center">N</td><td align="center">-</td><td align="center">-</td><td align="center">N</td></tr><tr><td colspan="2" align="center">
- <span class="emphasis"><em>Current group of process</em></span>
- </td><td colspan="2" align="center">
- <span class="emphasis"><em>-rw-rw-rw-</em></span>
- </td><td colspan="2" align="center">
- <span class="emphasis"><em>-rw-rw-rw-</em></span>
- </td></tr><tr bgcolor="#E3E3E3"><td align="center">-r*-r*----</td><td align="center">Y</td><td align="center">N</td><td align="center">-</td><td align="center">-</td><td align="center">Y</td></tr><tr bgcolor="#E3E3E3"><td colspan="2" align="center">
- <span class="emphasis"><em>Group to which GT.M is restricted</em></span>
- </td><td colspan="2" align="center">
- <span class="emphasis"><em>-rw-rw----</em></span>
- </td><td colspan="2" align="center">
- <span class="emphasis"><em>-rw-rw----</em></span>
- </td></tr><tr><td align="center">-r*-r*----</td><td align="center">-</td><td align="center">Y</td><td align="center">-</td><td align="center">Y</td><td align="center">-</td></tr><tr><td colspan="2" align="center">
- <span class="emphasis"><em>Group of database file</em></span>
- </td><td colspan="2" align="center">
- <span class="emphasis"><em>-rw-rw----</em></span>
- </td><td colspan="2" align="center">
- <span class="emphasis"><em>-r*-r*----</em></span>
- </td></tr><tr bgcolor="#E3E3E3"><td align="center">-r*-r*----</td><td align="center">-</td><td align="center">N</td><td align="center">-</td><td align="center">Y</td><td align="center">N</td></tr><tr bgcolor="#E3E3E3"><td colspan="2" align="center">
- <span class="emphasis"><em>Group of database file</em></span>
- </td><td colspan="2" align="center">
- <span class="emphasis"><em>-rw-rw-rw-</em></span>
- </td><td colspan="2" align="center">
- <span class="emphasis"><em>-rw-rw-rw-</em></span>
- </td></tr><tr><td align="center">-r*-r*----</td><td align="center">-</td><td align="center">N</td><td align="center">-</td><td align="center">Y</td><td align="center">Y</td></tr><tr><td colspan="2" align="center">
- <span class="emphasis"><em>Group to which GT.M is restricted</em></span>
- </td><td colspan="2" align="center">
- <span class="emphasis"><em>-rw-rw----</em></span>
- </td><td colspan="2" align="center">
- <span class="emphasis"><em>-rw-rw----</em></span>
- </td></tr><tr bgcolor="#E3E3E3"><td align="center">----r*----</td><td align="center">-</td><td align="center">N</td><td align="center">-</td><td align="center">Y</td><td align="center">-</td></tr><tr bgcolor="#E3E3E3"><td colspan="2" align="center">
- <span class="emphasis"><em>Group of database file</em></span>
- </td><td colspan="2" align="center">
- <span class="emphasis"><em>-rw-rw----</em></span>
- </td><td colspan="2" align="center">
- <span class="emphasis"><em>----r*----</em></span>
- </td></tr><tr><td align="center">-r*-------</td><td align="center">Y</td><td align="center">-</td><td align="center">-</td><td align="center">-</td><td align="center">-</td></tr><tr><td colspan="2" align="center">
- <span class="emphasis"><em>Current group of process</em></span>
- </td><td colspan="2" align="center">
- <span class="emphasis"><em>-rw-------</em></span>
- </td><td colspan="2" align="center">
- <span class="emphasis"><em>-rw-------</em></span>
- </td></tr></tbody></table></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>The resulting group ownership and permissions are found by matching the database file permissions, then determining which question columns produce the correct "Y" or "N" answer; "-" answers are "don't care".</p></li><li class="listitem"><p>An asterisk ("*") in the Database File Permissions matches writable or not writable. An asterisk in the Resulting File [...]
- <p>Area Impacted by MUPIP JOURNAL -ONLINE -ROLLBACK</p>
- </th><th>
- <p>Effect of MUPIP JOURNAL -ONLINE -ROLLBACK</p>
- </th></tr></thead><tbody><tr><td>
- <p>$ZONLNRLBK</p>
- </td><td>
- <p>Incremented by any online rollback that takes the database back to a prior state</p>
- </td></tr><tr><td>
- <p>M run-time actions that do not interact with the target database</p>
- </td><td>
- <p>None</p>
- </td></tr><tr><td>
- <p>M run-time database interactions</p>
- </td><td>
- <p>Suspended during the online rollback. Restart if the online rollback does not take the database back to a prior state or if within an explicit TP transaction. Otherwise, DBROLLEDBACK error if the interaction is a non-TP mini-transaction. Note that triggers act like an extension of their originating event: they get the same treatment as the trigger event would get - if they are within an implicit transaction triggered outside a TP transaction, the process gets a DBROLLE [...]
- </td></tr><tr><td>
- <p>M run-time larger KILLs</p>
- </td><td>
- <p>Because of the way GT.M manages multi-node KILLs, it possible for online rollback to remove bit-map cleanup while leaving the original KILL. This creates incorrectly marked busy errors, which represent unused, but protected space - they are benign, but should be cleaned up in a timely manner.</p>
- </td></tr><tr><td>
- <p>GT.CM GNP Server</p>
- </td><td>
- <p>Like the M run-time, except it sends any DBROLLEDBACK error to the client processes.</p>
- </td></tr><tr><td>
- <p>Starting most GT.M actions from the shell, including operator Utilities - see below for exceptions</p>
- </td><td>
- <p>Deferred until the ONLINE ROLLBACK is complete. The environment variable gtm_db_startup_max_wait determines the deferred time. For more information, refer to <a class="link" href="#GTM-4337">GTM-4337</a>. </p>
- </td></tr><tr><td>
- <p>MUMPS</p>
- </td><td>
- <p>None unless, and until, the process tries to interact with the target database</p>
- </td></tr><tr><td><p>Source Server</p></td><td><p>If the online rollback takes the database back to a prior state, disconnect from the receiving instance and restart the connection with a message that a rollback occurred.</p> </td></tr><tr><td><p>Update Process</p></td><td><p>If the online rollback takes the database back to a prior state, suspend processing and notify the Receiver Server that there was a rollback on this receiving instance.</p></td></tr><tr><td><p>Receiver [...]
- <p>LKE</p>
- </td><td>
- <p>None if already running before online rollback starts</p>
- </td></tr><tr><td>
- <p>Running GT.M utility commands that are mutually exclusive with MUPIP JOURNAL -ONLINE -ROLLBACK and require standalone access. For example:</p>
- <div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>MUPIP UPGRADE</p></li><li class="listitem"><p>MUPIP DOWNGRADE</p></li><li class="listitem"><p>MUPIP JOURNAL -ROLLBACK or MUPIP JOURNAL -RECOVER</p></li><li class="listitem"><p>MUPIP ENDIANCVT</p></li><li class="listitem"><p>MUPIP RUNDOWN</p></li><li class="listitem"><p>MUPIP RESTORE</p></li><li class="listitem"><p>MUPIP INTEG -FILE </p></li></ul></div>
- </td><td>
- <p>MUPIP JOURNAL -ONLINE -ROLLBACK does not run when these commands are running. Analogously, these commands cannot run during a MUPIP JOURNAL -ONLINE -ROLLACK. </p>
- </td></tr><tr><td>
- <p>Multi-action state dependent utility commands. For example: </p>
- <div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>MUPIP INTEG -REGION [-ONLINE|-NOONLINE]</p></li><li class="listitem"><p>MUPIP BACKUP</p></li><li class="listitem"><p>MUPIP LOAD</p></li></ul></div>
- </td><td>
- <p>Produces a DBROLLEDBACK error.</p>
- <p>Subsequent MUPIP BACKUP -BYTESTREAM -SINCE=<event> commands may start at transaction 1 if the rollback takes the database state back prior to the event (DATABASE, BYTESTREAM or RECORD).</p>
- </td></tr><tr><td><p>DSE</p></td><td><p>DSE cannot start while online rollback is running. If it has already started, its commands work as described in other rows of this table.</p> </td></tr><tr><td>
- <p>Utility commands that do not interact with database files. For example:</p>
- <div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>DSE CLOSE</p></li><li class="listitem"><p>DSE EVALUATE</p></li><li class="listitem"><p>DSE EXIT</p></li><li class="listitem"><p>DSE HELP</p></li><li class="listitem"><p>DSE OPEN</p></li><li class="listitem"><p>DSE PAGE</p></li><li class="listitem"><p>DSE QUIT</p></li><li class="listitem"><p>DSE SPAWN</p></li><li class="listitem"><p>DSE VERSION </p></li><li class="listitem"><p>GDE</p></l [...]
- </td><td>
- <p>DSE and LKE cannot start while online rollback is active, but if active they can continue to operate; MUPIP commands always start from the shell so each command may have different behavior.</p>
- <p>MUPIP CREATE does create database files but only if they do not already exist and if they do not exist, they can be rolled back.</p>
- <p>MUPIP INTRPT does not interact with a database, but the target process may and that could prevent it from recognizing the interrupt in a timely fashion.</p>
- </td></tr><tr><td>
- <p>Utility commands that update a database and interlock with online rollback. For example:</p>
- <div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>DSE ADD</p></li><li class="listitem"><p>DSE ALL -WCINIT</p></li><li class="listitem"><p>DSE ALL -BUFFER_FLUSH</p></li><li class="listitem"><p>DSE ALL -SEIZE</p></li><li class="listitem"><p>DSE ALL -RELEASE</p></li><li class="listitem"><p>DSE ALL -FREEZE -OVERRIDE</p></li><li class="listitem"><p>DSE BUFFER_FLUSH</p></li><li class="listitem"><p>DSE CACHE except -SHOW</p></li><li class="li [...]
- </td><td><p>These commands wait for online rollback to complete.</p></td></tr><tr><td>
- <p>Utility commands that only read database files and display current state information. For example: �</p>
- <div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>DSE ALL -DUMP </p></li><li class="listitem"><p>DSE ALL -NOFREEZE </p></li><li class="listitem"><p>DSE CACHE -SHOW </p></li><li class="listitem"><p>DSE CRITICAL -ALL </p></li><li class="listitem"><p>DSE CRITICAL -CRASH </p></li><li class="listitem"><p>DSE DUMP -BLOCK </p></li><li class="listitem"><p>DSE DUMP -RECORD </p></li><li class="listitem"><p>DSE DUMP -FILE </p></li><li class="list [...]
- </td><td><p>These commands show the state as of the time they are issued and if issued while there are any concurrent updates, including online rollback may show a transient and out-of-date state. </p></td></tr><tr><td>
- <p>Utility commands that interact with a database and are not blocked by online rollback: </p>
- <div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>DSE ALL -REFERENCE</p></li><li class="listitem"><p>DSE CRITICAL -INIT </p></li><li class="listitem"><p>DSE CRITICAL -REMOVE </p></li><li class="listitem"><p>DSE CHANGE -FILEHEADER -NOCRIT</p></li></ul></div>
- </td><td><p>These commands may disrupt the -online rollback and may cause database damage - they are available only for very unusual situations and should only be used under instructions from your GT.M support channel.</p></td></tr></tbody></table></div></div></div></div></body></html>
--
Alioth's /git/debian-med/git-commit-notice on /srv/git.debian.org/git/debian-med/fis-gtm.git
More information about the debian-med-commit
mailing list