Messages BMCDLP186800 through BMCDLP186899

This group includes messages for the BMC system administration family of products for IMS.
NumberDescription
BMCDLP186801W

BLDL failed for DMB in active ACBLIB concatenation


Explanation: A BLDL was performed against the active ACBLIB for a database (DMB) that is being added, revised, or reloaded but the member could not be located. The warning is indicated in the element and the application is marked as not initialized.

User response: Add the DMB to the active ACBLIB.

BMCDLP186802E

Member in active ACBLIB is not a valid DMB


Explanation: A BLDL was performed against the active ACBLIB for a database (DMB) that is being added, revised, or reloaded but the member found is not a valid DMB. The request is rejected.

User response: Ensure the name is correct and regenerate the DMB.

BMCDLP186804I

ACBLIB DMB specifies zero length buffer size


Explanation: The DMB read from the active ACBLIB for this database specifies a buffer size of zero, which is invalid. The element is processed, but the database will be marked as not initialized.

User response: Regenerate the DMB and reload the database.

BMCDLP186805W

FAST PATH MSDB set NOTINIT


Explanation: The DMB in the active ACBLIB for the database being added, revised, or reloaded indicates that it will become a FAST PATH main storage database (MSDB). The database will be added or revised as an MSDB but will not be usable until the next restart of IMS. The database is added but marked as not initialized (NOTINIT).

User response: No action is required.

BMCDLP186806E

ACBLIB DMB specifies FAST PATH but FAST PATH is not active


Explanation: The DMB read from the active ACBLIB indicates it is a FAST PATH database but FAST PATH is not genned. The element is rejected.

User response: Run an IMS gen to add FAST PATH to the system.

BMCDLP186807E

/DBR in progress for database


Explanation: /DBR processing is active for this database. The element is rejected.

User response: Wait until the /DBR completes and execute the request again.

BMCDLP186808E

/DBD in progress for database


Explanation: /DBD processing is active for this database. The element is rejected.

User response: Wait until the /DBD completes and execute the request again.

BMCDLP186809E

Database currently in use by resource


Explanation: This message is displayed for one or both of the following reasons:

  • The in-use count for this database (DDIRUSE) is not zero, indicating that it is in use by the indicated resource.

  • The DDIRRES (for Fast Path databases or MSDBs) is not zero, indicating that it is in use by the indicated resource.

The element is rejected.

User response: Perform /DBR processing and execute the request again. If the DDIRRES count is not zero, ensure that any FP interregion communication for IFP, WFI BMPs, and DBCTL threads is terminated, and execute the request again.

BMCDLP186810E

Database has open areas


Explanation: The database is a FAST PATH DEDB and has one or more areas currently open. The element is rejected.

User response: Perform /DBR processing and execute the request again.

BMCDLP186811E

Invalid action against FAST PATH MSDB


Explanation: Delete, revise, and reload operations are not allowed against FAST PATH main storage databases. The element is rejected.

User response: No action is required.

BMCDLP186812E

DEDB area statistics processing active, request cannot be completed at this time


Explanation: IMS processing, which gathers DEDB area statistics, is currently active; therefore, no action against DEDBs are allowed at this time. The element is rejected.

User response: Execute the request again at a later time.

BMCDLP186813E

DEDB area areaName is a duplicate


Explanation: One or more areas associated with this DEDB duplicate either existing areas or areas that are being added in this request. The element is rejected.

User response: Ensure that all DEDB area names are unique.

BMCDLP186814E

Error attempting to load compression routine routine


Explanation: An error occurred while trying to load the indicated compression routine from the STEPLIB concatenation. The element is rejected.

User response: Ensure that the compression routine exists in a library in the control region STEPLIB concatenation.

BMCDLP186815E

Error attempting to load randomizer routine routine


Explanation: An error occurred while trying to load the named randomizer routine from the STEPLIB concatenation. The element is rejected.

User response: Ensure that the randomizer routine exists in a library in the control region STEPLIB concatenation.

BMCDLP186816W

Unable to process RAND=YES, related database is not stopped


Explanation: The element being processed specified RAND=YES indicating that the randomizer used by this database should be reloaded and any other databases using the randomizer should be updated to use the new copy. One or more of the databases which use this randomizer, however, are currently in use. The randomizer is not reloaded. The database named in the element will use the copy of the randomizer already loaded.

