Messages › Messages Generated by CA ADS Alive › Severity Codes

Severity Codes

Informative – A code ending with the letter I indicates an informative message. Informative messages need no remedial action.

Warning – A code ending with the letter W indicates a warning. Warning messages report conflicting parameter data or processing conditions that may cause unexpected results.

Error – A code ending with the letter E indicates an error. Error messages report erroneous and conflicting parameter data that has caused processing to terminate.

E2001

KEYWORD NOT RECOGNIZED - keyword/command/operand

Reason:

The keyword, command, and/or operand that was entered have not been defined to GSIRECEL.

Action:

There are two possible courses of action:

1. Refer to the appropriate section in this guide for the correct spelling.
2. Enter the corrected command operand, and/or keyword, then press the ENTER key.

E5101

UNKNOWN COMMAND

Reason:

An unknown command was entered in the GSIRECEL command line.

Action:

Enter another command, or request HELP for information regarding valid commands.

E2002

OPERAND MUST BE NUMERIC LITERAL

Reason:

A non-numeric operand was entered with the LINE command.

Action:

Enter a numeric value and press the ENTER key.

E2019

FORMAT ERROR(S)

Reason:

A format error(s) occurred when processing new or modified data was entered. The field entered was in the wrong format (i.e., more than one decimal point entered in a numeric field. '1.2.3').

Action:

1. Enter the 'SET field-name NATIVE' command to determine the correct usage mode for the field.
2. Correct and reenter the data.

E2027

LOGICAL DATA WIDTH MUST BE NUMERIC

Reason:

The value that was entered for the logical data width was entered as a non-numeric value.

Action:

Reenter the field as a numeric value. (This value must be from 80 to 264.)

E2033

INVALID DISPLAY OPTION

Reason:

The operand entered on the DISPLAY command has not been defined to GSIRECEL.

Action:

There are two possible courses of action:

1. Validate the operand on the DISPLAY command or
2. Correct the operand and reenter the command.

E2034

CONTINUE ONLY VALID FOR THE LAST

Reason:

The CONTINUE operand on the DISPLAY command can only be used if a second screen is waiting to be viewed. (See the GSIRECEL online help facility for more details on the DISPLAY CONTINUE command.)

Action:

Delete CONTINUE operand and reenter the command.

E2038

LOGICAL DATA WIDTH IS OUT OF RANGE

Reason:

The Logical Data Width entered is either less than 80 or greater than 264. A value outside of this range is not permitted.

Action:

Enter a value between 80 and 264 as specified on the sign-on screen.

E2050

PA KEY/PF KEY NOT RECOGNIZED

Reason:

The value entered on Sign-on screen for the INTERRUPT key is not one of the supported keys. Valid values are PA1, PA2, PA3, and PF1 through PF24.

Action:

Change the value after the interrupt field on the Sign-on screen to one of the supported keys and reenter.

E2005

RECORD NOT IN SUBSCHEMA

Reason:

The record-name specified in an INITIALIZE command is invalid.

Action:

Correct the INIT and reissue the command.

E5512

COMMAND NOT ALLOWED AT THIS POINT

Reason:

You entered a command that is not allowed at this point in the session.

Action:

Remove the error command.

E5526

LOGICAL DATA WIDTH MUST BE NUMERIC AND 80-255

Reason:

You entered an invalid data width (screen width).

Action:

Correct the data width and retry.

F0100

TERMINAL READ/WRITE ERROR

Reason:

The terminal read or write routine has issued a return code greater than zero to GSIRECEL. A possible line or terminal error has occurred.

Action:

Re-invoke GSIRECEL, and try again. If the problem recurs, contact CA Technical Support.

F0102

INTERNAL SCAN ERROR ON INPUT DATA

Reason:

The 3270 scan routine cannot locate the end-of-record marker for the data string that was entered.

Action:

Re-invoke GSIRECEL, and try again. If the problem recurs, contact CA Technical Support.

F0103

TEMPORARY STORAGE ACQUIRE ERROR

Reason:

One of the following caused this message:

1. A non-zero return code was returned from CICS/VS temporary storage, or
2. An ID error was encountered.

Action:

Re-invoke GSIRECEL, and try again. If the problem recurs, contact CA Technical Support.

F0108

DUPLICATE HASH ENTRY

Reason:

GSIRECEL located a duplicate area or record name in the internal table.

Action:

Contact CA Technical Support.

F0118

RECORD HAS NO FIELDS

Reason:

A request was entered to process a record that did not have any elements defined.

Action:

Verify the record description in the subschema; if elements do exist, contact CA Technical Support.

F1002

PUSH STACK OVERFLOW

Reason:

GSIRECEL received a non-zero return code from the storage routine.

Action:

Allocate more storage to GSIRECEL. If the problem recurs, contact CA Technical Support.

F1003

ENTER STACK OVERFLOW

Reason:

GSIRECEL received a non-zero return code from the storage routine.

Action:

Allocate more storage to GSIRECEL. If the problem recurs, contact CA Technical Support.

F1718

INVALID USAGE FOR DEPENDS ON FIELD

Reason:

A record with an occurs depending on group has an object field whose usage mode is not numeric.

Action:

Verify the record. If the field is defined as numeric, contact CA Technical Support.

F1719

INVALID USAGE FOR SUBSCRIPTED FIELD

Reason:

The usage mode for a subscripted field must be filler, hexadecimal, or picture X.

Action:

Contact CA Technical Support.

F1938

PACKED FIELD GREATER THAN 16 BYTES

Reason:

GSIRECEL encountered a field with a usage mode of packed decimal and a length greater than 16 bytes.

Action:

Contact CA Technical Support.

F2005

OBTAIN FOR SS-026 FAILED

Reason:

A non-zero status was returned while CA IDMS was accessing the dictionary record 'SS-026' that relates to your subschema.

Action:

1. Correct the cause for the CA IDMS status code. The code is displayed on the screen.
2. Re-invoke GSIRECEL.

F2006

OBTAIN FOR SSR-032 FAILED

Reason:

