Welcome to the EzNoSQL for z/OS® content solution, your first stop for learning about IBM's EzNoSQL solution. Use it to improve your application design by creating JSON key:value databases on z/OS and take advantage of the advanced data sharing capabilities provided by IBM® Parallel Sysplex® technology.
With EzNoSQL you can easily create and access JSON databases through a comprehensive set of C-based APIs. The data can be shared from multiple application instances running on different processors, and EzNoSQL provides all the necessary serialization to protect the data.
Worried about having to code for eventual consistency with traditional NoSQL databases? Not with EzNoSQL’s single instance of the data. Data integrity and performance are met with EzNoSQL’s store-through caching design, in-memory buffering, and easy horizontal scaling. Let EzNoSQL be the database of choice to meet the growing demands of your application.
EzNoSQL is available on z/OS 2.4 and above with APAR OA62553.
Before creating your first EzNoSQL database on z/OS, ensure the proper system configuration is available to your application. If the required configuration is not available, help from the z/OS system administrators will be required to complete the setup.
Once the proper configuration is available, customize and execute the sample C program found in the system’s z/OS UNIX System Services (z/OS UNIX) directory: /samples/IBM/igwznsqsamp1.c. Any necessary customization steps are documented in the prolog of the sample program.
If the sample program successfully executes, you are now ready to design your own application using EzNoSQL. Refer to the documentation below for a detailed explanation of the APIs and the database features.
EzNoSQL requires at least one z/OS 2.4 image with APAR OA62553 installed and running in sysplex mode. Sysplex mode requires at least one internal or external coupling facility (CF). For better availability, configure more than one z/OS image and CF.
Initialize the SMSVSAM server address space on each z/OS instance in the sysplex or required by the application architect. If transactional consistency is required, enable the DFSMS transaction server (DFSMSTVS).
Ensure the availability of one or more SMS storage classes (STORCLAS) which contain a RLS CACHESET with the name of a valid CF cache structure. The STORCLAS names can be provided to the application architect or assigned by the SMS ACS routines.
Optionally ensure the availability of one or more SMS data classes (DATACLAS) which contain database attributes such as data compression, encryption, 64-bit buffering, and do on. The DATACLAS names can be provided to the application architect or assigned by the SMS ACS routines.
The application architect verifies the configuration.
- Customize and execute the sample C program to verify the EzNoSQL configuration is available and to become familiar with some of the APIs.
The sample program can be found in the system’s z/OS UNIX directory, /samples/IBM/igwznsqsamp1.c.
- Perform customization steps that are documented in the prolog of the sample program.
- Refer to the documentation to Learn about the database features and the available APIs.
EzNoSQL Overview and API Reference
Documentation, presentations, and more
Send us your ideas, vote or comment on ideas, and more! Add your idea under product IBM Z and operating System z/OS, then select category DFSMS EzNoQSL.
A link to the IBM Ideas portal, for submitting requests for enhancements, was added to the Technical resources section.