GT.M V6.2-000 available
19 views
Skip to first unread message
Bhaskar, K.S
Sep 17, 2014, 3:56:52 PM9/17/14
to Hardhats, Enterprise Web Developer Community, Vi...@googlegroups.com, worldvist...@yahoogroups.com
V6.2-000 is a major release that introduces auto-relink, a
publish+subscribe model that enables GT.M processes to automatically
and safely execute the latest published versions of routines; adds
support to read and write encrypted sequential disk files, pipes,
and FIFOs; adds the ability to pass SOCKET devices from one process
to another; and includes many other enhancements and fixes.
V6.2-000 also has numerous smaller enhancements, including:
The online help facilities provided through the ZHELP command in GT.M, and the HELP commands in the utilities, provide hierarchically organized information current with V6.2-000. These, as well as robustness improvements, fixes to issues, and performance enhancements, are described in the Release Notes.
Please do include an upgrade to V6.2-000 in your plans. As always, please do send any feedback our way. Thank you for using GT.M.
Regards
-- Bhaskar
- Released as field test grade functionality in a production release, auto-relink provides a way to allow long-running processes to automatically and safely execute the latest versions of routines. It also has uses in development and testing. Each process that wishes to subscribe to updates of object files in a directory appends an asterisk ("*") suffix to that directory name in $ZROUTINES before linking from it. When a process publishes updates to routines (including the presence of new routines, and the removal of existing routines) with the ZRUPDATE command, processes that have subscribed to those updates automatically perform a ZLINK on the next execution of a command or function call that explicitly invokes a routine with a published update. Safe execution means that auto-relink of new versions of routines ensures that prior versions of those routines on the M call stack continue executing correctly through their QUIT commands and are not "clobbered" when control returns to them. Field-test grade functionality in a production release means that FIS considers auto-relink functionality sufficiently robust for use in development and testing, but not robust enough for use in production environments. Except for auto-relink, all other functionality in V6.2-000 is robust enough for use in production.
- To protect non-database data at rest, and more securely exchange data with other systems and applications, both GT.M as well as non-GT.M processes, GT.M encryption functionality extends to file, pipe, and FIFO IO. As with all GT.M encryption features, GT.M itself includes no cryptographic software; instead it accesses external cryptographic libraries using a plugin architecture. The GT.M distribution includes a reference implementation of the plugin, which FIS tests during GT.M development against a couple of widely available cryptographic packages. FIS neither supports cryptographic libraries with GT.M nor recommends the use of any specific library - refer to the GT.M Administration and Operations Guide UNIX Edition for more details.
- Functionality to transfer DETACHed TCP or LOCAL sockets between GT.M processes using a LOCAL SOCKET device as the rendezvous is a fundamental enabling technology. Rich user interfaces can be built with multiple bi-directional TCP connections between clients such as browsers and server processes, using a layered protocol such as WebSockets. When a client and server wish to add a TCP connection between them, the client can initiate a new connection to a known port on server. An Internet superserver, such as xinetd, can screen the request and start a GT.M process, which can use an application-defined protocol to obtain the process id of the client's existing server process to whom it transfers the connection. The technique can also be used by a server to pass an existing client socket to a different process, for example, one that publishes information, such as a news feed or weather report.
V6.2-000 also has numerous smaller enhancements, including:
- $ZSOCKET() provides information about a SOCKET device and its attached sockets.
- $ZSYSLOG() allows a process to send a message to the syslog without requiring the POSIX plugin.
- GT.M for 32-bit Linux is compiled using the i586 ("Pentium compatible") instruction set, allowing it to run on recent System on Chip (SoC) based computers.
- MUPIP SIZE includes an estimate of adjacency.
- $PRINCIPAL can be a LOCAL socket.
The online help facilities provided through the ZHELP command in GT.M, and the HELP commands in the utilities, provide hierarchically organized information current with V6.2-000. These, as well as robustness improvements, fixes to issues, and performance enhancements, are described in the Release Notes.
Please do include an upgrade to V6.2-000 in your plans. As always, please do send any feedback our way. Thank you for using GT.M.
Regards
-- Bhaskar
-- GT.M - Rock solid. Lightning fast. Secure. No compromises.
_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
Nancy Anthracite
Sep 17, 2014, 4:27:30 PM9/17/14
to hard...@googlegroups.com, Bhaskar, K.S, Hardhats, Enterprise Web Developer Community, Vi...@googlegroups.com, worldvist...@yahoogroups.com
Even I know enogb to know these are great enhancements. Thank you! :-)
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Sent from my Android device with K-9 Mail. Please excuse my brevity.
DL Wicksell
Sep 17, 2014, 5:33:08 PM9/17/14
to vi...@googlegroups.com
Congratulations! That is a fantastic update. Great job!
On 09/17/2014 01:55 PM, Bhaskar, K.S wrote:
> V6.2-000 is a major release that introduces auto-relink, a
> publish+subscribe model that enables GT.M processes to automatically and
> safely execute the latest published versions of routines; adds support
> to read and write encrypted sequential disk files, pipes, and FIFOs;
> adds the ability to pass SOCKET devices from one process to another; and
> includes many other enhancements and fixes.
>
> * Released as field test grade functionality in a production release,
> for more details.
>
> * Functionality to transfer DETACHed TCP or LOCAL sockets between GT.M
> attached sockets.
> * $ZSYSLOG() allows a process to send a message to the syslog without
> requiring the POSIX plugin.
> * GT.M for 32-bit Linux is compiled using the i586 ("Pentium
> * $PRINCIPAL can be a LOCAL socket.
> You received this message because you are subscribed to the Google
> Groups "VistA" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to vista+un...@googlegroups.com
> <mailto:vista+un...@googlegroups.com>.
> To post to this group, send email to vi...@googlegroups.com
> <mailto:vi...@googlegroups.com>.
> Visit this group at http://groups.google.com/group/vista.
> For more options, visit https://groups.google.com/d/optout.
--
David Wicksell
President / CEO
Fourth Watch Software, LC
575-636-2229
On 09/17/2014 01:55 PM, Bhaskar, K.S wrote:
> V6.2-000 is a major release that introduces auto-relink, a
> publish+subscribe model that enables GT.M processes to automatically and
> safely execute the latest published versions of routines; adds support
> to read and write encrypted sequential disk files, pipes, and FIFOs;
> adds the ability to pass SOCKET devices from one process to another; and
> includes many other enhancements and fixes.
>
> auto-relink provides a way to allow long-running processes to
> automatically and safely execute the latest versions of routines. It
> also has uses in development and testing. Each process that wishes
> to subscribe to updates of object files in a directory appends an
> asterisk ("*") suffix to that directory name in $ZROUTINES before
> linking from it. When a process publishes updates to routines
> (including the presence of new routines, and the removal of existing
> routines) with the ZRUPDATE command, processes that have subscribed
> to those updates automatically perform a ZLINK on the next execution
> of a command or function call that explicitly invokes a routine with
> a published update. Safe execution means that auto-relink of new
> versions of routines ensures that prior versions of those routines
> on the M call stack continue executing correctly through their QUIT
> commands and are not "clobbered" when control returns to them.
> Field-test grade functionality in a production release means that
> FIS considers auto-relink functionality sufficiently robust for use
> in development and testing, but not robust enough for use in
> production environments. Except for auto-relink, all other
> functionality in V6.2-000 is robust enough for use in production.
>
> * To protect non-database data at rest, and more securely exchange
> automatically and safely execute the latest versions of routines. It
> also has uses in development and testing. Each process that wishes
> to subscribe to updates of object files in a directory appends an
> asterisk ("*") suffix to that directory name in $ZROUTINES before
> linking from it. When a process publishes updates to routines
> (including the presence of new routines, and the removal of existing
> routines) with the ZRUPDATE command, processes that have subscribed
> to those updates automatically perform a ZLINK on the next execution
> of a command or function call that explicitly invokes a routine with
> a published update. Safe execution means that auto-relink of new
> versions of routines ensures that prior versions of those routines
> on the M call stack continue executing correctly through their QUIT
> commands and are not "clobbered" when control returns to them.
> Field-test grade functionality in a production release means that
> FIS considers auto-relink functionality sufficiently robust for use
> in development and testing, but not robust enough for use in
> production environments. Except for auto-relink, all other
> functionality in V6.2-000 is robust enough for use in production.
>
> data with other systems and applications, both GT.M as well as
> non-GT.M processes, GT.M encryption functionality extends to file,
> pipe, and FIFO IO. As with all GT.M encryption features, GT.M itself
> includes no cryptographic software; instead it accesses external
> cryptographic libraries using a plugin architecture. The GT.M
> distribution includes a reference implementation of the plugin,
> which FIS tests during GT.M development against a couple of widely
> available cryptographic packages. FIS neither supports cryptographic
> libraries with GT.M nor recommends the use of any specific library -
> refer to the GT.M Administration and Operations Guide UNIX Edition
> <http://tinco.pair.com/bhaskar/gtm/doc/books/ao/UNIX_manual/index.html>
> non-GT.M processes, GT.M encryption functionality extends to file,
> pipe, and FIFO IO. As with all GT.M encryption features, GT.M itself
> includes no cryptographic software; instead it accesses external
> cryptographic libraries using a plugin architecture. The GT.M
> distribution includes a reference implementation of the plugin,
> which FIS tests during GT.M development against a couple of widely
> available cryptographic packages. FIS neither supports cryptographic
> libraries with GT.M nor recommends the use of any specific library -
> refer to the GT.M Administration and Operations Guide UNIX Edition
> for more details.
>
> * Functionality to transfer DETACHed TCP or LOCAL sockets between GT.M
> processes using a LOCAL SOCKET device as the rendezvous is a
> fundamental enabling technology. Rich user interfaces can be built
> with multiple bi-directional TCP connections between clients such as
> browsers and server processes, using a layered protocol such as
> WebSockets. When a client and server wish to add a TCP connection
> between them, the client can initiate a new connection to a known
> port on server. An Internet superserver, such as xinetd, can screen
> the request and start a GT.M process, which can use an
> application-defined protocol to obtain the process id of the
> client's existing server process to whom it transfers the
> connection. The technique can also be used by a server to pass an
> existing client socket to a different process, for example, one that
> publishes information, such as a news feed or weather report.
>
>
> V6.2-000 also has numerous smaller enhancements, including:
>
> * $ZSOCKET() provides information about a SOCKET device and its
> fundamental enabling technology. Rich user interfaces can be built
> with multiple bi-directional TCP connections between clients such as
> browsers and server processes, using a layered protocol such as
> WebSockets. When a client and server wish to add a TCP connection
> between them, the client can initiate a new connection to a known
> port on server. An Internet superserver, such as xinetd, can screen
> the request and start a GT.M process, which can use an
> application-defined protocol to obtain the process id of the
> client's existing server process to whom it transfers the
> connection. The technique can also be used by a server to pass an
> existing client socket to a different process, for example, one that
> publishes information, such as a news feed or weather report.
>
>
> V6.2-000 also has numerous smaller enhancements, including:
>
> attached sockets.
> * $ZSYSLOG() allows a process to send a message to the syslog without
> requiring the POSIX plugin.
> * GT.M for 32-bit Linux is compiled using the i586 ("Pentium
> compatible") instruction set, allowing it to run on recent System on
> Chip (SoC) based computers.
> * MUPIP SIZE includes an estimate of adjacency.
> Chip (SoC) based computers.
> * $PRINCIPAL can be a LOCAL socket.
>
>
> The online help facilities provided through the ZHELP command in GT.M,
> and the HELP commands in the utilities, provide hierarchically organized
> information current with V6.2-000. These, as well as robustness
> improvements, fixes to issues, and performance enhancements, are
> described in the Release Notes
> <http://tinco.pair.com/bhaskar/gtm/doc/articles/GTM_V6.2-000_Release_Notes.html>.
>
> The online help facilities provided through the ZHELP command in GT.M,
> and the HELP commands in the utilities, provide hierarchically organized
> information current with V6.2-000. These, as well as robustness
> improvements, fixes to issues, and performance enhancements, are
> described in the Release Notes
>
> Please do include an upgrade to V6.2-000 in your plans. As always,
> please do send any feedback our way. Thank you for using GT.M.
>
> Regards
> -- Bhaskar
>
> --
> GT.M - Rock solid. Lightning fast. Secure. No compromises.
>
> _____________
> The information contained in this message is proprietary and/or
> confidential. If you are not the intended recipient, please: (i) delete
> the message and all copies; (ii) do not disclose, distribute or use the
> message in any manner; and (iii) notify the sender immediately. In
> addition, please be aware that any message addressed to our domain is
> subject to archiving and review by persons other than the intended
> recipient. Thank you.
>
> --
> Please do include an upgrade to V6.2-000 in your plans. As always,
> please do send any feedback our way. Thank you for using GT.M.
>
> Regards
> -- Bhaskar
>
> --
> GT.M - Rock solid. Lightning fast. Secure. No compromises.
>
> _____________
> The information contained in this message is proprietary and/or
> confidential. If you are not the intended recipient, please: (i) delete
> the message and all copies; (ii) do not disclose, distribute or use the
> message in any manner; and (iii) notify the sender immediately. In
> addition, please be aware that any message addressed to our domain is
> subject to archiving and review by persons other than the intended
> recipient. Thank you.
>
> You received this message because you are subscribed to the Google
> Groups "VistA" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to vista+un...@googlegroups.com
> <mailto:vista+un...@googlegroups.com>.
> To post to this group, send email to vi...@googlegroups.com
> <mailto:vi...@googlegroups.com>.
> Visit this group at http://groups.google.com/group/vista.
> For more options, visit https://groups.google.com/d/optout.
--
David Wicksell
President / CEO
Fourth Watch Software, LC
575-636-2229
LD 'Gus' Landis
Sep 18, 2014, 1:28:54 AM9/18/14
to vi...@googlegroups.com
On Wed, Sep 17, 2014 at 2:15 PM, DL Wicksell <dlwic...@gmail.com> wrote:
Congratulations! That is a fantastic update. Great job!
Yes, great job!
Didn't you suggest that you were going to make the 586 flavor
be the default for x86 so that things like the Intel Magellan board
would have a prebuilt GT.M available?
be the default for x86 so that things like the Intel Magellan board
would have a prebuilt GT.M available?
Looking for the latest version?
Download gtm_V61000_linux_i686_pro.tar.gz (10.4 MB)
| Name | Modified | Size | Downloads / Week | Status |
|---|---|---|---|---|
| Parent folder | ||||
| Totals: 4 Items | 12.2 MB | 4 |
|
|
| gtm_V62000_linux_i686_pro.tar.gz | < 10 hours ago | 10.9 MB |
1 |
i |
| dbcertify_V62000_linux_i686_pro.tar.gz | < 10 hours ago | 1.2 MB |
1 |
i |
| GTMDefinedTypesInit_V62000_linux_i686_pro.tar.gz | < 10 hours ago | 162.7 kB |
1 |
i |
| readme.txt | < 10 hours ago | 204 Bytes |
1 | |
To unsubscribe from this group and stop receiving emails from it, send an email to vista+un...@googlegroups.com.
To post to this group, send email to vi...@googlegroups.com.
Visit this group at http://groups.google.com/group/vista.
For more options, visit https://groups.google.com/d/optout.
--
---
NOTE: If it is important CALL ME - I may miss email,
which I do NOT normally check on weekends nor on
a regular basis during any other day.
---
LD Landis - N0YRQ-1 - de la tierra del encanto
3960 Schooner Loop, Las Cruces, NM 88012
o:651-340-4007 / 575-636-2229 c:575-312-3995
NOTE: If it is important CALL ME - I may miss email,
which I do NOT normally check on weekends nor on
a regular basis during any other day.
---
LD Landis - N0YRQ-1 - de la tierra del encanto
3960 Schooner Loop, Las Cruces, NM 88012
o:651-340-4007 / 575-636-2229 c:575-312-3995
N32 21'48.28" W106 46'5.80" DM62OI77UD
Bhaskar, K.S
Sep 18, 2014, 7:43:43 AM9/18/14
to vi...@googlegroups.com
We should have renamed the file name i586. We'll do that in the
future. Even though it says 686, it was compiled for 586.
Apologies.
Regards
-- Bhaskar
Regards
-- Bhaskar
LD 'Gus' Landis
Sep 24, 2014, 6:37:53 PM9/24/14
to vi...@googlegroups.com
On Thu, Sep 18, 2014 at 5:43 AM, Bhaskar, K.S <ks.bh...@fisglobal.com> wrote:
We should have renamed the file name i586. We'll do that in the future. Even though it says 686, it was compiled for 586. Apologies.
Perfect! Perhaps you can put that statement in the readme without having
to repackage stuff. THANKS!
to repackage stuff. THANKS!
Bhaskar, K.S
Sep 24, 2014, 6:44:46 PM9/24/14
to vi...@googlegroups.com
The Overview section of the Release Notes already says:
We have no plans to repackage and re-release V6.2-000. We'll change the name of the tarball for the next release.
Regards
-- Bhaskar
-
GT.M for 32-bit Linux is compiled using the i586 ("Pentium compatible") instruction set, allowing it to run on recent System on Chip (SoC) based computers (GTM-7950).
We have no plans to repackage and re-release V6.2-000. We'll change the name of the tarball for the next release.
Regards
-- Bhaskar
LD 'Gus' Landis
Sep 24, 2014, 8:54:21 PM9/24/14
to vi...@googlegroups.com
Perfect!
Reply all
Reply to author
Forward
0 new messages