A non-zero status was returned while CA IDMS was accessing the dictionary record 'SSR-032' that relates to your subschema.

Action:

1. Correct the cause for the CA IDMS status code. The code is displayed on the screen.
2. Re-invoke GSIRECEL.

F2007

OBTAIN FOR SSOR-034 FAILED

Reason:

A non-zero status was returned while CA IDMS was accessing the dictionary record 'SSOR-034' that relates to your subschema.

Action:

1. Correct the cause for the CA IDMS status code. The code is displayed on the screen.
2. Re-invoke GSIRECEL.

F2008

OBTAIN FOR SR-036 FAILED

Reason:

A non-zero status was returned while CA IDMS was accessing the dictionary record 'SR-036' that relates to your subschema.

Action:

1. Correct the cause for the CA IDMS status code. The code is displayed on the screen.
2. Re-invoke GSIRECEL.

F2009

OBTAIN FOR SDR-042 FAILED

Reason:

A non-zero status was returned while CA IDMS was accessing the dictionary record 'SDR-042' that relates to your subschema.

Action:

1. Correct the cause for the CA IDMS status code. The code is displayed on the screen.
2. Re-invoke GSIRECEL.

F2012

OBTAIN FOR PROG-051 FAILED

Reason:

A non-zero status was returned while CA IDMS was accessing the dictionary record 'PROG-051' that relates to your subschema.

Action:

1. Correct the cause for the CA IDMS status code. The code is displayed on the screen.
2. Re-invoke GSIRECEL.

F2014

OBTAIN FOR RCDSYN-079 FAILED

Reason:

A non-zero status was returned while CA IDMS was accessing the dictionary record 'RCDSYN-079' that relates to your subschema.

Action:

1. Correct the cause for the CA IDMS status code. The code is displayed on the screen.
2. Re-invoke GSIRECEL.

F2015

OBTAIN FOR NAMESYN-083 FAILED

Reason:

A non-zero status was returned while CA IDMS was accessing the dictionary record 'NAMESYN-083' that relates to your subschema.

Action:

1. Correct the cause for the CA IDMS status code. The code is displayed on the screen.
2. Re-invoke GSIRECEL.

F2016

OBTAIN FOR SRCD-113 FAILED

Reason:

A non-zero status was returned while CA IDMS was accessing the dictionary record 'SRCD-113' that relates to your subschema.

Action:

1. Correct the cause for the CA IDMS status code. The code is displayed on the screen.
2. Re-invoke GSIRECEL.

F2020

INVALID FIELD BLOCK CHAIN POINTER

Reason:

An error has occurred within GSIRECEL.

Action:

Contact CA Technical Support.

F2023

INVALID PICTURE FOR FIELD

Reason:

The field name and picture clause that follow the message are invalid or not supported with the current release.

Action:

If the picture is invalid, correct the source.

F2024

BIT FIELD LENGTH TOO LONG FOR DISPLAY

Reason:

The requested bit field has exceeded your logical data width display area. (You defined this area when you signed on to GSIRECEL. For more information on logical data width, refer to the GSIRECEL online help facility.)

Action:

1. Re-invoke GSIRECEL.
2. Supply GSIRECEL with a number in the logical data width field to accommodate the length of the bit field you need to display.

F2025

DLENGTH DATA INCORRECT (SHORT)

Reason:

The record length defined in the SSR-032 record is less than the actual record length. This is due to an invalid record length calculation for records containing BIT fields.

Action:

Re-invoke GSIRECEL and bypass binding any records with BIT fields. GSIRECEL cannot access these records.

F2026

SESSION STORAGE UNAVAILABLE

Reason:

Request for storage returned a 'NOT AVAILABLE' condition.

1. The subschema being accessed requires more session storage than was available.
2. System load may be too high.
3. Dynamic storage pool defined in the TP environment may be too small.

Action:

1. Use a smaller subschema.
2. Wait until the system load decreases.
3. Increase TP environment dynamic storage pool. (For example, in CA IDMS/DC, increase STORAGE POOL SIZE; in CICS, increase DYNAMIC STORAGE POOL.)

F2027

PROGRAM LOAD FAILURE

Reason:

A module required by GSIRECEL could not be loaded.

Action:

Verify that USDDRCT, USDERRS, (and USDVMFS, if you are running under CMS) are located in the library used for the GSIRECEL environment.

F2028

OBTAIN FOR SSMR-068 FAILED

Reason:

A non-zero status was returned while CA IDMS was accessing the dictionary record 'SSMR-068' that relates to your subschema.

Action:

1. Correct the cause for the CA IDMS status code. The code is displayed on the screen.
2. Re-invoke GSIRECEL.

F2029

OBTAIN FOR SSCR-070 FAILED

Reason:

A non-zero status was returned while CA IDMS was accessing the dictionary record 'SSCR-070' that relates to your subschema.

Action:

1. Correct the cause for the CA IDMS status code. The code is displayed on the screen.
2. Re-invoke GSIRECEL.

F2031

INTERNAL ERROR, MISSING SET HTE

Reason:

GSIRECEL could not find a set control block.

Action:

Contact CA Technical Support.

F7702

LINK FOR GSIHELP FAILED

Action:

Ensure that the installation instructions appropriate for your TP monitor have been followed.

F9800

INTERNAL ERROR IN HASH LOGIC

Reason:

Internal error.

Action:

Call CA Technical Support.

F9990

INTERNAL ERROR

Reason:

Internal error.

Action:

Call CA Technical Support.

F9991

INTERNAL ERROR

Reason:

Internal error.

Action:

Call CA Technical Support.

F9992

INTERNAL ERROR

Reason:

Internal error.

Action:

Call CA Technical Support.

F9993

INTERNAL ERROR

Reason:

Internal error.

Action:

Call CA Technical Support.

F9994

INTERNAL ERROR

Reason:

Internal error.

Action:

Call CA Technical Support.

F9995

INTERNAL ERROR

Reason:

Internal error.

Action:

Call CA Technical Support.

F9996

INTERNAL ERROR

