What are some of the most common commands used in Eclipse iRecover?

Common commands include 'RECOVER', 'RESTORE', and 'VERIFY'. The 'RECOVER' command initiates the database recovery process using image copies. The 'RESTORE' command is used to restore the database to a specific point in time. The 'VERIFY' command checks the integrity of the image copies.

Can you provide examples of the command syntax?

The syntax for the 'RECOVER' command is typically: RECOVER DATABASE(db_name) FROMCOPY(copy_dataset) TO_TIME(timestamp). The 'RESTORE' command syntax is: RESTORE DATABASE(db_name) TO_TIME(timestamp). The 'VERIFY' command syntax is: VERIFY COPY(copy_dataset).

What configuration files or interfaces are used?

Configuration is managed through JCL and control cards. JCL is used to define the datasets and allocate resources. Control cards specify parameters such as database names, copy datasets, and recovery options. These files are essential for defining the recovery process.

What types of APIs does this product expose?

The product interacts with IMS through its APIs. These APIs allow it to interface with IMS databases. The specific API calls are used to initiate and manage the recovery process. The APIs are used to read and write data to the IMS databases.

What was the primary business value of using Eclipse iRecover?

Eclipse iRecover aimed to reduce database downtime during recovery. By providing faster recovery times, it helped minimize the impact of data loss or corruption on business operations. This was a key benefit for organizations relying on IMS databases.

How did Eclipse iRecover improve upon existing solutions?

The product offered improved recovery times compared to native IMS utilities. This faster recovery capability helped reduce the duration of outages. The ability to quickly restore databases was a significant advantage.

What impact did Eclipse iRecover have on data availability?

By minimizing downtime, Eclipse iRecover helped maintain data availability. This was critical for applications that required continuous access to data. The product's ability to quickly restore databases contributed to overall system reliability.

What authentication methods are supported?

The product's security features are limited. It relies on the underlying z/OS security mechanisms for authentication and access control. It does not provide its own authentication methods.

What access control model is used?

Access control is managed through z/OS security features, such as RACF or similar security products. These systems control access to datasets and resources used by Eclipse iRecover. The product itself does not have its own access control model.

What encryption is used and where?

Encryption is not a core feature of Eclipse iRecover. The product relies on the encryption capabilities provided by z/OS and the underlying storage systems. Data encryption is handled at the storage level.

What audit/logging capabilities exist?

Auditing and logging are handled through z/OS system logs. The product generates log entries that can be used for auditing. These logs provide information about the recovery operations performed.

What administrative interfaces are available?

The primary administrative interface is through JCL and control cards. Administrators use JCL to define datasets and allocate resources. Control cards are used to specify parameters for recovery operations. There is no GUI or web console.

How is user management handled?

User management is handled through the z/OS security system, such as RACF. Access to the product's resources is controlled through the z/OS security configuration. The product does not have its own user management system.

What are the main configuration parameters?

Key configuration parameters include database names, copy dataset locations, and recovery options. These parameters are specified in the JCL and control cards. Proper configuration is essential for successful recovery.

What monitoring/logging capabilities exist?

Monitoring and logging are primarily handled through z/OS system logs. The product generates log entries that provide information about the recovery process. These logs are used to monitor the status of recovery operations.

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

Eclipse iRecover

Name: Eclipse iRecover
Availability: InStock

BMC Not Supported z/OS

Databases Backup and Restore IMS

Vendor

BMC

Product Overview

The architecture of Eclipse iRecover comprised a recovery engine, an IMS interface, and a JCL processing component. The recovery engine handled the restoration of IMS databases from image copies. The IMS interface facilitated communication with IMS.

The JCL processing component parsed and executed JCL and control cards. The components communicated through z/OS system services. The product used IMS databases and z/OS datasets for storage.

There were no specific network ports required. The product is no longer supported. The recommended alternative is BMC AMI Recover for IMS, which offers similar functionality with enhanced features and support.

The migration involves reconfiguring backup and recovery processes using the new tools. The API endpoint patterns are not available, as the product is not supported.

Frequently Asked Questions

What is the primary function of Eclipse iRecover?

Eclipse iRecover is designed for high-speed recovery of IMS databases from image copies. It provides capabilities to restore databases to a consistent state following data corruption or system failures. The product focuses on minimizing downtime during the recovery process.

What is the history of Eclipse iRecover?

The product was initially developed by NEON Enterprise Software and later acquired by BMC. It was designed to address the need for faster IMS database recovery compared to native IMS utilities. The acquisition by BMC expanded its integration capabilities within the BMC product suite.

What is the current support status of Eclipse iRecover?

Eclipse iRecover is no longer actively supported. Users should consider alternative solutions that offer similar functionality. The product's capabilities are now available in other BMC products or third-party solutions.

What platforms does Eclipse iRecover support?

The product was designed to work with IMS databases on the z/OS platform. It leverages the underlying z/OS system to perform recovery operations. The specific integration points with IMS and z/OS are key to its 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

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

Eclipse iRecover

Product Overview

Frequently Asked Questions

What is the primary function of Eclipse iRecover?

What is the history of Eclipse iRecover?

What is the current support status of Eclipse iRecover?

What platforms does Eclipse iRecover support?

What are some of the most common commands used in Eclipse iRecover?

Can you provide examples of the command syntax?

What configuration files or interfaces are used?

What types of APIs does this product expose?

What was the primary business value of using Eclipse iRecover?

How did Eclipse iRecover improve upon existing solutions?

What impact did Eclipse iRecover have on data availability?

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 BMC

3270 SUPEROPTIMIZER/CICS

3270 SUPEROPTIMIZER/IMS

Administrative Assistant for DB2

Alter for DB2

Application Restart Control for DB2

Application Restart Control for IMS

Similar Products

3270 SUPEROPTIMIZER/IMS

ABARS/Assist

Access Manager for CICS

Access Manager for IMS

ADABAS

Adabas Delta Save

Help Improve This Directory

Are You a Vendor? Claim Your Listing