User response: Perform /DBR processing on all of the databases that use this randomizer, and then reload one of the databases specifying RAND=YES.

BMCDLP186817E

Element is attempting to delete the last or only database defined in the system


Explanation: This element is attempting to delete the last database defined to this system. This is not allowed. The element is rejected.

User response: No action is required.

BMCDLP186818E

Database has at least one open data set


Explanation: The database that is being deleted, revised, or reloaded has at least one data set currently open. The element is rejected.

User response: Perform /DBR processing on the database and stop all areas before executing this request.

BMCDLP186819E

Database is not stopped


Explanation: The database being deleted, revised, or reloaded is not stopped. The element is rejected.

User response: Perform /DBR processing on the database and stop all areas before executing this request.

BMCDLP186820E

DEDB Database request failed and backed out due to errors encountered in PFX


Explanation: The FAST PATH DEDB being added, revised, or reloaded has failed because of errors encountered in PFX processing. The DELTA PLUS changes are backed out. The element is rejected. The database will be left in an NOTINIT state (not usable).

User response: Review the job log (control region and DLI/SAS) looking for any PFX messages for this database that describe the PFX error. Run the request again after fixing the PFX error. Contact BMC Customer Support, if needed.

BMCDLP186821E

PSB PSBname references this database and is not being reloaded or deleted


Explanation: The database being revised, reloaded, or deleted is currently referenced by the named PSB, which is not being reloaded or deleted. In order to ensure consistency between IMS resources, any time a database is altered, all associated PSB’s must be reloaded so that the in-core control blocks are updated.

User response: Provide reload elements for all programs that reference this database.

BMCDLP186822E

Error encountered allocating TOQ for chain, RC=returnCode


Explanation: An internal error has occurred while performing auto-reload processing for a database. The request is aborted.

User response: Take an SVC dump of your IMS system and contact BMC Customer Support.

BMCDLP186823E

Error encountered adding element to chain, RC=returnCode


Explanation: An internal error has occurred while performing auto-reload processing for a database. The request is aborted.

User response: Take an SVC dump of your IMS system and contact BMC Customer Support.

BMCDLP186824E

Error attempting to reload PSB PSBname


Explanation: The database element specifies the auto-reload option but an attempt to reload the named PSB failed. To ensure consistency between IMS resources, the action against the database is rejected because one of the associated PSBs could not be reloaded.

User response: Display the failing PSB and make sure it is not currently scheduled or a transaction associated with it does not have messages queued. You may need to stop the PSB before attempting the action again.

BMCDLP186825I

Database set NOTINIT due to backout processing


Explanation: This database was being deleted in this request, but an error caused the request to be backed out. The DMB for this database was purged from the DMB pool to prevent possible abends due to invalid information in the DDIR. This database was set to NOTINIT (DDIRCOD2, DDIRBAD). The DDIR is marked as not initialized.

User response: Determine the reason for the failure in this request, correct the problems, and execute the request again. In order to put this database back into a usable state, issue a RELOAD request against it.

BMCDLP186826E

Invalid action against a database partition


Explanation: The database being deleted, revised, or reloaded is a database partition. Actions are not allowed against HALDB partitions. The element is rejected.

User response: Perform /DBR processing on the HALDB master, then re-execute the action against the database.

BMCDLP186827E

Partitioned database is not stopped


Explanation: The partitioned database being deleted, revised, or reloaded is not stopped. The element is rejected.

User response: Perform /DBR processing on the HALDB master, then re-execute the action against the database.

BMCDLP186828E

Database is being recovered


Explanation: The partitioned database that is being deleted, revised, or reloaded is currently being recovered. The element is rejected.

User response: Allow the HALDB recovery processing to complete before executing this request.

BMCDLP186829E

Cannot add DEDB - OTHREADS not initialized


Explanation: An attempt to add a Fast Path database failed because no DEDBs were initialized at IMS restart. No output threads (OTHREADS) are created at IMS restart because no DEDBs were initialized. The element is rejected, the DDIR is not added.

User response: IMS restart is needed to initialize certain DEDB fields in the ESCD. Perform the following actions:

  • Remove the DMB block from the active ACBLIB.

  • Re-execute the ADD database request.

  • Add DMB block to the active ACBLIB and restart IMS to initialize DEDBs.

This action is only required for the first DEDB defined to the IMS system.

BMCDLP186830E

Cannot add partition database - partitioning feature not initialized


