Messages BMC111100 through BMC111199

BMC111101E

Unable to find DFSVC000 in STEPLIB

Explanation: Required module DFSVC000 is used to determine the IMS level for the current action. Module DFSVC000 was not found in any library referenced by STEPLIB. The utility terminates with a user 3003 abend.

User response: Include the IMSVS.RESLIB data set in the STEPLIB concatenation.

BMC111102C

Return code returncode received from Memory Manager

Explanation: The returncode was received from a memory manager GETMAIN request. The utility terminates with a user 3003 abend.

User response: Increase the region size on the EXEC card and rerun.

BMC111103C

IMS level imslevel is not supported

Explanation: The imslevel in DFSVC000 does not match any IMS level supported by Fast Path/EP. The utility terminates with a user 3003 abend.

User response: Point STEPLIB to a RESLIB for an IMS level supported by Fast Path/EP.

BMC111104C

No databases selected for processing

Explanation: The ACBLIB processor receives a list of databases to process. The list had no entries in it. This is an indication that all databases were previously rejected for some reason. The utility returns with condition code 12.

User response: Correct any errors, and resubmit the job.

BMC111105C

BLDL failure on IMSACB DD statement: Return code returncode

Explanation: The ACBLIB processor performed a BLDL for all requested databases and received the returncode. The utility returns with condition code 12.

User response: Look for other error messages that may indicate the reason for the BLDL failure. Correct the problem, and resubmit the job.

BMC111106C

ddName directory entry member is not found

Explanation: The indicated member name is not present in the library that is associated with the specified ddName.

User response: Correct the problem, and resubmit the job.

BMC111107C

directoryentry - directory entry is not a DEDB database control block

Explanation: The directoryentry is not a DEDB control block. The utility returns with condition code 12.

User response: Correct and resubmit the command set.

BMC111108C

Database database - no buffer size defined for entry

Explanation: The ACBLIB processor retrieved the directory entry for the indicated database, but the field indicating the DMB size was empty. This may indicate a problem with the ACBGEN for this database, or may indicate the directory entry is invalid. The utility returns with condition code 12.

User response: Correct the entry, and resubmit the job.

BMC111109C

directoryentry - directory entry is not a database control block

Explanation: The directoryentry is not defined in the ACBLIB as a DMB. The entry appears to be for a PSB. The utility returns with condition code 12.

User response: Correct and resubmit the command set.

BMC111110C

Database database - ACB is not for this IMS level

Explanation: The database cannot be processed for the IMS level indicated by the RESLIB being used. The utility returns with condition code 12.

User response: Change the RESLIB to the correct level, or change the ACBLIB being used.

BMC111111C

Database database - I/O error reading ACBLIB

Explanation: The database received an I/O error while reading the ACBLIB. The utility returns with condition code 12.

User response: Correct the problem, and resubmit the job.

BMC111112C

Database database - unexpected end of data on ACBLIB

Explanation: The database did not have as much data as was indicated in the directory entry. This error may indicate an error during the last ACBGEN. The utility returns with condition code 12.

User response: Correct the problem, and resubmit the job.

BMC111113C

Unable to open IMSACB DD statement

Explanation: The open for the IMSACB DD statement failed. This DD statement points to the IMS ACBLIB library. The utility returns with condition code 12.

User response: Look for any other MVS messages that may describe the failure. Correct the problem, and resubmit the job.

BMC111114C

ddname DD statement was not found

Explanation: A required Fast Path/EP product ddname was not allocated in the JCL and was not dynamically allocated. The utility returns with condition code 12.

User response: Include the required ddname DD statement or ensure that STEPLIB points to a library that includes a dynamic allocation member.

BMC111115C

Dynamic allocation error on ddname=returncode

Explanation: A Fast Path/EP product found a dynamic allocation member for ddname. When the member was used, it returned return code returncode. The utility returns with condition code 12.

User response: Look up the dynamic allocation (SVC99) code, and correct the problem. To look up the code, use either of the following methods:

