What are the common commands and their syntax?

Common commands include START, STOP, and REPORT. The syntax for starting a change accumulation job might be: `//RUNJCARD JOB ... //STEP EXEC PGM=ICHANGE,PARM='START'`. Configuration is managed through JCL and control cards, defining input datasets, output datasets, and processing options.

What configuration files or interfaces are used?

Eclipse iChange uses JCL (Job Control Language) for job submission and control cards for defining processing parameters. These control cards specify input and output datasets, selection criteria, and other operational settings. There are no exposed APIs.

What are the main system components?

The main system components include the Change Accumulation Engine, the Input Processor, and the Output Writer. The Change Accumulation Engine coordinates the overall process. The Input Processor reads and validates input data. The Output Writer formats and writes the accumulated change data.

What is the business value of using Eclipse iChange?

Eclipse iChange accelerates the change accumulation process compared to the IBM utility. This results in reduced batch window times and improved efficiency for database maintenance and recovery operations. It also provides more detailed reporting capabilities.

How does Eclipse iChange support business continuity?

By efficiently accumulating database changes, Eclipse iChange supports faster recovery times in case of data loss or corruption. This minimizes downtime and helps maintain business continuity.

How can Eclipse iChange help reduce costs?

The improved performance and reporting features of Eclipse iChange can lead to cost savings by reducing the time required for database maintenance tasks and providing better insights into database activity.

How does Eclipse iChange support auditing and compliance?

Eclipse iChange provides detailed reporting on database changes, which can be used for auditing purposes. This helps organizations meet compliance requirements and track data modifications.

What security features are available in Eclipse iChange?

Eclipse iChange does not have built-in security features like authentication or access control. Security is managed through the z/OS environment, including RACF or similar security products. Data encryption is not a feature of the product.

How is user management handled?

User management is handled through the z/OS security system, such as RACF. Eclipse iChange itself does not have its own user management interface.

What audit/logging capabilities exist?

Audit logging is primarily managed through the z/OS system logs and any logging configured within the IMS environment. Eclipse iChange itself does not provide specific audit logging capabilities.

What administrative interfaces are available?

Administration is primarily performed through JCL and control cards. There is no GUI or web console. Monitoring is typically done through z/OS system monitoring tools and reviewing job logs.

What are the main configuration parameters?

The main configuration parameters are defined in JCL and control cards. These parameters specify input datasets, output datasets, and processing options. There is no central configuration file.

What monitoring capabilities exist?

Monitoring is typically performed through z/OS system monitoring tools and by reviewing the job logs generated by Eclipse iChange. These logs provide information about job status, errors, and performance metrics.

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 iChange

Name: Eclipse iChange
Availability: InStock

BMC Not Supported z/OS

Tools and Utilities IMS Backup and Restore Databases

Vendor

BMC

Product Overview

The architecture of Eclipse iChange centers around the Change Accumulation Engine, which orchestrates the change accumulation process. The Input Processor reads and validates input data, while the Output Writer formats and writes the accumulated change data to VSAM datasets. The system interacts with IMS databases for change accumulation.

The primary interface is through JCL and control cards. There are no exposed APIs. Security is delegated to the z/OS environment, utilizing security products like RACF for authentication and access control.

Data encryption is not a feature. The system uses VSAM datasets for storing intermediate and output data. Network requirements are minimal, primarily for accessing datasets on shared storage.

Since Eclipse iChange is not supported, organizations should migrate to alternatives like BMC AMI Change Manager for IMS, which offers a similar architecture and functionality.

Frequently Asked Questions

What is Eclipse iChange?

Eclipse iChange is a high-speed change accumulation utility designed for IMS databases on z/OS. It replaces the IBM IMS change accumulation utility (DFSUCUM0) by providing faster processing and improved efficiency for managing IMS change data.

Who developed Eclipse iChange and who owns it now?

Eclipse iChange was initially developed by NEON Enterprise Software. BMC Software acquired NEON in 2011, and with that acquisition, they also acquired Eclipse iChange.

What is the main function of Eclipse iChange?

The primary function of Eclipse iChange is to accumulate changes made to IMS databases. This process involves capturing and storing database modifications, which is essential for backup and recovery operations, auditing, and data analysis.

What operating system does Eclipse iChange run on?

Eclipse iChange is designed to run on the z/OS operating system. It is specifically tailored to work with IMS databases within the z/OS environment.

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

Eclipse iChange

Product Overview

Frequently Asked Questions

What is Eclipse iChange?

Who developed Eclipse iChange and who owns it now?

What is the main function of Eclipse iChange?

What operating system does Eclipse iChange run on?

What are the common commands and their syntax?

What configuration files or interfaces are used?

What are the main system components?

What databases or storage mechanisms are used?

What is the business value of using Eclipse iChange?

How does Eclipse iChange support business continuity?

How can Eclipse iChange help reduce costs?

How does Eclipse iChange support auditing and compliance?

What security features are available in Eclipse iChange?

How is user management handled?

What audit/logging capabilities exist?

What administrative interfaces are available?

What are the main configuration parameters?

What monitoring 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

_beta access admin

_beta access audit

_beta access easy

_beta doc|z plus

_beta doc|z transform

(E)JES

Help Improve This Directory

Share Your Product Experience