Reason:

Internal error.

Action:

Call CA Technical Support.

F9997

INTERNAL ERROR

Reason:

Internal error.

Action:

Call CA Technical Support.

F9998

INTERNAL ERROR

Reason:

Internal error.

Action:

Call CA Technical Support.

F9999

INTERNAL ERROR VALUE TOO LARGE

Reason:

An error has occurred within GSIRECEL.

Action:

Contact CA Technical Support.

FILE905E

GSSFILE RETURNED AN ERROR DURING file-function, FILE= file-name, CODES n1, n2, n3, n4

Reason:

The file handler is unable to perform the file function with the indicated file.

Action:

See Exhibit 5.1 for an explanation and appropriate action for the return codes indicated.

GSCK000W

USER RECORD NOT FOUND user-id

Reason:

No user ID was entered.

Action:

Enter correct user ID.

GSCK001E

DATABASE ERROR STATUS idms-status-code

Reason:

An unexpected status code was returned from an CA IDMS call.

Action:

Check the status code for appropriate action.

GSCK002E

ENTITY REC NOT FOUND entity-calc-key

Reason:

Internal error.

Action:

Contact CA Technical Support.

GSCK003E

AUTH. CODE NOT DEFINED invalid-request

Reason:

Internal error.

Action:

Contact CA Technical Support.

GSCK004E

SET NOT FOUND set-name

Reason:

Internal error.

Action:

Contact CA Technical Support.

Two types of errors can be reported by the return codes of n1, n2, n3, and n4--non-VSAM file errors and VSAM file errors. The error is described by n2 and n4. For VSAM file errors, n4 is always equal to 28. The error is described by n1, n2, and n3. A general return code is given by n4 for both non-VSAM and VSAM errors. All return codes are decimal values.

GSCK005E

ENTITY TYPE NOT FOUND entity-type

Reason:

Internal error.

Action:

Contact CA Technical Support.

GSCK999E

UNDEFINED ERROR

Reason:

Internal error.

Action:

For assistance, contact CA Technical Support at http://ca.com/support

GSFL999I

file-id IS NOT VSAM - WILL TRY QSAM

Reason:

In z/VSE, the indicated file is not a VSAM file. The message is preceded by a system message indicating an open error for a VSAM file.

Action:

None. If the attempt to open the file for QSAM processing is successful, CA IDMS/DC Sort will continue with normal processing.

I2001

FIELD RESET TO USAGE MODE LENGTH nnn BYTES, LEVEL nn

Reason:

The field-name was previously changed to hexadecimal usage mode. This message is returned after the field has been reset to its native mode by using the 'SET field-name NATIVE' command.

Action:

None. This message is informative only.

I2002

USAGE CHANGED

Reason:

The field or record in the 'SET field-name HEX' command was changed to hexadecimal usage mode.

Action:

None. This message is informative only.

I5001

AUTOHEX MODE NOW on/off

Reason:

The SET command for this option was processed.

Action:

None.

I5002

COBOL DISPLAY MODE NOW on/off

Reason:

The SET command for this option was processed.

Action:

None.

I5003

COMMAND DISPLAY WILL BE as input / as used

Reason:

The SET command for this option was processed.

Action:

None.

I5004

LOWER CASE OPTION NOW on/off

Reason:

The SET command for this option was processed.

Action:

None.

IDMS001E

PROGRAM program-name ABORTED WITH STATUS OF idms-status

Reason:

A non-zero return code was encountered in a CA IDMS call.

Action:

See the CA IDMS Messages and Codes Guide.

LMSG900E

GSILMSG FAILURE CC = n

Reason:

A severe error occurred during an attempt to format another error message.

Action:

Condition code (CC) n indicates the specific problem and course of action:

• 4 – An attempt was made to generate the message associated with a message code that is not in the message table. Reinstall load module TPSMSGT. If the problem persists, contact CA Technical Support.
• 8 – The message table could not be loaded. Check for a proper sysgen and load module for TPSMSGT.
• 12 – Not enough storage is available for message processing. Check the amount of storage allocated to the TP monitor and increase it, if necessary.
• 16 – Incompatible parameters were passed to the message handler. Ensure that the most recent versions of CA IDMS/DC Sort and GSILMSG are installed. Contact CA Technical Support if the problem persists.

SGEN001I

SUCCESSFUL PREPROCESS FOR LANGUAGE language-name ENVIRONMENT CICS/IDMS

Reason:

The preprocessor was successfully executed.

Action:

None.

TPE7001E

INVALID PARM LIST FOR process-name - PARM NUMBER = parm-number

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 CA Technical Support.

TPE7002E

INVALID TPS-REQUEST VALUE OF request-type

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 syntax is correct, contact CA Technical Support.

TPE7003E

INVALID TPS-ELEMENTS TYPE OF element-type

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 CA Technical Support.

TPE7004E

REQUEST OF request-type INVALID WITH ELEMENTS OF element-type

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 CA Technical Support.

TPE7005E

INVALID VALUE FOR PROCESS process-type - PARM NUMBER = parm-number

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 CA Technical Support.

TPE7006E

INVALID PROCESS VALUE OF process-type

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 CA Technical Support.

TPE7007E

NO SETSORT PERFORMED FOR SESSION session-number

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.

TPE7008E

DUPLICATE SETSORTS ISSUED FOR SESSION session-number

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.

TPE7009E

INVALID NUMBER OF SORT KEYS SPECIFIED FOR SESSION session-number

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 CA Technical Support.

TPE7010E

RECORD LENGTH IS 0 OR BEYOND MAXIMUM FOR SESSION session-number

Reason:

The TPSRLEN field is less than 1 or greater than 32,000 for CA IDMS or 16,000 for CICS.

Action:

Contact CA Technical Support.

TPE7011E

PUTSORT BUFFER NOT SPECIFIED FOR SESSION session-number

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 CA Technical Support.

TPE7012E

INVALID DISPLACEMENT FOUND IN KEY OCCURRENCES FOR SESSION session-number

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.

TPE7013E