• Look up the code in the IBM reference manual MVS/ESA SPL: Application Development Guide.

• Look up the code using TSO HELP by selecting 1) TSO HELP, 2) INDEX, 3) D, 4) D1 (DAIR return codes). If the code you received is not displayed, press Enter, then type in the code (0-7) of the range containing the return code you received in the error message.

BMC111116C

Unable to open MODSTAT DD statement

Explanation: The open for the MODSTAT DD statement failed. This DD statement points to the IMS ACBLIB library. The utility returns with condition code 12.

User response: Look for any other MVS systems that may describe the failure. Correct the problem, and resubmit the command set.

BMC111117C

Cannot find IMSACB in MODSTAT data set record

Explanation: A Fast Path/EP product found, allocated, and read the MODSTAT data set record but could not find any reference to IMSACB. The MODSTAT record shows the active IMS ACBLIB DD statement, IMSACBA or IMSACBB. This record may indicate that the MODSTAT data set has been corrupted. The utility returns with condition code 12.

User response: Correct the problem, and resubmit the command set.

BMC111118C

Dynamic allocation member is missing for IMSACB imsacb

Explanation: A Fast Path/EP product found, allocated, and read the MODSTAT data set record. When the product tried to find the indicated dynamic allocation member for the indicated imsacb (IMSACBA or IMSACBB), the member did not exist in STEPLIB. The utility returns with condition code 12.

User response: Ensure that the STEPLIB points to the IMS library that contains the dynamic allocation members for IMSACBA and IMSACBB.

BMC111119C

Dynamic allocation error on IMSACB RC=returncode

Explanation: A Fast Path/EP product found a dynamic allocation member for IMSACBA or IMSACBB. When the member was used, it produced the returncode. The utility returns with condition code 12.

User response: Look up the dynamic allocation (SVC99) code, and correct the problem. To look up the code, use either of the following methods:

• Look up the code in the IBM reference manual MVS/ESA SPL: Application Development Guide.

• Look up the code using TSO HELP by selecting 1) TSO HELP, 2) INDEX, 3) D, 4) D1 (DAIR return codes). If the code you received is not displayed, press Enter, then type in the code (0-7) of the range containing the return code you received in the error message.

BMC111120C

Unable to open ddname DD statement

Explanation: A Fast Path/EP product found a dynamic allocation member for IMSACBA or IMSACBB. When the ddname was used, it produced the associated error code. The utility returns with condition code 12.

User response: Look up the error code, and correct the problem.

BMC111121C

Invalid MODSTAT record found

Explanation: A Fast Path/EP product found an invalid format on the MODSTAT record read from the MODSTAT data set. The utility returns with condition code 12.

User response: Correct the problem, and resubmit the job.

BMC111122C

Unexpected end of file on MODSTAT data set

Explanation: A Fast Path/EP product found an unexpected end-of-file condition on the first read to the MODSTAT data set, which indicates that there are no records in the file. The utility returns with condition code 12.

User response: Correct the problem, and resubmit the job.

BMC111123C

Database database - unsupported IMS level in DMB

Explanation: The database was defined for an IMS level not supported by a Fast Path/EP product. The utility returns with condition code 12.

User response: Redefine the DMB, and resubmit the command set.

BMC111124C

Database database - randomizer randomizer not found in ddname

Explanation: The utility failed to locate the randomizer module within the specified library DDname. The utility returns with condition code 12.

User response: Correct the library concatenation for the DDname given in the message, and then resubmit the command set.

BMC111125C

Database database - compression routine routine not found in STEPLIB

Explanation: The indicated compression routine was not found in the STEPLIB for the database. The utility returns with condition code 12.

User response: Ensure the STEPLIB DD statement points to a library containing the compression routine. Correct the error, and resubmit the command set.

BMC111126C

Database database, area areaname not defined in database

Explanation: The areaname was not defined as part of the database. The utility returns with condition code 12.

User response: Correct the area statement, and resubmit the command set.

BMC111127C