Explanation: An attempt to add a partitioned full function database failed because the IMS partitioning function was not initialized at IMS restart. The element is rejected and the partitioned database is not added.

User response: The partitioning feature is initialized based on the RES= parameter and whether any defined partitioned databases exist in the ACBLIB. Perform the following actions:

  • Specify RES=Y and the partitioning feature will be initialized at startup regardless if any partitioned databases are defined in the ACBLIB.

  • Specify RES=N and the partitioning feature will only be initialized at startup if any defined partitioned databases are found in the ACBLIB. Ensure the defined partitioned databases are placed in the ACBLIB.

  • The default for FDR systems is RES=N and this setting cannot be overridden. You must ensure the defined partitioned databases are placed in the ACBLIB.

BMCDLP186831E

DMCB name does not match database name.


Explanation: The DMCB name did not match the name of the database during the loading of the DMB block from the ACBLIB. The action specified could be an ADD, REVISE, or RELOAD. The element is rejected

User response: Review the DMB block in the ACBLIB. Correct the error and rerun the ACBGEN.

BMCDLP186832E

Delete DMB DMBname call to the DMB Pool Manager failed


Explanation: An attempt to change a database element fails because the existing DMB failed to be purged from the DMB pool. This message indicates that after a delete call to the pool manager for this DMB, the DMB was still in the DMB pool. The element is rejected.

User response: This situation was not expected. The cause of the failure is unknown because IMS was called to perform this action. Retry the operation again.

BMCDLP186833E

Secondary index database databaseName not defined


Explanation: The database being added, revised, deleted or reloaded that is part of a shared secondary index group is not a defined database. Databases that make up the group are defined in the DMB block that resides in the ACBLIB. The element is rejected.

User response: Ensure that the database exists if a revise, delete or reload is being executed. If the database is being added, ensure that all databases in the shared group either exist or are being added in the same request. When you originally add shared secondary indexes, the request should be executed in optimized mode.

BMCDLP186835E

Attempting to delete secondary index but still exist in shared group


Explanation: The database being deleted still exists in the secondary index sequence list in the DMB block. The element is rejected.

User response: If you are deleting a database that is part of a shared secondary index group, ensure that a DBDGEN and an ACBGEN are performed to eliminate the database from the secondary sequence list. The exception to this is that all databases in the same shared group can be deleted at the same time even though the DMB still exists in the ACBLIB.

BMCDLP186836E

No other fields can be selected if reloading DEDB 2-stage randomizer.


Explanation: No other fields can be selected in the element if the Reload DEDB 2-stage randomizer ONLY field is selected. The element is rejected.

User response: Ensure that no other fields are marked in the element when reloading a 2-stage randomizer only.

BMCDLP186837E

Reloading 2-stage randomizer but database not DEDB or the database currently set NOTINIT.


Explanation: DELTA PLUS is attempting to process a RELOAD or REVISE request to reload a 2-stage randomizer only, but the database is not a DEDB or the DEDB database is currently set as NOTINIT. The element is rejected.

User response: Ensure that the database specified in RELOAD or REVISE request is a DEDB and that the DEDB is not set as NOTINIT. If the database is set as NOTINIT, then a full RELOAD of the database is needed (but do not select the Reload DEDB 2-stage randomizer ONLY field).

BMCDLP186838E

Randomizer being reloaded not defined as DEDB 2-stage randomizer.


Explanation: DELTA PLUS is attempting to process a RELOAD or REVISE request to reload a 2-stage randomizer only, but the randomizer is not defined as 2-stage in the DBD definition. The element is rejected.

User response: Ensure the randomizer is defined as a 2-stage randomizer in the DBD definitions.

BMCDLP186839E

Unable to process RAND=ONLY to reload 2-stage randomizer, it is shared with DEDB database databaseName


Explanation: DELTA PLUS is attempting to process a RELOAD or REVISE request to reload a 2-stage randomizer only, but the randomizer is used by another database (or databases). The element is rejected.

User response: If you specify RAND=ONLY, then the randomizer being reloaded cannot be used by any other database. Use the following command to display which databases are sharing this randomizer: /DIS DLP XREF RAND randName

BMCDLP186840E

DMB not defined as DEDB or DMB set in NOTINIT state