KEY LENGTH EXCEEDS RECORD BOUNDARY FOR SESSION session-number

Reason:

The field-length specified for a field-name in a FIELDS statement exceeds the record boundary.

Action:

Correct the invalid FIELDS statement.

TPE7014E

INVALID KEY ORDER OF sort-order FOR SESSION session-number

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.

TPE7015E

MAIN AND AUX EXCEEDED - UNABLE TO CONTINUE

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 Operations for more information.

TPE7016E

PUTSORT DISALLOWED AFTER GETSORTS FOR SESSION session-number

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 and open the session with an ENDSORT/SETSORT sequence.

TPE7017E

STORAGE FAILURE DURING SORT PROCESSING

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.

TPE7018E

THE RETURN ADDRESS FOR SORTED RECORDS WAS NOT SPECIFIED FOR GETSORT

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 CA Technical Support.

TPE7019E

NO RECORDS WERE SORTED FOR SESSION session-number

Reason:

The sort queue for the indicated session-number was empty. A GETSORT 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.

TPE7020E

END OF SET ENCOUNTERED FOR SESSION session-number DURING process-type PROCESS

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.

TPE7040E

INVALID SESSION VALUE OF session-number

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.

TPE7041E

MISMATCH ON TPSKNUM AND ACTUAL PARAMETERS FOR SESSION session-number

Reason:

The number in TPSKNUM and the number of parameters in the interface call to TPSET do not agree.

Action:

Contact CA Technical Support.

TPE7044E

SETLIMIT OCCURRED AFTER PUTSORT FOR SESSION n

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.

TPE7045E

SETLIMIT ATTEMPTED, BUT INSTALLATION PROHIBITS USE

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.

TPP7021E

MODULE module-name NOT FOUND

Reason:

The user has attempted to execute the CA IDMS/DC Sort CA ADS preprocessor. The module name parameter from the datastream or the user display cannot be located in the dictionary/node/version specified.

Action:

Correct module name, dictionary, node, and/or version.

TPP7022E

DATABASE BIND FAILED FOR INDICATED DICT AND NODE--RECHECK THESE VALUES

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.

TPP7023E

INVALID DATA LINE ON TPSG

Reason:

An invalid or missing datastream has been entered as part of the execution of the TPSG task.

Action:

Enter the required information in the screen display.

TPP7024E

INVALID MODULE NAME IN INPUT DATA LINE

Reason:

An invalid module-name format was specified as part of the TPSG task datastream. The module name must be between 1 and 32 alphanumeric, non-space characters.

Action:

Correct the module name in the user display.

TPP7025E

INVALID PARAMETER AFTER DEFAULT VERSION

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.

TPP7026E

INVALID VERSION NUMBER IN INPUT DATA LINE

Reason:

The parameter after the module name in the TPSG task datastream 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.

TPP7027E

INVALID ALTERNATE DICTIONARY NAME

Reason:

The dictionary name in the TPSG task datastream 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.

TPP7028E

INVALID ALTERNATE NODE NAME

Reason:

The node name in the TPSG task datastream is not either a 1- to 8-character alphanumeric field, or the node default (represented by a comma).

Action:

Enter a valid node name in the user display.

TPP7029E

MODULE TEXT ENDED WITH IMPROPERLY TERMINATED TPSORT SYNTAX

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.

TPP7030E

MINIMUM ENTRY OF MODULE NAME IS REQUIRED

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.

TPP7031I

PREPROCESSING TERMINATED BY USER REQUEST

Reason:

The user has requested the termination of the current CA IDMS/DC Sort preprocessing.

Action:

None.

TPP7032E

SYNTAX OVERFLOW - TOO MANY CONTIGUOUS LINES IN A SINGLE TPSORT STATEMENT

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.

TPP7033E

INVALID WORD word IN STATEMENT/WORD word-position

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.

TPP7034E

INCOMPLETE OR INVALID STATEMENT AT WORD word

Reason:

A CA IDMS/DC Sort statement has been incorrectly specified. Usually this error occurs because the statement terminator was encountered before a substatement was fully qualified.

Action:

Correct the CA IDMS/DC Sort syntax, and enter RETRY in the EDITOR command line.

TPP7035E

SUBPARAM parameter-number SEQUENTIAL POSITION OF WORD IS OF INCORRECT LENGTH

Reason:

A parameter substatement 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.

TPP7036E

WORD word WAS FOUND WHEN TERMINATION WAS EXPECTED

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.

TPP7037E

AT LEAST ONE SET OF FIELDS MUST BE SPECIFIED

Reason:

The current SETSORT request requires a FIELDS keyword and one or more sets of FIELDS subparameters.

Action:

Correct the SETSORT syntax and retry the preprocessor.

TPP7038E

RECORD record-name NOT FOUND

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.

TPP7039E

ELEMENT element-name NOT IN INDICATED RECORD

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.

TPP7042I

SUCCESSFUL UPDATE OF MODULE module-name

Reason:

The indicated module has been successfully updated.

Action:

None.

TPP7043E

DICTIONARY UNABLE TO BE READIED IN UPDATE MODE

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.

TPP7046I

SUCCESSFUL PREPROCESS OF TPSORT STATEMENTS

Reason:

The TPSG verb was entered in CA IDMS DME, and the syntax was preprocessed without errors.

Action:

None.

TPP7047E

ERROR(S) DETECTED IN TPSORT STATEMENT(S)

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.

TPP7048E

ELEMENT element-name IS A CONDITIONAL NAME (88 LEVEL)

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.

TPP7091E

ESAMcode END OF FILE REACHED (BEYOND BOTTOM)

Reason:

An error occurred during the CA IDMS/DC Sort CA ADS preprocessor interface to the EDITOR.

Action:

Contact CA Technical Support.

TPP7092E

ESAMcode INVALID PARAMETER LIST

Reason:

An error occurred during the CA IDMS/DC Sort CA ADS preprocessor interface to the EDITOR.

Action:

Contact CA Technical Support.

TPP7093E

ESAMcode ILLEGAL CALL (PUT BEFORE OPEN)