Database database, area areaname; area is marked returncode1 by DBRC, should be marked returncode2

Explanation: For database, areaname, the indicated area is marked either unavailable returncode1 when it should be available returncode2 (as in the case of Fast Path Analyzer/EP), it is marked available returncode1 when it should be unavailable returncode2 (as in the case of initialization). The utility returns with condition code 12.

User response: Use DBRC to set the area available flag to the appropriate status.

BMC111128C

Database database, area areaname duplicate ddname found

Explanation: For the database and the areaname, a duplicate ddname exists in the job, meaning it has already been opened for another DBD (see DFS3702I RC=10). The utility returns with condition code 12.

User response: Remove the DD statement or, if the ddname is in error (matching another ddname), correct it and resubmit the command set.

BMC111129C

database areaname, DDname ddname allocation failed

Explanation: For the database areaname, the ddname cannot be found allocated in the JCL or as a dynamic allocation member in STEPLIB (see DFS3702I RC=17). The utility returns with condition code 12.

User response: Add a DD statement to the JCL, or create a dynamic allocation member for this area.

BMC111130C

dbdName, areaName, DDname ddname dynamic allocation failure. Code=code DSN: dataSetName

Explanation: Dynamic allocation returned the indicated code for the indicated data set. The utility returns with condition code 12.

User response: Look up the dynamic allocation (SVC99) code, and correct the problem. To look up the code, use either of the following methods:

• Look up the code in the IBM reference manual MVS/ESA SPL: Application Development Guide.

• Look up the code using TSO HELP by selecting 1) TSO HELP, 2) INDEX, 3) D, 4) D1 (DAIR return codes). If the code you received is not displayed, press Enter, then type in the code (0-7) of the range containing the return code that you received in the error message.

BMC111131I

Area areaname, DDname ddname device type is not DASD

Explanation: For the areaname, the indicated DD name ddname is allocated to a non-DASD device type (for example, tape). The utility continues normally.

User response: No action is required.

BMC111132C

DDname ddname - Cannot determine input file type

Explanation: The unload input file type for the indicated DD name ddname cannot be determined. Processing terminates.

User response: Check the unload input file to ensure that it matches one of the valid formats.

BMC111134C

DBRC SIGNOFF call failed, DBRC reason code=reasoncode

Explanation: The call to DBRC to signoff failed with the returncode. A message is sent, and the job generates return code 12.

User response: Determine the action to be taken from the reason code indicated. Refer to the IBM IMS Messages and Codes manual for message DFS030I for an explanation of the reason code.

BMC111135C

DBRC TERMINATION call failed, DBRC reason code=reasoncode

Explanation: The call to DBRC to terminate failed with the eturncode. A message is sent, and the job generates return code 12.

User response: Determine the action to be taken from the reason code indicated. Refer to the IBM IMS Messages and Codes manual for message DFS030I for an explanation of the reason code.

BMC111136I

DBD dbdname, area areaname, is not registered with DBRC

Explanation: The dbdname and areaname are not registered with DBRC.

User response: No action is required.

BMC111137C

dbdname, area areaname: Unable to obtain authorization. Reason code= reasoncode

Explanation: A Fast Path/EP product was unable to obtain database authorization for the indicated DBD and area for the specified reason code. The database open fails.

User response: Determine the action to be taken from the reason code indicated. Refer to the IBM IMS Messages and Codes manual for message DFS047A for explanation of the reason code.

BMC111138C

DBRC request failed for database dbdname, area areaname. Reason code=reasoncode

Explanation: A Fast Path/EP product was unable to obtain database authorization for the dbdname and areaname for the reasoncode. The database open fails.

User response: Determine the action to be taken from the reason code indicated. Refer to the IBM IMS Messages and Codes manual for message DFS047A for explanation of the reason code.

BMC111139C

dbdname, areaname: DBRC UNAUTH request failed. Reason code=reasoncode

Explanation: A Fast Path/EP product was unable to unauthorize the database for the specified reason code. The database close fails.

