Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

MVS Direct API

C-Cubed Active z/OS

Legacy Application/Data Access Application Development

Vendor

C-Cubed

Product Overview

The architecture of MVS Direct API comprises several key components. The Client Application initiates requests and interacts with the MVS Direct API Server. The Server acts as the intermediary, handling communication with the mainframe.

The Communication Layer, supporting SNA or TCP/IP, ensures reliable data transfer. The Mainframe Application Interface facilitates interaction with mainframe resources. The API exposes native APIs for direct integration, with methods like SubmitJob, CallProgram, ReadDataset, and WriteDataset.

The API uses a user-based permission model for access control. Encryption is used to secure data transmission. Administrative interfaces include a CLI and potentially a GUI.

Monitoring capabilities track system performance and resource usage. The API supports various mainframe applications, such as CA 7, CA Endevor, and CA Spool. The API's design prioritizes direct access to mainframe resources, streamlining integration and improving operational efficiency.

The API's audit and logging capabilities provide essential insights into system usage and security.

Frequently Asked Questions

What is MVS Direct API used for?

undefined

MVS Direct API enables PC-based applications to access mainframe applications and data. It provides a bridge for modern applications to interact with legacy systems, facilitating tasks such as job submission, program calls, and dataset management. This allows for integration between different computing environments.

undefined

What types of mainframe applications can be accessed?

undefined

MVS Direct API supports access to a variety of mainframe applications. This includes core functionalities like job submission and program calls, as well as optional support for CA 7, CA Endevor, CA Spool, CA Top Secret, and CA View. It also supports access to Info/man.

undefined

What communication protocols are supported?

undefined

MVS Direct API supports both SNA and TCP/IP communication protocols. This flexibility allows it to integrate with different network environments and ensures compatibility with a wide range of systems.

undefined

What non-mainframe application environments are supported?

undefined

MVS Direct API supports integration with several non-mainframe application environments. These include C-Cubed MVS Portal, Microsoft .NET, Microsoft ASP, Microsoft Office, Fujitsu PowerCOBOL, COBOL97, MicroFocus COBOL, and Windows COM. This broad support enables diverse application integration.

undefined

What are the main system components?

undefined

The main system components include the Client Application, the MVS Direct API Server, the Communication Layer (SNA or TCP/IP), and the Mainframe Application Interface. These components work together to facilitate communication and data transfer between PC-based applications and mainframe systems.

undefined

What types of APIs does MVS Direct API expose?

undefined

MVS Direct API exposes native APIs for direct integration. These APIs allow developers to incorporate mainframe access functionality directly into their applications, providing a streamlined approach to data exchange and program execution.

undefined

What are some example API endpoint patterns?

undefined

API endpoint patterns include methods for job submission (e.g., SubmitJob), program calls (e.g., CallProgram), and dataset management (e.g., ReadDataset, WriteDataset). These methods provide the core functionality for interacting with mainframe resources.

undefined

What programming languages and SDKs are supported?

undefined

MVS Direct API supports integration with various programming languages and environments. This includes support for Microsoft .NET, Microsoft ASP, and Windows COM, enabling developers to use their preferred tools for application development.

undefined

What are the main configuration parameters?

undefined

Main configuration parameters include settings for communication protocols (SNA or TCP/IP), mainframe system addresses, user authentication details, and dataset access permissions. These parameters are essential for establishing and maintaining secure connections.

undefined

What business problems does MVS Direct API solve?

undefined

MVS Direct API solves the problem of integrating modern applications with legacy mainframe systems. It enables businesses to leverage existing mainframe investments while developing new applications, reducing the need for costly mainframe modernization projects.

undefined

How does MVS Direct API improve efficiency?

undefined

By providing direct access to mainframe resources, MVS Direct API streamlines data exchange and program execution. This reduces manual processes and accelerates workflows, leading to improved operational efficiency.

undefined

What are the key benefits of using MVS Direct API?

undefined

Key benefits include reduced development time, lower integration costs, and the ability to extend the life of mainframe applications. It allows businesses to modernize their IT infrastructure without a complete overhaul.

undefined

What use cases are common for MVS Direct API?

undefined

Common use cases include accessing mainframe data from web applications, integrating mainframe processes into business workflows, and enabling mobile access to mainframe applications. These use cases highlight the versatility of the API.

undefined

What authentication methods are supported?

undefined

MVS Direct API supports user authentication through various methods. These include username/password authentication, which is a standard approach for verifying user identities. The specific methods available depend on the configuration and security policies.

undefined

What access control model is used?

undefined

The access control model typically involves user-based permissions and potentially role-based access control (RBAC). This model ensures that users only have access to the resources and functions they are authorized to use.

undefined

What encryption is used?

undefined

Encryption is used to secure data transmission between the client application and the MVS Direct API Server. This protects sensitive information during transit, ensuring data confidentiality and integrity. The specific encryption methods depend on the communication protocol used (SNA or TCP/IP).

undefined

What audit/logging capabilities exist?

undefined

MVS Direct API includes audit and logging capabilities to track user activities and system events. This allows administrators to monitor system usage, identify potential security breaches, and ensure compliance with security policies.

undefined

What administrative interfaces are available?

undefined

Administrative interfaces typically include a Command Line Interface (CLI) for scripting and automation, and potentially a Graphical User Interface (GUI) for easier management. These interfaces provide tools for configuring and monitoring the API.

undefined

How is user management handled?

undefined

User management is typically handled through the administrative interfaces, allowing administrators to create, modify, and delete user accounts. User authentication and authorization are also managed through these interfaces.

undefined

What monitoring capabilities exist?

undefined

Monitoring capabilities include the ability to track system performance, monitor resource usage, and view logs of system events. These features help administrators ensure the API is running smoothly and efficiently.

undefined

What are the network requirements?

undefined

Network requirements include the need for a stable network connection between the client application and the MVS Direct API Server. The specific ports required depend on the communication protocol used (e.g., TCP/IP ports). Firewall configurations must allow traffic on these ports.

undefined

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

Are You a Vendor? Claim Your Listing

MVS Direct API

Product Overview

Frequently Asked Questions

What is MVS Direct API used for?

undefined

undefined

What types of mainframe applications can be accessed?

undefined

undefined

What communication protocols are supported?

undefined

undefined

What non-mainframe application environments are supported?

undefined

undefined

What are the main system components?

undefined

undefined

What types of APIs does MVS Direct API expose?

undefined

undefined

What are some example API endpoint patterns?

undefined

undefined

What programming languages and SDKs are supported?

undefined

undefined

What are the main configuration parameters?

undefined

undefined

What business problems does MVS Direct API solve?

undefined

undefined

How does MVS Direct API improve efficiency?

undefined

undefined

What are the key benefits of using MVS Direct API?

undefined

undefined

What use cases are common for MVS Direct API?

undefined

undefined

What authentication methods are supported?

undefined

undefined

What access control model is used?

undefined

undefined

What encryption is used?

undefined

undefined

What audit/logging capabilities exist?

undefined

undefined

What administrative interfaces are available?

undefined

undefined

How is user management handled?

undefined

undefined

What monitoring capabilities exist?

undefined

undefined

What are the network requirements?

undefined

undefined

Related Products

More from C-Cubed

Similar Products

Help Improve This Directory

Share Your Product Experience