This chapter lists all messages generated by CA IDMS DME. All messages are preceded by a unique eight-character code. The message code is in an xxxnnnns format, where xxx is the ID of the product issuing the message, nnn is a number for the message within the module, and s is the severity code for the message. The severity code will be I, W, or E. Severity codes are explained below. Condition codes are explained on the following page.
(I) Informative—A message with a severity code of I is an informative message. Informative messages need no remedial action.
(W) Warning—A message with a severity code of W is a warning message. Warning messages describe situations which may lead to unexpected results.
(E) Error—A message with a severity code of E is an error message. Error messages report erroneous and conflicting data that inhibits processing. You must take some corrective action to resolve the problem.
Reason:
An invalid parameter sequence was specified during CA IDMS/DC Sort processing, where x represents the TPSPROC value, and y represents the number of the invalid parameter.
Action:
Review the CA IDMS/DC Sort parameters for errors. If the syntax is correct, contact Technical Support.
Reason:
CA IDMS/DC Sort found a value other than 'U' or 'S' in TPSRQST.
Action:
Review the CA IDMS/DC Sort parameters for errors. If the syntaxes correct, contact Technical Support.
Reason:
CA IDMS/DC Sort found a value other than 'I', 'C' or 'P' in TPSELEM.
Action:
Review the CA IDMS/DC Sort parameters for errors. If the syntax is correct, contact Technical Support.
Reason:
The value in TPSRQST conflicts with the value in TPSELEM.
Action:
If TPSRQST has a value of 'U', TPSELEM must have a value of 'I' or 'C'. If TPSRQST has a value of 'S', TPSELEM must have a value of 'P' or blank.
Review the CA IDMS/DC Sort parameters for errors. If the syntax is correct, contact Technical Support.
Reason:
The parameter number is in the format xy. A value in the TPSPROC parameter list, represented by x, is invalid. Y represents the sequential number of the parameter.
Action:
Review the CA IDMS/DC Sort parameters for errors. If the syntax is correct, contact Technical Support.
Reason:
TPSPROC contains a value other than 'SETSORT', 'PUTSORT','GETSORT' or 'ENDSORT'.
Action:
Review the CA IDMS/DC Sort parameters for errors. If the syntax is correct, contact Technical Support.
Reason:
TPSPROC value of 'PUTSORT', 'GETSORT' or 'ENDSORT' was specified, but no CA IDMS/DC Sort controls were set up for this session.
Action:
Enter the necessary syntax to establish a SETSORT for this session.
Reason:
The indicated sort session contains two SETSORT requests without an intervening ENDSORT within a single task invocation.
Action:
Include an ENDSORT prior to the second SETSORT for this session.
Reason:
The number of keys is either less than 1 or greater than 16.
Action:
Review the CA IDMS/DC Sort parameters for errors. If the syntax is correct, contact Technical Support.
Reason:
The TPSRLEN field is less than 1 or greater than 32,000 for CA IDMS or 16,000 for CICS.
Action:
Contact Technical Support.
Reason:
In the indicated session-number, a SETSORT request was made without a record-name parameter.
Action:
Review the CA IDMS/DC Sort parameters for errors. If the syntax is correct, contact Technical Support.
Reason:
The sort-control record for the indicated session contains incorrect values. An element that is not in the session record has been specified in the FIELDS statement.
Action:
Correct the invalid FIELDS statement.
Reason:
The field-length specified for a field-name in a FIELDS statement exceeds the record boundary.
Action:
Correct the invalid FIELDS statement.
Reason:
An invalid sort order was specified in the keys section.
Action:
Correct the value to either A or D in the sort keys table.
Reason:
In the current sort session, the maximum number of bytes allowed in MAIN and AUX has been exceeded.
Action:
In the user program, check for program loops which may be causing excessive PUT requests. If the program logic is correct, have your system programmer review the MAIN and AUX values in the TPSPARM macro to determine whether they need to be increased. See Chapter 4, “Commands” for more information.
Reason:
The applications program has attempted to write another record after one or more GET requests have been issued.
Action:
Either remove the PUTSORT from the program logic, or close or open the session with an ENDSORT/SETSORT sequence.
Reason:
A required storage block allocation failed.
Action:
Retry the application. If this message is frequently issued, review storage pool definitions for your online regions.
Reason:
The buffer address of the area into which sorted records are returned has been overlaid.
Action:
Review program logic to ensure that a loop has not overlaid TPSORT control blocks. If there is no apparent cause for the control block alteration, contact Technical Support.
Reason:
The sort queue for the indicated session-number was empty. AGETSORT request was issued, but no records were sent to CA IDMS/DC Sort through PUTSORT requests.
Action:
Review your program to determine if the condition is appropriate.
Reason:
The top or bottom of the sorted queue for the indicated session has been reached. Process-type indicates if the condition occurred during NEXT or PRIOR processing.
Action:
If you wish to take advantage of this condition and execute special processing at the end of the queue, add program logic to trap the TPSRETN value 7020. The content of the sorted record is unpredictable until another GETSORT request is successfully executed.
Reason:
The session-number specified in the SESSION statement is not an integer between 0 and 9.
Action:
Correct the SESSION statement and retry the preprocessor.
Reason:
The number in TPSKNUM and the number of parameters in the interface call to TPSET do not agree.
Action:
Contact Technical Support.
Reason:
A SETLIMIT statement for session n appears in the program after one or more PUTSORT statements for session n. For a given session, SETLIMIT must appear before any PUTSORTs.
Action:
Correct the program by moving the SETLIMIT statement for session n to a position after the SESSION statement for session n and before any PUTSORTs for session n.
Reason:
The program contains a SETLIMIT statement, but your installation prohibits its use.
Action:
Correct the program by removing the SETLIMIT statement. Or, contact your systems programmer to reassemble the tailoring macro TPSPARM. This macro currently specifies LIMLOCK=Y, which prohibits use of the SETLIMIT statement. To allow use of SETLIMIT, TPSPARM must be reassembled with LIMLOCK=N, and CA IDMS/DC Sort must be relinked with the reassembled TPSPARM object deck.
Reason:
The user has attempted to execute the CA IDMS/DC Sort CA ADS preprocessor. The module name parameter from the data stream or the user display cannot be located in the dictionary/node/version specified.
Action:
Correct module name, dictionary, node, and/or version.
Reason:
The dictionary and/or node specified to the CA IDMS/DC Sort CA ADS preprocessor does not exist under the current CV.
Action:
Correct dictionary and/or node names.
Reason:
An invalid or missing data stream has been entered as part of the execution of the TPSG task.
Action:
Enter the required information in the screen display.
Reason:
An invalid module-name format was specified as part of the TPSG task data stream. The module name must be between 1 and 32 alphanumeric, non-space characters.
Action:
Correct the module name in the user display.
Reason:
Following the version-number default, the next fields must be a 1-to 8-character dictionary name or dictionary name default (represented by a comma), followed by a 1-to 8-character node name or node name default (represented by a comma).
Action:
Correct dictionary and/or node values in the user display.
Reason:
The parameter after the module name in the TPSG task data stream must be a display integer between 1 and 9999, or the version number default (represented by a comma).
Action:
Enter a valid version number in the user display.
Reason:
The dictionary name in the TPSG task data stream is not either a 1-to 8-character alphanumeric field, or the dictionary default (represented by a comma).
Action:
Enter a valid dictionary name in the user display.
Reason:
The node name in the TPSG task data stream is not either a 1- to8-character alphanumeric field, or the node default (represented by a comma).
Action:
Enter a valid node name in the user display.
Reason:
The end of the CA ADS process source was reached, but a CA IDMS/DC Sort syntax set was still in progress. CA IDMS/DC Sort syntax must be terminated with a period (.) or a semi-colon (;), and must wholly reside within a single, non-included module.
Action:
Either correct the syntax using the EDITOR, issuing a RETRY in the EDITOR command line, or CANCEL the preprocessor section.
Reason:
To initiate a CA IDMS/DC Sort CA ADS Preprocessor session, a minimum entry of module name is required.
Action:
Enter a module name in the user display.
Reason:
The user has requested the termination of the current CA IDMS/DC Sort preprocessing.
Action:
None.
Reason:
A single CA IDMS/DC Sort syntax statement can only occupy 50 lines of user source.
Action:
Reduce the number of lines in the indicated statement to 50.
Reason:
An invalid or misplaced word has been detected in the CA IDMS/DC Sort syntax, where word-position represents the sequential position in the CA IDMS/DC Sort statement.
Action:
Correct the CA IDMS/DC Sort syntax, and enter RETRY in the EDITOR command line.
Reason:
A CA IDMS/DC Sort statement has been incorrectly specified. Usually this error occurs because the statement terminator was encountered before a sub statement was fully qualified.
Action:
Correct the CA IDMS/DC Sort syntax, and enter RETRY in the EDITOR command line.
Reason:
A parameter sub statement has failed a length edit at the specified word.
Action:
Correct the CA IDMS/DC Sort syntax, and enter RETRY in the EDITOR command line.
Reason:
Instead of the expected terminator, the specified word was encountered.
Action:
Correct the CA IDMS/DC Sort syntax, and enter RETRY in the EDITOR command line.
Reason:
The current SETSORT request requires a FIELDS keyword and one or more sets of FIELDS sub parameters.
Action:
Correct the SETSORT syntax and retry the preprocessor.
Reason:
The SETSORT statement specified a record that could not be located in the indicated dictionary/node/version.
Action:
Correct the FOR statement, and retry the preprocessor.
Reason:
An element name in the FIELDS statement could not be located in the record specified in the FOR statement.
Action:
Correct the statement in error and retry the preprocessor.
Reason:
The indicated module has been successfully updated.
Action:
None.
Reason:
An attempt has been made to update the indicated dictionary in update mode. This error is associated with the CA ADS Preprocessor only.
Action:
Check the status of the area or specify another dictionary.
Reason:
The TPSG verb was entered in CA IDMS DME, and the syntax was preprocessed without errors.
Action:
None.
Reason:
The TPSG verb was entered in CA IDMS DME, and errors were encountered in the TPSORT syntax.
Action:
Review the embedded error messages following each TPSORT statement in error, and reenter the TPSG verb after all errors are corrected.
Reason:
Element-name is an 88-level condition name and cannot be used as a sort key. A field name is required.
Action:
Replace element-name with a valid field name.
Reason:
An error occurred during the CA IDMS/DC Sort CA ADS preprocess or interface to the EDITOR.
Action:
Contact Technical Support.
Reason:
An error occurred during the CA IDMS/DC Sort CA ADS preprocess or interface to the EDITOR.
Action:
Contact Technical Support.
Reason:
An error occurred during the CA IDMS/DC Sort CA ADS preprocess or interface to the EDITOR.
Action:
Contact Technical Support.
Reason:
An error occurred during the CA IDMS/DC Sort CA ADS preprocessor interface to the EDITOR.
Action:
Contact Technical Support.
Reason:
An error occurred during the CA IDMS/DC Sort CA ADS preprocessor interface to the EDITOR.
Action:
Contact Technical Support.
TPP7096E GSIUPLOW MODULE ERROR MESSAGE: error-message
Reason:
An error occurred during the case change to CAPS ON for the CA IDMS/DC Sort CA ADS preprocessor.
Action:
Contact Technical Support.
Reason:
The current request requires a record name in TPSRECN.
Action:
Contact Technical Support.
Reason:
A non-CA IDMS USER request requires element names in TPSKOCCS.
Action:
If the call was formatted by a preprocessor, contact Technical Support.
Reason:
A CA IDMS USER request is in progress, but the value specified in TPSRECN cannot be located using the values in TPSRVRS, TPSDICT, and TPSNODE.
Action:
Correct the values which are in error, recompile the dialog or program, and reexecute.
Reason:
This release of CA IDMS/DC Sort does not support a USER request for records that contain more than 720 elements.
Action:
Create a new record equivalent containing 720 or fewer elements, recompile the dialog or program, and reexecute.
Reason:
Sufficient storage was not available to complete the USER request.
Action:
Increase the available user storage for the TP monitor.
Reason:
A USER sort request was terminated before a key was specified.
Action:
None. The user program must contain logic to recognize this condition.
Reason:
During a USER sort request, the user specified more than 16 keys.
Action:
Reinvoke the USER sort request, specifying 16 or fewer keys.
Reason:
A value other than 1 through 16 was specified in the SEQUENCE field on the CA IDMS/DC Sort USER screen.
Action:
Correct the indicated SEQUENCE field.
Reason:
More than one SEQUENCE field contains the same value on a USER sort screen.
Action:
Correct the appropriate SEQUENCE entry.
Reason:
A SEQUENCE value was specified for an element in the CA IDMS/DC Sort USER screen, but the ORDER value is missing.
Action:
Add a related ORDER value or remove the indicated SEQUENCE value.
Reason:
An ORDER value other than 'A' or 'D' was specified on the USER screen.
Action:
Specify 'A' to sort in ascending order, or 'D' to sort in descending order, or remove the SEQUENCE and ORDER entries.
Reason:
During USER screen processing, an undefined PF key was pressed.
Action:
Press the appropriate key.
Reason:
The PF3 key was pressed to execute the sort from the USER screen, but errors remain in the SEQUENCE and ORDER fields.
Action:
Correct the indicated errors, press ENTER to validate, and then retry PF3.
Reason:
During CA IDMS/DC Sort USER processing, an unidentified CA IDMS abend occurred. The CA IDMS status code for the error can be found in TPSRETN.
Action:
See CA IDMS Messages and Codes Guide.
Reason:
The sequence numbers specified on the USER screen must begin with1 and proceed sequentially.
Action:
Correct the sequence number order, press ENTER to validate, and retry PF3.
Reason:
PF1 was pressed during a USER session to expand a short error message on a detail line. There are two possible errors:
Action:
Move the cursor to the detail line item for which a message expansion is needed, and press PF1 again.
Reason:
ORDER or SEQUENCE fields have errors. Each field in error has its own associated short error message.
Action:
Move the cursor to a detail line item for which a message has been issued. Press PF1 to see an expanded message.
Correct the fields in error, and press ENTER to reedit the screen values.
Reason:
A command was entered in the command line that is not supported in this function.
Action:
Check spelling and/or enter the correct command.
Reason:
Invalid action code was entered.
Action:
Enter:
Reason:
The CA IDMS DME communication area stack was compromised by a failure and recovery cannot continue.
Action:
Exit CA IDMS DME, log off the terminal, or free a terminal using the DCMT V LT terminal-ID resources DELETE command. If condition reoccurs consistently, contact Technical Support.
Reason:
A transfer command (=N.N) was attempted, but the transfer does not exist, or is not valid from this function.
Action:
Specify a valid transfer command. A table of transfer points is in the User Guide.
Reason:
Upon exit from the CA IDMS DME system, a severe error occurred.
Action:
Review the message text supplied in the message. If the error is not correctable, contact Technical Support with the full message text.
Reason:
No entry entered in CLASS field.
Action:
Enter a valid class.
Reason:
Entry made to both MASK and PREFIX fields.
Action:
Enter only MASK or PREFIX for selected list.
Reason:
Class entered does not exist in this DICTIONARY/NODE.
Action:
Correct spelling, change to proper dictionary, or contact your DBA staff.
Reason:
A valid class was entered, but it has no attributes associated with it.
Action:
Enter another class.
Reason:
An error was encountered in the CA IDMS/DC Sort subroutine.
Action:
Contact Technical Support.
Reason:
More than one item was selected from a list.
Action:
Clear erroneous selection.
Reason:
Item was selected from a list with an invalid selection value.
Action:
Enter valid values:
Reason:
You have selected the EXECUTE option and must specify the compiler to execute. The compilers listed are the only valid entries.
Action:
Correct compiler name.
Reason:
No owner record for module-modattr set.
Action:
Notify your DBA.
Reason:
A valid CLASS/ATTRIBUTE was entered but no modules are associated.
Action:
Check other dictionaries or contact your DBA.
Reason:
You have selected the signon program and hit enter. Valid dictionary, node, and user values are displayed.
Action:
If values are correct, no action required. If they are not correct, select the signon function again.
Reason:
You have selected a DICTIONARY/NODE combination that is not valid (from the USEASON signon program). Error code is the CA IDMS return code.
Action:
Choose valid DICTIONARY/NODE.
Reason:
Invalid sort option has been entered for module or dialog list.
Action:
Enter valid value.
Reason:
Either no password was entered, or password entered does not match the password for your user-ID in the dictionary. Or you have changed to a different dictionary and your password for your user-ID in that dictionary is different.
Action:
Enter valid password for the dictionary you want to access.
USE0025E USER <user> NOT DEFINED TO DICT <dict> node <node>
Reason:
The DICTIONARY and NODE are valid, but your user-ID is not defined to the dictionary. Or you can have access a different dictionary but if you are not defined to that dictionary activity against that dictionary is not allowed.
Action:
Either correct the field in error or contact your DBA. Or exit CA IDMS DME and signon to the correct dictionary.
Reason:
A system failure occurred, but CA IDMS DME was successfully recovered.
Action:
No action required.
Reason:
The CA IDMS DME communication storage was compromised.
Action:
Contact Technical Support with the integer return code and the name of the CA IDMS DME program in which the error occurred.
Reason:
The communication area was compromised.
Action:
Contact Technical Support with the error number and the name of the CA IDMS DME program in which the error occurred.
Reason:
You have selected a valid class, but the attribute selected is not valid or not valid within that class.
Action:
If you are not sure of an ATTRIBUTE, leave it blank and a list of attributes for that class will display.
Reason:
A VERSION number has been entered which is alphanumeric - but not= to 'high' or 'low'
Action:
Enter a valid VERSION number. Valid entries are:
Reason:
MODULE NAME field was left blank.
Action:
Enter a valid module name. If module name is not known, you can select from CLASS/ATTRIBUTE screens to obtain a list of modules.
Reason:
An invalid value was entered for source level.
Action:
Enter a valid number, 'HIGH', 'LOW', or leave the field blank.
Reason:
You are selecting a backup source level option without specifying VERSION or LANGUAGE.
Action:
Enter a valid VERSION and LANGUAGE.
Reason:
Program is attempting to generate a list of dialogs. A database structure error occurred with the OOAK-155 record.
Action:
Contact your DBA.
Reason:
Program is attempting to generate a list of dialogs. No dialogs have been found in LOADHDR-156, or none match mask criteria.
Action:
Check that you have correct dictionary. Change using 'S' function, or contact your DBA for further assistance.
Reason:
Processes were not found for dialog selected for BROWSE/EDIT.
Action:
Verify VERSION number selected is correct.
Reason:
The indicated program updates DC control values but the MPMODE parameter on the sysgen statement is incorrect.
Action:
Correct the MPMODE parameter on the sysgen statement for the program in error.
Reason:
Format of VERSION field is incorrect.
Action:
Leaving field blank will result in selection of default (highest/lowest) version that was specified during the product installation. If specific version is required, enter a numeric value.
Reason:
You entered DIALOG name and MASK/PREFIX.
Action:
MASK and PREFIX should be entered only if requesting a dialog list.
Reason:
Requested dialog does not have a valid loadlib member.
Action:
Dialog must have successfully compiled before the CA IDMS DME Dialog Access function can be used.
Reason:
First line or last line has been entered on the Copy screen, but not both.
Action:
Enter the missing line number or clear the existing line entered to copy an entire module.
Reason:
Line numbers have been entered for copy, but line type has not been entered.
Action:
Enter line type.
Reason:
Last line number request for copy is less that the first line number.
Action:
Correct the entered line numbers.
Reason:
Line numbers requested for a copy are outside of the range of the lines in the module to be copied.
Action:
Browse the module to be copied to determine the number of lines.
Reason:
Either the user did not sign on to CA IDMS/DC, or the user is an unauthorized user.
Action:
Exit CA IDMS DME and use an authorized signon.
Reason:
If the user is defined to a dictionary, and the user record contains a password, CA IDMS DME requires a password match.
Action:
Enter a valid password or exit CA IDMS DME.
Reason:
You are not authorized to access requested module.
Action:
Contact your security administrator.
Reason:
A system internal failure has occurred during editor interface processing.
Action:
Contact Technical Support with the message test.
Reason:
A system internal failure has occurred during editor interface processing.
Action:
Contact Technical Support with the message text.
Reason:
A system internal failure has occurred during editor interface processing.
Action:
Contact Technical Support with the message text.
Reason:
A system internal failure has occurred during editor interface processing.
Action:
Contact Technical Support with the message text.
Reason:
A system internal failure has occurred during editor interface processing.
Action:
Contact Technical Support with the message text.
Reason:
The prototype specified for COPY has a duplicate module name/version combination.
Action:
Enter a language name or a different version number.
Reason:
Module requested for Edit/Browse has a duplicate module name/version combination.
Action:
Enter a language name or a different version number.
Reason:
A serious database error has occurred while accessing a module.
Action:
Contact your DBA or Technical Support with the message text.
Reason:
Your security classes have failed against the class of the indicated DICTIONARY/NODE structure, or against the task code security of the function task code.
Action:
Either select an authorized structure function combination or contact your security administrator to acquire proper authorizations.
Reason:
The module selected is not in the dictionary.
Action:
Select correct module name, change dictionaries, or list modules from Class/Attribute selections.
Reason:
Module, language, version combination are not found in the dictionary.
Action:
Check for accuracy, check dictionary, or list modules with Class/Attribute selections.
Reason:
Module with specified language is not found.
Action:
Check for accuracy, check dictionary, or list modules from Class/Attribute selections.
Reason:
Module with specified version and language is not in specified dictionary.
Action:
Check for accuracy, check dictionary, or list modules from Class/Attribute selections.
Reason:
You do not have security to access requested module.
Action:
Check for correct name and select, or contact your security administrator.
Reason:
An internal load error has occurred during open of ESAM file.
Action:
Contact Technical Support, for this may be due to a software problem.
Reason:
Edited module was saved in the dictionary.
Action:
No action required.
Reason:
Module selected for edit is currently being edited by another user.
Action:
Try again later.
Reason:
An internal error has occurred while attempting to add a module to the dictionary.
Action:
Contact Technical Support.
Reason:
Suspend requested by user.
Action:
No action required.
Reason:
Add module requires entry in USER field if dictionary signon is required. You may have erased existing user-ID.
Action:
Enter user-ID.
Reason:
User-ID is not in the dictionary selected and security requires that the user signon is required.
Action:
Correct user-ID, correct dictionary, or contact the security administrator at site.
Reason:
A password is required to use the ADD function. The password entered must match the password in the user record.
Action:
Enter correct password.
Reason:
You attempted to add a module that already exists in the dictionary.
Action:
Choose MODIFY mode, or change VERSION or DICTIONARY.
Reason:
You attempted to add a module with a language which has not been defined to the system.
Action:
Correct LANGUAGE.
Reason:
User-ID entered is not authorized to access the dictionary entered.
Action:
Correct user-ID, dictionary, or contact your security administrator.
Reason:
This message has been returned from the dictionary when the you attempted to add a module and are not authorized for ADD.
Action:
Contact your security administrator.
Reason:
An error occurred when you attempted to add a module to the dictionary. This is an unexpected error and was not translated to a CA IDMS DME error.
Action:
Error will be listed in CA IDMS/DC system software error codes and messages manual. This must be referenced to determine cause and action. Contact your DBA if help is needed.
Reason:
You are attempting to suspend a module and the system thinks it is already suspended.
Action:
Contact Technical Support.
Reason:
You entered TSUSPEND command when not under TCF. The assumption was that the suspend command was wanted, and module was suspended.
Action:
No action required.
Reason:
You entered SWITCH command when not under TCF. Assumption was made that SUSPEND command was wanted and module was suspended.
Action:
No action required.
Reason:
You entered SWITCH without a task name to switch to. Module was suspended.
Action:
No action required.
Reason:
EXECUTE option was selected and executed.
Action:
No action necessary.
Reason:
SWAP command was entered and executed. After compiler executes the output from the compiler is displayed. If you enter SWAP again, the input commands to the compiler are displayed.
Action:
First you must enter the commands to execute the compiler.
Reason:
CANCEL or END command was executed from the report file.
Action:
No action required.
Reason:
An error has occurred reading or writing a queue record for suspend processing.
Action:
Contact your DBA for assistance. Technical Support for CA IDMS may need to be contacted.
Reason:
Error has occurred while obtaining storage during suspends processing.
Action:
Contact your DBA for assistance. Technical Support for CA IDMS may need to be contacted.
Reason:
An error has occurred during CA ADS Alive interface processing.
Action:
Sign off and sign on again to clear the scratch areas. If the problem continues, contact Technical Support for CA IDMS.
Reason:
The SWAP command was entered while within a module Edit session during ADSC compile error processing. The error listing is redisplayed for review
Action:
Enter SWAP again to return to the Edit session.
Reason:
The SWAP command was entered from the ADSC error review display while no open Edit is in process.
Action:
You may enter the EDIT command.
Reason:
The EDIT command has been successfully executed from the ADSC error list review.
Action:
Normal EDIT functions may be performed.
Reason:
The END command has been entered at the ADSC error list review while an open Edit session remains. Control is passed back to that open Edit session for final termination requirements.
Action:
END, CANCEL, or SUSPEND the Edit session before ending the Browse session.
Reason:
The SWAP command has been successfully executed from a previous swap to an ADSC error list review. Control is passed back to that open Edit session.
Action:
Continue normal edit functions.
Reason:
One of the scratch areas needed for the transfer from CA ADS Dialog Compiler to CA IDMS DME is missing.
Action:
Contact Technical Support.
Reason:
You requested a print of current edit/browse session. Your print request has been executed.
Action:
None.
Reason:
Print class entered on screen is invalid.
Action:
Enter a valid print class.
Reason:
In adding a module, you specified a prototype that has a language of PROCESS, OLQ, or TABLE. The module language specified is not in agreement.
Action:
Correct the module language or remove the prototype, or specify a prototype with the same language.
Reason:
An unexpected CA IDMS status error occurred during CA IDMS DME processing.
Action:
Refer to the error status values in the CA IDMS error messages manual. If the reason for the error is not apparent, contact Technical Support.
Reason:
An invalid primary command was encountered. The cursor will be on the command.
Action:
Check the syntax of the command. Correct and reenter the command.
Reason:
A valid command has been entered with an unrecognizable parameter.
Action:
Check the syntax of command parameter. Correct and reenter the parameter.
Reason:
A line number was not included as a parameter in the LOCATE command.
Action:
Check the syntax of the command. Correct the command (include line number parameter) and re execute.
Reason:
An illegal option has been used with the LEFT, RIGHT, UP, or DOWN command.
Action:
Check the syntax of the parameter. Correct the parameter (you may have included some erroneous characters in the syntax line) and re execute.
Reason:
An illegal option has been used with the NULLS command or CAPS command.
Action:
Check the syntax of the parameter. Correct the parameter (you may have included some erroneous characters in the syntax line) and re execute.
Reason:
A parameter has been included in the syntax of the CANCEL command which excludes parameters.
Action:
Check the syntax of the command. Correct the command (delete the parameter) and re execute.
Reason:
The string indicated has been found in the text. The cursor will be positioned at the beginning of the found string.
Action:
None.
Reason:
The string indicated has been replaced with the replacement string. The cursor will be positioned at the replacement string.
Action:
None.
Reason:
The RFIND (repeat find) or RCHANGE (repeat change) command was entered without a FIND or a CHANGE command being entered first.
Action:
Be sure to enter the FIND command or the CHANGE command before the RFIND command or the RCHANGE command.
Reason:
The bottom of the text was found. If you enter an RFIND (repeat find) or an RCHANGE (repeat change) at this time, the editor will begin searching for the string at the top of the text.
Action:
None.
Reason:
A single quotation mark was found where a pair is required or embedded blanks were found in the search string.
Action:
Check quotation marks, correct, and reenter the command. If a string has embedded blanks, enclose it in quotation marks.
Reason:
The string specified in the FIND command is invalid. If the string has embedded blanks or quotation marks, it may appear to the editor to be more than one string; you can specify only one string in the FIND command.
Action:
Check the syntax of the command. If the string has embedded blanks, enclose it in quotation marks. If the string has embedded single quotation marks, enclose it in double quotation marks. If the string has embedded double quotation marks, enclose it in single quotation marks. Then reenter the command.
Reason:
The string specified in the CHANGE command is invalid. If the string has embedded blanks or quotation marks, it may appear to the editor to be more than two string; you can specify only two strings in the CHANGE command.
Action:
Check the syntax of the command. If a string has embedded blanks, enclose it in quotation marks. If a string has embedded single quotation marks, enclose it in double quotation marks. If a string has embedded double quotation marks, enclose it in single quotation marks. Then reenter the command.
Reason:
The editor has search the entire text without finding the indicated string.
Action:
None.
Reason:
The string used to replace the one found is too long.
Action:
Adjust the length of the found string or reduce the length of the replacement string to match the length of the found one.
Reason:
A string specified in the FIND ALL command has been found the specified number of times.
Action:
None.
Reason:
A string specified in the CHANGE ALL command has been changed in the text the specified number of times.
Action:
None.
Reason:
The CHANGE command was used in the Browse Option to search for and change the next occurrence of a string.
Action:
None. The CHANGE command can only be used when editing text (Edit Option) and not while in Browse mode.
Reason:
The string identified in the CHANGE ALL command has been changed successfully (nnn OCCURRENCES) with (nnn ERRORS).
Action:
Look for the error message on the line number field(s) and make the necessary correction(s).
Reason:
An invalid line command has been entered.
Action:
Check the syntax of the line command on the line number field. Correct and reenter the command.
Reason:
A line command has been entered on a line for which the command is invalid.
Action:
Reenter the line command on an appropriate line.
Reason:
An invalid Scroll Option was entered in the SCROLL field.
Action:
Check the syntax of the Scroll Option next to the word SCROLL. Be sure the option starts in the left-most position of the field. Correct syntax or position.
Reason:
A partial sequence of Line Commands, in block form, is incomplete and cannot be executed.
Action:
If you are just scrolling or using the FIND command to locate the line to complete the block command, this message serves as a warning. Complete the command and execute. Otherwise, check the syntax of the commands to be sure all commands in block form are in pairs. Correct the commands and re execute.
Reason:
A sequence of Line Commands cannot be executed.
Action:
Check the order of the commands. Correct the commands and reexecute.
Reason:
A move or copy cannot be executed because of a missing 'A'(after),'B' (before), 'C' (copy), or 'M' (move) line command or COPY Primary command.
Action:
Enter the missing command.
Reason:
Block (RR) line command iterations have conflicting values.
Action:
Check the syntax of the command. Make sure that the values of the iterations match (one or both may be left blank).
Reason:
A sequence of Line Commands cannot be executed because the range of one line command overlaps the range of another.
Action:
Check the order of the commands. Correct the commands and reexecute.
Reason:
A MOVE/OVERLAY command was issued where MM...MMnumber-of-lines was greater than the available lines to be overlaid as specified by 00..00 or 0 n where n=number-of-lines. Only the number of lines as specified in the OVERLAY portion of the command was moved.
Action:
Check the results of the MOVE process. Make adjustments if necessary.
Reason:
A MOVE/OVERLAY command was issued where the receiving line was not completely overlaid because non-matching data existed on the line being overlaid. Only blanks and matching characters are overlaid in this process. The line to be moved was not deleted.
Action:
Check the results of the MOVE process. If desired, manually delete the line(s).
|
Copyright © 2013 CA.
All rights reserved.
|
|