FAQs

Migrating OpenVMS System Internals: Locks, Transactions & Messaging

Sector7's VX/LCKMGR, VX/RTR, VX/DMQ, and VX/MSG ensure critical OpenVMS system-level functions like lock management, reliable transactions, and messaging queues operate seamlessly on Linux.

Reliable System Operations on Linux

Our VX/Tools replicate essential OpenVMS system internals, from high-speed lock management with VX/LCKMGR to reliable transaction routing with VX/RTR.

What is VX/DMQ and what does it do?
VX/DMQ is an asynchronous messaging solution that allows VMS and OpenVMS applications to use Oracle MQ for reliable, event-driven communication. It’s designed for organizations migrating from legacy DMQ/PAMS messaging to modern Linux environments, ensuring compatibility and minimal disruption.

If you want to see how similar migrations have helped major enterprises, check out our case study on Sprint (T-Mobile):
/case-studies/sprint-t-mobile

Have more questions? Contact us.
How does VX/DMQ handle asynchronous messaging on Linux?
VX/DMQ uses the VX/RT Asynchronous Backplane to provide event-driven messaging, even though Oracle MQ is synchronous by default. This means your applications can monitor message completion and maintain high performance without relying on legacy ASTs.

For a deeper dive into real-world results, see our Allianz migration case study.

Still have questions? Contact us.
What are the key features and benefits of VX/DMQ?
Some of the most important features of VX/DMQ include:
  • Full compatibility with the OpenVMS DMQ (PAMS) API set
  • Implementation on top of Oracle MQ for reliability and scalability
  • Enhanced support for Linux, including AST replacement mechanisms
  • Optimized for low-latency inter-process communication (IPC)
These features have enabled organizations like Amprion GmbH to modernize their infrastructure. Read more at /case-studies/amprion-gmbh.

Questions about your use case? Contact us.
What are common use cases for VX/DMQ?
Organizations use VX/DMQ to migrate DMQ-based applications from VMS/OpenVMS to Linux, replace legacy messaging with Oracle MQ, and enable high-performance messaging in multi-platform environments. For example, BNY Mellon leveraged similar migration strategies to modernize their financial systems: /case-studies/bny-mellon.

Want to discuss your scenario? Contact us.
How does VX/DMQ ensure a smooth migration from OpenVMS to Linux?
VX/DMQ intercepts and translates DMQ/PAMS calls to Oracle MQ functions, mimicking OpenVMS behavior. It provides asynchronous message queuing, persistence, priority queuing, and reliable delivery. VX/RT is used for event-driven processing, ensuring minimal latency and high compatibility.

For a real-world example of a smooth migration, see our AMCO migration case study.

Need migration advice? Contact us.
What is VX/RTR and how does it work?

VX/RTR enables seamless migration of OpenVMS RTRV2 applications to Linux RTRV3 by utilizing the VX/RT Asynchronous Backplane. It provides a transparent compatibility layer that ensures existing applications can run on modern Linux environments without code rewrites.

For a real-world example of successful RTR migration, see our Ford migration case study.

How does VX/RTR handle RTRV2 to RTRV3 migration?
VX/RTR fully maps RTRV2 API calls onto RTRV3, implementing VMS AST (Asynchronous System Trap) handling within Linux to ensure smooth transition without requiring code modifications.
What are the key features of VX/RTR?
Key features of VX/RTR include:
  • Full mapping of RTRV2 API calls to RTRV3
  • VMS AST handling implementation on Linux
  • Transparent compatibility layer for existing applications
  • Integration with VX/RT Asynchronous Backplane
How does VX/RTR integrate with other Sector7 tools?

VX/RTR integrates seamlessly with VX/RT APIs and the broader VX/RT ecosystem to provide comprehensive OpenVMS compatibility on Linux platforms.

How does VX/RTR ensure application compatibility?
VX/RTR ensures compatibility by providing a transparent layer that maintains all original RTRV2 behaviors and API responses, allowing applications to function identically on Linux as they did on OpenVMS.
What migration benefits does VX/RTR provide?
VX/RTR enables organizations to modernize their reliable transaction processing infrastructure while preserving existing application logic and reducing migration risk. This approach minimizes development costs and accelerates time-to-market for Linux deployment.
How can I get started with VX/RTR migration?

To learn more about VX/RTR and how it can streamline your OpenVMS RTR migration to Linux, contact us for a detailed assessment and migration roadmap.

What is VX/MSG and how does it help with VMS message migration?

VX/MSG is a VMS/OpenVMS message file compiler that translates message definitions (.msg) into indexed memory files on Linux, ensuring full compatibility with SYS$ API calls. It enables seamless application migration while preserving original messaging functionality and generates 3GL message constants for multiple programming languages including C, C++, BASIC, Fortran, COBOL, and PASCAL.

This tool simplifies VMS modernization by maintaining message-handling capabilities without requiring code modifications. Contact us to discuss your VMS message migration requirements.

Which programming languages does VX/MSG support for message constants?

VX/MSG generates message constants for C, C++, Fortran, COBOL, BASIC, and Pascal programming languages.

What SYS$ API calls are supported by VX/MSG?

