DLAKWT (or DDCKWT) NOT FOUND, VERIFY AND CORRECT DLALIB: dataSetName
Explanation: An attempt to load the DELTA IMS keyword table (DLAKWT or DDCKWT) failed. The requested function is not executed.
User response: Ensure that the appropriate module (DLAKWT or DDCKWT) is present in the DELTA IMS options library. Correct the name of the library if necessary.
SHARED SECONDARY INDEX DATABASE database NOT SUPPORTED
Explanation: The ADD, REVISE, or RELOAD operation referenced a shared secondary index database. Shared secondary index DMBs are not currently supported. The operation is not performed. Processing continues.
User response: No action is required.
DATABASE database REFERENCED BY PSB program
Explanation: The intent list for the named program (PSB/ACB) references this database. The operation is not performed.
User response: Issue an IMS operator /STOP command for the named program, issue a DELTA IMS RELOAD ACB for the program to flush the resident or non-resident intent list, and then retry the operation.
DELETE DMB database CALL TO POOL MANAGER FAILED
Explanation: This message indicates that after a delete call to the pool manager for this DMB, the DMB was still in virtual storage. The operation is not performed.
User response: This situation was not expected. The cause of the failure is unknown. Retry the operation. Contact BMC Customer Support if the problem persists.
BMCLINK USING INCORRECT DELTA LOGS
Explanation: The IMSID options in use by BMCLINK reference a different set of DELTA Logs from those used by IMS. When the logs referenced are different from those used by IMS, an IMS abend U0168 might occur during the next restart. Therefore, the update is rejected.
User response: Ensure that the IMSID options module in use by IMS and the one in use by BMCLINK reference the same DELTA Log data set names. Re-execute the DELTA List.
Note
If the RESLIB that is specified on the IMSID Basic Options (Page 2 of 8) panel contains a copy of the IMSID options module DLA#imsID, it should be identical to the copy contained in the APF authorized library.
DUPLICATE LOGS
Explanation: DELTA IMS requires the use of two distinct log data sets, but the same data set name was specified as both the primary and the secondary log data set. DELTA IMS prompts you for a valid log data set name.
User response: Specify different data set names for the primary and the secondary DELTA Log data sets.
PROGRAM program IS NOT STOPPED
Explanation: The ADD, REVISE, or RELOAD operation referenced a program that was neither STOPPED nor NOTINIT. DELTA IMS requires either or both of these conditions before performing this type of operation. The operation is not performed.
User response: Use the /STOP command for the indicated program and retry the operation.
PROGRAM program IS CURRENTLY SCHEDULED
Explanation: One of the following conditions occurred:
The ADD, REVISE, or RELOAD operation referenced a program that was currently scheduled in a batch (BMP) or online (MPR) region.
The program’s associated transaction has some messages queued.
User response: If the associated transaction has queued some messages, stop the transaction and retry the operation.
DELETE PSB program CALL TO POOL MANAGER FAILED
Explanation: After a delete call to the pool manager for this program (PSB/ACB), the control block was still in virtual storage. The operation is not performed.
User response: This situation was not expected. The cause for the failure is unknown. Retry the operation. Contact BMC Customer Support if the problem persists.
RTCODE routeCode REQUIRES UNKNOWN APPLCTN program
Explanation: The ADD or REVISE of the Fast Path routing code specified an APPLCTN (PSB) that is not currently defined to IMS. The operation is not performed.
User response: Use DELTA IMS to define the APPLCTN then retry the operation.
RTCODE routeCode IS CURRENTLY ACTIVE
Explanation: The APPLCTN (PSB) that is the target of this routing code is currently scheduled. The operation is not performed.
User response: Stop the region(s); then retry the operation.
LTERM lterm WILL DUPLICATE name NAME
Explanation: The proposed LTERM name will duplicate the name of another type of element already defined to IMS. The variable name can be one of the following values:
The operation is not performed. The Error Recovery panel is displayed, and the function is halted.User response: No action is required.
ACBLIB BLDL FAILED
Explanation: The ACB/DMB specified was not found in the ACBLIB data set. If the operation was an ADD or REVISE, the operation is performed, but the element is flagged NOTINIT. If the operation is a RELOAD, the operation fails, and the element is flagged NOTINIT.
User response: If the element added is a Fast Path DEDB, perform a DELETE-and-ADD operation after resolving the ACBLIB problem. If the element reloaded is a Fast Path DEDB, retry the operation after resolving the ACBLIB problem.
BLOCK FOUND IN ACBLIB WAS NOT A DMB
Explanation: The name specified on an ADD, REVISE, or RELOAD was expected to be a database name (DMB). The control block found in the ACBLIB data set was not a DMB (probably an ACB). If the operation was an ADD or REVISE, the operation is performed, but the element is flagged NOTINIT. If the operation is a RELOAD, the operation fails, and the element is flagged NOTINIT.
User response: No action is required.
BLOCK FOUND IN ACBLIB WAS NOT AN ACB
Explanation: The name specified on an ADD, REVISE, or RELOAD was expected to be a program name (PSB/ACB). The control block found in the ACBLIB data set was not an ACB (probably a DMB). If the operation was an ADD or REVISE, the operation was performed, but the element is flagged NOTINIT. If the operation is a RELOAD, the operation fails, and the element is flagged NOTINIT.
User response: No action is required.
BLOCK FOUND IN ACBLIB WAS FAST PATH MSDB
Explanation: The name specified on an ADD, REVISE, or RELOAD was expected to be a DL/I full function DMB or a Fast Path DEDB. The control block found in the ACBLIB data set was a Fast Path MSDB. If the operation was an ADD or REVISE, the operation is performed, but the element is flagged NOTINIT. If the operation is a RELOAD, the operation fails, and the element is flagged NOTINIT. After an MSDB database is added, any MODBLKS online change operation will fail with DFS3498W.
User response: To use MODBLKS online change, SYSGEN the MSDB and cold-start the system.
BLOCK FOUND IN ACBLIB NOT CURRENT IMS LEVEL
Explanation: The name specified on an ADD, REVISE, or RELOAD was expected to be an ACB or DMB that was generated by the ACBGEN utility under the current level of IMS. The control block found in the ACBLIB was not generated by the current level of the IMS utility. If the operation was an ADD or REVISE, the operation is performed, but the element is flagged NOTINIT. If the operation is a RELOAD, the operation fails, and the element is flagged NOTINIT.
User response: No action is required.
BLOCK NAME IN ACBLIB IS AN ALIAS
Explanation: The name specified on an ADD, REVISE, or RELOAD was expected to be a DMB. This name was found to be an alias in the ACBLIB data set (probably part of a shared secondary index). Shared secondary index databases are not currently supported by DELTA IMS. If the operation was an ADD or REVISE, the operation is performed, but the element is flagged NOTINIT. If the operation was a RELOAD, the operation fails, and the element is flagged NOTINIT.
User response: No action is required.
BLOCK FOUND IN ACBLIB PART OF SHARED INDEX
Explanation: The name specified on an ADD, REVISE, or RELOAD was expected to be a DMB. The control block found in the ACBLIB data set was a shared secondary index DMB. Shared secondary index databases are not currently supported by DELTA IMS. If the operation was an ADD or REVISE, the operation is performed, but the element is flagged NOTINIT. If the operation is a RELOAD, the operation fails, and the element is flagged NOTINIT.
User response: No action is required.
ACBLIB USER DATA INDICATES ZERO ACB/DMB LENGTH
Explanation: The name specified on an ADD, REVISE, or RELOAD was expected to be an ACB or a DMB. The control block found in the ACBLIB data set was not a valid ACB or DMB because the user data indicated zero for its length. If the operation was an ADD or REVISE, the operation is performed, but the element is flagged NOTINIT. If the operation is a RELOAD, the operation fails, and the element is flagged NOTINIT.
User response: No action is required.
TRANSACTION transaction WILL DUPLICATE name NAME
Explanation: The proposed transaction code name will duplicate the name of another type of element already defined to IMS. The variable name can be one of the following values:
The operation is not performed. The Error Recovery panel is displayed, and the check or execute is halted.User response: Specify another name for the transaction and retry the operation.
RESTART MESSAGE REGIONS BEFORE USING THIS ACB
Explanation: The name specified on an ADD, REVISE, or RELOAD was a valid ACB. However, its size was larger than the largest ACB found in the ACBLIB so far. Since the size of DIRCA (dependent interregion communication area) obtained by IMS at dependent region (BMP or MPP) initialization depends on the largest ACB size, DIRCA for currently active regions will be too small for this ACB. The operation is successfully performed, but the program is stopped to ensure that it will not be used.
User response: Restart all dependent regions where this program will execute then start the program.
FAST PATH INVALID FOR PGM program WITH CONV TRAN
Explanation: See the explanation for message BMC1623. The operation is not performed.
User response: No action is required.
FAST PATH INVALID CONV TRAN transaction
Explanation: The transaction named in the message is conversational. Conversational messages are not permitted for Fast Path exclusive or potential transactions. The operation is not performed.
User response: Revise the SPA size to zero for the transaction and retry the operation.
IMODULE LOAD FAILED FOR routine
Explanation: The explanation for this message depends on the product that issued the message:
(DELTA IMS)The initialization processor for DELTA IMS attempted to load DELTA IMS service routines (DLAXMVTn, DLAXCRMn, DLAXRSTn) dynamically from the IMS APF-authorized library using IMS IMODULE load. The IMODULE load failed.
DELTA IMS will be inactive for the duration of this execution of IMS.
(DELTA PLUS)The initialization processor for DELTA PLUS tried to load DELTA VIRTUAL TERMINAL service routines (VTFXVCDx, VTFEXITx, VTFSMSG0, VTFINTWA, or DFSRST00) dynamically from the IMS APF-authorized library by using IMS IMODULE load. The IMODULE load failed.
During this execution of IMS, DELTA PLUS VIRTUAL TERMINAL is inactive.
(LOCAL COPY PLUS)The initialization processor for LOCAL COPY PLUS attempted to dynamically load LOCAL COPY PLUS service routines from IMS RESLIB using IMS IMODULE load. The IMODULE load failed.
During this execution of IMS, LOCAL COPY PLUS is inactive.
User response: One or more MVS messages precede this message and clarify the error.
FAST PATH INVALID FOR QUEUED TRAN transactionType
Explanation: Transactions of the type named in the message are currently queued for processing. Queuing is not permitted prior to a revision to Fast Path. The operation is not performed.
User response: No action is required.
FAST PATH INVALID FOR PGM program WITH QUEUED TRAN
Explanation: The program named in the message currently has transactions queued for processing. Queuing is not permitted prior to a revision to Fast Path. The operation is not performed.
User response: Process or clear these transactions from the message queue then retry the operation.
ESCD LOCATE FAILED
Explanation: An attempt to locate the Fast Path extended SCD (ESCD) failed. Internal indicators indicating the presence of the Fast Path feature are inconsistent. The operation is not performed.
User response: Contact BMC Customer Support.
FAST PATH IS NOT ACTIVE IN THIS IMS SYSTEM
Explanation: The ADD or REVISE was either for a Fast Path element (that is, routing code) or a Fast Path attribute. In either event, the Fast Path feature is not part of this IMS system. The operation is not performed.
User response: No action is required.
DELTA LOGIC ERROR IN csect AT label
Explanation: An unrecoverable program logic error was detected by the named CSECT at the named label. This error usually occurs after IMS maintenance for which DELTA PLUS VIRTUAL TERMINAL may be incompatible is applied. IMS initialization fails.
User response: Check recent flashes from BMC Software for temporary circumventions, and then contact BMC Customer Support for a permanent fix.
FAST PATH REQUIRED FOR PGM program WITH RTCODE routeCode
Explanation: The REVISE did not specify the Fast Path attribute for this program; however, this program is the target of the indicated Fast Path routing code (RTCODE). The operation would result in an invalid condition. The operation is not performed.
User response: Correct any errors and retry the operation. When correcting errors, remember that the Fast Path process adds and deletes programs and transactions, depending on whether the program running is Fast Path exclusive. To include Fast Path exclusive programs and transactions, perform the following steps:
Add APPLCTN (name) and set FPATH=YES.
Add RTCODE (name) using the TRANSACT name (see step 3) and designate the PSB name added in the first step.
Add TRANSACT (name) using the RTCODE name (see step 2) and designate the PSB name added in the first step.
Delete TRANSACT.
Delete RTCODE.
Delete APPLCTN.
Add APPLCTN (name) and set FPATH=NO.
Add APPLCTN (name) and set FPATH=YES.
Add RTCODE (name) designating the PSB name added in Step 2.
Add TRANSACT (name) and set FPATH=YES, while designating the PSB name added in step 1.
Delete all RTCODES used exclusively by the transactions being deleted.
Delete all APPLCTNs used exclusively by the RTCODES deleted in the first step.
Delete Fast Path potential transactions.
Delete APPLCTN.
TRANSACTION transaction PARLIM INVALID FOR APPLCTN
Explanation: Before DELTA IMS will permit a parallel processing limit greater than zero, the associated application (APPLCTN/PSB) must specify parallel scheduling (SCHDTYP=PARALLEL). Processing continues.
User response: Use DELTA IMS to REVISE the associated application to specify parallel scheduling; then retry the transaction ADD/REVISE.
APPLCTN program CANNOT PROCESS TRANSACTIONS IN PARALLEL
Explanation: One or more transactions processed by this APPLCTN specify a PARLIM greater than zero. This value is invalid when the scheduling option for this APPLCTN is SERIAL. Processing continues.
User response: Either change the APPLCTN to SCHDTYP=PARALLEL, or REVISE the transactions processed by the APPLCTN to PARLIM=0.
SYSID EXCEEDS MAXIMUM SYSGEN SPECIFICATION
Explanation: The local or remote SYSID (numerical system identification) exceeds the maximum number that was defined during this IMS system definition with the MSNAME statements, or the SYSID does not match the MSNAME statements in the IMSGEN. The operation is not performed.
User response: No action is required.
DELTA LOGS REBUILT
Explanation: The DELTA IMS Log data sets have been successfully re-created. The error condition that may have been associated with either log data set has been cleared. Entries in the log data sets have been preserved.
User response: No action is required.
INCORRECT DELTA IMS LEVEL
Explanation: The level (version) of DELTA IMS used by the BMCLINK BMP task is not the same as the level used for DELTA IMS service routines within the IMS control region. The operation is not performed.
User response: Use the maintenance installation process to update DELTA IMS; then restart IMS or BMCLINK and retry the operation.
INCORRECT IMS VERSION
Explanation: The IMSID options defined for this IMS control region specify the incorrect IMS release. The operation is not performed.
User response: Use the IMSID Options panel to specify the correct IMS version and release. Save the updated options and retry the operation.
LTERM lterm ASSIGN FAILED - MESSAGE DFSnumber PRODUCED
Explanation: The LTERM ADD or REVISE requested that the LTERM be assigned to a specific node (IMS VTAM terminal) or subpool. DELTA IMS found that a valid node or subpool name had been provided and generated an internal /ASSIGN command. The /ASSIGN command failed and produced the indicated DFSnumber message. The operation is not performed.
User response: Research the DFSnumber message in the appropriate IBM manual. Resolve the problem and reexecute the DELTA List.
LTERM lterm CANNOT BE ASSIGNED TO NONEXISTING NODE
Explanation: The LTERM ADD or REVISE requested that the LTERM be assigned to a specific node (IMS VTAM terminal). DELTA IMS found that the node name was invalid. The operation is not performed.
User response: Reenter with a valid node name.
MSC LINK NAME INVALID ON NON-MSC SYSTEM
Explanation: The IMS control region does not use the Multiple System Coupling (MSC) feature. The MSC link name field is permitted only on systems that use the MSC feature. The operation is not performed.
User response: Blank the MCS link name field and retry the operation.
MSC LINK NAME EXCLUDES USE OF SECURITY, ASSIGN, AND AGN ACTION
Explanation: When the MSC link name is specified, the LTERM being added or revised is assumed to be MSC remote. The SECURITY, ASSIGN, and AGN ACTION fields do not apply to MSC remote LTERMs. The operation is not performed.
User response: Blank the MSC link name field or all of the other named fields and retry the operation.
MSC LINK NAME BLOCK NOT FOUND
Explanation: The MSC remote LTERM ADD or REVISE specified the name of an unknown MSC link name. The operation is not performed.
User response: Correct or blank the MSC link name field and retry the operation.
ELEMENT ALREADY HAS A DELETED STATUS
Explanation: The REVISE operation specified a new name for the element (database, program, transaction, or routing code). DELTA IMS found that the new name was the same as a name previously used and subsequently deleted. This condition is not supported. The Error Recovery panel is displayed, and the check or execute is halted.
User response: Use the ADD operation to re-add the deleted name to the system.
PROGRAM program NOT DELETED, REQUIRED BY TRAN CODE transaction
Explanation: The DELETE or REVISE WITH NEW NAME operation specified a program name that required (at least) the named transaction. The operation is not performed.
User response: Delete the transaction code then retry the operation.
UNABLE TO PROCESS - /MODIFY COMMIT PENDING
Explanation: IMS was in the process of performing an online change. That is, a /MODIFY PREPARE command was entered that was not followed by /MODIFY COMMIT or ABORT. The operation is not performed.
User response: No action is required.
UNABLE TO ASSIGN MASTER TERMINAL
Explanation: The LTERM ADD or REVISE specified the name of the Master or Secondary Master Terminal. It also specified that the Master Terminal was to be reassigned. DELTA IMS does not support reassignment of the Master Terminal. The operation is not performed.
User response: No action is required.
DLAXALUx/DLAXALIx/DLAXGNIx MISSING
Explanation: The requested user exit load module name was not found in the STEPLIB. The requested function is not executed.
User response: Respecify the suffix of an existing user exit module.
COMPLETE THE NAME
Explanation: A user exit name is required for option 4 (User Report). Processing continues.
User response: Type one character to complete the name of the user exit for option 4.
DUPLICATE SORT LVLS
Explanation: Sort levels are the numbers 1 through 5. You can use a sort level only once. DELTA IMS prompts you for the correct sort level.
User response: Respecify unique sort level numbers.
INVALID SORT LEVEL
Explanation: Sort levels are the numbers 1 through 5. A sort level outside this range was selected. DELTA IMS prompts you for the correct sort level.
User response: Respecify sort level numbers within the range 1 through 5.
VERIFY/PRESS 'Enter'
Explanation: Specified parameters for log data set allocation have been inspected and approved by DELTA IMS. DELTA IMS waits for you to press Enter or cancel the operation.
User response: Check the allocation parameters. If they are correct, press Enter to begin formatting. If they are incorrect, cancel the operation.
FORMATTING LOG log
Explanation: The named DELTA Log is currently being formatted.
User response: No action is required.
LOGS FORMATTED
Explanation: Both DELTA Log data sets have been successfully formatted and are ready for use.
User response: No action is required.
STATUS=NEW REQUIRED
Explanation: The specified log data set was not cataloged. DELTA IMS prompts you for the correct input.
User response: Specify STATUS=NEW for the data set. If the data set already exists but is not cataloged, you must catalog it before you can format it.
STATUS=OLD REQUIRED
Explanation: The specified log data set was cataloged. DELTA IMS prompts you for the correct input.
User response: Specify STATUS=OLD for the data set. If the data set does not exist but is cataloged, you must uncatalog, reallocate, and then format it.
UNIT REQUIRED
Explanation: The unit name (for example, DISK or SYSDA) is required when volume-serial is specified. DELTA IMS prompts you for the correct input.
User response: Specify the type of unit where the log data set is to be allocated and press Enter.
VOLUME REQUIRED
Explanation: The volume serial number is required when allocating new data sets. DELTA IMS prompts you for the correct input.
User response: Specify the volume serial number of the storage device where the log data set is to be allocated and press Enter.
CHECK SPACE UNITS
Explanation: The supported units of space allocation are CYLS and TRKS. DELTA IMS prompts you for the correct input.
User response: Type TRKS or CYLS for the space units and press Enter.
NOT EXPDT AND RETPD
Explanation: EXPDT (expiration date) and RETPD (retention period) are mutually exclusive. If you specify one, you cannot specify the other. DELTA IMS prompts you for the correct input.
User response: Blank out one or the other and press Enter.
CHECK NUMERIC FIELD
Explanation: A nonnumeric character was entered where only numeric data was expected. DELTA IMS prompts you for the correct input.
User response: Re-enter the data using numeric digits only.
LOG data set dataSetName, condition imsID
Explanation: One of the following unusual conditions applies to the log data set. In addition to this message, DELTA IMS issues a return code that indicates the system action that was taken. This error message will be suffixed with the system’s IMSID if the message is issued in a batch environment.
condition | Description |
|---|---|
OPEN RC=4 | The log control record indicates the log was not closed after its last use by the DELTA IMS subtask of BMCLINK. This record might also mean that it is currently in use by BMCLINK or that an IMS restart is in progress. |
FULL RC=4 | All of the available log records have been used. No additional DELTA IMS updates to IMS may be made until either the log is expanded or inactive records have been purged from the log. |
IN ERROR RC=4 | A prior error occurred on this log data set. No additional DELTA IMS updates may be made until the error condition has been reset. The error condition will not inhibit IMS restart or input only type functions. |
UNAVAILABLE RC=8 | A prior message should have indicated why the log is unavailable. The log data set might have been deleted, uncataloged, or allocated for exclusive use by another task. This condition should be investigated and resolved. |
REQUIRES AN IMS RESTART RC=4 | DELTA IMS made an incomplete update to the log data set. Either an update is in progress, or the DELTA IMS BMP subtask of BMCLINK failed during an update. If the BMP task failed, the following conditions apply:
|
OPEN FAILED RC=8 | An OPEN macro against the log data set did not complete execution successfully. Research the system log for messages that reveal why the OPEN failed. Resolve the problem. |
INVALID DATA SET RC=8 | This condition occurs when one of the following conditions exists:
If one of the DELTA Logs is valid, the error condition will not inhibit IMS restart or input only type functions. If none of the DELTA Logs are valid, this condition will be followed by a U4063 abend. You can use the DELTA IMS - Log Utility panel to display the status of the DELTA Log data sets. |
GET CALL SEQUENCE ERROR RC=8 | DELTA IMS detected an internal logic error. A GET NEXT record call was issued to the log I/O routine, but position had never been previously established. Contact BMC Customer Support. |
INCORRECT IMSID RC=8 | The IMSID passed to the log I/O routine for which log data sets have been allocated does not equal the IMSID contained in the log control record. The IMSID is inserted in the log control record when the data set is formatted. This situation means that one of the following statements is true:
|
UNEXPECTED END-OF-FILE RC=4 | A read against the log data set resulted in an end-of-file. DELTA IMS manages records in the log data set based on information contained in the log control record created when the log was formatted. When the log control record is valid, a read will normally not be issued if it will result in an end-of-file. This unexpected condition is treated as an I/O error. The log data sets must be recovered before additional DELTA IMS updates will be allowed. This condition can also occur if the DELTA Logs have been properly allocated (with an LRECL of 150, and a BLKSIZE which is a multiple of 300) but have not been formatted. The DELTA Logs must be formatted before DELTA IMS updates can be made. |
RECORD NUMBER EXCEEDS MAXIMUM RC=8 | DELTA IMS detected an internal logic error. A read or write call to the log I/O routine specified a record number greater than the number of records in the log. Contact BMC Customer Support. Processing status depends on the return code, which can be any of the following:
|
User response: If you are overriding the DELTA Logs in the IMS control region with DD statements BMCDLAL1 and BMCDLAL2, verify that they are pointing to the correct set of DELTA Logs.
READING LOGS
Explanation: This message informs you of the progress of the log utility function being performed.
User response: No action is required.
QSAM OUTPUT OPEN FAILED
Explanation: An attempt to open an output data set failed. Possible data sets include the log list browse file, the optional log list output data set, and the Stage-1 output data set when using the CONVERT option to convert a DELTA List to Stage-1 output. The requested function is not executed.
User response: Use the HELP key to display the long message text to further identify the failure.
USER EXIT exitName NOT FOUND
Explanation: The user authorization exit specified in the IMSID options for the IMSID or the customization exit was not found. The operation is not performed.
User response: Ensure that the same STEPLIB is being used by ISPF and BMCLINK. If necessary, correct or blank the authorization exit in the IMSID options display.
REJECTED BY USER EXIT exitName
Explanation: Your installation authorization exit for this IMSID or the customization exit disallowed this request. The requested function is not executed.
User response: No action is required.
DELTA OPTIONS MODULE module MISSING
Explanation: The IMSID options module for this IMSID was not found in the DELTA IMS options library (or APF-authorized library if the message was issued from the IMS control region). The requested function is not executed.
User response: Verify that you typed the IMSID correctly. If the IMSID is correct, examine the IMS APF-authorized library to ensure that the options module has been copied from the options library to the APF-authorized library. If the module is not present, use the IMSID Options panel SAVE command to create an IMSID options module (which will be link-edited to the options library).
LOG RECOVER REQUIRED, WRITE REJECTED
Explanation: The DELTA Log control record indicated that a prior error had occurred. The operation is not performed.
User response: Use the Log Utility Recover panel to clear the error and reconstruct the log data sets. Then retry the operation.
PRIOR ERROR ON BOTH LOGS
Explanation: The DELTA Log control record indicates that prior errors have occurred on both log data sets. Therefore, all DELTA Log data is irretrievably lost. The requested function is not executed.
User response: Use the Log Utility Format panel to reformat the log data sets, cold-start IMS, then retry the operation.
END-OF-FILE - LOG status
Explanation: The DELTA IMS Log data sets are full, functionally null, or empty. The requested function is not executed.
User response: Perform the appropriate DELTA log maintenance. For more information, see the DELTA IMS User Guide.
SORT sortProgram FAILED
Explanation: The Sort/Merge program passed a nonzero return code. An attempt will be made to display the sort message data set for problem determination. The requested function is not executed.
User response: No action is required.
SORT MESSAGE OPEN FAILED
Explanation: The Sort/Merge program passed a nonzero return code. An attempt to open and read the sort message data set also failed. The requested function is not executed.
User response: Gather problem determination information for this condition by allocating ddname SORTMSGS to the terminal and retrying the operation. Contact BMC Customer Support if the problem persists.
SYNTAX ERROR
Explanation: The contents of the DUMP field do not comply with syntax conventions. The requested function is not executed.
User response: Correct the syntax error and retry the operation. For the syntax rules for this field, see the DELTA IMS VIRTUAL TERMINAL User Guide.
INVALID BLOCK TYPE
Explanation: The first operand of the DUMP field was neither the name of a supported control block type nor a valid hexadecimal number. The requested function is not executed.
User response: Correct the operand and retry the operation. For more information, see the DELTA IMS VIRTUAL TERMINAL User Guide.
BLOCK NOT FOUND
Explanation: The specified control block name was not found. The requested function is not executed.
User response: Correct the name of the DUMP field and retry the operation. For more information, see the DELTA IMS VIRTUAL TERMINAL User Guide.
MEMORY ACCESS VIOLATION
Explanation: A storage protection program interruption occurred when accessing or attempting to alter the specified storage. This occurrence might mean that an invalid address was developed or that the storage was fetch or store protected. The display or zap is not performed.
User response: No action is required.
VERIFY FAILED
Explanation: The contents of storage to zap did not match the contents as originally displayed by DELTA IMS. The zap is not performed.
User response: Redisplay the storage, make the desired alteration, and retry the zap.
FUNCTION UNAVAILABLE
Explanation: This feature is prohibited or disabled by the IMSID options for the desired IMS control region. The requested function is not executed.
User response: Ensure that the IMSID options do not prohibit the requested feature. Ensure that the IMSID options are configured to support the desired feature. If you are running both DELTA VIRTUAL TERMINAL and DELTA PLUS, only the following functions are supported from the DELTA VIRTUAL TERMINAL interface:
Update IMSID options in the IMS control region
Refresh TSS tables in the IMS control region
Refresh CPU-ID in the IMS control region
Execute IMS commands
FOUND - OFFSET offset
Explanation: The string was found at the indicated offset in the area displayed. The string will be displayed in the top line of scrollable area.
User response: No action is required.
YOU ZAPPED IT
Explanation: The zap was successfully applied.
User response: No action is required.
TYPE DUMP REQUEST
Explanation: The address of storage to be displayed is missing from the DUMP field. DELTA IMS prompts you for further action.
User response: Type the address in the DUMP field.
A ZAP IS PENDING
Explanation: A request to exit the Zap/Display facility cannot be honored while changes to the currently displayed IMS storage are still pending. DELTA IMS prompts you for further action.
User response: Type ZAP (or RESET) to apply (or discard) all pending changes.
NO CHANGES
Explanation: This message is issued in response to a ZAP command when no changes have been made to the storage displayed. The command is ignored.
User response: No action is required.
INCONSISTENT PARMS
Explanation: Duplicate or inconsistent FIND command parameters were encountered. DELTA IMS prompts you for further action.
User response: Check for duplicate or contradictory keywords. Place quotation marks around the search string if it duplicates a keyword.
INVALID HEX DIGIT
Explanation: A character entered in the hexadecimal display area was other than 0 to 9 and A to F. Only these hexadecimal digits are allowed. DELTA IMS prompts you for further action.
User response: Type a valid storage address as the operand of the LOCATE command.
INVALID HEX STRING
Explanation: The string to find was not enclosed in quotation marks and contained characters other than 0 to 9 and A to F. Character strings may contain any characters, but they must be enclosed in single quotation marks. DELTA IMS prompts you for further action.
User response: Type the hexadecimal value using an even number of hexadecimal digits (0 to 9, A to F).
INVALID DUMP LENGTH
Explanation: Either a nonnumeric value or an out-of-range value was entered as the storage dump length. DELTA IMS prompts you for further action.
User response: Type a valid, numeric dump length between 0 and 9999.
PARM NOT RECOGNIZED
Explanation: The NEXT, ALL, FIRST, LAST, or PREV keyword is misspelled. DELTA IMS prompts you for further action.
User response: Check for misspelled keywords or embedded blanks and correct.
TOP/BOTTOM OF DATA REACHED
Explanation: Either the beginning or the end of the area was reached before (another) occurrence of the string was found. Processing continues.
User response: Type RFIND again to restart from either the top or bottom of the data.
COMMENT REQUIRED
Explanation: A comment is required as documentation for all storage zap(s). DELTA IMS prompts you for an entry in the Comment field.
User response: Place a short comment documenting the zap in the Comment field and press Enter.
TSS BUFFERS EMPTY, NO PREVIOUS TABLE READS
Explanation: A TSS refresh request could not complete processing because there were no TSS look-aside buffers to refresh. IMSID options were specified incorrectly, or the TSS table you specified has not been accessed. Processing continues.
User response: Verify that the IMSID options specify a non-zero TSS look-aside buffer count and a valid TSS data set. Also verify that the TSS translation tables are actually being used in the target IMS control region.
LOAD OF DELTA IMS INITIALIZER name FAILED
Explanation: See the explanation for message BMC1691. IMS restart continues without DELTA IMS.
User response: No action is required.
DELTA IMS INACTIVE
Explanation: The DELTA IMS initialization routine could not be loaded, probably because it was not found in an APF-authorized library. The module name is DLAXNTL n (IMS control region) or DLAXDL1 n (DL/I SAS). IMS restart continues without DELTA IMS.
User response: Use the install procedure to update DELTA IMS and restart IMS.
DELTA VIRTUAL TERMINAL { INITIALIZATION | RESTART } COMPLETE
Explanation: This message is issued after successful DELTA VIRTUAL TERMINAL initialization and at the completion of IMS restart. During this execution of IMS, DELTA VIRTUAL TERMINAL is active.
User response: No action is required.
*BMCLINK* ACTIVE
Explanation: The BMCLINK task is active. The outstanding operator reply (WTOR) associated with this message may be used by the operator to communicate with BMCLINK. You can delete this WTOR by replying nnDEL to the WTOR.
User response: No action is required.
*BMCLINK* SHUTDOWN IN PROGRESS
Explanation: BMCLINK has been instructed to shut down. All active subtasks have been posted to shut down. BMCLINK terminates when all subtasks have terminated.
User response: No action is required.
*BMCLINK* BMP CONTROL FOR imsID ABENDED completionCode
Explanation: The BMP control task for the indicated IMSID bended. The variable completionCode is the system or user completion code. The requested function is not executed.
User response: You might need to restart the BMCLINK PSB and transaction code on this IMS system before retrying the transaction.
*BMCLINK* VTAM INTERFACE ACTIVE
Explanation: The BMCLINK VTAM interface has successfully initialized and is ready for user session logons.
User response: No action is required.
*BMCLINK* VTAM function OBTAINED RC=returnCode, FDBK2=feedbackCode problem
Explanation: The named function received the indicated return code and feedback code. The requested function is not executed. Message text RC=x'14', FDBK2=x'13', INVALID CID indicates that the communication link between BMCLINK and DELTA IMS is broken. This problem typically occurs when BMCLINK does not receive a response from the IMS control region in a timely fashion.
User response: For message text RC=x'14', FDBK2=x'13', INVALID CID, try restarting BMCLINK. Otherwise, see IBM’s manual for VTAM messages and codes for a more detailed description of the return code and feedback code for the indicated function.
IMS OPTIONS MODULE DLA#imsID MISSING
Explanation: The parameter module for the IMSID named DLA#imsID was not found in the STEPLIB or the Network Luname specified in the DLA#imsID module might be referencing the wrong BMCLINK. An attempt to load DLA#imsID by the BMCLINK task fails.
User response: Ensure that the BMCLINK STEPLIBs point to the same DELTA IMS data set that is used for the TSO/ISPF DELTA user session. Also, confirm that the Network Task Luname specified in the DELTA options module DLA# imsID is the correct name for the desired BMCLINK task. If necessary, use the IMSID Options panel to re-create the options modules for this IMSID.