Reason:

An error occurred during the CA IDMS/DC Sort CA ADS preprocessor interface to the EDITOR.

Action:

Contact CA Technical Support.

TPP7094E

ESAMcode AN I/O ERROR OCCURRED. I/O ERROR CODE: error-code

Reason:

An error occurred during the CA IDMS/DC Sort CA ADS preprocessor interface to the EDITOR.

Action:

Contact CA Technical Support.

TPP7095E

ESAMcode UNEXPECTED RETURN CODE WHILE CREATING THE SOURCE TEXT AREA

Reason:

An error occurred during the CA IDMS/DC Sort CA ADS preprocessor interface to the EDITOR.

Action:

Contact CA 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 CA Technical Support.

TPU7050E

NO RECORD NAME FOUND IN SORT-CONTROL BLOCK

Reason:

The current request requires a record name in TPSRECN.

Action:

Contact CA Technical Support.

TPU7051E

NON-IDMS INTERFACE REQUIRES ELEMENT NAMES

Reason:

A non-CA IDMS USER request requires element names in TPSKOCCS.

Action:

If the call was formatted by a preprocessor, contact CA Technical Support.

TPU7052E

RECORD NOT FOUND IN DICTIONARY

Reason:

An 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.

TPU7053E

NUMBER OF ELEMENTS IN RECORD EXCEEDS 720

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.

TPU7054E

MAIN STORAGE NOT AVAILABLE

Reason:

Sufficient storage was not available to complete the USER request.

Action:

Increase the available user storage for the TP monitor.

TPU7055I

USER CANCELED SORT

Reason:

A USER sort request was terminated before a key was specified.

Action:

None. The user program must contain logic to recognize this condition.

TPU7056E

NUMBER OF SORT KEYS EXCEEDS 16

Reason:

During a USER sort request, the user specified more than 16 keys.

Action:

Reinvoke the USER sort request, specifying 16 or fewer keys.

TPU7057E

SEQUENCE NUMBER MUST BE BETWEEN 1 AND 16

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.

TPU7058E

SEQUENCE NUMBER IS A DUPLICATE

Reason:

More than one SEQUENCE field contains the same value on a USER sort screen.

Action:

Correct the appropriate SEQUENCE entry.

TPU7059E

SORT ORDER IS MISSING

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.

TPU7060E

SORT ORDER MUST BE (A) OR (D)

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.

TPU7061E

AN IMPROPER PF KEY WAS PRESSED

Reason:

During USER screen processing, an undefined PF key was pressed.

Action:

Press the appropriate key.

TPU7062E

EXECUTION REQUIRES ALL ERRORS CORRECTED

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.

TPU7063E

IDMS INTERFACE ABEND - IDMS STATUS idms-status

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 the CA IDMS Messages and Codes Guide.

TPU7064E

SEQUENCE NUMBER MISSING

Reason:

The sequence numbers specified on the USER screen must begin with 1 and proceed sequentially.

Action:

Correct the sequence number order, press ENTER to validate, and retry PF3.

TPU7065E

CURSOR NOT POSITIONED ON SEQUENCE OR ORDER FIELD IN ERROR

Reason:

PF1 was pressed during a USER session to expand a short error message on a detail line. There are two possible errors:

1. The cursor must be on an item in either the SEQUENCE or ORDER column that has a short error message following it.
2. The indicated detail line has no error message(s).

Action:

Move the cursor to the detail line item for which a message expansion is needed, and press PF1 again.

TPU7066E

ONE OR MORE DETAIL FIELDS ARE IN ERROR

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.

USG0001E

COMMAND x IS NOT ACTIVE FOR THIS FUNCTION

Reason:

A primary command "x" was entered which is not active for this function, or is an unknown command.

Action:

Enter another command or request HELP concerning valid commands for this function.

USG0002E

DICTIONARY "x" -- NODE "y" NOT FOUND

Reason:

The dictionary/node combination does not exist in the central version.

Action:

Correct the dictionary and/or node and retry the transaction.

USG0003E

PROCESSING INTERRUPTED BY USER REQUEST

Reason:

The END command was specified without completing the selection of a dialog for animation or removal.

Action:

None.

USG0004E

AN ERROR OCCURRED DURING RECOVERY PROCEDURES

Reason:

An error occurred during an attempt to restart a previously interrupted session specification.

Action:

Enter the QUIT command and reenter the menu.

USG0005E

DIALOG NOT DEFINED OR NOT GENERATED

Reason:

A dialog name has been specified for animation that is either non-existent or non-generated.

Action:

Correct the dialog name or use ADSC to create an executable dialog.

USG0006E

HIGHLIGHTED FIELD VALUES ARE IN CONFLICT -- PLEASE RESOLVE AND REENTER

Reason:

The indicated field values are in conflict.

Action:

Correct the field conflict and retry the transaction. If the reason for the conflict is not apparent, enter the HELP command for information concerning the current screen.

USG0007E

SOURCE CODE EQUIVALENT OF DIALOG IS MISSING

Reason:

Although the selected dialog has a fixed dialog block (FDB), there is no equivalent source code structure in the indicated dictionary.

Action:

Migrate the source code structure or select another dialog for testing.

USG0008E

UNABLE TO TRANSFER TO a

Reason:

A transfer command "=a" was entered, but no function exists for function identifier.

Action:

Select another function identifier or use the END command to step upward to the Session Specification screen that lists the identifiers.

USG0009E

SUBROUTINE ERROR -- a

Reason:

An unexpected internal program error has occurred.

Action:

Contact CA Technical Support with the message text following the error.

USG0010E

THE HIGHLIGHTED FIELD(S) CONTAINS AN INVALID VALUE

Reason:

Invalid values were entered in the indicated fields.

Action:

Correct the invalid values and retry the transaction. If the reason for the error is not clear, enter the HELP command for information regarding the correct value entries.

USG0011E

PLEASE MAKE A SELECTION FROM THE INDICATED OPTIONS

Reason:

The ENTER key was pressed before a primary command or option was selected.

