[med-svn] [fis-gtm] 01/01: Remove debian/upstream-files containing versioned changelogs as well as the extra licensing statement in favour of a simple link to the online pages in d/README.Debian
Andreas Tille
tille at debian.org
Mon Nov 25 07:53:17 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 cd21d90ddc3d850b82a5bfa4d409134b340d6a4b
Author: Andreas Tille <tille at debian.org>
Date: Mon Nov 25 08:56:45 2013 +0100
Remove debian/upstream-files containing versioned changelogs as well as the extra licensing statement in favour of a simple link to the online pages in d/README.Debian
---
debian/README.Debian | 10 +
debian/copyright | 459 ---------------------
.../upstream-files/GTM_V6.0-001_Release_Notes.html | 331 ---------------
3 files changed, 10 insertions(+), 790 deletions(-)
diff --git a/debian/README.Debian b/debian/README.Debian
new file mode 100644
index 0000000..b8df879
--- /dev/null
+++ b/debian/README.Debian
@@ -0,0 +1,10 @@
+FIS GT.M for Debian
+===================
+
+Please note the Release Notes & Supplementary Information for the latest
+versions here:
+
+ http://tinco.pair.com/bhaskar/gtm/doc/articles/index.html
+
+ -- Andreas Tille <tille at debian.org> Sun, 24 Nov 2013 09:26:25 +0100
+
diff --git a/debian/copyright b/debian/copyright
index 3b674d8..3c8f04d 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -18,10 +18,6 @@ Copyright: 2012 Luis Ibanez <luis.ibanez at kitware.com>
2013 Amul Shah <Amul.Shah at fisglobal.com>
License: AGPL-3.0
-Files: debian/upstream-files/*
-Copyright: 2013 Fidelity Information Services, Inc. All Rights Reserved
-License: GFDL
-
License: AGPL-3.0
GNU AFFERO GENERAL PUBLIC LICENSE
Version 3, 19 November 2007
@@ -684,458 +680,3 @@ License: AGPL-3.0
if any, to sign a "copyright disclaimer" for the program, if necessary.
For more information on this, and how to apply and follow the GNU AGPL, see
-License: GFDL
- Permission is granted to copy, distribute and/or modify this document under the
- terms of the GNU Free Documentation License, Version 1.3 or any later version
- published by the Free Software Foundation; with no Invariant Sections, no
- Front-Cover Texts and no Back-Cover Texts.
- .
- GNU Free Documentation License
- Version 1.3, 3 November 2008
- .
- Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
- <http://fsf.org/>
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
- .
- 0. PREAMBLE
- .
- The purpose of this License is to make a manual, textbook, or other
- functional and useful document "free" in the sense of freedom: to
- assure everyone the effective freedom to copy and redistribute it,
- with or without modifying it, either commercially or noncommercially.
- Secondarily, this License preserves for the author and publisher a way
- to get credit for their work, while not being considered responsible
- for modifications made by others.
- .
- This License is a kind of "copyleft", which means that derivative
- works of the document must themselves be free in the same sense. It
- complements the GNU General Public License, which is a copyleft
- license designed for free software.
- .
- We have designed this License in order to use it for manuals for free
- software, because free software needs free documentation: a free
- program should come with manuals providing the same freedoms that the
- software does. But this License is not limited to software manuals;
- it can be used for any textual work, regardless of subject matter or
- whether it is published as a printed book. We recommend this License
- principally for works whose purpose is instruction or reference.
- .
- .
- 1. APPLICABILITY AND DEFINITIONS
- .
- This License applies to any manual or other work, in any medium, that
- contains a notice placed by the copyright holder saying it can be
- distributed under the terms of this License. Such a notice grants a
- world-wide, royalty-free license, unlimited in duration, to use that
- work under the conditions stated herein. The "Document", below,
- refers to any such manual or work. Any member of the public is a
- licensee, and is addressed as "you". You accept the license if you
- copy, modify or distribute the work in a way requiring permission
- under copyright law.
- .
- A "Modified Version" of the Document means any work containing the
- Document or a portion of it, either copied verbatim, or with
- modifications and/or translated into another language.
- .
- A "Secondary Section" is a named appendix or a front-matter section of
- the Document that deals exclusively with the relationship of the
- publishers or authors of the Document to the Document's overall
- subject (or to related matters) and contains nothing that could fall
- directly within that overall subject. (Thus, if the Document is in
- part a textbook of mathematics, a Secondary Section may not explain
- any mathematics.) The relationship could be a matter of historical
- connection with the subject or with related matters, or of legal,
- commercial, philosophical, ethical or political position regarding
- them.
- .
- The "Invariant Sections" are certain Secondary Sections whose titles
- are designated, as being those of Invariant Sections, in the notice
- that says that the Document is released under this License. If a
- section does not fit the above definition of Secondary then it is not
- allowed to be designated as Invariant. The Document may contain zero
- Invariant Sections. If the Document does not identify any Invariant
- Sections then there are none.
- .
- The "Cover Texts" are certain short passages of text that are listed,
- as Front-Cover Texts or Back-Cover Texts, in the notice that says that
- the Document is released under this License. A Front-Cover Text may
- be at most 5 words, and a Back-Cover Text may be at most 25 words.
- .
- A "Transparent" copy of the Document means a machine-readable copy,
- represented in a format whose specification is available to the
- general public, that is suitable for revising the document
- straightforwardly with generic text editors or (for images composed of
- pixels) generic paint programs or (for drawings) some widely available
- drawing editor, and that is suitable for input to text formatters or
- for automatic translation to a variety of formats suitable for input
- to text formatters. A copy made in an otherwise Transparent file
- format whose markup, or absence of markup, has been arranged to thwart
- or discourage subsequent modification by readers is not Transparent.
- An image format is not Transparent if used for any substantial amount
- of text. A copy that is not "Transparent" is called "Opaque".
- .
- Examples of suitable formats for Transparent copies include plain
- ASCII without markup, Texinfo input format, LaTeX input format, SGML
- or XML using a publicly available DTD, and standard-conforming simple
- HTML, PostScript or PDF designed for human modification. Examples of
- transparent image formats include PNG, XCF and JPG. Opaque formats
- include proprietary formats that can be read and edited only by
- proprietary word processors, SGML or XML for which the DTD and/or
- processing tools are not generally available, and the
- machine-generated HTML, PostScript or PDF produced by some word
- processors for output purposes only.
- .
- The "Title Page" means, for a printed book, the title page itself,
- plus such following pages as are needed to hold, legibly, the material
- this License requires to appear in the title page. For works in
- formats which do not have any title page as such, "Title Page" means
- the text near the most prominent appearance of the work's title,
- preceding the beginning of the body of the text.
- .
- The "publisher" means any person or entity that distributes copies of
- the Document to the public.
- .
- A section "Entitled XYZ" means a named subunit of the Document whose
- title either is precisely XYZ or contains XYZ in parentheses following
- text that translates XYZ in another language. (Here XYZ stands for a
- specific section name mentioned below, such as "Acknowledgements",
- "Dedications", "Endorsements", or "History".) To "Preserve the Title"
- of such a section when you modify the Document means that it remains a
- section "Entitled XYZ" according to this definition.
- .
- The Document may include Warranty Disclaimers next to the notice which
- states that this License applies to the Document. These Warranty
- Disclaimers are considered to be included by reference in this
- License, but only as regards disclaiming warranties: any other
- implication that these Warranty Disclaimers may have is void and has
- no effect on the meaning of this License.
- .
- 2. VERBATIM COPYING
- .
- You may copy and distribute the Document in any medium, either
- commercially or noncommercially, provided that this License, the
- copyright notices, and the license notice saying this License applies
- to the Document are reproduced in all copies, and that you add no
- other conditions whatsoever to those of this License. You may not use
- technical measures to obstruct or control the reading or further
- copying of the copies you make or distribute. However, you may accept
- compensation in exchange for copies. If you distribute a large enough
- number of copies you must also follow the conditions in section 3.
- .
- You may also lend copies, under the same conditions stated above, and
- you may publicly display copies.
- .
- .
- 3. COPYING IN QUANTITY
- .
- If you publish printed copies (or copies in media that commonly have
- printed covers) of the Document, numbering more than 100, and the
- Document's license notice requires Cover Texts, you must enclose the
- copies in covers that carry, clearly and legibly, all these Cover
- Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
- the back cover. Both covers must also clearly and legibly identify
- you as the publisher of these copies. The front cover must present
- the full title with all words of the title equally prominent and
- visible. You may add other material on the covers in addition.
- Copying with changes limited to the covers, as long as they preserve
- the title of the Document and satisfy these conditions, can be treated
- as verbatim copying in other respects.
- .
- If the required texts for either cover are too voluminous to fit
- legibly, you should put the first ones listed (as many as fit
- reasonably) on the actual cover, and continue the rest onto adjacent
- pages.
- .
- If you publish or distribute Opaque copies of the Document numbering
- more than 100, you must either include a machine-readable Transparent
- copy along with each Opaque copy, or state in or with each Opaque copy
- a computer-network location from which the general network-using
- public has access to download using public-standard network protocols
- a complete Transparent copy of the Document, free of added material.
- If you use the latter option, you must take reasonably prudent steps,
- when you begin distribution of Opaque copies in quantity, to ensure
- that this Transparent copy will remain thus accessible at the stated
- location until at least one year after the last time you distribute an
- Opaque copy (directly or through your agents or retailers) of that
- edition to the public.
- .
- It is requested, but not required, that you contact the authors of the
- Document well before redistributing any large number of copies, to
- give them a chance to provide you with an updated version of the
- Document.
- .
- .
- 4. MODIFICATIONS
- .
- You may copy and distribute a Modified Version of the Document under
- the conditions of sections 2 and 3 above, provided that you release
- the Modified Version under precisely this License, with the Modified
- Version filling the role of the Document, thus licensing distribution
- and modification of the Modified Version to whoever possesses a copy
- of it. In addition, you must do these things in the Modified Version:
- .
- A. Use in the Title Page (and on the covers, if any) a title distinct
- from that of the Document, and from those of previous versions
- (which should, if there were any, be listed in the History section
- of the Document). You may use the same title as a previous version
- if the original publisher of that version gives permission.
- B. List on the Title Page, as authors, one or more persons or entities
- responsible for authorship of the modifications in the Modified
- Version, together with at least five of the principal authors of the
- Document (all of its principal authors, if it has fewer than five),
- unless they release you from this requirement.
- C. State on the Title page the name of the publisher of the
- Modified Version, as the publisher.
- D. Preserve all the copyright notices of the Document.
- E. Add an appropriate copyright notice for your modifications
- adjacent to the other copyright notices.
- F. Include, immediately after the copyright notices, a license notice
- giving the public permission to use the Modified Version under the
- terms of this License, in the form shown in the Addendum below.
- G. Preserve in that license notice the full lists of Invariant Sections
- and required Cover Texts given in the Document's license notice.
- H. Include an unaltered copy of this License.
- I. Preserve the section Entitled "History", Preserve its Title, and add
- to it an item stating at least the title, year, new authors, and
- publisher of the Modified Version as given on the Title Page. If
- there is no section Entitled "History" in the Document, create one
- stating the title, year, authors, and publisher of the Document as
- given on its Title Page, then add an item describing the Modified
- Version as stated in the previous sentence.
- J. Preserve the network location, if any, given in the Document for
- public access to a Transparent copy of the Document, and likewise
- the network locations given in the Document for previous versions
- it was based on. These may be placed in the "History" section.
- You may omit a network location for a work that was published at
- least four years before the Document itself, or if the original
- publisher of the version it refers to gives permission.
- K. For any section Entitled "Acknowledgements" or "Dedications",
- Preserve the Title of the section, and preserve in the section all
- the substance and tone of each of the contributor acknowledgements
- and/or dedications given therein.
- L. Preserve all the Invariant Sections of the Document,
- unaltered in their text and in their titles. Section numbers
- or the equivalent are not considered part of the section titles.
- M. Delete any section Entitled "Endorsements". Such a section
- may not be included in the Modified Version.
- N. Do not retitle any existing section to be Entitled "Endorsements"
- or to conflict in title with any Invariant Section.
- O. Preserve any Warranty Disclaimers.
- .
- If the Modified Version includes new front-matter sections or
- appendices that qualify as Secondary Sections and contain no material
- copied from the Document, you may at your option designate some or all
- of these sections as invariant. To do this, add their titles to the
- list of Invariant Sections in the Modified Version's license notice.
- These titles must be distinct from any other section titles.
- .
- You may add a section Entitled "Endorsements", provided it contains
- nothing but endorsements of your Modified Version by various
- parties--for example, statements of peer review or that the text has
- been approved by an organization as the authoritative definition of a
- standard.
- .
- You may add a passage of up to five words as a Front-Cover Text, and a
- passage of up to 25 words as a Back-Cover Text, to the end of the list
- of Cover Texts in the Modified Version. Only one passage of
- Front-Cover Text and one of Back-Cover Text may be added by (or
- through arrangements made by) any one entity. If the Document already
- includes a cover text for the same cover, previously added by you or
- by arrangement made by the same entity you are acting on behalf of,
- you may not add another; but you may replace the old one, on explicit
- permission from the previous publisher that added the old one.
- .
- The author(s) and publisher(s) of the Document do not by this License
- give permission to use their names for publicity for or to assert or
- imply endorsement of any Modified Version.
- .
- .
- 5. COMBINING DOCUMENTS
- .
- You may combine the Document with other documents released under this
- License, under the terms defined in section 4 above for modified
- versions, provided that you include in the combination all of the
- Invariant Sections of all of the original documents, unmodified, and
- list them all as Invariant Sections of your combined work in its
- license notice, and that you preserve all their Warranty Disclaimers.
- .
- The combined work need only contain one copy of this License, and
- multiple identical Invariant Sections may be replaced with a single
- copy. If there are multiple Invariant Sections with the same name but
- different contents, make the title of each such section unique by
- adding at the end of it, in parentheses, the name of the original
- author or publisher of that section if known, or else a unique number.
- Make the same adjustment to the section titles in the list of
- Invariant Sections in the license notice of the combined work.
- .
- In the combination, you must combine any sections Entitled "History"
- in the various original documents, forming one section Entitled
- "History"; likewise combine any sections Entitled "Acknowledgements",
- and any sections Entitled "Dedications". You must delete all sections
- Entitled "Endorsements".
- .
- .
- 6. COLLECTIONS OF DOCUMENTS
- .
- You may make a collection consisting of the Document and other
- documents released under this License, and replace the individual
- copies of this License in the various documents with a single copy
- that is included in the collection, provided that you follow the rules
- of this License for verbatim copying of each of the documents in all
- other respects.
- .
- You may extract a single document from such a collection, and
- distribute it individually under this License, provided you insert a
- copy of this License into the extracted document, and follow this
- License in all other respects regarding verbatim copying of that
- document.
- .
- .
- 7. AGGREGATION WITH INDEPENDENT WORKS
- .
- A compilation of the Document or its derivatives with other separate
- and independent documents or works, in or on a volume of a storage or
- distribution medium, is called an "aggregate" if the copyright
- resulting from the compilation is not used to limit the legal rights
- of the compilation's users beyond what the individual works permit.
- When the Document is included in an aggregate, this License does not
- apply to the other works in the aggregate which are not themselves
- derivative works of the Document.
- .
- If the Cover Text requirement of section 3 is applicable to these
- copies of the Document, then if the Document is less than one half of
- the entire aggregate, the Document's Cover Texts may be placed on
- covers that bracket the Document within the aggregate, or the
- electronic equivalent of covers if the Document is in electronic form.
- Otherwise they must appear on printed covers that bracket the whole
- aggregate.
- .
- .
- 8. TRANSLATION
- .
- Translation is considered a kind of modification, so you may
- distribute translations of the Document under the terms of section 4.
- Replacing Invariant Sections with translations requires special
- permission from their copyright holders, but you may include
- translations of some or all Invariant Sections in addition to the
- original versions of these Invariant Sections. You may include a
- translation of this License, and all the license notices in the
- Document, and any Warranty Disclaimers, provided that you also include
- the original English version of this License and the original versions
- of those notices and disclaimers. In case of a disagreement between
- the translation and the original version of this License or a notice
- or disclaimer, the original version will prevail.
- .
- If a section in the Document is Entitled "Acknowledgements",
- "Dedications", or "History", the requirement (section 4) to Preserve
- its Title (section 1) will typically require changing the actual
- title.
- .
- .
- 9. TERMINATION
- .
- You may not copy, modify, sublicense, or distribute the Document
- except as expressly provided under this License. Any attempt
- otherwise to copy, modify, sublicense, or distribute it is void, and
- will automatically terminate your rights under this License.
- .
- However, if you cease all violation of this License, then your license
- from a particular copyright holder is reinstated (a) provisionally,
- unless and until the copyright holder explicitly and finally
- terminates your license, and (b) permanently, if the copyright holder
- fails to notify you of the violation by some reasonable means prior to
- 60 days after the cessation.
- .
- Moreover, your license from a particular copyright holder is
- reinstated permanently if the copyright holder notifies you of the
- violation by some reasonable means, this is the first time you have
- received notice of violation of this License (for any work) from that
- copyright holder, and you cure the violation prior to 30 days after
- your receipt of the notice.
- .
- Termination of your rights under this section does not terminate the
- licenses of parties who have received copies or rights from you under
- this License. If your rights have been terminated and not permanently
- reinstated, receipt of a copy of some or all of the same material does
- not give you any rights to use it.
- .
- .
- 10. FUTURE REVISIONS OF THIS LICENSE
- .
- The Free Software Foundation may publish new, revised versions of the
- GNU Free Documentation License from time to time. Such new versions
- will be similar in spirit to the present version, but may differ in
- detail to address new problems or concerns. See
- http://www.gnu.org/copyleft/.
- .
- Each version of the License is given a distinguishing version number.
- If the Document specifies that a particular numbered version of this
- License "or any later version" applies to it, you have the option of
- following the terms and conditions either of that specified version or
- of any later version that has been published (not as a draft) by the
- Free Software Foundation. If the Document does not specify a version
- number of this License, you may choose any version ever published (not
- as a draft) by the Free Software Foundation. If the Document
- specifies that a proxy can decide which future versions of this
- License can be used, that proxy's public statement of acceptance of a
- version permanently authorizes you to choose that version for the
- Document.
- .
- 11. RELICENSING
- .
- "Massive Multiauthor Collaboration Site" (or "MMC Site") means any
- World Wide Web server that publishes copyrightable works and also
- provides prominent facilities for anybody to edit those works. A
- public wiki that anybody can edit is an example of such a server. A
- "Massive Multiauthor Collaboration" (or "MMC") contained in the site
- means any set of copyrightable works thus published on the MMC site.
- .
- "CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0
- license published by Creative Commons Corporation, a not-for-profit
- corporation with a principal place of business in San Francisco,
- California, as well as future copyleft versions of that license
- published by that same organization.
- .
- "Incorporate" means to publish or republish a Document, in whole or in
- part, as part of another Document.
- .
- An MMC is "eligible for relicensing" if it is licensed under this
- License, and if all works that were first published under this License
- somewhere other than this MMC, and subsequently incorporated in whole or
- in part into the MMC, (1) had no cover texts or invariant sections, and
- (2) were thus incorporated prior to November 1, 2008.
- .
- The operator of an MMC Site may republish an MMC contained in the site
- under CC-BY-SA on the same site at any time before August 1, 2009,
- provided the MMC is eligible for relicensing.
- .
- .
- ADDENDUM: How to use this License for your documents
- .
- To use this License in a document you have written, include a copy of
- the License in the document and put the following copyright and
- license notices just after the title page:
- .
- Copyright (c) YEAR YOUR NAME.
- Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.3
- or any later version published by the Free Software Foundation;
- with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
- A copy of the license is included in the section entitled "GNU
- Free Documentation License".
- .
- If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
- replace the "with...Texts." line with this:
- .
- with the Invariant Sections being LIST THEIR TITLES, with the
- Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
- .
- If you have Invariant Sections without Cover Texts, or some other
- combination of the three, merge those two alternatives to suit the
- situation.
- .
- If your document contains nontrivial examples of program code, we
- recommend releasing these examples in parallel under your choice of
- free software license, such as the GNU General Public License,
- to permit their use in free software.
diff --git a/debian/upstream-files/GTM_V6.0-001_Release_Notes.html b/debian/upstream-files/GTM_V6.0-001_Release_Notes.html
deleted file mode 100644
index a7a163d..0000000
--- a/debian/upstream-files/GTM_V6.0-001_Release_Notes.html
+++ /dev/null
@@ -1,331 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
-<html><head>
-<title>404 Not Found</title>
-</head><body>
-<h1>Not Found</h1>
-<p>The requested URL /bhaskar/gtm/doc/articles/GTM_V6.0wget was not found on this server.</p>
-</body></html>
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>GT.M V6.0-001 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="_blank">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="#GTMrel_overview">V6.0-001</a></span></dt><dd><dl><dt><span class="sect2"><a href="#overview"> Overview </a></span></dt><dt><span class="sect2"><a href="#conventions">Conventions</a></span></dt><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="se [...]
- Recompile </a></span></dt><dt><span class="sect2"><a href="#rebuild">Rebuild Shared Libraries or Images</a></span></dt><dt><span class="sect2"><a href="#addn_instr">Additional Installation Instructions</a></span></dt><dt><span class="sect2"><a href="#upgrade"> Upgrading to GT.M V6.0-000</a></span></dt><dt><span class="sect2"><a href="#mng_mode">Managing M mode and UTF-8 mode</a></span></dt><dt><span class="sect2"><a href="#setterm">Setting the environment variable TERM</a></span></dt><d [...]
- <p></p></th><th>
-
-<p>UNIX</p>
- </th><th>
-
-<p>OpenVMS</p>
- </th></tr></thead><tbody><tr><td>
-
-<p><span class="bold"><strong>Syntax</strong></span></p>
- </td><td>
-
-<p>lower case</p>
- </td><td>
-
-<p>Both lower case and upper case</p>
- </td></tr><tr><td>
-
-<p><span class="bold"><strong>Flag/Qualifiers</strong></span></p>
- </td><td>
-
-<p>-</p>
- </td><td>
-
-<p>/</p>
- </td></tr><tr><td>
-
-<p><span class="bold"><strong>Program Names or Functions</strong></span></p>
- </td><td colspan="2">
-<p>upper case. For example, MUPIP BACKUP</p>
- </td></tr><tr><td>
-
-<p><span class="bold"><strong>Examples</strong></span></p>
- </td><td colspan="2">
-<p>lower case. For example: <br> mupip backup -database ACN,HIST /backup</p>
- </td></tr><tr><td>
-
-<p><span class="bold"><strong>Reference Number</strong></span></p>
- </td><td colspan="2">
-<p> A reference number is used to track software <br> enhancements and support requests. <br> It is enclosed between parentheses (). </p>
- </td></tr><tr><td rowspan="2" valign="middle">
-<p><span class="bold"><strong>Platform Identifier</strong></span></p>
- </td><td>
-
-<p>[UNIX]</p>
- </td><td>
-
-<p>[OpenVMS]</p>
- </td></tr><tr><td colspan="2">
-<p>The platform identifier does not appear <br> for those new features or <br> enhancements that apply to both the platforms. </p>
- </td></tr></tbody></table></div><p></p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Note"><tr><td rowspan="2" align="center" valign="top" width="12pt"><img alt="[Note]" src="images/note.jpg"></td><th align="left">Note</th></tr><tr><td align="left" valign="top"><p>The term UNIX refers to the general sense of all platforms on which GT.M uses a POSIX API. As of this date, this includes: AIX, HP-UX on IA64, GNU/Linux on x86 [...]
-
-<p>Pre V5.5-000 terminology</p>
- </th><th>
-
-<p>Pre V5.5-000 qualifier</p>
- </th><th>
-
-<p>Current terminology</p>
- </th><th>
-
-<p>Current qualifiers </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><p>Effective V6.0-000, GT.M documentation is adopting IEC standard <a class="ulink" href="http://physics.nist.gov/cuu/Units/binary.html" target="_blank">Prefixes for binary multiples</a>. This document therefore uses prefixes Ki, Mi and Ti (e.g., 1MiB for 1,048,576 bytes). All GT.M documentation will over time be updated to this standard.</p><p><span class="inlinemediaobject"><img src="images/chkmrkg.png" alt="New Feature"></span>
- denotes a new feature that requires updating the manuals. </p><p><span class="inlinemediaobject"><img src="images/chkmrkb.png" alt="New Feature"></span>
- denotes a new feature or an enhancement that is not upward compatible and might affect your application code. </p><p><span class="inlinemediaobject"><img src="images/deprecated.png" alt="Deprecated"></span>
- denotes deprecated error messages.</p><p><span class="inlinemediaobject"><img src="images/revised.png" alt="Deprecated"></span>
- denotes revised error messages.</p></div><div class="sect2" title="Platforms"><div class="titlepage"><div><div><h3 class="title"><a name="platforms"></a> Platforms </h3></div></div></div><p> Over time, computing platforms evolve. Vendors obsolete hardware architectures. New versions of operating systems replace old ones. We at FIS continually evaluate platforms and versions of platforms that should be Supported for GT.M. In the table below, we document not only the ones that are current [...]
- <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> Hewlett-Packard Alpha/AXP OpenVMS </p>
- </td><td>
-
-<p> 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. A GT.M database file on this platform can grow to a maximum size of 1TiB-512 bytes.</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 this platform. </p>
- </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> 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 6; Ubuntu 12.04 LTS; 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 Linux kernel (2.6 or later), 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 6, 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> GT.M requires the libtinfo library. If it is not already installed on your system, and is available using the package manager, install it using the package manager. If a libtinfo package is not available (for example on SuSE 11):</p>
- <div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> Find the directory where libncurses.so is installed on your system.</p></li><li class="listitem"><p> Change to that directory and make a symbolic link to libncurses.so.<ver> from libtinfo.so.<ver>. Note that some of the libncurses.so entries may themselves be symbolic links, for example, libncurses.so.5 may itself be a symbolic link to libncurses.so.5.9.</p></li></ul></div>
- </td></tr><tr><td>
-
-<p> x86 GNU/Linux </p>
- </td><td>
-
-<p> Red Hat Enterprise Linux 6 </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 Linux kernel (2.6 or later), 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>
- </td></tr></tbody></table></div><div class="sect3" title="Platform support lifecycle"><div class="titlepage"><div><div><h4 class="title"><a name="GTMplatform_lifecycle"></a> Platform support lifecycle </h4></div></div></div><p> FIS usually supports new operating system versions six months or so 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 pro [...]
- <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><p></p><div class="caution" title="Caution" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Caution: Caution"><tr><td rowspan="2" align="center" valign="top" width="12pt"><img alt="[Caution]" src="images/caution.jpg"></td><th align="left"> Caution</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 type [...]
- <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><p></p><div class="important" title="Important" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Important: Important"><tr><td rowspan="2" align="center" valign="top" width="12pt"><img alt="[Important]" src="images/important.jpg"></td><th align="left"> Important</th></tr><tr><td align="left" valign="top"><p> Assuming other aspects of code are 64-bit capable, collation routines should require only recompilation. </p></td></tr></ [...]
- <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><p></p><div class="important" title="Important" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Important: Important"><tr><td rowspan="2" align="center" valign="top" width="12pt"><img alt="[Important]" src="images/important.jpg"></td><th align="left">Important</th></tr><tr><td align="left" valign="top"><p>Assuming other aspects of code are 64-bit capable, environment translation routines should require only recompilation.</p></ [...]
- Recompile </h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
- Recompile all M and C source files.</p></li></ul></div></div><div class="sect2" title="Rebuild Shared Libraries or Images"><div class="titlepage"><div><div><h3 class="title"><a name="rebuild"></a>Rebuild Shared Libraries or Images</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Rebuild all Shared Libraries (UNIX) or Shareable Executable Images (OpenVMS) after recompiling all M and C source files..</p></li></ul></div></div><div [...]
- <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-3357">GTM-3357</a></p></td><td><p>C9A10-001605</p></td><td><p>MUMPS</p></td><td><p>ZMESSAGE guards against a set of messages it should not issue</p></td></tr><tr><td><p><a class="link" href="#GTM-3907">GTM-3907</a></p></td><td><p>C9B10-001766</p></td><td><p>MUMPS</p></td><td><p>Option for strict left-to-right order of evaluation where side effect expressions can impact the result <span class="inlinemediaobject"> [...]
- </h3></div></div></div><p>Previous: <span class="emphasis"><em> CRYPTDLNOOPEN, Error loading encryption library. eeee </em></span></p><p>Revised: <span class="emphasis"><em> CRYPTDLNOOPEN, Failed to load encryption library while opening encrypted file ffff. eeee</em></span></p></div><div class="sect2" title="CRYPTDLNOOPEN2"><div class="titlepage"><div><div><h3 class="title"><a name="CRYPTDLNOOPEN2"></a>CRYPTDLNOOPEN2</h3></div></div></div><p><span class="emphasis"><em>CRYPTDLNOOPEN, Fai [...]
- </h3></div></div></div><p>Previous: <span class="emphasis"><em>CRYPTHASHGENFAILED, Error generating encryption hash. eeee </em></span></p><p>Revised: <span class="emphasis"><em>CRYPTHASHGENFAILED, Failed to generate cryptographic hash for symmetric key corresponding to file ffff. eeee </em></span></p></div><div class="sect2" title="CRYPTINIT"><div class="titlepage"><div><div><h3 class="title"><a name="CRYPTINIT"></a>CRYPTINIT <span class="inlinemediaobject"><img src="images/revised.png" [...]
- </h3></div></div></div><p>Previous: <span class="emphasis"><em> CRYPTINIT, Error initializing encryption library. eeee </em></span></p><p>Revised: <span class="emphasis"><em> CRYPTINIT, Failed to initialize encryption library while opening encrypted file ffff. eeee</em></span></p></div><div class="sect2" title="CRYPTINIT2"><div class="titlepage"><div><div><h3 class="title"><a name="CRYPTINIT2"></a>CRYPTINIT2</h3></div></div></div><p><span class="emphasis"><em>CRYPTINIT2, Failed to initi [...]
- </h3></div></div></div><p>Previous: <span class="emphasis"><em>CRYPTKEYFETCHFAILED, Cannot obtain encryption key for ffff. eeee </em></span></p><p>Revised: <span class="emphasis"><em>CRYPTKEYFETCHFAILED, Failed to retrieve encryption key corresponding to file ffff. eeee</em></span></p></div><div class="sect2" title="CRYPTKEYFETCHFAILEDNF"><div class="titlepage"><div><div><h3 class="title"><a name="CRYPTKEYFETCHFAILEDNF"></a>CRYPTKEYFETCHFAILEDNF <span class="inlinemediaobject"><img src= [...]
- </h3></div></div></div><p><span class="emphasis"><em> CRYPTKEYFETCHFAILEDNF,Cannot obtain encryption key. xxxx </em></span></p><p>Obsolete Error: No longer issued by GT.M. </p></div><div class="sect2" title="CRYPTINIT"><div class="titlepage"><div><div><h3 class="title"><a name="CRYPTOPFAILED"></a>CRYPTINIT <span class="inlinemediaobject"><img src="images/revised.png" alt="Revised"></span>
- </h3></div></div></div><p>Previous: <span class="emphasis"><em>CRYPTOPFAILED, Encrypt/Decrypt operation failed. eeee</em></span></p><p>Revised: <span class="emphasis"><em> CRYPTOPFAILED, Encrypt/Decrypt operation failed for file ffff. eeee </em></span></p></div><div class="sect2" title="DBCOLLREQ"><div class="titlepage"><div><div><h3 class="title"><a name="DBCOLLREQ"></a>DBCOLLREQ</h3></div></div></div><p><span class="emphasis"><em>DBCOLLREQ, JOURNAL EXTRACT proceeding without collation [...]
- </h3></div></div></div><p>Previous: <span class="emphasis"><em>Journal control unsynchronized. Journaling closed for xxxx.</em></span></p><p>Revised: <span class="emphasis"><em>Journal control unsynchronized for ffff.</em></span></p></div><div class="sect2" title="JNLEXTEND"><div class="titlepage"><div><div><h3 class="title"><a name="JNLEXTEND"></a>JNLEXTEND <span class="inlinemediaobject"><img src="images/revised.png" alt="Revised"></span>
- </h3></div></div></div><p><span class="emphasis"><em>JNLEXTEND, Journal file extension error for file xxxx.</em></span></p><p>Run Time Error: Journal file xxxx failed to extend. If the environment is not configured for instance freeze, this causes journaling to be turned off for the region.</p><p>Action: Review the accompanying message(s) and take appropriate action. If the environment is not configured for instance freeze, perfrom a MUPIP BACKUP, that turns journaling on again, to rees [...]
- </h3></div></div></div><p><span class="emphasis"><em>REQROLLBACK, Error accessing database dddd. Run MUPIP JOURNAL ROLLBACK on cluster node ccccc.</em></span></p><p>Runtime Error: This indicates that GT.M could not open a previously replicated database file dddd due to a prior improper shutdown on cluster node ccccc. A GT.M process on cluster node ccccc may have failed to attach a database memory segment or it was terminated by a method other than MUPIP STOP.</p><p>Action: Perform MUPIP [...]
--
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