Explanation: While processing a RELOAD DB RLDAREA=YES request, DELTA PLUS determined that either the old DMB (existing) or new DMB (in ACBLIB) was set to a NOTINIT state which implies that the database is not in a usable state. Another reason this error can occur is that the database is not defined as DEDB (which is determined in the DMB). The DELTA List request is rejected.

User response: Determine why the database is set to NOTINIT as this status normally indicates that the DMB is not in the active ACBLIB or the DMB in ACBLIB is not defined as a DEDB database. After the error is determined, then submit a RELOAD DB request without specifying RLDAREA=YES to reload the entire DEDB database.

BMCDLP186842E

DMAC field fieldName in AREA areaName changed and not selected to be reloaded


Explanation: While processing a RELOAD DB RLDAREA=YES request, DELTA PLUS determined that the indicated field had changed between the existing DMB and the new DMB for an area that is not selected to be reloaded. If the area is not in a stopped state, then it is not being considered for reload. Individual areas are stopped with the /DBR AREA command. This condition is being checked as a precaution to ensure that problems do not occur later for this area. The DELTA List request is rejected.

User response: Determine if this area is to be reloaded. If so, then stop the area using the /DBR AREA command. If this area is not to be reloaded, then DBD changes were made for this area and they exist in the new DMB in the active ACBLIB. Correct the situation and resubmit the request.

BMCDLP186843E

Randomizer name cannot change between old and new DMB in RELOAD DB RLDAREA


Explanation: While processing a RELOAD DB RLDAREA=YES request, DELTA PLUS determined that the randomizer name is being changed in the new DMB (in active ACBLIB). The randomizer name cannot change across a RELOAD DB RLDAREA=YES request because some areas could still be opened using the randomizer. The DELTA List request is rejected.

User response: If the randomizer name needs to be changed in the new DMB, then submit a RELOAD DB RLDAREA=NO request to reload the entire DEDB database.

BMCDLP186844E

AREA areaName is being deleted from database but not stopped


Explanation: While processing a RELOAD DB RLDAREA=YES request, DELTA PLUS determined that an area was being removed (or deleted) from the database but the area is not in a stopped state. This message is issued as a precaution in case the area was not intended to be deleted. The DELTA List request is rejected.

User response: Any area to be removed from the database must be in a stopped state (just like any area to be reloaded must be in a stopped state). Issue the /DBR AREA command against this area and resubmit the RELOAD DB RLDAREA=YES request.

BMCDLP186845E

RLDAREA only valid for RELOAD DB request


Explanation: While processing a request other than a RELOAD DB request, DELTA PLUS determined that the RLDAREA=YES parameter was specified. The RLDAREA=YES parameter is valid only when running a RELOAD DB request. The DELTA List request is rejected.

User response: If the RLDAREA parameter is to be specified, then ensure that the request is a RELOAD and not a REVISE or an ADD.

BMCDLP186846I

AREA areaname in DATABASE databasename IOVF extended by RELOAD DB IOVFEXT request


Explanation: This informational message is displayed on the IMS joblog and explains the processing done in the RELOAD DB RELAREA request (including which areas were changed, not changed, added or deleted). If this is a RELOAD DB IOVFEXT request, it displays which areas had their IOVF extended. This information is displayed only after  the request runs successfully. The DELTA List request runs successfully.

User response: No action is required. Information only.

BMCDLP186847E

RELOAD DB RLDAREA request being executed but entire DEDB database is stopped


Explanation: While processing a RELOAD DB RLDAREA=YES request, DELTA PLUS determined that the entire DEDB database was stopped using a /DBR DB command or a /STOP DB command. The database cannot be in a stopped state. Only the areas being changed or deleted must be stopped. The DELTA List request is rejected.

User response: This error message is displayed as a precaution to make the user aware of the condition. If the entire database was stopped, the user might have intended to reload all areas in the DEDB database. If this was the intent, then a RELOAD DB request should be submitted without specifying RLDAREA=YES. If the user intended to reload only certain areas, then the user should issue a /STA DB command to start the database and issue a /STA AREA command for all areas that are not to be reloaded.

BMCDLP186848E

AREA areaName stopped but ADSC still exist


Explanation: While processing a RELOAD DB RLDAREA=YES request, DELTA PLUS determined that the indicated area was stopped, but the ADSC control block still exists. If the ADSC still exists for this DMAC, then the area is still opened. The DELTA List request is rejected.

