Amul

Hi William, Sorry for the delay. No worries about the typo, we understood you. As far as we know, customers have transitioned from xinted to systemd with just the changes that needed to go from xinetd to systemd. As I understand it, one can continue to use xinted with systemd. Please let us know if you do encounter any problems. thanks, Amul

If you try to use GT.M, what error messages do you see? There must be some log file with error messages in it. Have you checked syslog for error messages? Amul

Hi Zachary, I sent you a private message to contact us directly over email. Thanks, Amul

(On behalf of Roger) The difference in result arises because GT.M’s order of evaluation was originally optimized when the standard only had one side-effect (the “naked” reference, which it managed). When the language adopted other features, such as $INCREMENT() and extrinsics, with side-effects, GT.M did not, at first, change its evaluation scheme as it incorporated those features. Applications either adapted or even relied on its behavior. The $gtm_side_effects environment variable allows applications...

(on behalf of Roger) This is a consequence of the way GT.M handles concatenation of WRITE arguments, which is documented as follows in the WRITE section of the Commands chapter of the Programmer’s Guide: The GT.M compiler breaks a concatenated WRITE argument into a series of WRITE arguments to eliminate the overhead of the concatenation. If circumstances provide a reason for a single WRITE, perform the concatenation prior to the WRITE. This means the GT.M compiler does not see the concatenated WRITE...

Hello, Sorry for the delay and we’re glad to hear that everything is working for you now. We have a few questions.. 1. Is it possible for you to give us a stack trace? 2. I assume that you are using the prebuilt GTM binaries. However please let us know if you are using a custom compiled GTM. 3. Could you provide more details about the OS and processor levels? 4. Is there anyway for you to request support from SuSe or the hardware vendor about the crashes? They may have more insight. 5. Can you provide...

Hi Salman, Could you be more specific? Did you want to compress after the backup or compress the DBs on the fly? Amul

Hi Konstantin, Thanks for reporting this issue and apologies for our silence. We have fixed the bug and it will be included in the next release. Here is the release note: IF @<literal> works correctly when the literal evaluates to FALSE; in versions V6.3-001 to V6.3-004, it tended to fail with an inappropriate INDEXTRACHARS error or a segmentation violation (SIG-11). (GTM-8981)