Rocket MultiValue

We had a D3 customer who did a Windows update which updated the version of NTDLL.DLL (that's Windows' .dll not D3's). After that his 10.4.0.2 VME crashed five times in one day. After some investigation we determined that there was some heap corruption going on in D3 that was not detected by the earlier version of the NTDLL.DLL (10.0.20348.5020) but was detected by the updated version (10.0.20348.5139). When this heap corruption was detected, NTDLL killed the D3 VME. The customer then rolled back the NTDLL.DLL version and the VME crashes have ceased. In this particular instance, the NTDLL.DLL was updated by Windows update (Microsoft release) KB5087545 from May 12th, 2026, but that will change from update to update.We at Rocket are looking into this, but meanwhile please be aware. We have not had this reported by anyone else other than this one customer, but that doesn't guarantee that it wouldn't happen to anyone else. We suggest that you NOT apply any Windows updates that contain the u

Rocket® MultiValue Pulse | August 2026Welcome BackHi, MultiValue Community!Welcome to Rocket® MultiValue Pulse, the refreshed newsletter experience for the MultiValue community—created to bring you timely customer updates, practical resources, and community conversations in one place.As we move through the second half of 2026, our focus remains simple: helping you maximize the value of your MultiValue investment while preparing for what's next.For many MultiValue organizations, that also means ensuring critical applications remain stable, supported, and ready for the future. In upcoming editions, we’ll share resources and conversations focused on business continuity, long-term planning, and practical steps to help teams reduce risk while continuing to modernize.Over the coming months, you'll hear more from us through customer webinars, community discussions, product updates, and practical resources designed to help you strengthen operational resilience, modernize with confidence, and c

Rocket® MultiValue Pulse | August 2026Welcome BackHi, MultiValue Community!Welcome to Rocket® MultiValue Pulse, the refreshed newsletter experience for the MultiValue community—created to bring you timely customer updates, practical resources, and community conversations in one place.As we move through the second half of 2026, our focus remains simple: helping you maximize the value of your MultiValue investment while preparing for what's next.For many MultiValue organizations, that also means ensuring critical applications remain stable, supported, and ready for the future. In upcoming editions, we’ll share resources and conversations focused on business continuity, long-term planning, and practical steps to help teams reduce risk while continuing to modernize.Over the coming months, you'll hear more from us through customer webinars, community discussions, product updates, and practical resources designed to help you strengthen operational resilience, modernize with confidence, and c

10.4 is D3 Windows FSI architecture over Linux, not Windows. The main differences:1) Almost everything is stored in the local file system (FSI = File System Interface) and not the VME blob. A good consequence of this is that you no longer have to allocate a disk partition or logical volume for D3. In the Linux file system there would be a /usr/lib/pick/database directory with subdirectories for each D3 account, each containing subdirectories for each dict-level file in that account, each containing subdirectories for each data-level in that file, each containing the D3 data file itself in main and overflow files with indexes in separate files (.D3C, .D3T, .D3O, .D3X). The data structure within those files is extremely similar to the 10.3 VME blob where you have frames containing your data hashed to the appropriate frame.2) D3 is a single multi-threaded Linux process instead of each PIB being a separate Linux process. This actually makes it faster, but introduces some problems, like mem

I'm trying to get ssh working into a Windows 2022 system with UniVerse via openssh. It works much better than the last time I tried it, but for one problem: the escape key. The problem is that the escape key is not passed to UniVerse. I'm wondering if anyone has any suggestions or has managed to get this going? Let me illustrate this a little. If I ssh into the Windows server, CD to a UniVerse account, and run the uv (or uvsh) command, and then run the following program: GETKEY 0001 PRINT 'This will list the ASCII code of the key pressed until you hit "Q"' 0002 loop 0003 c = keyin() 0004 print seq(c) 0005 until c = 'Q' ! c = 'q' do repeat It returns the ASCII code for any key I press - except for the ESC key, when it simply doesn't respond. Curiously, the same problem occurs if I run the program after opening a UniVerse command line session using Start > Rocket U2 > UniVerse Shell (so the problem isn't exclusively related to ssh, it would seem). Furthermore, if from th