User response: Determine the action to be taken from the reason code indicated. Refer to the IBM IMS Messages and Codes manual for message DFS030I for explanation of the reason code.

BMC111141C

dbdname, areaname, ddname: Inconsistent DSN between RECON and allocated data setDSN from DBRC: dsn1 DSN from JCL : dsn2

Explanation: DBRC is active and the data set name dsn2 in the JCL for ddname in areaname does not match the dataset name dsn1 in the RECON data set. The open for the area terminates.

User response: Correct the DD statement for the affected area.

BMC111142C

dbdname, areaname: DMAC inconsistent with DMB - DMAC fieldname DMACvalue DMBvalue

Explanation: In the area areaname, the data set DMAC does not match the DMB definition in ACBLIB. Specifically, the value DMACvalue of the DMAC field DMAC fieldname in the dataset DMAC does not match the value DMBvalue for the field in the DMB definition in ACBLIB. The open for the area terminates.

User response: Correct the data set or the DMB definition.

BMC111143C

dbdname, areaname: DMAC area number DMACarea not equal to DMB area number DMBarea

Explanation: The area number on the DMAC for the areaname does not match the area number from DMB. The open for the area terminates.

User response: Correct the data set or the DBD definition.

BMC111144C

areaname, ddname: Exceeded maximum number of EEQEs

Explanation: The areaname has reached a maximum EEQE count and should be recovered. The open for the area terminates.

User response: Recover the area.

BMC111145C

areaname, ddname: DMAC CUSN value1 inconsistent with DMB CUSN value2

Explanation: There is an update inconsistency error in the CUSN for areaname. The open for the area terminates.

User response: Determine the cause of the inconsistency, and resubmit the job.

BMC111146C

areaname, ddname Dynamic area free failure. Code=code

Explanation: An error occurred while the areaname data set was being freed. The utility returns with condition code 12.

User response: Look up the dynamic allocation (SVC99) code, and correct the problem. To look up the code, use either of the following methods:

• Look up the code in the IBM reference manual MVS/ESA SPL: Application Development Guide.

• Look up the code using TSO HELP by selecting 1) TSO HELP, 2) INDEX, 3) D, 4) D1 (DAIR return codes). If the code you received is not displayed, press Enter, then type in the code (0-7) of the range containing the return code you received in the error message.

BMC111147C

DBRC function processing failed with return code=returncode

Explanation: An error occurred while an area data set was being freed. DBRC processing failed with the indicated returncode . The utility returns with condition code 12.

User response: Determine the action to be taken from the reason code indicated. Refer to the IBM IMS Messages and Codes manual for message DFS041I for explanation of the reason code.

BMC111148C

VSAM macro (controlblock) Return code returncode, REASON CODE reasoncode

Explanation: The indicated VSAM macro returned the indicated return and reason codes. The utility returns with condition code 16.

User response: Determine the error from the code, correct the problem, and rerun the job.

BMC111149C

Return code returncode received from READ JFCB

Explanation: The returncode was received from a RDJFCB macro issued for data set attributes in logical open. The utility returns with condition code 12.

User response: Determine the error from the code, and correct the problem.

BMC111150C

Return code returncode received from file manager CONNECT for area areaname

Explanation: The returncode was received from a file manager connect for areaname. The utility returns with condition code 12.

User response: Determine the error from the code, and correct the problem.

BMC111151C

Return code returncode received from file manager READ for area areaname

Explanation: The returncode was received from a file manager connect for areaname. The utility returns with condition code 12.

User response: Determine the error from the code, and correct the problem.

BMC111152C

Return code returncode received from buffer manager for area areaname

Explanation: The returncode was received from a buffer manager call for areaname. The utility returns with condition code 12.

User response: Determine the cause of the error from the return code. Correct the problem, and resubmit the job.

BMC111153C

Return code returncode received while freeing file areaname

Explanation: The returncode was received because an error occurred while the areaname data set was being freed. The utility returns with condition code 12.