VX/MSG provides full compatibility with VMS SYS$ API calls including SYS$GETMSG, SYS$FAO, and SYS$FAOL for message retrieval and formatting.

How does VX/MSG compile message files?

VX/MSG compiles VMS/OpenVMS message files (.msg) into indexed binary files (.dat and .idx), creating an efficient storage and retrieval system that mirrors the VMS SYS$MESSAGE system.

Can VX/MSG integrate with existing build processes?

Yes, VX/MSG integrates seamlessly into Linux build environments through makefile commands and standard build processes. It ensures messages are correctly compiled and deployed while maintaining message-handling functionality without application modifications.

Organizations like SEB have successfully integrated similar VMS modernization tools into their development workflows.

Does VX/MSG support message display and viewing?

VX/MSG supports message display via VX/DCL, allowing messages to be viewed and retrieved similarly to VMS environments.

What file formats does VX/MSG create for message storage?

VX/MSG creates an indexed file format consisting of .dat and .idx files that contain binary message data along with indexing information for fast retrieval, ensuring efficient message storage and access.

What are the key benefits of using VX/MSG for VMS migration?

VX/MSG provides a seamless, high-performance migration path for VMS/OpenVMS message systems to Linux. It ensures applications retain their original message-handling capabilities with full SYS$ API compatibility, efficient message storage, and minimal code modifications required.

The tool simplifies the migration process by automatically handling message compilation and generating language-specific constants, reducing development time and maintaining system reliability. Companies like IKEA have leveraged similar modernization strategies to successfully migrate legacy systems.

Ready to modernize your VMS message systems? Contact us to explore how VX/MSG can streamline your migration project.

What is VX/LCKMGR and how does it help with OpenVMS migrations?

VX/LCKMGR is a fully compatible OpenVMS lock management system designed for Linux environments. It ensures identical functionality to OpenVMS lock management while leveraging Sector7's high-speed AST backplane for enhanced performance.

This solution supports core OpenVMS lock manager functions like SYS$ENQ(W), SYS$DEQ(W), and SYS$GETLKI(), enabling seamless integration with existing OpenVMS applications during migration to Linux. Contact us to discuss your OpenVMS lock manager migration requirements.

What lock modes does VX/LCKMGR support?

VX/LCKMGR supports all major OpenVMS lock modes including Protected Read (LCK$K_PRMODE), Protected Write (LCK$K_PWMODE), Concurrent Read (LCK$K_CRMODE), Concurrent Write (LCK$K_CWMODE), Exclusive (LCK$K_EXMODE), and NULL (LCK$K_NLMODE).

How fast can VX/LCKMGR process lock operations?

In stress testing, VX/LCKMGR demonstrated exceptional performance by handling 80,000 lock conversions per second on a 1997-era quad-core Opteron server.

What $ENQ and $DEQ codes are supported?

VX/LCKMGR supports essential $ENQ/$DEQ codes including LCK$V_VALBLK (Value Block), LCK$V_CONVERT (Convert Lock), LCK$V_NOQUEUE (No Queue), LCK$V_SYNCSTS (Sync Status), LCK$V_SYSTEM (System Lock), and LCK$V_RECOVER (Recovery Mode).

How does VX/LCKMGR handle lock diagnostics and monitoring?

VX/LCKMGR provides comprehensive diagnostic capabilities including real-time lock request logging and replay functionality. The system can log all lock requests and replay them for performance tuning and diagnostic purposes.

Additionally, it offers real-time display of all lock requests, making it easier for system administrators to track lock statuses and manage resources effectively. Companies like Telstra have benefited from similar real-time monitoring capabilities during their OpenVMS migrations.

What $GETLKI information can be retrieved?

VX/LCKMGR supports $GETLKI codes for retrieving lock information including LKI$C_LENGTH (Lock Length), LKI$_BLOCKEDBY (Blocked By Lock), LKI$_BLOCKING (Blocking Lock), LKI$_LCKCOUNT (Lock Count), and LKI$_LOCKID (Lock ID).

Are there any limitations with VX/LCKMGR implementation?

VX/LCKMGR fully supports OpenVMS lock management functions but is limited to single-node environments. It does not operate across multiple nodes, which is important to consider when planning implementation in distributed systems.

What are the key benefits of migrating to VX/LCKMGR?

VX/LCKMGR delivers exceptional performance with high-speed lock processing capabilities and comprehensive diagnostic tools. Organizations gain full OpenVMS lock manager compatibility while moving to modern Linux environments.

The system provides advanced logging, real-time monitoring, and replay capabilities that help optimize performance and troubleshoot issues. This enables seamless migration from OpenVMS while maintaining all critical locking functionality.

Financial institutions like BNY Mellon have successfully leveraged similar OpenVMS migration strategies. To explore how VX/LCKMGR can support your specific migration requirements, contact our team for a detailed consultation.

Message Us
Email us with your queries and a team member will get back to you ASAP.
Call Us
Want to chat? Give us a call and we’ll answer all your questions.
Location
Prefer to visit? Sector7 is based in Austin, Texas.

Transform Your Legacy Software Today!

Get In Touch
Unlock the potential of your legacy software with our expert migration services.