User response: This condition should not occur. If it does, the area was not closed successfully during DBR AREA processing (even though the area is in a stopped state). During close processing, the ADSC should be cleaned up by IMS. Start the area and then issue the /DBR AREA command. Resubmit the RELOAD DB RLDAREA request.

BMCDLP186849E

No changes detected in RELOAD DB RLDAREA processing


Explanation: While processing a RELOAD DB RLDAREA=YES request, DELTA PLUS determined that no changes were detected to be done (no areas were stopped), no areas were detected to be added, or no areas were detected to be deleted. The DELTA List request is rejected.

User response: If a RELOAD DB RLDAREA=YES request is supposed to be done, ensure that the individual areas to be reloaded are in a stopped state. This error most likely occurs when no areas have been stopped prior to executing the request, no areas were in a stopped state that were to be deleted, or no areas were detected to be added in the new DMB.

BMCDLP186850E

ADD database request rejected, the maximum DMB count of 32767 exceeded.


Explanation: While processing an ADD request, DELTA PLUS determined that adding this database will exceed the maximum DMB count of 32767. This limit is an IMS restriction.

User response: As this limit is an IMS restriction, delete any redundant or unused databases in this IMS system. Restart IMS with a cold start to remove gaps in the DMB number. The cold start will resequence the DDIRNUMB field in the DDIRs to start at one. This action should ensure that the DMB high count of 32767 will not be exceeded when the next database is added.

BMCDLP186851

AREA areaName being added, all areas that follow it must be closed


Explanation: While processing a RELOAD DB RELAREA request, DELTA PLUS detected an error when attempting to add area(s) in the middle of a DEDB. Any area that follows the area (DMAC) being added must be closed and not accessible for DLI calls. The DELTA List request fails.

User response: Issue a DBR AREA command for each area following the area being added in the DEDB. When these areas are closed, DLA will update the DMAC area number (DMACARID/DMACRAID) to match the new DMB loaded and insure there are no duplicate DMAC area numbers.

BMCDLP186852

AREA areaName being deleted, all areas that follow it must be closed


Explanation: While processing a RELOAD DB RELAREA request, DELTA PLUS detected an error when attempting to delete area(s) in the middle of a DEDB. Any area that follows the DELTA IMS (DMAC) being deleted must be closed and not accessible for DLI calls. The DELTA List request fails.

User response: Issue a DBR AREA command for each area following the area being deleted in the DEDB. When these areas are closed, DLA will update the DMAC area number (DMACARID/DMACRAID) to match the new DMB loaded and insure there are no duplicate DMAC area numbers.

BMCDLP186853E

Mutually exclusive options specified in RELOAD request

Explanation: When processing a RELOAD DB IOVFEXT request, Delta PLUS was cross-checking parameters and found an additional parameter or parameters that were selected. If you have selected IOVFEXT to reload the database to extend the IOVF in the DEDB areas, no other parameter can be selected. RELOAD DB IOVFEXT can only be executed if IBM IMS is running in an IMS Managed ACB environment. The DELTA List request is rejected.

User response: Ensure that no other parameters are selected in the RELOAD request if you have specified IOVFEXT. You cannot specify 'AUTO' to reload sensitive ACBs, 'RAND' to reload DEDB randomizer, or 'RELAREA' to reload specific areas in the DEDB in the same request with IOVFEXT.

BMCDLP186854E

DMB dmbname was not located in staging IMS directory, request fails.


Explanation: While processing a RELOAD DB IOVFEXT request, the DMB object for the database was not found in the staging IMS directory. The DELTA List request is rejected.

User response: Run the IMS Populate utility that will update the IMS Catalog with a new version of the DBD. This utility will then create the DMB block and place it in the staging IMS directory.

BMCDLP186855E

RELOAD DB IOVFEXT fails, DMB in staging directory is not a DEDB.


Explanation: While processing a RELOAD DB IOVFEXT request, the target database is not defined in the staging directory as a DEDB. You can only extend and IOVF for areas in a DEDB and only if IBM IMS is running in an IMS Managed ACB environment. The DELTA List request is rejected.

User response: Ensure that the target database in this request is defined as a DEDB.

BMCDLP186856E

Field fieldname AREA areaname mismatch between in-core DMCB and DMB in stage directory.


Explanation: While processing a RELOAD DB IOVFEXT request, the fieldname field does not match the in-core DMAC with the same DMAC that resides in the DMB in the IMS staging directory. This field must match along with the other DMAC fields. The DELTA List request is rejected.