User response: Determine the error from the code, and correct the problem.

BMC111154C

database name: Module module name not found in ddname

Explanation: Fast Path Indexer/EP attempted to load the indicated module, but could not find it in the load library. The utility returns with condition code 12.

User response: Ensure that the load library DD statement points to a library containing the module.

BMC111155C

segment/field not found within database/segment

Explanation: Either the indicated segment is not defined within the hierarchical path of the designated database, or the indicated field is not found in the designated segment. The utility returns with condition code 12.

User response: Correct the control statement, and rerun the job.

BMC111156C

dbdname, areaname: Unable to open DDNAME ddname. Return code returncode ; Reason code reasoncode

Explanation: Fast Path Reorg/EP was unable to open the indicated ddname, but received the returncode and reasoncode from open process. Processing on this area terminates.

User response: A previous message from open should indicate the cause of the open failure. Correct the problem and rerun the reorganization for this area.

BMC111157E

dbdname: HD Unload/Reload conversion utility DDname ddname not found

Explanation: The HD unload/reload conversion process for dbdname required ddname, but it was not specified in the JCL. Processing terminates.

User response: Specify a DD statement for the unload/reload file with a ddname of the database, or use the unload/reload ddname keyword to specify a ddname.

BMC111158E

STARTUOW (value) larger than total UOW's (number) in area areaname

Explanation: The STARTUOW value entered for the areaname was greater than the maximum number of UOWs for the area. Processing on this area terminates.

User response: Correct the UOW statement, and rerun the utility for this area.

BMC111159C

dbdname, areaname: Return code returncode; Reason code reasoncode received from File Manager

Explanation: File Manager returned the returncode and reasoncode while Fast Path Reorg/EP was attempting to read the area. The following reason codes are displayed for this message. These reason codes are generated with a return code = 24.

Processing on this area terminates.

User response: These errors might be caused by environmental factors, such as storage constraints, when several areas are processed at the same time. Look for any previous problems in the job. Run an IDCAMS list of the area, and look for integrity problems. Correct any problems, and rerun the job. If the problem persists, contact BMC Customer Support.

BMC111160C

dbdname, areaname: Segment RBA pointer pointer, points outside of UOW UOW#=uow

Explanation: The indicated RBA pointer, taken from the prefix of a segment, pointed outside the current UOW. Depending on the error threshold set, the UOW is bypassed or processing terminates with a user abend U1001.

User response: There is a pointer problem in the area. Run Fast Path Analyzer/EP to determine the problem. Correct the problem, and rerun the job.

BMC111161C

dbdname, areaname: Expected segment code segmentcode; found value. UOW#=uow

Explanation: The indicated segmentcode was expected at the current RBA , but value was found instead. Depending on the error threshold set, either the segment and all its dependents are bypassed, or the UOW is bypassed. Processing terminates against the segment or UOW, but continues with the rest of the area.

User response: If this message is issued on a CHANGE or UNLOAD command that is executed to remove pointer errors, then no action is required. If removing pointer errors was not intended or if this message is issued by a REORGANIZE command, run Fast Path Analyzer/EP to determine the problem. If the pointer errors can be tolerated, set an appropriate pointer error threshold using the ERROR_THRESHOLD keyword on the next execution of the process. If the detected pointer errors cannot be tolerated, follow your site’s standard database recovery procedures.

BMC111163C

dbdname, areaname, segment RBA Segment length error - segment=segmentName length=value DMB specifies LENGTH=(max, min )

Explanation: A segment was found of the indicated segment type that is not within the range specified in the DMB. This message is issued where a segment length that is greater than the defined maximum is detected by a reload or change process. The utility returns with a condition code 12. Processing terminates for the area where the error occurred.

User response: Run Fast Path Analyzer/EP to determine the extent of the problem. Correct the segment lengths, then rerun the job.

BMC111164C

dbdname, areaname: Not all subset pointers resolved for parent segment. UOW#=uow

