This section details messages generated in the course of Search and Replace Utility processing, along with possible causes and corrective actions to take in error situations.
Reason:
Informational. Identifies the Element name.
Action:
None.
Reason:
This message indicates that processing for the specified statement has begun. A formatted version of the SCL statement appears immediately after this message.
Action:
None.
Reason:
This message indicates that the Search & Replace utility has finished processing, and displays the highest return code received during execution. This return code is also used to set the return code for the batch jobstep.
Action:
None.
Reason:
This message appears after the utility completed processing for a Search Element statement. ENBS007I follows this message and displays the number of Elements that were searched and updated, as well as the number of errors encountered during processing.
Action:
None.
Reason:
This message appears after the utility completed processing for a Search Element Component List statement. ENBS007I follows this message and displays the number of Element component lists that were searched and updated, as well as the number of errors encountered during processing.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
A previous error occurred that was severe enough to warrant termination of further processing. An example of such an error is a corrupt Master Control File (MCF) index. Further activity against the MCF may produce erroneous results or possible loss of data.
Action:
Examine the listing for previous error messages to determine the exact cause of this condition.
Reason:
This message appears after the utility completed processing for a Search Element or Search Element Component List statement. The message displays the number of Elements or Element component lists that were searched and updated, as well as the number of errors encountered during processing.
Action:
None.
Reason:
A search string was identified, but due to insufficient space in the line, it could not be replaced with the entire replacement string. This message appears after the messages that display a portion of the line in error.
Action:
Either check the boundary columns to make sure that they are not restrictive, or check that the length of the replacement string is not excessive. Modify the search string or the replacement string, or both, if necessary.
Reason:
The Element was searched and the replacement strings were applied, but no net changes were produced. The altered image of the Element is identical to the image searched.
Action:
Check whether the search and replacement strings contain redundant requests. For example, the first request changes the letter A to the letter B. The second request changes the letter B to the letter A. If the letter B did not exist in the original line, the text after the second request would be the same as the original text; see below:
First Request:
────+----1
Original text: AACCCC
Search string: Az
Replacement string: B
Updated text: BBCCCC
Second Request:
────+----1
Original text: BBCCCC
Search string: B
Replacement string: A
Updated text: AACCCC
The updated text after the second replacement takes place is the same as the original text before the first search took place. Therefore, there is no net change in the Element. If this is not acceptable, modify the search string or the replacement string, or both, if necessary.
Reason:
Message ENBS012I is displayed when the SEARCH ELEMENTS statement contains both a search string and a replacement string. This message lists the altered contents of the text shown by message ENBS016I. The message indicates that a line was altered but the before and after images of the line are identical. All non-printable characters are displayed as periods.
Action:
The column ruler and Element text appear when OPTIONS LIST DETAILS has been coded. If you want to suppress listing details, do not code the OPTIONS LIST DETAILS clause in the SEARCH ELEMENTS statement.
Reason:
No eligible Elements were found for one of the following reasons:
This statement cannot be processed any further.
Action:
Increase the scope of the search or specify other qualifying information.
Reason:
This message displays a column ruler for the Element text that follows in subsequent messages. The column offset, nnnn, will be a multiple of 10 and every tenth character thereafter represents the next highest multiple of ten. For example, if nnnn=0, t1=1, t2=2, t3=3, . . ., t9=9.
Action:
The column ruler and text appear when OPTIONS LIST DETAIL has been coded. If you want to suppress listing details, do not code the OPTIONS LIST DETAILS clause in the SEARCH ELEMENTS statement.
Reason:
Either all or a portion of the Element data is displayed. Examine the preceding ENBS015I message to determine the offset of the first byte of data that is displayed. Up to 90 bytes of data may be shown with non-printable characters being displayed as a period. This message is used to display the original, unmodified, Element data at line number nnnnn within the Element being processed.
Note: Only 90 bytes of the record are displayed at or near the offset of the first search string found in the record. If the record length is larger than 90 bytes, other occurrences of the search string may be found but are not shown.
Action:
The column ruler and Element text are displayed when you are using OPTIONS LIST DETAILS and a search string has been located. If you want to suppress listing details, do not code the OPTIONS LIST DETAILS clause in the SEARCH ELEMENTS statement.
Reason:
Message ENBS017I is displayed when the SEARCH ELEMENTS statement contains both a search string and a replacement string. This message lists the altered contents of the text shown by message ENBS016I, and shows all or part of the record that will be written to the entry Stage for the Element being processed. All non-printable characters are displayed as periods.
Action:
The column ruler and Element text appear when OPTIONS LIST DETAILS has been coded. If you want to suppress listing details, do not code the OPTIONS LIST DETAILS clause in the SEARCH ELEMENTS statement.
Reason:
Message ENBS018C is displayed when the SEARCH ELEMENTS statement contains both a search string and a replacement string, and the following conditions exist:
This message lists the altered contents of the text shown by message ENBS016I, and shows all or part of the record that will be written to the entry Stage for the Element being processed. Note that a portion of the original data is lost when the replacement-string is inserted into the record. All non-printable characters are displayed as periods.
Action:
The column ruler and subsequent Element text is displayed when OPTIONS LIST DETAILS has been coded. If you want to suppress listing details, do not code the OPTIONS LIST DETAILS clause in the SEARCH ELEMENTS statement.
If you want to prevent data truncation and possible loss of Element data, do not code the OPTIONS DATA TRUNCATION IS PERMITTED clause in the SEARCH ELEMENTS statement. Data truncation is prohibited by default.
Reason:
Message ENBS019E displays when the SEARCH ELEMENTS statement contains both a search string and a replacement string, and the following conditions exist:
This message lists the altered contents of the text shown by message ENBS016I, and shows all or part of the record that will be written to the entry Stage for the Element being processed. Note that one of two situations cause this message to appear:
All non-printable characters display as periods. Message ENBS019E may also be issued when a search string is found at the end of the modifiable columns (as determined by the IN COLUMNS and BOUNDS ARE clauses) but the replacement string cannot be inserted without being truncated. The column ruler and subsequent Element text display when OPTIONS LIST DETAILS has been coded. To suppress listing details, do not code the OPTIONS LIST DETAILS clause in the SEARCH ELEMENTS statement.
If you want to enable data truncation, and possible loss of Element data, code the OPTIONS DATA TRUNCATION IS PERMITTED clause in the SEARCH ELEMENTS statement.
Reason:
An I/O error was encountered when trying to write to the file indicated in the message (DDname). The return code nnnn was received by the routine issuing the write request. Either the machine is out of disk space or a medium error has been encountered.
Action:
Check the output for other messages that may indicate the nature of the I/O error and take corrective action. Consider increasing the amount of space allocated to the file associated with the DDname. Also consider moving the file to another location (for example, to another physical device).
Reason:
Indicates the number of Elements (component lists) eligible for processing. This value represents the number of Elements (component lists) that satisfy the search qualifications specified on the Search Element statement or the Search Element Component List statement. Each Element (component list) is searched for possible occurrences of the search strings specified in the request, if Search Element is being executed. If Search Element Component List is being executed, each Element with associated component data is examined for the output data set name specified in the request.
Action:
None.
Reason:
Message ENBS022C indicates the number of Elements (component lists) that were eligible for processing. These Elements satisfied the search criteria on the SEARCH ELEMENT statement, but were not processed due to a previous error that caused the search operation to terminate.
Action:
Check the output to find the error that caused processing to stop. Take corrective action, as necessary. You should consider, however, the effect that rerunning the search operation may have on the Elements that were successfully processed before the error occurred.
Reason:
The Element specified in message C1G0000I was found at the location indicated and will be searched.
Action:
None.
Reason:
The SEARCH ELEMENT (SEARCH ELEMENT COMPONENT LIST) statement specified one or more search strings, but no replacement strings. This message indicates the number of occurrences of the search string found within the search columns of the Element (component list) specified.
Action:
None.
Reason:
The SEARCH ELEMENTS (SEARCH ELEMENT COMPONENT LIST) statement specified one or more search strings and at least one replacement string. This message indicates the number of occurrences of the search string found within the search columns of the Element (component list) specified and the number of substitutions that were made.
Action:
None.
Reason:
The Element (component list) specified cannot be updated because of errors that occurred during the search phase of processing.
Action:
Check the output for a prior error message. Take corrective action, as necessary.
Reason:
An error occurred when attempting to replace the search string with its corresponding replacement string. Therefore, the specified Element (component list) cannot be updated. The error occurred on the line number indicated. The error may have occurred due to insufficient space in the record. Either of the following conditions could cause the error:
Action:
Check the output for a prior error message and take corrective action, as necessary. If you decide that you want to permit data truncation, you need to consider the effects of using that option on the Element data.
Reason:
Processing for the SEARCH ELEMENT (SEARCH ELEMENT COMPONENT LIST) has completed. The message indicates the highest return code encountered while processing this statement.
Action:
None.
Reason:
This message indicates where the Element specified would be added back into CA Endevor SCM. This message appears when you use replacement mode or when you generate SEARCH ELEMENT SCL. If you are using replacement mode—that is, OPTIONS UPDATE ELEMENTS is coded in the SEARCH ELEMENT statement—the update operation begins after this message is written.
Action:
None.
Reason:
You do not have the authority to retrieve the Element specified in the message from the location shown.
Action:
Contact your administrator.
Reason:
You do not have the authority to add the Element specified in the message into the location shown.
Action:
Contact your administrator.
Reason:
You do not have the authority to update the Element specified in the message at the location shown.
Action:
Contact your administrator.
Reason:
You do not have the authority to generate the Element specified in the message at the location shown.
Action:
Contact your administrator.
Reason:
The calling module is not passing the information expected by the called module. The function in the module received control but the calling routine did not provide the proper calling parameters. The called module (specified in this message) may be associated with a different release of the product than the calling-module.
Action:
Contact your administrator.
Reason:
Informational message. The Search and Replace utility is skipping the current Element because the Element name contains mixed or special case characters, or it is a long name, or both.
Action:
None.
Reason:
The data set name displayed is that specified in the For Output Dsname clause of the Search Element Component List statement. The data set name has been found in an output component record for the Element. This message is used to display the original, unmodified, output data set component item.
Action:
The column ruler and output data set name are displayed when you specify the Options List Details clause and the output data set name has been located in the output component data. If you want to suppress listing details, do not code Options List Details in the Search Element Component List statement.
Reason:
The record number could not be stored either in memory or on the ENSSPILL file. This message appears when all available memory is exhausted and one of the following conditions occurs
Processing for this Element is terminated. The next Element may be processed if enough storage can be released to the operating System.
Action:
Consider increasing the region size or the size of the ENSSPILL file.
Reason:
The record indicated in the message was previously written to the ENSSPILL file, but cannot be read from the file. This situation is due to one of the following reasons:
Action:
Consider increasing the region size or the size of the ENSSPILL file. Check the output for any other messages that may indicate why the record could not be obtained.
Reason:
You do not have the authority to update the Element specified in the message at the location shown.
Action:
Contact your administrator.
Reason:
The Element specified in the message is signed out to another user and one of the following conditions is true:
Therefore, processing cannot continue for this Element.
Action:
Try the operation again when the Element is no longer signed out. Consider using the OPTIONS OVERRIDE SIGNOUT parameter if you have the proper level of authority.
Reason:
The Element specified in the message is signed out to another user and you do not have the proper authority to override the signout.
Action:
Try the operation again when the Element is no longer signed out.
Reason:
The ENSSCLIN file does not contain any SEARCH ELEMENTS statements.
Action:
Specify a valid SEARCH ELEMENTS statement in the ENSSCLIN file.
Reason:
An unexpected parameter was received by function specified in module specified. This is an internal error.
Action:
The function returns to the calling module with a severe return code (RC=16). Otherwise, processing of the request is ignored.
Reason:
Update processing has begun for the Element specified at the location shown in the message. Update processing adds or updates the Element at the entry Stage of the Environment, and executes the generate processor if applicable.
Action:
None.
Reason:
A CCID is required in order to update Elements in the Environment and System specified. The SEARCH ELEMENTS statement does not contain a CCID, however.
Action:
Specify a CCID on the SEARCH ELEMENTS statement by coding the OPTIONS CCID clause. Check the System record to see if comments are also required for the update operation.
Reason:
A comment is required in order to update Elements in the Environment and System specified. The SEARCH ELEMENTS statement does not contain a comment, however.
Action:
Specify a comment on the SEARCH ELEMENTS statement by coding the OPTIONS COMMENT clause. Check the System record to see if CCIDs are also required for the update operation.
Reason:
The column values specified on the SEARCH ELEMENTS statement are outside the range of columns permitted for all Elements of the type specified, in all Subsystems, in the Environment, Stage, and System indicated. The column values in error are coded in either the IN COLUMNS clause or the BOUNDS ARE clause.
For example, COBOL programs are stored with a type restricting compare columns to column 7 through column 72. The error message appears if the SEARCH ELEMENTS statement refers to a column outside this range. Either of the following clauses would invoke this message:
SEARCH . . .FOR TEXT value IN COLUMN 1 to 72 SEARCH . . .FOR TEXT value IN COLUMN 7 to 8_
Action:
Modify the appropriate column information in the SEARCH ELEMENTS statement, to provide a value that lies within the Element type's compare columns. You can specify FIRST or LAST, or both, to dynamically select the first or last column of the types compare column range.
Reason:
An error that cannot be corrected occurred and caused the program's error recovery exit to be invoked. Termination processing is immediately invoked. The program may try to print the Summary Report before terminating unless the ESTAE exit was previously invoked.
This situation is caused by any condition that might result in an abnormal end (ABEND) state, such as a storage violation (usually caused by a corrupt or invalid pointer).
Action:
Determine the nature of the abnormal termination and consider trying the operation again. If the problem persists or you are not certain about the effects of trying the operation again, talk with your administrator.
Reason:
The ENSSCLIN DD statement was not allocated. The Search & Replace utility program reads the SEARCH ELEMENTS SCL statements from the ENSSCLIN file.
Action:
Correct the JCL statements and try the operation again.
Reason:
The SEARCH ELEMENTS statement was successfully parsed but was not processed because the VALIDATE parameter was specified on the PARM= statement in the execution JCL.
Action:
If you do not want to run in validate mode, remove the VALIDATE parameter from the PARM= statement in the execution JCL.
Reason:
The boundary columns are invalid for Elements of the type indicated in the location indicated in the message. This message appears if the from-column is greater than the to- column (in the IN COLUMNS clause) or the left-column is greater than the right-column (in the BOUNDS ARE clause). Message ENBS907E or message ENBS908E, or both, may follow this message. These messages specify the column values that were coded in the SEARCH ELEMENTS statement or derived from the Element type compare columns.
Action:
Review the SEARCH ELEMENTS statement and the values displayed in the subsequent ENBS907E and ENBS908E messages. Take corrective action as necessary.
Reason:
The Element indicated in the message was found in the location specified, but this location is an "in-between" Stage. That is, the Stage (location) is not on the Environment map. For example, consider the following Environment map:
ENV1.STAGE1ENV1.STAGE2ENV2.STAGE2
The first occurrence of the Element in the map is found at ENV2.STAGE2. The utility then checks whether the Element exists anywhere else between Stage 1 of the base Environment (ENV1.STAGE1) and the location in which the Element was found, and finds an occurrence of the Element at ENV2.STAGE1—which is not on the map. The Element cannot be processed because ENV2.STAGE1 is an in-between Stage of the Environment map.
Action:
Move or delete the Element from the in-between Stage and try the operation again.
Reason:
A record with an invalid record length was read for the Element specified in the message, at the location specified. Record lengths must be within the range of 1 to 32000, inclusive. This situation may indicate an internal error.
Action:
Check for other error messages that may indicate a problem with your System. Contact your administrator.
Reason:
The ENSSCLOT DD statement is present but the data set allocated to that DD statement does not have the proper attributes. Either the wrong data set was allocated or the attributes of the data set were other than those required.
Message ENBS056I, which immediately follows this message, provides the correct attributes for the data set.
Action:
Make sure that the data set allocated to the ENSSCLOT DD statement is not a NULLFILE data set. Also, ensure that the attributes of the data set allocated to ENSSCLOT correspond to those described in message ENBS056I.
Reason:
This message immediately follows message ENBS055E and describes the attributes permitted for the data sets allocated to the ENSSCLOT DD statement:
Action:
Make sure that the data set allocated to ENSSCLOT has the appropriate attributes: DSORG=PS, RECFM=F│.FB, and LRECL=80.
Reason:
The ENSSPILL DD statement was present and the data set allocated to that DD statement does not have the proper attributes. Either the wrong data set was allocated or the attributes of the data set were other than those required.
Message ENBS058I, which immediately follows this message, provides the correct attributes for the data set.
Action:
Make sure that the data set allocated to the ENSSPILL DD statement is not a NULLFILE data set. Also, make sure that the attributes of the data set allocated to ENSSPILL correspond to those described in message ENBS058I.
Reason:
This message describes the attributes permitted for the data sets allocated to the ENSSPILL DD statement. The data set must be sequential with a logical record length not less than 32004 for variable length (RECFM=V) data sets or variable length blocked (RECVM=FB) data sets. For RECFM=VB data sets, the block size must be 4 bytes larger than the record length.
This message immediately follows message ENBS057E and describes the attributes permitted for the data sets allocated to the ENSSPILL DD statement:
Action:
Be sure the data set allocated to ENSSPILL has the appropriate attributes: DSORG=PS, RECFM=V│.VB, and LRECL=32004.
Reason:
The logical end-of-file on the ENSSPILL was reached prematurely. This may indicate a possible loss of data. This situation may be caused by an I/O error on the ENSSPILL file.
Action:
Determine if there was any loss of data for the Element being processed. Take corrective action as necessary.
Reason:
When running in replacement mode, the Search & Replace program attempts to gain exclusive use of an Element at both the source and entry Stages. The ENQ request for the Element specified, in the location indicated, failed. The return code returned by the ENQ/DEQ processor is shown.
This situation may occur if the Element is being used by another user for an update operation.
Action:
Try the operation again at a later time.
Reason:
After processing an Element, the Search & Replace program releases exclusive use of the resources via a DEQ request. The DEQ request for the Element specified, in the location indicated, failed. The return code returned by the ENQ/DEQ processor is shown. If the resource is not released, other jobs or users may be unable to update the Element until the present job or user session is terminated.
This situation most likely occurs if there is an internal error.
Action:
The operating System automatically releases the resource when the current job or user session is terminated. Contact your administrator if this problem continues.
Reason:
The process group specified in the message was not found. Element processing is terminated.
Action:
Check whether the processor group name exists at the Stage 1 of the base Environment. If it does not, specify another processor group name or create a processor for the name indicated.
Reason:
The process group name specified in the message cannot be invoked. The return code and reason code is shown in the message.
Action:
None.
Reason:
The update processing for the Element specified in the message has completed. The highest return code detected during the update processing for this Element is also shown in the message.
Action:
None.
Reason:
The BOUNDS ARE values specified for the SEARCH ELEMENTS statement are outside the compare column range defined for the type shown in the message.
Action:
Correct the BOUNDS ARE clause and try the operation again.
Search string was not found in any of the Elements (component lists) that were searched
Reason:
The search string cannot be found in any Elements (component lists), in the columns specified (or derived from the Element type compare columns). Either the Elements (component lists) do not contain the string at all or Elements contain the string in other than the columns specified. This warning message is issued to draw attention to this condition; it does not necessarily indicate a problem.
Action:
None.
Reason:
The Element has been moved or updated, to the location indicated in the message, since the Search & Replace utility identified it as a possible candidate for processing. The Element will not be processed.
Action:
None.
Reason:
The length of the search string is larger than the size of the search area.
Action:
Check whether the IN COLUMNS and BOUNDS ARE parameters are too restrictive. Then, either increase the size of the search area or decrease the length of the search string.
Reason:
The size of the replacement string is larger than the size of the area that can be modified (modifiable range) for the Element being processed. The replacement string may be too large or the BOUNDS ARE right-column (or IN COLUMNS to-column) may be too restrictive.
Action:
Correct the appropriate clause in the SEARCH ELEMENTS statement and try the operation again.
Reason:
The Stage number or Stage ID specified in the Search Element Component List statement does not exist. This error condition is not recognized during SCL syntax checking. It appears when the utility attempts to search for the output data set name in the output component information.
Action:
Change the Search Element Component List statement to specify a valid and explicit Stage number or Stage ID for the location at which you want to execute the action. Correct the appropriate clause in the SEARCH ELEMENT statement and try the operation again.
Reason:
A sourceless Element was selected for processing and its last level timestamp is different from the next sourced Element found up the map.
Action:
Re-generate or delete the sourceless Element then perform the Search and Replace action.
Reason:
The corresponding source for the selected sourceless Element was not found up the map from the sourceless Element.
Action:
Try to determine the cause for the missing source. If the sourceless Element is no longer needed, delete it.
Reason:
The source location for the selected sourceless Element has changed between the Element selection process and the source retrieval process.
Action:
Retry the Search and Replace action.
Reason:
Informational. Identifies the Element name.
Action:
None.
ENBS900I Control statement parsing is beginning
Reason:
Records from the ENSSCLIN file are being read, interpreted and validated.
Action:
None.
Reason:
The text of statement nnn, as it was read by the parser, appears below this message. This text appears in the same format as it appeared in the ENSSCLIN file.
Action:
None.
Reason:
The utility has successfully parsed all the control statements.
Action:
None.
Reason:
The utility detected one or more errors in the control statements during the parsing process. This condition prevents further processing of the statements.
Action:
Correct the errors and try again.
Reason:
The utility detected one or more errors in the SCL statement just parsed. The utility continues parsing the next SCL statements, if any.
Action:
Correct the errors and try again.
Reason:
The SEARCH ELEMENTS statement contains an invalid FOR TEXT clause. The search string was either omitted from the clause or was null (that is, " "). The FOR TEXT clause must contain a search string of one or more bytes in length.
Action:
Specify a search string of one or more bytes in the FOR TEXT clause.
Reason:
The SEARCH ELEMENTS statement contains a FOR TEXT clause with identical search and replacement strings. This is explicitly prohibited for performance reasons.
Action:
If you do not intend to replace the search string, do not specify a replacement string. If you want to replace the search string with another value, specify that value and make sure that it is not the same as the search string value.
Reason:
The boundary columns, as specified by the BOUNDS operand of the FOR TEXT parameter, are invalid. Either the left-column boundary is greater than the right-column boundary, or the use of the FIRST and LAST qualifiers is improper.
Action:
Check that the left-column boundary specified is not greater than the right- column boundary specified. If you use the FIRST and LAST parameters, avoid coding clauses such as the following:
BOUNDS ARE LAST TO FIRST BOUNDS ARE LAST to 2_ BOUNDS ARE 2_ TO FIRST
Reason:
The boundary columns, as specified by the IN COLUMNS operand of the FOR TEXT parameter, are invalid. Either the from-column is greater than the to-column or the use of the FIRST and LAST qualifiers is improper.
Action:
Check that the from-column is not greater than the to-column parameter. If you use the FIRST and LAST parameters, avoid coding clauses such as the following:
IN COLUMNS LAST TO FIRST IN COLUMNS LAST to 2_ IN COLUMNS 2_ TO FIRST
Reason:
The SEARCH ELEMENTS statement did not contain a FOR TEXT clause.
Action:
You must code at least one FOR TEXT clause on the SEARCH ELEMENTS statement.
Reason:
The SEARCH ELEMENTS statement did not specify which Elements are to be searched.
Action:
Specify an Element name, a wildcarded Element name, or a range of Element names on the SEARCH ELEMENTS statement.
Reason:
The SEARCH ELEMENTS statement specified a range of Elements in the wrong order.
Action:
Either specify the Elements in the order shown in this message or change the Element names as necessary to make sure that the second Element is greater than the first.
Reason:
The FROM ENVIRONMENT clause is required but was not specified.
Action:
Specify the Environment from which the search is to originate. Be sure to enter an explicit Environment name.
Reason:
The FROM ENVIRONMENT clause was specified but contained a wildcard character.
Action:
You must specify an explicit Environment name. You cannot use a wildcard with this value.
Reason:
The FROM SYSTEM clause is required but was not specified.
Action:
Specify the System from which the search is to originate. You can enter an explicit System name or use a wildcard.
Reason:
The FROM SUBSYSTEM clause is required but was not specified.
Action:
Specify the Subsystem from which the search is to originate. You can enter an explicit Subsystem name or use a wildcard.
Reason:
The FROM TYPE clause is required but was not specified.
Action:
Specify the type associated with the Elements to be searched. You can enter an explicit type or use a wildcard.
Reason:
The FOR TEXT IN COLUMNS parameter specified a column value that was not in the range of 1 to 32000 inclusive, which is the valid range for this parameter.
Action:
Specify a column number in the range of 1 to 32000 inclusive. Or, if appropriate, specify FIRST or LAST.
Reason:
The FOR TEXT IN COLUMNS parameter specified a column value that was not in the range of 1 to 32000 inclusive, which is the valid range for this parameter.
Action:
Specify a column number in the range of 1 to 32000 inclusive. Or, if appropriate, specify FIRST or LAST.
Reason:
The FOR TEXT BOUNDS ARE parameter specified a column value that was not in the range of 1 to 32000 inclusive, which is the valid range for this parameter.
Action:
Specify a column number in the range of 1 to 32000 inclusive. Or, if appropriate, specify FIRST or LAST.
Reason:
The FOR TEXT BOUNDS ARE parameter specified a column value that was not in the range of 1 to 32000 inclusive, which is the valid range for this parameter.
Action:
Specify a column number in the range of 1 to 32000 inclusive. Or, if appropriate, specify FIRST or LAST.
Reason:
The data set name specified as the replacement data set name in the Search Element Component List statement is not a cataloged data set.
Action:
Specify the name of a cataloged data set that is a valid name and an existing data set in the Replace With Output Dsname clause in the Search Element Component List statement.
Reason:
An invalid data set name was specified in Search Element Component List statement. The data set name specified exceeds 44 characters in length.
Action:
Ensure that the data set name is a valid name and is an existing data set.
A Stage number or Stage ID must be specified.
Reason:
The Search Element Component List statement did not contain a Stage number or Stage ID value. This value is required.
Action:
Specify an explicit Stage number or Stage ID for the location at which you want to execute the Search and Replace utility.
A Stage number or Stage ID cannot be wildcarded.
Reason:
The Search Element Component List statement contained a wildcarded value for Stage number or Stage ID. Only explicit Stage number and Stage ID values are valid.
Action:
Specify an explicit Stage number or Stage ID for the location at which you want to execute the Search and Replace utility.
Reason:
The Search Component List statement contained a wildcarded value for the DSName value specified in either the For Output Dsname or the Replace With Output Dsname clause. These data set names cannot contain wild card characters.
Action:
Specify the fully qualified name of an existing data set in the SCL.
Reason:
The EOF control statement was automatically generated when the parser reached the logical end- of-file on the ENSSCLIN file. Or, the control statements in the ENSCCLIN file were not terminated by the EOF control statement.
Action:
Code an EOF control statement at the end of the ENSSCLIN file if you want to avoid generating this message; otherwise, no further action is required.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|