Abstract: Methods and systems enable a database reorganization to occur without a database outage. In one aspect, the method includes creating a shadow copy of a database, the shadow having at least one partition associated with a plurality of first data sets and the database having at least a first partition associated with a plurality of second data sets and a second partition associated with a plurality of third data sets. The method also includes reorganizing the at least one partition of the shadow, taking the first partition offline, replacing the plurality of second data sets with the plurality of first data sets in a schema, and restarting the first partition.

Abstract: Methods and systems enable a database reorganization to occur without a database outage. In one aspect, the method includes pausing transactions directed to the database, keeping a logical view of the database online. The method may also include taking individual partitions offline, changing the names of datasets associated with the individual partitions in a database schema, and bringing the partitions online, all while the logical view of the database remains online. The database schema may be changed to reflect the name of datasets associated with a shadow copy of the database that has been reorganized.

Abstract: Methods and systems enable a database reorganization to occur without a database outage. In one aspect, the method includes pausing transactions directed to the database, keeping a logical view of the database online. The method may also include taking individual partitions offline, changing the names of datasets associated with the individual partitions in a database schema, and bringing the partitions online, all while the logical view of the database remains online. The database schema may be changed to reflect the name of datasets associated with a shadow copy of the database that has been reorganized.

Abstract: Methods and systems enable a database reorganization to occur without a database outage. In one aspect, the method includes pausing transactions directed to the database, keeping a logical view of the database online. The method may also include taking individual partitions offline, changing the names of datasets associated with the individual partitions in a database schema, and bringing the partitions online, all while the logical view of the database remains online. The database schema may be changed to reflect the name of datasets associated with a shadow copy of the database that has been reorganized.

Abstract: An IMS DEDB database restructure operation creates an empty offline DEDB having the desired structure. The offline database is populated with data from a source (online) database while keeping the source database online (i.e., available for access and update operations). Updates to the source database made during this process are selectively processed in parallel with the offline DEDB load operation. When the contents of the offline database is substantially the same as the source or online database, the source database is taken offline, final updates to the offline database are applied whereafter the offline database is brought online, thereby replacing the source database. It is significant to note that updates occurring to the source or online DEDB are applied to the offline DEDB.

Abstract: A method includes providing an application accelerator to an IMS region controller, which is coupled to an IMS data language interpreter (DL/I) interface. The IMS DL/I interface provides standard data access paths to a user application launched in an IMS environment. The application accelerator is configured to make alternate data access paths available to the user application in addition to the standard data access paths provided by the IMS environment. The method further includes intercepting an IMS DL/I call made by the user application and determining whether the intercepted call should be processed by the IMS DL/I interface or by an I/O engine of the application accelerator.

Abstract: A method includes providing an application accelerator to an IMS region controller, which is coupled to an IMS data language interpreter (DL/I) interface. The IMS DL/I interface provides standard data access paths to a user application launched in an IMS environment. The application accelerator is configured to make alternate data access paths available to the user application in addition to the standard data access paths provided by the IMS environment. The method further includes intercepting an IMS DL/I call made by the user application and determining whether the intercepted call should be processed by the IMS DL/I interface or by an I/O engine of the application accelerator.

Abstract: An IMS DEDB database restructure operation creates an empty offline DEDB having the desired structure. The offline database is populated with data from a source (online) database while keeping the source database online (i.e., available for access and update operations). Updates to the source database made during this process are selectively processed in parallel with the offline DEDB load operation. When the contents of the offline database is substantially the same as the source or online database, the source database is taken offline, final updates to the offline database are applied whereafter the offline database is brought online, thereby replacing the source database. It is significant to note that updates occurring to the source or online DEDB are applied to the offline DEDB.

Abstract: An IMS DEDB database restructure operation creates an empty offline DEDB having the desired structure. The offline database is populated with data from a source (online) database while keeping the source database online (i.e., available for access and update operations). Updates to the source database made during this process are selectively processed in parallel with the offline DEDB load operation. When the contents of the offline database is substantially the same as the source or online database, the source database is taken offline, final updates to the offline database are applied whereafter the offline database is brought online, thereby replacing the source database. It is significant to note that updates occurring to the source or online DEDB are applied to the offline DEDB.

Abstract: Methods and systems enable a database reorganization to occur without a database outage. In one aspect, the method includes pausing transactions directed to the database, keeping a logical view of the database online. The method may also include taking individual partitions offline, changing the names of datasets associated with the individual partitions in a database schema, and bringing the partitions online, all while the logical view of the database remains online. The database schema may be changed to reflect the name of datasets associated with a shadow copy of the database that has been reorganized.

Abstract: An IMS DEDB database restructure operation creates an empty offline DEDB having the desired structure. The offline database is populated with data from a source (online) database while keeping the source database online (i.e., available for access and update operations). Updates to the source database made during this process are selectively processed in parallel with the offline DEDB load operation. When the contents of the offline database is substantially the same as the source or online database, the source database is taken offline, final updates to the offline database are applied whereafter the offline database is brought online, thereby replacing the source database. It is significant to note that updates occurring to the source or online DEDB are applied to the offline DEDB.

Abstract: An enterprise data movement (EDM) system and method for more intelligently recording changes made to an IMS database. According to the present invention, when an application issues SETS/SETU and ROLS calls during the application's unit of work, the EDM system operates to create sub-units of work for identifying changes which correspond to the SETS/SETU and ROLS calls. This allows the EDM system to individually record or monitor the status of these changes, and either discard and/or commit the individual changes within that total application's unit of work, depending on the SETS/SETU and ROLS calls received.