Explanation: Fast Path Reorg/EP was unable to resolve all subset pointers for a segment, indicating that they may point outside the UOW. Depending on the error threshold set, the unit of work (UOW) is bypassed or processing terminates with a user abend U1001.

User response: There is a pointer problem in the area, or the area has been corrupted. Run Fast Path Analyzer/EP to determine the problem. Correct the problem, and rerun the job.

BMC111165C

Expected RAP CI; found block ID=blockid. UOW#=uow

Explanation: While moving to a new root anchor point (RAP) control interval (CI), Fast Path Reorg/EP found the indicated invalid block ID. Depending on the error threshold set, the UOW is bypassed or processing terminates with a user abend U1001.

User response: There is a pointer problem in the area, or the area has been corrupted. Run Fast Path Analyzer/EP to determine the extent of the problem.

BMC111166I

Parent rba1; pointer rba2.

Explanation: This message follows the issuance of BMC111161C, which indicates that a pointer problem was found and bypassed. rba1 indicates the RBA of the segment that contained the bad pointer , and rba2 indicates the bad pointer. Any information pointed to by rba2 is bypassed, and processing will continue with the next pointer from the parent.

User response: There is a pointer problem in the area, or the area has been corrupted. Run Fast Path Analyzer/EP to determine the extent of the problem.

BMC111167C

dbdname, areaname: Insufficient IOVF space to continue. UOW#=uow

Explanation: There is not enough IOVF space to fulfill the requested reorganization for the indicated UOW in the indicated area. Fast Path Reorg/EP stops on the UOW. All preceding UOWs have been reorganized.

User response: This problem probably occurred because of a load control or a user exit that requested too many segments be placed into overflow (DOVF or IOVF). Increase the space, or reduce the number of segments going into overflow.

BMC111168C

dbdname, areaname: Condition code code received from Analyzer call

Explanation: A call to the Fast Path/EP interface returned the indicated condition code. Depending on the error threshold set, the UOW is bypassed or processing terminates with a user abend U1001.

User response: There is a pointer problem in the area, or the area has been corrupted. Look at the Fast Path Analyzer/EP messages to determine the problem.

BMC111169C

dbdname, ddname: Cluster to be initialized is not empty

Explanation: The cluster being initialized did not have a high used RBA of zero, indicating that it was not empty. Initialization for this cluster is terminated.

User response: Ensure the correct data set was specified. If so, use IDCAMS to delete and redefine the cluster.

BMC111170C

dbdname, areaname: Cluster CI size cisize1 does not match DMB CI size csize2.

Explanation: The control interval (CI) size defined in the cluster does not match the CI size cluster that was defined in the database definition for the indicated area. Reorganization terminates.

User response: Correct the CI size value, redefine the cluster, and rerun the job.

BMC111171C

dbdname, areaname: High Used RBA is not equal to the High Allocated RBA

Explanation: The indicated area was to be used for database change, but the high-used RBA was not zero, indicating it is not empty. The high-allocated RBA was not equal to the high-used RBA, indicating the area was not initialized correctly. Database change terminates.

User response: Determine why the high-used and high-allocated RBAs are not equal. Use IDCAMS to delete and redefine the area.

BMC111172C

dbdname, areaname: Insufficient space defined for area - minimum required cylinders: number cylinders1; allocated: number cylinders2

Explanation: The indicated area did not have enough space allocated to it to allow processing to continue. There is not enough space in the RAA as indicated in the DMB. Reorganization for the indicated area terminates.

User response: Use IDCAMS to delete and define a cluster, allocating more space, and rerun the job.

BMC111173I

dbdname, areaname: Area initialization complete

Explanation: The indicated area for the indicated database has completed initialization for the database change process. Processing continues.

User response: No action is required.

BMC111174I

dbdname, areaname: Area termination complete

Explanation: The indicated area for the indicated database has completed termination for the database change process. Processing continues.

User response: No action is required.

BMC111175C

dbdname, areaname: Unable to resolve PCL pointer. Expected pointer1, found pointer2 . UOW#=uow

