Rocket MultiValue

The Rocket Software MultiValue team is pleased to invite all Rocket UniVerse customers with an active maintenance agreement to participate in the UniVerse 14.3.1 Beta Program.This is your opportunity to gain early access to upcoming enhancements, evaluate new capabilities in your own environment, and provide direct feedback that helps shape the final release before general availability.OpenTelemetry Support (Phase 1)Gain greater visibility into system behaviour and performance through the first phase of OpenTelemetry integration, providing a modern foundation for monitoring and diagnostics.Enhanced Auditing CapabilitiesThis release delivers a number of improvements to UniVerse auditing capabilities, including:User-defined audit event handlers Enhanced audit configuration & logging General audit usability and reliability improvementsUpgradesPython 3.14 OpenSSL 3.5Beta Program DetailsBeta begins: September 23, 2026 Beta concludes: November 4, 2026 Supported platforms: AIX, Linux, and

I've been building a tool that puts a MultiValue account under real version control. It runs on UniData and UniVerse today, and it's built to port to any MV system — the engine sits on a deliberately narrow set of record primitives, so a new platform means implementing that handful, not the tool. jBASE is in active development — its test suite is passing and I expect it in 2.1.What it does. It commits the account's own records directly to git objects — your records, your dictionaries, your VOC. The live account is the working tree, so there's no export copy drifting out of step and no import step to forget. Change a record, GIT STATUS shows it changed.Both surfaces work. From the shell it's udt-git / uv-git, taking the same subcommands and flags as stock git. From inside a session it's a cataloged GIT verb — GIT ADD -A, GIT COMMIT -m "...". Since 2.0.0 both commit identical bytes, which took longer to get right than everything else put together: a dictionary isn't stored the way it's h

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

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.

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

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----------

TBW&W (throw back Wednesday & wondering)Just a “gee whiz” question for any/all, is there a PICK DBMS that continues to use SYSPROG? NEWACC?THX!Doc

We’re excited to announce that Rocket® DBTools 4.6.2 is now available!Released on May 20, 2026, this update brings key improvements across XAdmin, EDA Schema Manager, Web Services, and Security, with a focus on reliability, visibility, and modern operations.What’s new in this release? We’re thrilled to bring OpenTelemetry to UniData with the release of version 8.4.1!XAdmin now includes a built‑in interface to configure OpenTelemetry (OTEL) and view OTEL logs, making observability easier and more accessible than ever. In addition, UniData 8.4.1 upgrades OpenSSL to version 3.5, delivering the latest security fixes and cryptographic enhancements to ensure continued compliance with current security standards - all configurable directly in XAdmin.OTEL in UniData 8.4.1 is only the start, with plenty of other great highlights in this release:Improved Administration & ReliabilityThe Data Encryption view now opens correctly for UniData connections, including scenarios where the master encry

We are thrilled to announce the release of Rocket® UniData 8.4.1 on May 20, 2026 a feature rich release designed to boost observability, application modernization, performance monitoring, security, and replication reliability.Whether you’re a developer, administrator, or part of an ops team, this release delivers meaningful improvements that help you build smarter, run faster, and operate with confidence.Let’s explore what’s new!Observability Takes Off: OpenTelemetry (Phase 1)Gain deeper, actionable insights into UniData workloads with the initial release of OpenTelemetry (OTEL) support. Delivering immediate observability value today and establishing a solid foundation for future monitoring and observability enhancements, including:A new OTEL licensing flag to enable OpenTelemetry functionality. Updates to the confprod and confcmd commands for the OTEL flag.BASIC Language EnhancementsTry/Catch Error HandlingThis new feature paths the way in providing modern and resilient control of err

The languge server that comes with Rocket MV Basic likes to complain about undefined variables in code such asfoo = 4bar = foo-1where it will say “Referenced undefined variable: foo-1” because it is detecting the minus operator as part of a variable name. Am I the only person experiencing this issue? Can this be addressed? It’s rather annoying as much of the code I’m looking at was last formatted with the Accuterm wED editor which did not enforce spacing around operators.

UOPY Example - Working with JSON  Making the connection The following code is a simple example to connect to a local U2 Database. In this example I am connecting to UniData, but the code would work the same against UniVerse, the only thing you would need to modify is the server and account settings. In [1]: import uopy import getpass user = input("Enter user name? ") passwd = getpass.getpass("Enter Password? ") def makeconnection(user, password): config = { 'user': user, 'password': passwd, 'service': 'udcs', 'account': 'C:\\\\U2\\\\ud82\\\\XDEMO', 'encoding': 'GB18030', 'pooling_on': 'False' } thissession = uopy.connect(**config) return thissession session = makeconnection(user, passwd) print(str(session)) Enter user name? mrajkowski Enter Password? ········ <uopy._session.Session object {'host': 'localhost', 'account': 'C:\\\\U2\\\\ud82\\\\XDEMO', 'por

We get asked every now and then where to get the U2 client software.  These include:U2 Clients ODBC, JDBC, UOJ and .NET drivers and associated tools Visual Schema Generator SSL Setup Tool Certificate Management Tool Dynamic Connect Intercall U2 DBTools U2 Basic Developer Toolkit U2 EDA Replication Configuration Tool U2 EDA Schema Manager U2 Extensible Administration Tool (XAdmin) U2 Metadata Manager U2 RESTful Web Services Developer U2 XML/DB Mapping Tool These two packages are all available for public download from RBC | Rocket Software - just choose : Resources  Product Availability Choose the Product and 'Search',  either for U2 DBTools or U2 Clients (these will always show as for Windows, though the JAVA clients are multi-platform) Use the 'Product' link under the 'Downloads' column for the version required - this will usually be the latest version. You will now have options to download the Product - which includes the Documentation - or the Documentation only, All Documentat