What are some common commands and their syntax?

Common commands include those for starting and stopping the emulator, managing virtual devices, and monitoring system resources. The exact syntax depends on the specific operations being performed.

What are the main system components?

Soft390's architecture includes components for CPU emulation, I/O handling, and memory management. These components communicate through internal interfaces to simulate mainframe behavior.

What databases or storage mechanisms are used?

Soft390 uses a combination of file-based storage for configuration and potentially direct access to host system resources for emulated devices. The specific storage mechanisms depend on the host operating system.

What was the business value of Soft390?

Soft390 allowed organizations to run mainframe applications on less expensive hardware. This could reduce hardware costs. It also provided flexibility in terms of hardware choices.

How did Soft390 provide vendor independence?

Soft390 enabled organizations to continue using their mainframe applications without being tied to specific mainframe hardware. This provided a degree of vendor independence.

How did Soft390 impact application development?

By emulating the mainframe environment, Soft390 allowed for easier testing and development of mainframe applications. This could speed up the development lifecycle.

What authentication methods are supported?

Specific authentication methods supported by Soft390 are not detailed in available documentation. Security features were likely limited due to the product's age and focus on emulation.

What access control model is used?

The access control model used by Soft390 is not explicitly defined in available documentation. It likely relied on the host operating system's security features.

What encryption is used and where?

Encryption details are not available in the public documentation. Security features were likely limited due to the product's age and focus on emulation.

What audit/logging capabilities exist?

Audit and logging capabilities are not explicitly detailed in the available documentation. It likely relied on the host operating system's logging mechanisms.

What administrative interfaces are available?

Administrative interfaces likely included a command-line interface (CLI) for configuration and management tasks. A graphical user interface (GUI) may have been available.

How is user management handled?

User management was likely handled through the host operating system's user management tools. Soft390 would have relied on the host system for user authentication and authorization.

What monitoring/logging capabilities exist?

Monitoring and logging capabilities likely included the ability to monitor CPU usage, memory consumption, and I/O activity. Logs would have recorded system events and errors.

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

Soft390

Name: Soft390
Availability: InStock

IBM Not Supported z/OS

Operating System UNIX and Windows Emulation

Vendor

IBM

Product Overview

The Soft390 architecture comprised several key components designed to emulate the functionality of a System z mainframe on a UNIX host. The CPU emulation component was responsible for interpreting and executing z/Architecture instructions. The I/O handling component managed the interaction between the emulated system and virtual devices, such as disks and network interfaces.

The memory management component handled the allocation and deallocation of memory, simulating the mainframe's memory architecture. These components communicated through internal interfaces to simulate mainframe behavior. Configuration files, typically text-based, defined the emulated hardware environment, including CPU configuration, memory allocation, and device definitions.

For example, a configuration file might specify the number of CPUs to emulate and the amount of memory to allocate. The system relied on the host operating system for underlying services, such as file storage and network communication. Due to the product's end-of-life status, detailed architectural diagrams and specifications are not readily available.

Organizations should consider alternative solutions for mainframe emulation or re-platforming.

Frequently Asked Questions

What is Soft390?

Soft390 emulates System z mainframes on UNIX systems. It allows users to run z/OS applications on different hardware. The product is no longer supported by IBM.

When was Soft390 first released, and when did sales end?

Soft390 was initially released in 1997. IBM acquired Platform Solutions in 2008, which led to the end of sales for Soft390.

What architecture does Soft390 emulate?

Soft390 emulates the Amdahl ESA/390 architecture. This allows it to run z/OS applications. It provides a way to run mainframe workloads on alternative hardware.

Is Soft390 still supported?

Soft390 is no longer supported. IBM does not provide updates or technical assistance for this product.

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

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

Are You a Vendor? Claim Your Listing

Soft390

Product Overview

Frequently Asked Questions

What is Soft390?

When was Soft390 first released, and when did sales end?

What architecture does Soft390 emulate?

Is Soft390 still supported?

What are some common commands and their syntax?

What configuration files are used?

What are the main system components?

What databases or storage mechanisms are used?

What was the business value of Soft390?

How did Soft390 provide vendor independence?

How did Soft390 impact application development?

What authentication methods are supported?

What access control model is used?

What encryption is used and where?

What audit/logging capabilities exist?

What administrative interfaces are available?

How is user management handled?

What are the main configuration parameters?

What monitoring/logging capabilities exist?

Related Products

More from IBM

Access 1

ACF/NCP

ACF/SSP

ACO SolutionPac

Ada/370

ADF II

Similar Products

(E)JES

3270Link

3770Link

3780Link

4Tune

ACC

Help Improve This Directory

Are You a Vendor? Claim Your Listing