Explanation: Fast Path Reorg/EP was unable to resolve the physical child last (PCL) pointer for the indicated RBA. There is a pointer problem in the area, or the area has been corrupted. Depending on the error threshold set, the UOW is bypassed or processing terminates with user abend U1001.

User response: To determine the extent of the problem, run Fast Path Analyzer/EP.

BMC111176C

dbdName, areaName: Unable to resolve PCF pointer. Expected pointer1 , found pointer2. UOW#=uow

Explanation: Fast Path Reorg/EP was unable to resolve the physical child first (PCF) pointer for the indicated RBA. There is a pointer problem in the area, or the area has been corrupted. Depending on the error threshold set, the UOW is bypassed or processing terminates with user abend U1001.

User response: To determine the extent of the problem, run Fast Path Analyzer/EP.

BMC111177E

dbdname, indexName: Duplicate key found in index file

Explanation: A duplicate index key has been detected for the index file that is being created. The index file is skipped.

User response: The duplicate index file error might occur because the index definition does not provide a unique key. Check the SRC and SUBSEQ field definitions to ensure that a unique key is created for each index file.

BMC111179E

dbdname, segname: Invalid hierarchical structure change

Explanation: An invalid or unsupported hierarchical structure change has been detected in the DMB from the data set identified by the NEWACB DD statement. The utility returns with a condition code 12.

User response: Verify the NEWACB data set is correctly specified and the DBDGEN and ACBGEN have been performed correctly for the database being processed. Refer to the product documentation for information about the structure changes that are supported. Correct any errors, and rerun the job.

BMC111180E

dbdname: Root segment name mismatch between oldsegname and newsegname

Explanation: The root segment name in the DMB from the NEWACB data set does not match the old DMBs root segment name. The utility returns with a condition code 12.

User response: Verify the NEWACB data set is correctly specified and the DBDGEN and ACBGEN have been performed correctly for the database being processed. Correct any errors, and rerun the job.

BMC111181I

dbdname, segname: Segment code segcode added to hierarchical structure

Explanation: A segment has been added in the new DMB with the indicated segcode. Processing continues.

User response: Ensure that you intended to add the segment code. If not, correct the NEWACB DMB, and rerun the job.

BMC111182I

dbdname, segname: Segment code segcode deleted from hierarchical structure

Explanation: A segment with the indicated segcode in the old DMB has been deleted in the new DMB. Processing continues.

User response: Ensure that you intended to delete the segment code. If not, correct the NEWACB DMB, and rerun the job.

BMC111183I

dbdname, segname: Segment code changed from oldsegcode to newsegcode

Explanation: The segment code in the old DMB has been changed in the new DMB. Processing continues.

User response: Ensure that you intended to change the segment code. If not, correct the NEWACB DMB, and rerun the job.

BMC111184I

dbdname, segname: Key parameters (START,BYTES) changed from (oldstart, oldbytes) to (oldstart, oldbytes)

Explanation: The segment's key position and/or length in the old DMB has been changed in the new DMB. Processing continues.

User response: Ensure that you intended to change the key. If not, correct the NEWACB DMB, and rerun the job.

BMC111185I

dbdname, segname: COMPRTN parameter parameter added

Explanation: The segment edit/compression exit routine has been added in the new DMB. Processing continues.

User response: Ensure that you intended to add the segment edit/compression exit routine. If not, correct the NEWACB DMB, and rerun the job.

BMC111186I

dbdname, segname: COMPRTN parameter parameter deleted

Explanation: The segment edit/compression exit routine has been deleted from the new DMB. Processing continues.

User response: Ensure that you intended to delete the segment edit/compression exit routine. If not, correct the NEWACB DMB, and rerun the job.

BMC111187I

dbdname, segname: COMPRTN parameter changed from oldparameter to newparameter

Explanation: The segment edit/compression exit routine has been changed in the new DMB. Processing continues.

User response: Ensure that you intended to change the changed segment edit/compression exit routine. If not, correct the NEWACB DMB, and rerun the job.

