What infrastructure is required?

Janus TCP/IP Base requires a Model 204 database and a TCP/IP network. It also needs the z/OS or z/VM operating system, depending on the deployment environment.

For mainframe products: Does this run in an LPAR?

Yes, for mainframe deployments, Janus TCP/IP Base runs in an LPAR under z/OS or z/VM. It is dependent on the operating system's TCP/IP stack.

Is this a standalone product or does it extend another product?

Janus TCP/IP Base extends the capabilities of Model 204 by providing TCP/IP connectivity. It requires Model 204 to be present to function.

What are the main system components?

The main system components include the server component running on the mainframe and the client component, which is often a C routine library. These components communicate using TCP/IP sockets.

What is the business value of using Janus TCP/IP Base?

Janus TCP/IP Base enables organizations to leverage their existing Model 204 databases in modern, distributed environments. This allows them to extend the life and value of their mainframe assets.

What would happen if an organization did NOT use this product?

Without Janus TCP/IP Base, organizations would need to find alternative ways to connect client applications to Model 204 databases, potentially involving more complex or less efficient solutions.

How does this product integrate with enterprise ecosystems?

Janus TCP/IP Base integrates with enterprise ecosystems by providing a standard TCP/IP interface to Model 204. This allows it to work with a wide range of client applications and middleware products.

What specific authentication methods are supported?

Janus TCP/IP Base supports standard authentication methods provided by the underlying operating system and Model 204. Specific methods include user IDs and passwords.

What access control model is used?

The access control model is typically based on the security mechanisms provided by Model 204, which often includes access control lists (ACLs) to control access to data and resources.

What encryption is used and where?

Encryption can be used to protect data in transit between the client and the Model 204 server. This is typically achieved using SSL/TLS over the TCP/IP connection.

What audit/logging capabilities exist?

Janus TCP/IP Base provides logging capabilities to track client connections and data access. These logs can be used for auditing and security monitoring.

How is this product typically deployed?

Janus TCP/IP Base is typically deployed on-premise, alongside the Model 204 database. It requires technical expertise to configure and maintain the TCP/IP connection and the C routine library.

What ongoing operational requirements exist?

Ongoing operational requirements include monitoring the TCP/IP connection, ensuring the Model 204 database is available, and maintaining the C routine library. Staffing requirements depend on the size and complexity of the environment.

What are common implementation challenges?

Common implementation challenges include configuring the TCP/IP network, ensuring compatibility between the client and server components, and managing security settings.

What administrative interfaces are available?

Administrative interfaces are typically command-line interfaces (CLIs) or configuration files. User management is handled through the Model 204 security system.

Share Your Product Experience

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

Share Your Experience

Janus TCP/IP Base

Rocket Software Active z/OS z/VM

Networks and Communication Databases

Vendor

Rocket Software

Product Overview

Janus TCP/IP Base provides client/server access to Model 204 databases over TCP/IP networks. It includes a C routine library, enabling distributed programs to communicate with Model 204 applications. The architecture consists of a server component running on the mainframe and a client component, typically the C routine library, which resides on the client system.

These components communicate using TCP/IP sockets. The server component listens for incoming connections from clients. When a client connects, the server authenticates the client and establishes a session.

The client can then send requests to the server, which processes the requests and returns the results. The C routine library provides functions for establishing connections, sending requests, and receiving responses. For example, `m204_connect()` establishes a connection, `m204_send()` sends a request, and `m204_receive()` receives a response.

Alternatives include other TCP/IP connectivity solutions, such as Janus Open Client and Janus Open Server. It requires a Model 204 database and a TCP/IP network.

Frequently Asked Questions

What does Janus TCP/IP Base do?

Janus TCP/IP Base provides client/server access to Model 204 databases over TCP/IP networks. It includes a C routine library, enabling distributed programs to communicate with Model 204 applications.

Is this a system, application, or tool?

Janus TCP/IP Base is middleware. It facilitates communication between client applications and Model 204 databases, acting as an intermediary layer.

What types of organizations use this?

Organizations that rely on Model 204 databases and require client/server access over TCP/IP networks use Janus TCP/IP Base. These are often large enterprises in industries like finance, insurance, and government.

When should we consider Janus TCP/IP Base?

A company should consider Janus TCP/IP Base when they need to enable client/server access to Model 204 databases, particularly when they have distributed applications that need to interact with Model 204.

What are the alternatives to Janus TCP/IP Base?

Alternatives include other TCP/IP connectivity solutions for Model 204, such as other middleware products or custom-built solutions. Janus Open Client and Janus Open Server are related products that can also provide similar functionality.

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

Share Your Product Experience

Janus TCP/IP Base

Product Overview

Frequently Asked Questions

What does Janus TCP/IP Base do?

Is this a system, application, or tool?

What types of organizations use this?

When should we consider Janus TCP/IP Base?

What are the alternatives to Janus TCP/IP Base?

What infrastructure is required?

For mainframe products: Does this run in an LPAR?

Is this a standalone product or does it extend another product?

What are the main system components?

What is the business value of using Janus TCP/IP Base?

What would happen if an organization did NOT use this product?

How does this product integrate with enterprise ecosystems?

What specific authentication methods are supported?

What access control model is used?

What encryption is used and where?

What audit/logging capabilities exist?

How is this product typically deployed?

What ongoing operational requirements exist?

What are common implementation challenges?

What administrative interfaces are available?

Related Products

More from Rocket Software

Similar Products

Help Improve This Directory

Share Your Product Experience