Action:

Enter a primary command or option, or enter the HELP command for information concerning valid values.

USG0012E

SOURCE OF DIALOG HAS CHANGED -- REGENERATION REQUIRED

Reason:

CA ADS Alive has detected a discrepancy between the "LAST CHANGED" dates of the PROG-051 record in the dictionary, and the related fixed dialog block (FDB).

Action:

Use ADSC to recompile the dialog, and retry animation.

USG0013E

UNABLE TO LOAD FDB FOR REQUESTED DIALOG

Reason:

The indicated dialog and version exists in source code, but has never been generated.

Action:

Enter a valid, generated dialog or request the Dialog List screen to make a selection.

USG0014E

DIALOG MUST BE GENERATED WITH SYMBOL TABLE

Reason:

A dialog has been selected for animation, but it has been defined without symbol tables.

Action:

Recompile the dialog using ADSC and select the symbol table option, or select another dialog.

USG0015E

DIALOG MUST BE GENERATED WITH DIAGNOSTIC TABLES

Reason:

A dialog has been selected for testing, but it has been defined without diagnostic tables.

Action:

Recompile the dialog using ADSC and select the diagnostic table, or select another dialog.

USG0016I

FUNCTION SUCCESSFULLY COMPLETED

Reason:

The requested function was completed without errors.

Action:

None.

USG0017E

PROCESS a VERSION b NOT FOUND

Reason:

The selected process, as indicated by membership in the current dialog's fixed dialog block (FDB), cannot be located in the dictionary. The probable cause is that the process was deleted, but the dialog has not been corrected and regenerated.

Action:

Correct the dialog by removing references to the indicated process, and regenerate the dialog.

USG0018E

PROCESS a VERSION b DATE CONFLICT

Reason:

The indicated process and version has been changed at the source level since the dialog was last generated. CA ADS Alive is unable to animate the dialog, or the Post-Abort Browse Facility cannot display the dialog source.

Action:

Regenerate the dialog before attempting animation, or review the print log to determine the cause for the dialog abend.

USG0020E

ESAMVVVV -- INVALID PARAMETER LIST

Reason:

A system internal failure has occurred during EDITOR interface processing.

Action:

Contact CA Technical Support with the message text following the error.

USG0021E

ESAMVVVV -- ILLEGAL CALL (PUT BEFORE OPEN)

Reason:

A system internal failure has occurred during EDITOR interface processing.

Action:

Contact CA Technical Support with the message text following the error.

USG0022E

ESAMVVVV -- I/O ERROR VVVV OCCURRED

Reason:

A system internal failure has occurred during EDITOR interface processing.

Action:

Contact CA Technical Support with the message text following the error.

USG0023E

ESAMVVVV -- UNEXPECTED RETURN CODE WHILE CREATING THE SOURCE TEXT AREA

Reason:

A system internal failure has occurred during EDITOR interface processing.

Action:

Contact CA Technical Support with the message text following the error.

USG0024E

ESAM -- END OF FILE REACHED (BEYOND BOTTOM)

Reason:

A system internal failure has occurred during EDITOR interface processing.

Action:

Contact CA Technical Support with the message text following the error.

USG0025E

DIALOG a VERSION b NOT ANIMATED

Reason:

Animation removal was requested for a dialog for which no animation was enabled.

Action:

Do one of the following:

• Select another dialog for removal
• Request a list of test enabled dialogs
• Request another function

USG0026I

RECOVERY WAS SUCCESSFUL

Reason:

An abnormally interrupted Animation Setup Session was successfully restarted.

Action:

None.

USG0027E

BAD RETURN OF a FROM KEY HANDLER

Reason:

An internal key-handling error was encountered.

Action:

1. Issue the QUIT command.
2. Reenter CA ADS Alive.
3. Attempt a PFKey substitution.

If the error reoccurs, contact CA Technical Support with the message text following the error.

USG0028I

DIALOG a VERSION b REMOVED FROM ANIMATION

Reason:

The indicated dialog and version has been successfully removed from animation.

Action:

None.

USG0029I

DIALOG a VERSION b ENABLED FOR ANIMATION

Reason:

The indicated dialog has been successfully enabled for animation.

Action:

None.

USG0032E

NO DIALOGS IN DICTIONARY "a" NODE "b"

Reason:

The Dialog List screen was requested but the dictionary contains no dialogs.

Action:

Select another dictionary/node.

USG0033E

TPSORT ERROR OF a

Reason:

An error occurred during the sorting of a list.

Action:

Contact CA Technical Support with the error message and return code.

USG0034E

ONLY ONE SELECTION IS ALLOWED FROM THIS FUNCTION

Reason:

Multiple selections were made from the Dialog List screen or the Record List screen when only one selection is allowed.

Action:

Limit the selection to one.

USG0035E

NO DIALOG IS IN THE PROCESS OF ANIMATION SPECIFICATION

Reason:

A function requiring animation of a dialog has been attempted, but no dialog has been specified.

Action:

Select another function or enable a dialog for testing.

USG0036W

VALUES ACCEPTED -- INTERVAL IS EXCESSIVE

Reason:

A value of 10 or more seconds has been enabled for non-interruptible testing. An interval of this duration will lead to excessive dialog execution time.

Action:

Specify a shorter duration or accept the entered value.

USG0037I

CONTROL VALUES ACCEPTED -- SELECT PROCESSES FOR ANIMATION

Reason:

Process-level animation specification has been enabled, and the sorted Process List screen presented.

Action:

Select processes for global or line-specific animation.

USG0038E

DIALOG a VERSION b OWNS NO PROCESSES

Reason:

Process-level animation has been requested for a dialog which owns no processes.

Action:

Add a process to the indicated dialog and regenerate, or select another dialog.

USG0039E

PROGRAM a NOT DEFINED CORRECTLY FOR MPMODE

Reason:

The indicated program updates DC control values but the MPMODE parameter on the sysgen statement is incorrect.

Action:

Respecify the PROGRAM statement on the sysgen as MPMODE SYSTEM and STORAGE PROTECTION.

