What are the common commands and syntax used in Eclipse iCopy?

Common operations include creating full image copies, incremental copies, and utilizing the FastCopy feature. The syntax involves JCL statements to define input datasets, output datasets, and control parameters. Configuration relies on JCL and control cards.

What APIs or integration points does Eclipse iCopy offer?

Eclipse iCopy primarily interacts with DFSMSdss for its FastCopy feature, leveraging its concurrent copy capabilities. It does not expose APIs for external integration.

What is the architecture of Eclipse iCopy?

The main components include the JCL interface, the copy engine, and the DFSMSdss interaction layer. These components communicate through JCL and system services. Data is stored on DASD volumes. There are no specific network ports required.

How is Eclipse iCopy administered?

Administration is performed through JCL and system console commands. User management is handled through z/OS security mechanisms. Configuration parameters are defined in JCL control cards. Monitoring and logging are provided through system logs and job output.

What business value did Eclipse iCopy provide?

Eclipse iCopy provided high-speed image copy capabilities, reducing the time required for backup and recovery operations. The FastCopy feature, utilizing DFSMSdss, was a key differentiator.

What were the key benefits of using Eclipse iCopy?

The primary benefit was improved backup and recovery times for IMS databases. This minimized downtime and data loss risks.

What were the key differentiators of Eclipse iCopy?

The FastCopy feature, which leveraged DFSMSdss, was a significant advantage, enabling concurrent copying and reducing the impact on IMS database availability.

What security features were available in Eclipse iCopy?

Eclipse iCopy relied on z/OS security features for access control. Specific authentication methods were not explicitly defined within the product itself, but rather inherited from the z/OS environment.

How was access control and encryption handled?

Access control was managed through the z/OS security model, which typically includes features like RBAC (Role-Based Access Control). Encryption was handled at the storage level by DFSMS, not within iCopy itself.

What audit and logging capabilities were available?

Audit and logging capabilities were provided through z/OS system logs and job output. These logs captured information about copy operations and any errors encountered.

How were operations performed with Eclipse iCopy?

Operations involved submitting JCL jobs to perform image copy operations. Monitoring was done through system logs and job output. There were no specific operational interfaces beyond the z/OS console.

What were the key operational considerations?

Performance tuning involved optimizing JCL parameters and leveraging DFSMSdss features. Capacity planning was based on the size of the IMS databases and the frequency of image copy operations.

How was troubleshooting handled?

Troubleshooting involved examining system logs, job output, and DFSMSdss messages. Common issues included dataset allocation problems and errors during the copy process.

Share Your Product Experience

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

Share Your Experience

Eclipse iCopy

BMC Not Supported z/OS

IMS Backup and Restore Databases

Vendor

BMC

Product Overview

The architecture of Eclipse iCopy comprised several key components. The JCL interface served as the primary point of interaction, allowing users to define copy operations. The copy engine was responsible for managing the copy process, including reading data from the input datasets and writing it to the output datasets.

The DFSMSdss interaction layer was crucial, as it enabled the FastCopy feature, which utilized DFSMSdss concurrent copy facilities for improved performance. Data storage was on DASD volumes. The communication between components was primarily through JCL and system services.

There were no specific network ports required. The product's design focused on efficiency and speed, leveraging the capabilities of DFSMSdss to minimize the impact on IMS database availability. The lack of support necessitates a migration to a supported solution, such as BMC AMI Copy for IMS or IBM IMS Database Recovery Facility, which offer similar architectural designs and features.

Frequently Asked Questions

What is Eclipse iCopy, and what is its primary function?

Eclipse iCopy is a high-speed image copy utility designed for IMS databases on z/OS. It facilitates the creation of image copies, which are crucial for backup and recovery operations. The utility leverages DFSMSdss concurrent copy facilities for enhanced performance.

What is the history of Eclipse iCopy?

Eclipse iCopy was initially part of the Eclipse Reorganization Utilities suite. It was later acquired by BMC. The product's development and support have since been discontinued.

What platforms and databases does Eclipse iCopy support?

The utility is designed to work with IMS databases on the z/OS platform. It is not compatible with other database systems or operating environments.

Is Eclipse iCopy still supported?

Eclipse iCopy is no longer supported by BMC. Users should explore alternative solutions for IMS image copy and backup operations.

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

Share Your Product Experience

Eclipse iCopy

Product Overview

Frequently Asked Questions

What is Eclipse iCopy, and what is its primary function?

What is the history of Eclipse iCopy?

What platforms and databases does Eclipse iCopy support?

Is Eclipse iCopy still supported?

What are the common commands and syntax used in Eclipse iCopy?

What APIs or integration points does Eclipse iCopy offer?

What is the architecture of Eclipse iCopy?

How is Eclipse iCopy administered?

What business value did Eclipse iCopy provide?

What were the key benefits of using Eclipse iCopy?

What were the key differentiators of Eclipse iCopy?

What security features were available in Eclipse iCopy?

How was access control and encryption handled?

What audit and logging capabilities were available?

How were operations performed with Eclipse iCopy?

What were the key operational considerations?

How was troubleshooting handled?

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