Had a customer report today that there’s a strange bug in the SB+ expression parser.  The sample he provided was this:IF(1,170,””)”MR2”)The spurious ) at the end should be a syntax error.  But it is not.    As long as all quotes are “, this returns either 170 or “)”MR2 depending on if the condition is true or false.  It also gets converted in EEGC as follows:IF 1 THEN   VALUE = 170END ELSE   VALUE = '")"MR2'ENDThis is not a crisis, but I wanted to post this in case anyone else happens to make the same mistake we did, with that extra “)” at the end of an expression. 

Hi everyone, been a while since I visited and even longer since I shared.We are moving from SQL file triggers to the IDX file triggers and ran into a small issue where we have a trigger on the DICT and a trigger on the DATA levels of the same file.Getting the DATA level trigger working is simple but how to get the trigger in the DICT working?Not sure if anyone has done this before but in short the answer is you need two dictionary items: INDEX.ITYPE for the data level and D_INDEX.ITYPE for the dictionary level. To build the index on D_INDEX.ITYPE you need to use the “USING” clause in the CREATE.INDEX command:CREATE.INDEX DICT FILENAME D_INDEX.ITYPE USING DICT FILENAME NO.NULLSThe trigger will now fire when a record is added/deleted/modified in DICT FILENAME.

Accredited in the following solutioning categories:Application Development and Enhancement Modernization and Cloud Migration Integration with Non-MultiValue Systems Performance Tuning and Optimization Upgrade and Version Migration Services Managed Services and Ongoing Support Training and Knowledge TransferFor more information visit the partner’s website 