USG0040E

WORD PARSE FAILURE -- ORIGINAL LENGTH OF STRING EXCEEDED

Reason:

A command string has been entered which overflows the command line.

Action:

Correct the length of the command string.

USG0041E

WORD PARSE FAILURE -- ARRAY AREA OVERFLOW

Reason:

A string has been entered for the STOP WHEN command that exceeds the space allowed.

Action:

Correct the command syntax and retry.

USG0042E

THE a COMMAND CANNOT BE ASSOCIATED WITH THIS LINE

Reason:

The indicated command was associated with an invalid B-Before or A-At line command.

Action:

Specify the B or A line command on a valid line.

USG0043E

INVALID NUMERIC IN a AT WORD NUMBER b

Reason:

The word at "b" should have been a numeric integer.

Action:

Correct the command and retry.

USG0044E

INVALID SYNTAX IN a AT WORD NUMBER b

Reason:

The word at position "b" is incorrect.

Action:

Correct the syntax and retry.

USG0045E

INCOMPLETE OR INVALID COMMAND STRING

Reason:

A partial or incorrect command stream was entered.

Action:

Correct the command syntax and retry.

USG0046E

ENDING QUOTE IS MISSING

Reason:

The ending quote of a quoted string has not been detected.

Action:

Correct the command syntax and retry.

USG0047E

HEX STRING MUST CONTAIN EVEN NUMBER OF CHARACTERS

Reason:

A hex format quoted string was entered with an uneven number of character positions.

Action:

Correct the hex format quoted string to contain an even number of characters and retry.

USG0048E

NON-HEX CHARACTER FOUND IN HEX STRING

Reason:

A hex format quoted string was entered with one or more non-hex values.

Action:

Correct the hex format quoted string to contain only 0-9 or A-F.

USG0049E

"WHEN" ELEMENT REQUIRES NUMERIC OR HEX VALUE

Reason:

The element object of a STOP WHEN command is defined as display numeric, zone decimal, or computational. The comparison string contains a non-numeric or non-hex character string.

Action:

Correct the comparison value and retry.

USG0050E

UNSUPPORTED ELEMENT TYPE AS TARGET OF "WHEN"

Reason:

The indicated element is of a non-supported data type.

Action:

Select another element as the target of the STOP WHEN command.

USG0051E

"WHEN" LENGTH MISMATCHES ELEMENT DEFINITION

Reason:

The comparison string portion of the STOP WHEN command is longer than the element against which the comparison is directed.

Action:

Correct the length of the comparison string.

USG0052I

STOP PARAMETERS <ADDED&vbar.MODIFIED>

Reason:

The indicated STOP parameter was successfully processed.

Action:

None.

USG0053E

OVERFLOW OF MTC TABLE IN USGAESH

Reason:

The dialog owns more than 200 records.

Action:

This is a CA ADS Alive dialog limitation. Contact CA Technical Support if this becomes an operational limitation.

USG0054E

TRANSFER COMMANDS ARE DISABLED FOR THIS FUNCTION

Reason:

Transfer commands may not be entered from this function.

Action:

Select another function.

USG0056I

ANIMATION MODIFIED TO STOP AT ALL LINES IN THIS PROCESS

Reason:

The STEP command was successfully completed.

Action:

None.

USG0057I

PROCESS SELECTIONS SUCCESSFULLY COMPLETED

Reason:

The PROCESS command was successfully completed.

Action:

None.

USG0060I

RECORD a VERSION b <REVIEWED&vbar.MODIFIED>

Reason:

The RECORD command was successfully completed, and the indicated record was either REVIEWED or MODIFIED.

Action:

None.

USG0061E

INVALID SELECTION VALUE

Reason:

An invalid select code was entered.

Action:

Enter a correct select value or enter the HELP command for information on selection values.

USG0062I

DIALOG a VERSION b ALREADY ENABLED FOR ANIMATION -- BEGIN MODIFICATION

Reason:

The indicated dialog was already enabled for animation, but a subsequent animation request has been entered.

Action:

Alter the current animation values or select another dialog for animation.

USG0063E

RECORD a VERSION b NOT FOUND

Reason:

The indicated record was specified in a RECORD command that is either not owned by the dialog or is not a supported record type.

Action:

Select another record or request the Record List screen.

USG0064E

ELEMENT NAME a NOT IN ANY DIALOG-OWNED RECORD

Reason:

An element name was specified that is not in any record associated with the dialog.

Action:

Specify another element name.

USG0065E

ADSOMAIN MUST BE DEFINED AS RESIDENT

Reason:

The following message appears in the DC LOG at startup: "In order for CA ADS Alive to properly enable, ADSOMAIN must be defined as RESIDENT."

Action:

Correct the sysgen to define ADSOMAIN as resident.

USG0066E

ADSOMAIN CONTENT VALIDATION ERROR AT a

Reason:

The following message appears in the DC LOG at startup: "In order for CA ADS Alive to properly enable, validation of ADSOMAIN contents occurs."

Action:

When the error is at ADSOPTCH, then the dynamic patch may be occurring at a previously patched area. Refer to SRCLIB member USGTPARM on re-specifying the dynamic patch point.

For other validation failures, contact CA Technical Support with the message and a dump of the ADSOMAIN load module.

USG0067I

ADSOMAIN ENABLED FOR ANIMATION

Reason:

The following message appears in the DC LOG at startup: "CA ADS Alive has been successfully enabled."

Action:

None.

USG0068I

nnnn STATEMENTS WILL BE SKIPPED BEFORE STOPPING

Reason:

You entered a SKIP command. If you did not concatenate a GO with the SKIP, this message is presented to verify that you entered the correct SKIP count.

Action:

Specify GO to enact the SKIP or specify another SKIP value.

USG0069E

FEATURE DISABLED THROUGH SITE OPTION

Reason:

The attempted function has been disabled using the CA ADS Alive customization macro.

Action:

Select another action or contact your DBA to enable this feature.

USG0070E