User response: Determine the cause of the mismatching field in the in-core DMAC against the new DMB in the IMS staging directory. It is possible that the IOVF was not extended by running the BMC FP Online Reorg utility first, which is a requirement. When the FP Online Reorg utility runs to extend the IOVF, several fields will be updated in the in-core DMAC. The DBD definition needs to be updated to include this in the DBD ROOT parameter. Run DBDGEN and ACBGEN, followed by running the IMS Populate utility, to create a new version of the DBD definition in the IMS Catalog. IMS Populate utility builds the new DMB block and saves it in the IMS staging directory. RELOAD DB IOVFEXT request will ensure that all fields match up, then it will copy the DMB from the staging to the active IMS directory.

BMCDLP186857E

Field fieldname DMCB dcmbname mismatch between in-core DMCB and DMB in staging directory.


Explanation: While processing a RELOAD DB IOVFEXT request, the fieldname field does not match the in-core DMCB with the same DMB in the IMS staging directory. This field must match. The DELTA List request is rejected.

User response: Determine the cause of the mismatching field in the in-core DMAC against the new DMB in the IMS staging directory. It is possible that the IOVF was not extended by running the BMC FP Online Reorg utility first, which is a requirement. When the FP Online Reorg utility runs to extend the IOVF, several fields will be updated in the in-core DMAC. The DBD definition needs to be updated to include this in the DBD ROOT parameter. Run DBDGEN and ACBGEN, followed by running the IMS Populate utility, to create a new version of the DBD definition in the IMS Catalog. IMS Populate utility builds the new DMB block and saves it in the IMS staging directory. RELOAD DB IOVFEXT request will ensure that all fields match up, then it will copy the DMB from the staging to the active IMS directory.

BMCDLP186858E

AREA areaname DMCB dmcbname mismatch between active and staging directory


Explanation: While processing a RELOAD DB IOVFEXT request, the areaname area does not match the in-core DMCB with the same DMB in the IMS staging directory. This field must match. The DELTA List request is rejected.

User response: Determine the cause of the mismatching area name in the in-core DMCB and DMB in the IMS staging directory. When extending the IOVF using BMC's FP Online Reorg utility, the utility does not make any configuration changes such as adding or deleting areas in the in-core DMCB. It is possible that, when the existing DBD definition was changed (to increase the value of the ROOT parameter), a configuration change was detected that either added or deleted an area. This is not allowed. Determine the error, then run DBDGEN, ACBGEN followed by running the IMS Populate utility. This will create a new version of the DBD in the IMS Catalog. IMS Populate utility will build a new DMB block and save it in the IMS staging directory.

BMCDLP186859E

Changes detected in DEDB CRTE entries during RELOAD DB IOVFEXT


Explanation: While processing a RELOAD DB IOVFEXT request, DELTA PLUS detected changes made to the DEDB CRTE control block entries in the new DMB. The DELTA List request is rejected.

User response: Ensure that no changes are made to the secondary index cross-reference table entries in the new DMB. The only changes that you can make with a RELOAD DB RELAREA request are adding new areas, deleting old areas, or updating existing areas. The only change that you can make with a RELOAD DB IOVFEXT request is to change the ROOT parameter for the areas that had their IOVF extended by running BMC's FP Online Reorg utility.

BMCDLP186860E

Changes detected in DEDB SDBF entries during RELOAD DB IOVFEXT request


Explanation: While processing a RELOAD DB IOVFEXT request, DELTA PLUS detected changes made to the DEDB SDBF control block entries in the new DMB. The DELTA List request is rejected.

User response: Ensure that no changes are made to the segment description table in the new DMB. The only change that you can make with the RELOAD DB IOVFEXT is to change the ROOT parameter for the areas that had their IOVF extended by running BMC's FP Online Reorg utility.

BMCDLP186861E

RELOAD DB IOVFEXT fails, IMS not running with IMS Directory


Explanation: RELOAD DB IOVFEXT is supported if running with IMS Managed ACBs Support enabled. You must be running with the IMS Catalog and directory. The DELTA List request is rejected.

User response: This request is only valid if running with the IMS Catalog and Directory. RELOAD DB IOVFEXT is not supported if IMS is running with the active ACBLIB.

Was this page helpful? Yes No Submitting... Thank you

Comments