SGCO Logo

What is SGCO OpenVMS RMS API?

The Stirling & Young Group's OpenVMS RMS API is the first ever API designed to give your applications direct access to your RMS / RDB data files in real time. The SGCO API is a JSON-based RESTful API Installed on your VMS server which then listens for incoming JSON requests and then interacts with your RMS or RDB files. Solutions based on competing tools, such as Attunity Connect and Connx, require data synchronization. SGCO API is the only OpenVMS RMS API which offers real-time data.


Interact REALTIME with your RMS / RDB data. The Stirling API enables your external application to: INSERT * READ * UPDATE * DELETE records in your RMS data files or RDB tables in real time. RMS functionality includes file and record locking and all data types including binary as both keys and members of compound keys.

SGCO OpenVMS RMS / RDB RESTful JSON API. Simple access to RMS / RDB data. No ODBC. No more trying to pretend that RMS is a SQL database! Use your RMS files like RMS files to create remote GUI type apps that interact real time with RMS. Alpha or Itanium (no need to downgrade back to Alpha for emulation) 100% native OpenVMS and licensing 80% less than other less efficient or no longer supported solutions.

If your company is looking to migrate OpenVMS applications to Windows, Linux or the cloud we may offer a better alternative. The SGCO OpenVMS RMS / RDB RESTful API is a Qlik Replicate alternative, Don’t replicate access your RMS files Realtime. Modernization solution & services for every layer of your OpenVMS. OpenVMS modernization for web, mobile or BI dashboards now available directly by using SGCO OpenVMS RMS / RDB RESTful JSON API.

If you are looking for an alternative from Attunity Connect based systems or Connx we can help.

The Stirling API OpenVMS RMS / RDB RESTful Dynamic API that enables you to implement the Windows, Web, and Mobile (Android / iOS) style GUI applications that your users want while still delivering the robust performance and proven reliability you’ve come to depend on from your OpenVMS/RMS systems.

As an OpenVMS professional, we’re confident you will immediately appreciate the unlimited opportunities this new API can mean for your existing system. With the ability to insert, read, update, and delete OpenVMS records in real-time, your OpenVMS system can communicate instantly with dashboards, web applications/portals, mobile devices, reporting services, even report templates.

Lightweight

The major design concern in architecting our API was to be lightweight and efficient. The competing solutions put an unnecessary load onto the host computer resulting in the need to upgrade hardware to compensate. This is turn leads to more issues and a cycle of constant hard to identify problems.

Our API is the only 100% native to OpenVMS API on the market. The web service will listen on the OpenVMS box on any assigned ports either HTTP or HTTPS as well as running multiple instances. On multiple ports so that you can have a prod instance on 443 SSL and a dev instance on 8443. The API uses config files to pass command line arguments so that sections of the JSON config file can point to different locations for RMS data (again a prod instance and dev instance with prod pointing to the prod data and the dev pointing to the test data).Our API consists of only a very small application the runs detached on the OpenVMS OS. It accepts JSON input via posts to a listener that can be assigned to any port, processes that input, performs the requested tasks on the data and returns and necessary response.

The Stirling API is ideal for user authentication and custom content filtering based on user ID or other user characteristics. The Stirling API also plays well with others by interacting seamlessly with other APIs.

The fact that it is 100% native gives you the flexibility to hit the web service with any standard JSON call from anywhere. Unlike Attunity Connect and Connex you are. Not limited to connecting only from their client server solution. We have used out API in many different environments from Web Based cloud portals to iOS apps, MS Power BI and other dashboards, and syncing large amounts of data from and to external databases. Again 100% native on OpenVMS. There is very little load on the OpenVMS box as well once the RMS files have been tuned with the needed indexing. This is an important step that is skipped open by the other solutions but makes a huge performance difference. A recent use case for inserting large amounts of data vie the API with JSON calls gives up to 3,000 records per second performance.

API Grid


API Chart

Dynamic:

Because it is dynamic, the Stirling API eliminates the multi-step process of creating copies of your data files, a requirement for other solutions. No duplicate of data or duplication of effort.