DIALOG NAME AND VERSION REQUIRED DUE TO SITE OPTION

Reason:

The Area Sweep option for Dialogs has been disabled in the Installation Parameter settings.

Action:

Specify appropriate values for the Dialog Name and Version number.

USG0071E

DIALOG <dialog-name> V <version-number> ABENDED - ERROR STATUS <error status> - DETAILS IN QREVIEW

Reason:

The name dialog has abended and the Post Abort Browse screen facility has been disabled in the Installation Parameter settings. The abend details will still be written to the DEBUGQUEUE for later review with QREVIEW.

Action:

See details of abend using QREVIEW task.

USG0072W

SOURCE CHANGED SINCE DIALOG GENERATED – OVERRIDE SPECIFIED

Reason:

There has been a change to the Process code source since the dialog was last generated. The installation settings dictate that this condition should be overrided.

Action:

Continue with the animation session.

USXD002E

INVALID COMMAND

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.

USXD202E

INVALID PARAMETER ON COMMAND

Reason:

A valid command has been entered with an unrecognizable parameter.

Action:

Check the syntax of command parameter. Correct and reenter the parameter.

USXD204E

ENTER LOCATE 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 reexecute.

USXD206E

ONLY A NUMBER, MAX, HALF, CSR, OR PAGE IS ALLOWED

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 reexecute.

USXD208E

ONLY "ON" OR "OFF" IS ALLOWED. "ON" IS THE DEFAULT

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 reexecute.

USXD210E

NO PARAMETER IS ALLOWED ON COMMAND

Reason:

A parameter has been included in the syntax of the CANCEL command that excludes parameters.

Action:

Check the syntax of the command. Correct the command (delete the parameter) and reexecute.

USXF001I

FOUND CHARS "string"

Reason:

The string indicated has been found in the text. The cursor will be positioned at the beginning of the found string.

Action:

None.

USXF003I

REP "string" WITH "replacement-string"

Reason:

The string indicated has been replaced with the replacement string. The cursor will be positioned at the replacement string.

Action:

None.

USXF004E

MUST ENTER A FIND OR CHANGE COMMAND FIRST

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.

USXF005I

BOTTOM OF DATA REACHED

Reason:

The bottom of the text was reached before the string 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.

USXF006E

ENCLOSE STRING IN QUOTES

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.

USXF007E

INVALID FIND SYNTAX

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 only specify 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.

USXF008E

INVALID CHANGE SYNTAX

Reason:

A string specified in the CHANGE command is invalid. If one of the strings has embedded blanks or quotation marks, it may appear to the editor that you are entering more than two strings; you can only specify 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.

USXF009I

NO CHAR "string" FOUND

Reason:

The EDITOR has searched the entire text without finding the indicated string.

Action:

None.

USXF010W

ERROR CHARACTERS "string"

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 one found.

USXF012I

FOUND nnn OCCURRENCES OF "string"

Reason:

A string specified in the FIND ALL command has been found the specified number of times.

Action:

None.

USXF014I

CHANGED nnn OCCURRENCES OF "string"

Reason:

A string specified in the CHANGE ALL command has been changed in the text the specified number of times.

Action:

None.

USXF016E

CHANGE COMMAND NOT ENABLED IN BROWSE MODE

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.

USXF018W

CHANGED nnn OCCURRENCES WITH nnn ERRORS OF "string"

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).

USXI002E

INVALID COMMAND

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.

USXI006E

INVALID ON THIS LINE

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.

USXI008E

INVALID SCROLL AMOUNT

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.

USXL002W

BLOCK COMMAND INCOMPLETE

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 reexecute.

USXL004E

COMMAND CONFLICT

Reason:

A sequence of Line Commands cannot be executed.

Action:

Check the order of the commands. Correct the commands and reexecute.

USXL006W

MOVE/COPY PENDING

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.

USXL008E

ITERATION COUNT MISMATCH

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).

USXL009E

LINE COMMAND RANGE CONFLICT

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.

W2001

MODIFIED DATA ENTERED, COMMAND IGNORED

Reason:

This message is displayed when data has been entered in the unprotected area and in the command input area. The data entered in the unprotected area always takes precedence over any command entered. (Refer to the GSIRECEL online help for a detailed discussion.)

Action:

To enter the command, rekey the first character in the displayed command and press the ENTER key.

Note: This will not occur if MAPIN mode is FAST.

W2003

OCCURS DEPENDING ON CONTROL FIELD ALTERED - REDISPLAY RECORD

Reason:

A control field in an 'OCCURS DEPENDING ON' clause has been changed.

Action:

GSIRECEL has changed the field in the record data buffer. If you want to add or delete data in a field, enter 'DISPLAY record-name'. This will reformat the record to allow data to be added or deleted in the display record buffer area.

W2004

A REDEFINING FIELD WAS MODIFIED

Reason:

This message indicates that a field in a redefined group has been changed.

Action:

GSIRECEL has changed the field in the record data buffer. To view the record in its new format, enter the 'DISPLAY record-name' command. This will avoid possible confusion when the display is different.

W2008

RECORD DISPLAY INCOMPLETE - TOO MANY (FIELDS/OCCURS)

Reason:

The record to be displayed could not fit into the display buffer area. The display buffer area ran out of line storage space.

Action:

Enter the 'DISPLAY record-name CONTINUE' command to view the remaining fields.

W2009

RECORD DISPLAY INCOMPLETE - FIELD TOO LONG

Reason:

The record to be displayed could not fit into the display buffer area. The display buffer area ran out of line storage space.

Action:

Enter the 'DISPLAY record-name CONTINUE' command to view the remaining fields. (If you were displaying a field, the entire record must be displayed to use the CONTINUE option.)

W2010

USAGE MODE MAY NOT BE CHANGED FOR A BIT FIELD

Reason:

The usage mode can be changed for any type of field except bit.

Action:

None.

W5001

MODIFIED DATA ENTERED, PF KEY IGNORED

Reason:

Record data was changed at the same time that a PF key associated with a command was pressed, and MAPIN mode was not FAST.

Action:

None.