I read through the documentation and compared it to what I am seeing on the system. There is a DEVICES record called OKIDATA.  This has control character definitions and such. In the USER-COLD-START, there is a STARTPTR 0, 0, 0, S13 & STARTPTR 1, 1, 0, S10 and other for the rest. There is also an ASSIGNFQ 1,OKIDATA (C If I do LISTPTR I have several printers, 0, 1, 2, 6 and 7 and all say serial and DEV or PROCESS # is 13, 10, 11, 14 and 9.On the server itself, the OKIDATA printer name is OKI-C711-DCA9AC. How is the OKI-C711-DCA9AC assign to the OKIDATA?  I am thinking it is something to do with a configuration somewhere for the Dev or Process, but not sure what.  Any help would be greatly appreciated.------------------------------Troy DittbernerPresidentNorthstar Data Services IncBrooklyn Park VA US------------------------------

Hi everyone, Does anyone know how to make the "Universe Telnet Service" that runs on our IBS Application server, to only use 128bitblock Ciphers, and disable the other lower 64bit block ciphers? The service listens on port 992. The problem is that our Qualys VUN scanning tool is picking up that port 992 is a security risk againstBirthday attacks against TLS ciphers with 64bit block size vulnerability (Sweet32) and goes on to say"Disable and stop using DES, 3DES, IDEA or RC2 ciphers.  We believe that the "Universe Telnet Service" uses OpenSSL that offers out these lower level ciphers, but we have no idea how to to best address this sothat the only ciphers used are 128-bit or higher ciphers. We are waiting on our third party support to get back to us as they have opened a ticket today. Current version of OpenSSL is OpenSSL 1.0.2m-fips  2 Nov 2017, though "Programs and Features" is saying OpenSSL 1.1.1k (64-bit) was installed on March 2021. Universe is 12.1.1 is installed. Thanks in advan

We want to inform you that the Rocket® MultiValue Developer Assistant will be retired effective June 30, 2026.This tool, integrated within the VS Code development environment, provided early AI-assisted capabilities for MultiValue developers. After careful evaluation, we have determined that it has not consistently delivered the level of impact our customers deserve in real-world development workflows. We made the decision to retire it rather than continue investing in a solution that doesn't meet that bar.-------------------------------------What's ChangingThe Rocket® MultiValue Developer Assistant will be decommissioned on June 30, 2026 Existing users will no longer have access after this date No technical action is required — though you may wish to update any internal documentation or workflows that referenced the tool-------------------------------------Data & PrivacyNo user prompts were recorded All server logs will be deleted as part of the decommissioning process------------

New features. Live demos. Practical insights. Rocket® UniData 8.4.1 is here – and it brings powerful updates designed to modernize your applications, improve observability, strengthen security, and boost developer productivity.Watch this customer enablement webinar to get a clear, practical walkthrough of what’s new in UniData 8.4.1, followed by live demonstrations of OpenTelemetry and BASIC enhancements so you can see the latest capabilities in action.UniData 8.4.1 HighlightsOpenTelemetry integration (Phase 1) for deeper observability BASIC enhancements: Try/Catch, dynamic objects & native JSON UniData Performance Monitoring (udtpm) now on Windows Compiler directives for easier multi-version code management Improved replication with sequential I/O Updated security & platforms: OpenSSL 3.5, Python 3.13Live demosOpenTelemetry observability in action BASIC extensions for more efficient development

We’re excited to announce that SB/XA 6.6.5 is available as of June 8, 2026. This release represents a major step forward, delivering meaningful improvements in modernization, security, and performance you can rely on.Modernization & Architecture EnhancementsNative ARM64 Support for the Rich ClientThe SB/XA Rich Client now includes native ARM64 support for modern Windows devices running ARM processors, such as Windows 11 systems with Snapdragon CPUs.What this means for you:Improved performance and efficiency on ARM-based hardware Native execution on Windows 11 ARM64 environments Automatic fallback to x86 emulation on Windows 10 ARM64 systemsAs part of this enhancement, the Rich Client now runs on .NET Framework 4.8.1 bringing modernized project files that make it easier than ever for customers to build and customize Rich Clients aligned with the new architecture.Security ImprovementsSecurity enhancements in this release address both cryptographic standards and client-side vulnerabil

New Features. Live Demos. Practical Insights.Rocket® UniData 8.4.1 is here and it brings powerful updates designed to modernize your applications, improve observability, strengthen security, and boost developer productivity.Join this customer enablement webinar to get a clear, practical walkthrough of what’s new in UniData 8.4.1, followed by live demonstrations of OpenTelemetry and BASIC enhancements so you can see the latest capabilities in action. What you’ll learnUniData 8.4.1 highlights• OpenTelemetry integration (Phase 1) for deeper observability• BASIC enhancements: Try/Catch, dynamic objects & native JSON• UniData Performance Monitoring (udtpm) now on Windows• Compiler directives for easier multi-version code management• Improved replication with sequential I/O• Updated security & platforms: OpenSSL 3.5, Python 3.13Live demos• OpenTelemetry observability in action• BASIC extensions for more efficient development Why attend?This webinar will help you:• Understand the full

Hi folks, I have a performance issue with the large-scale system. I know that this discussion depends on resources, so please assume sufficient resources are available. Let's think about a single read-only transaction performance by just 'run  <file name>'.  Assuming that elapsed time is 5 sec and CPU time is 1 sec. Then I tried processing this query by concurrent 2 users by phantom, but each user of elapsed and CPU time was very much worse than single. Roughly, it's 10 times worse. In reality, Is it impossible to get a benefit from parallel processing? ---- Sample basic program. cnt = 300000 open "STOCK" to fp else abort startTime = Time()startTimeCpu = System(9) for i=1 to cnt    read rec from fp,"101" else abortnext i endTime = Time()endTimeCpu = System(9) print "elapse      : ":(endTime - startTime)print "elapse(cpu) : ":(endTimeCpu - startTimeCpu)/1000 end ------------------------------------- ------------------------------Yukio KozukaSimount CorpBunkyo-ku JP----------

I have put together a JAVA/DataBasic  program for D3 that works with https://messagemedia.com Bulk SMS texting API if anyone's interested goto http://www.custlang.nz -> utilities->SMS for notes and to try it, see also other things such as a Natural Language Demo. ------------------------------Robert DavenportProgrammerCustom Language SolutionsAuckland NZ------------------------------