We all pay great attention to having granular control over the functionality of all levels of record and row locking.

Secure:

Our API is by design as secure as possible. The API is not only limited to accept only properly structured JSON input but will only accept input stings that are structurally compatible with the target RMS file. This prevents the API from blindly accepting possibly dangerous input.

Security may also be further enhanced by front ending the API using a second network interface on the host OpenVMS box onto a dedicated LAN with two other entities: A PCI compliant - WAF enabled reverse proxy and a Cisco 5500 series firewall. The Cisco 5500 provides further traffic management as well as the ability to add Cisco Firebox IDS functionality.

It should be noted that this is addressing only the security of the API and that security for the remote applications that manipulate the RMS filesystem via the API are a separate and equally important issue.


Connect your OpenVMS data files to any external file or report source including:
  • Business Intelligence applications such as dashboards,
  • Web services such as sales/vendor portals, customer portals,
  • Mobile device applications/portals,
  • Spreadsheet report templates,
  • Any Dynamic Reporting Service(s).

How does Open VMS RMS API Work?

SGCO OpenVMS RMS API runs on your own infrastructure. The API is installed to your VMS Server or Server Cluster, and depending on your requirements it can be connected to your intranet solutions, or even to your web app server. Here is one example of a solution using OpenVMS RMS API:

OpenVMS API Diagram

The Stirling API is ideal for user authentication and custom content filtering based on user ID or other user characteristics. The Stirling API also plays well with others by interacting seamlessly with other APIs.

The Stirling API is the latest addition to a full suite of mission critical products which include: custom PDF Conversion system, document management system, and RFID asset Tracking systems. The Stirling API is now available for installation on your VMS system. For pricing, licensing, or other product information contact: The Stirling Young & Murch Group LLC, at info@sgco.com.

See PRODUCT INFORMATION API HIGHLIGHTS

See OPENVMS API

See TECHNICAL QA API

See OpenVMS / RMS API Demo

API UpdatesNEWS and Updates

OpenVMS RESTful API update: Recent additions to our API have included server and all modules distributed compiled (huge performance increase), passing file and row locking parameters, multi-step insert/update routine and a few others. This OpenVMS RESTful API runs 100% native on VAX, Alpha and Itanium with no slinging data to MSSql! - July 2019




OpenVMS Restful API performance tuned new module returns search results 5k records per second! Native and very lightweight. No more slinging data to MSSql. - June 2019




SGCO OpenVMS RESTful API latest: query (search) tuned to 150,000 records returned in 20 sec, insert / update 10,000 records with local decision to insert or update (no DUP key, row lock when update) in 1 min. - May 2019




“SGCO OpenVMS RESTful API: One of the more unexpected uses for our API has been keeping RMS databases in sync real time during development of the transition of RMS data to other platforms.” - May 2019




OpenVMS RMS RESTful API: It’s amazing what tuning can do when you have to. Tuning end to end we can query RMS and returnover the wire JSON for 1m records in 70 seconds and insert 10k records in 25 seconds. - May 2019




SGCO OpenVMS RESTful API query (search) tuned to 150,000 records returned in 20 seconds, insert / update 10,000 records with local decision to insert or update )no DUP key, row lock when update) in 1 min - April 2019




SGCO OpenVMS RESTful API new module perf tuned returns JSON array of search results 5k records per second! 100% native OpenVMS. - April 2019




SGCO OpenVMS RESTful API update: Recent addiions to our API have included server and all modules distributed compiled, passing file and row locking parameters and multi-step insert/update. API runs 100% native on VAX Alpha and Itanium with no sling data to MSSql. – April 2019




SGCO OpenVMS RESTful API now distributed and run as a compiled Python extension. 300% performance increase – February 2019




SGCO OpenVMS RESTful API update: We just completed the ability to fully interact with binary field types for complete CRUD functionality including simple and compound binary indexes. – February 2019




OpenVMS RMS RestFul JSON API update: We just completed the ability to fully interact with binary field types for complete CRUD functionality including simple and compound binary indexes. hashtag#json hashtag#openvms hashtag#api. - July 2018