BMC111188I

dbdname: RMNAME parameter changed from oldparameter to newparameter

Explanation: The randomizer name in the old DMB has been changed in the new DMB. Processing continues.

User response: Ensure that you intended to change the randomizer name. If not, correct the NEWACB DMB, and rerun the job. If you are using a generalized randomizer, ensure all areas of the database are reorganized with the new DBD before starting the database.

BMC111189I

dbdname, areaname: SIZE parameter changed from oldparameter to newparameter

Explanation: The area's control interval size in the old DMB has been changed in the new DMB. Processing continues.

User response: Ensure that you intended to change the control interval size. If not, correct the NEWACB DMB, and rerun the job.

BMC111190I

dbdname, areaname: Area number areanumber added to database structure

Explanation: An area has been added in the new DMB. Processing continues.

User response: Ensure that you intended to add the area. If not, correct the NEWACB DMB, and rerun the job. If you are using a generalized randomizer, ensure all areas of the database are reorganized with the new DBD before starting the database.

BMC111191I

dbdname, areaname: Area number areanumber deleted from database structure

Explanation: An area has been deleted from the new DMB. Processing continues.

User response: Ensure that you intended to delete the area. If not, correct the NEWACB DMB, and rerun the job. If you are using a generalized randomizer, ensure all areas of the database are reorganized with the new DBD before starting the database.

BMC111192I

dbdname, areaname: Area number changed from oldarea to newarea

Explanation: The area's area number in the old DMB has been changed in the new DMB. Processing continues.

User response: Ensure that you intended to change the area number. If not, correct the NEWACB DMB, and rerun the job. If you are using a generalized randomizer, ensure all areas of the database are reorganized with the new DBD before starting the database.

BMC111193I

dbdname, areaname: ROOT parameter changed from oldparameter to newparameter

Explanation: The area's root parameter in the old DMB has been changed in the new DMB. Processing continues.

User response: Ensure that you intended to change the root parameter. If not, correct the NEWACB DMB, and rerun the job. If you are using a generalized randomizer, ensure all areas of the database are reorganized with the new DBD before starting the database.

BMC111194I

dbdname, areaname: UOW parameter changed from oldparameter to newparameter

Explanation: The area's uow parameter in the old DMB has been changed in the new DMB. Processing continues.

User response: Ensure that you intended to change the uow parameter. If not, correct the NEWACB DMB, and rerun the job. If you are using a generalized randomizer, ensure all areas of the database are reorganized with the new DBD before starting the database.

BMC111195C

dbdname: Change affecting COMPRTN without EXPAND=YES

Explanation: The new database description has a change to a segment edit/compression exit routine name or to a segment attribute, and the exit routine will not be invoked. Processing terminates.

User response: Specify the EXPAND=YES keyword and rerun the job.

BMC111196W

dbdname, segname: Segment format changed without START of key changing

Explanation: The segment changed from variable or fixed format, but the relative starting position of the key field has not changed. Processing continues.

User response: Ensure the start of the key field is in the proper location for this segment format. If not, correct the NEWACB DMB, and rerun the job.

BMC111197I

dbdname: All UOWs will be selected for processing.

Explanation: Either COMPRESS=YES has been requested, or the database has defined SDEPs and EXTEND_IOVF_#UOW has been specified. As a result, all UOWs must be processed, and the SELECT_UOW and FRAGMENTATION_PERCENT keywords will be ignored. Processing continues.

User response: No action is required.

BMC111198C

dbdname, areaname: Output Thread Terminated, S value ; U value

Explanation: A task started to perform a database change function terminated with the indicated abend. Processing for the indicated database and area is terminated. Processing for other areas being done by other tasks will continue.

User response: Correct the problem, and resubmit the job indicating processing for those areas only.

BMC111199I

dbdname: count Output Threads started for Database Change

Explanation: Fast Path Reorg/EP has started the indicated number of output threads to process a database change request. Processing will continue using these tasks.

User response: No action is required.