This section details messages generated by the SCL parser in the course of processing, along with possible causes and corrective actions to take in error situations.
Reason:
A member name was entered, but a name mask was used with the Element name in the "action ELEMENTS name" clause.
Action:
A fully qualified Element name must be specified in the ELEMENTS clause of the action statement. Correct the error and resubmit the job.
Reason:
A member name was entered, but a name mask was used with the Element name in the ELEMENTS clause.
Action:
A fully qualified Element name must be specified in the ELEMENTS clause of the action statement. Correct the error and resubmit the job.
Reason:
Both a THROUGH clause and a member name were coded for the action; only one of these selections is allowed.
Action:
Remove the THROUGH clause and code individual action statements for all Elements against which you wish to operate.
Reason:
The request contains one of the Version or Level keywords but is missing the required second keyword.
Action:
Specify both the Version and Level in the request or do not specify either keyword.
Reason:
FROM ENVIRONMENT information, which is required for this action, cannot be found in the syntax.
Action:
Make sure that a FROM ENVIRONMENT clause is entered. The clause can be coded in the SET FROM statement or specified in the FROM clause within the action.
Reason:
FROM SYSTEM information, which is required for this action, cannot be found in the syntax.
Action:
Make sure that a FROM SYSTEM clause is entered. The clause can be coded in the SET FROM statement or specified in the FROM clause within the action.
Reason:
FROM SUBSYSTEM information, which is required for this action, cannot be found in the syntax.
Action:
Make sure that a FROM SUBSYSTEM clause is entered. The clause can be coded in the SET FROM statement or specified in the FROM clause within the action.
Reason:
FROM TYPE information, which is required for this action, cannot be found in the syntax.
Action:
Make sure that a FROM TYPE clause is entered. The clause can be coded in the SET FROM statement or specified in the FROM clause within the action.
Reason:
FROM STAGE or FROM STAGE NUMBER is required for this action, but was not found in the syntax.
Action:
Make sure that a FROM STAGE or FROM STAGE NUMBER clause is entered. The clause can be coded in the SET FROM statement or specified in the FROM clause within the action.
Reason:
The source location for this action is an archive file, but the source specification does not include a Stage number.
Action:
Specify a Stage number in the source statement, and then resubmit the action request.
Reason:
An Element name was entered, but a name mask was used with the Element name in the ELEMENTS clause for the source of the action.
Action:
A fully qualified Element name must be specified in the ELEMENTS clause of the action statement. Correct the error and resubmit the job.
Reason:
TO ENVIRONMENT information, which is required for this action, was not found in the syntax.
Action:
Make sure that a TO ENVIRONMENT clause is entered. The clause can be coded in the SET TO statement or specified in the TO clause within the action.
Reason:
TO SYSTEM information, which is required for this action, cannot be found in the syntax.
Action:
Make sure that a TO SYSTEM clause is entered. The clause can be coded in the SET TO statement or specified in the TO clause within the action.
Reason:
TO SUBSYSTEM information, which is required for this action, cannot be found in the syntax.
Action:
Make sure that a TO SUBSYSTEM clause is entered. The clause can be coded in the SET TO statement or specified in the TO clause within the action.
Reason:
TO TYPE information, which is required for this action, cannot be found in the syntax.
Action:
Make sure that a TO TYPE clause is entered. The clause can be coded in the SET TO statement or specified in the TO clause within the action.
Reason:
TO FILE information, which is required for this action, cannot be found in the syntax.
Action:
Make sure that a TO FILE clause is entered. The clause can be coded in the SET TO statement or specified in the TO clause within the action.
Reason:
An attempt was made to code both CA Endevor SCM location information and DSNAME location information. Entry of both types of information is invalid.
Action:
Code either CA Endevor SCM location data - Environment, System, subSystem, type, and Stage (as required) - or a DSNAME, but not both. Resubmit the job.
Reason:
An attempt was made to code both FILE location information and DSNAME location information. Entry of both types of information is invalid.
Action:
Code either FILE or DSNAME data, but not both. Resubmit the job.
Reason:
The specified STOPRC is not within the range indicated in the message.
Action:
Specify a STOPRC value of 4 through 16 and resubmit the job.
Reason:
The FROM clause is required for this action, but none was found in the syntax.
Action:
For a description of the syntax required for this action, see the appropriate section of the SCL Reference Guide
Reason:
All SCL statements must be terminated with a period. The last statement in the input did not contain a period.
Action:
Specify a period in the last statement and resubmit the job.
Reason:
An "&&ACTION. ELEMENTS name" statement was encountered, but no SET ACTION statement precedes. A SET ACTION statement must be coded prior to any &&ACTION. ELEMENTS statements.
Action:
Specify a SET ACTION clause and resubmit the job. For information regarding the SET ACTION and &&ACTION. clauses, see the appropriate section of the SCL Reference Guide.
Reason:
No valid action requests were found when the SCL was parsed.
Action:
Correct all syntax errors. Be sure that an action clause has been specified as input to the SCL run.
Reason:
An invalid date was entered. The date specified is either not in the correct format or is outside the valid range of dates.
Action:
Enter a valid date and retry the action.
Reason:
An invalid time was entered. The time specified is either not in the correct format or is outside the valid time range.
Action:
Specify a valid time and retry the action.
Reason:
You cannot use both a name mask with the Element name in the "action ELEMENTS name" clause and code a level specification for the Element. Only one of these entries is allowed.
Action:
If you want to specify a particular level, each Element must be explicitly identified (that is, no name mask). Define an individual action statement for each Element against which you wish to operate. For additional information, see the appropriate section in the SCL Reference Guide.
Reason:
You have specified a FROM date and time in a WHERE clause that is later than the THROUGH date and time. This is not allowed.
Action:
Respecify the date and time information, and then resubmit.
Reason:
Both a Stage ID and a Stage number were found in the syntax for either the FROM or TO clause. Only one Stage IDentifier is allowed.
Action:
Enter either the Stage ID or Stage number and resubmit the job.
Reason:
Stage number was specified but contained a value other than 1 or 2. Only 1 or 2 is allowed for the STAGE NUMBER statement.
Action:
Specify either 1 or 2 in the STAGE NUMBER clause and resubmit the job.
Reason:
The Stage is missing from a Generate Copyback or Generate Nosource action.
Action:
Supply the Stage on the Generate action and resubmit the job.
Reason:
Both options cannot be active at the same time.
Action:
Change the Generate action option to either Copyback or Nosource and then re-submit the job.
Reason:
Generate Copyback implies Search. Nosearch is no longer a valid option with Generate Copyback.
Action:
Remove the Nosearch option and re-submit the job.
Reason:
SCL requires that if one of the following fields is coded in the WHERE COMPONENTS EQUAL clause, all fields (that is, all location information) must be specified: Environment, System, Subsystem, type, Stage number. You can use the name mask with any or all of these fields.
Action:
Enter the required (missing) information and resubmit the job. For additional information, see the appropriate section in the SCL Reference Guide.
Reason:
A BUILD WITH COMPONENTS clause was coded for the List action, but no WHERE COMPONENTS EQUAL clause can be found. Use of the BUILD WITH COMPONENTS clause requires entry of an associated WHERE COMPONENTS EQUAL clause.
Action:
Enter the required WHERE COMPONENTS EQUAL clause and resubmit the job.
Reason:
Both a WHERE TEXT EQUALS clause and a WHERE COMPONENTS EQUAL clause was specified for the List action, but only one of these clauses is allowed in the syntax.
Action:
Enter either a WHERE TEXT EQUALS clause or a WHERE COMPONENTS EQUAL clause and resubmit the job.
Reason:
Both a WHERE GENERATE FAILED clause and a WHERE COMPONENTS EQUAL clause were specified for the List action, but only one of these clauses is allowed in the syntax.
Action:
Enter either a WHERE GENERATE FAILED clause or a WHERE COMPONENTS EQUAL clause and resubmit the job.
Reason:
A name mask was used in the FROM ENVIRONMENT name clause, but a name mask is not allowed with this particular field.
Action:
Enter a complete (fully qualified) Environment name in the FROM clause and resubmit the job.
Reason:
An invalid characters was coded in the name specified.
Action:
The only characters allowed when coding the name are: A-Z, 0-9, @, #, and $. Correct the error and resubmit the job.
Reason:
A name mask was used in the TO ENVIRONMENT name clause, but a name mask is not allowed with this particular field.
Action:
Enter a complete (fully qualified) Environment name in the TO clause and resubmit the job.
Reason:
A name mask was used in the TO SYSTEM name clause, but a name mask is not allowed with this particular field.
Action:
Enter a complete (fully qualified) System name in the TO clause and resubmit the job.
Reason:
A name mask was used in the TO SUBSYSTEM name clause, but a name mask is not allowed with this particular field.
Action:
Enter a complete (fully qualified) Subsystem name in the TO clause and resubmit the job.
Reason:
A name mask was used in the TO TYPE name clause, but a name mask is not allowed with this particular field.
Action:
Enter a complete (fully qualified) type name in the TO clause and resubmit the job.
Reason:
The FROM clause specified contains CA Endevor SCM location information (Environment, System, Subsystem, type, or Stage), but these are not allowed for this action.
Action:
Remove the CA Endevor SCM location information coded for the indicated action and resubmit the job. For details about coding this action, see the appropriate section in the SCL Reference Guide.
Reason:
A FROM FILE name ENVIRONMENT (or SYSTEM, SUBSYSTEM, TYPE, or STAGE) clause was found for this action, indicating that input comes from an archive file created by the Transfer or Archive actions. Archive file input is not supported for the action being flagged (in error).
Action:
Do not specify both FILE information and CA Endevor SCM location information (that is, Environment, System, Subsystem, type, and Stage). For information about the required and optional fields allowed for the indicated action, see the SCL Reference Guide. Correct the error and resubmit the job.
Reason:
The SET TO clause contains both CA Endevor SCM location information (that is, Environment, System, Subsystem, type, and Stage) and a member name. Entering both specifications is not allowed.
Action:
Specify either CA Endevor SCM location information (that is, Environment, System, Subsystem, type, and Stage) or a member name, but not both. For additional coding information, see the SCL Reference Guide. Correct the error and resubmit the job.
Reason:
An invalid character was coded in the site ID specified.
Action:
The only characters allowed when coding the site ID are: A-Z, 0-9, @, #, and $. Correct the error and resubmit the job.
Reason:
An invalid character was coded in the Environment name specified.
Action:
The only characters allowed when coding the Environment name are: A-Z, 0-9, @, #, and $. Correct the error and resubmit the job.
Reason:
An invalid character was coded in the System name specified.
Action:
The only characters allowed when coding the System name are: A-Z, 0-9, @, #, and $. Correct the error and resubmit the job.
Reason:
An invalid character was coded in the Subsystem name specified.
Action:
The only characters allowed when coding the Subsystem name are: A-Z, 0-9, @, #, and $. Correct the error and resubmit the job.
Reason:
An invalid character was coded in the type name specified.
Action:
The only characters allowed when coding the type name are: A-Z, 0-9, @, #, and $. Correct the error and resubmit the job.
Reason:
An invalid character was coded in the Stage ID value specified.
Action:
The only characters allowed when coding the Stage ID are: A-Z, 0-9, @, #, and $. Correct the error and resubmit the job.
Reason:
The THROUGH Element name was specified but the LEVEL clause was also found. If specifying the LEVEL clause, the THROUGH Element clause is not allowed.
Action:
If you want to use the LEVEL clause, you must explicitly define each Element. Remove either the LEVEL clause or the THROUGH clause and resubmit the job.
Reason:
A TO FILE named ENVIRONMENT (or SYSTEM, SUBSYSTEM, TYPE, or STAGE) clause was found for this action, indicating that an archive file was specified as the TO location. An archive file (or file created by the Transfer action) is not supported by the action indicated.
Action:
Do not specify an archive file in the TO clause for this action. For information about the coding requirements and options available for the action, see the SCL Reference Guide. Correct the error and resubmit the job.
Reason:
A TO FILE clause was found in the syntax, but is not supported for this action.
Action:
Do not specify a TO FILE clause for this action. For information about the coding requirements and options available for the action, see the SCL Reference Guide. Correct the error and resubmit the job.
Reason:
A TO DSNAME clause was found in the syntax, but is not supported for this action.
Action:
Do not specify a TO DSNAME clause for this action. For information about the coding requirements and options available for the action, see the SCL Reference Guide. Correct the error and resubmit the job.
Reason:
CA Endevor SCM location information (that is, Environment, System, Subsystem, type, and Stage) was coded in the TO clause, but this data is not supported for this action.
Action:
Do not specify CA Endevor SCM location information (that is, Environment, System, Subsystem, type, and Stage) in the TO clause for this action. For information about the coding requirements and options available for the action, see the appropriate section in the SCL Reference Guide. Correct the error and resubmit the job.
Reason:
A FROM FILE clause was found in the syntax, but is not supported for this action.
Action:
Do not specify a FROM FILE clause for this action. Refer to the appropriate section in the SCL Reference Guide for information about the coding requirements and options available for the action. Correct the error and resubmit the job.
Reason:
A FROM DSNAME clause was found in the syntax, but is not supported for this action.
Action:
Do not specify a FROM DSNAME clause for this action. Refer to the appropriate section in the SCL Reference Guide for information about the coding requirements and options available for the action. Correct the error and resubmit the job.
Reason:
When using a name mask, one of the following situations occurred:
Action:
Enter only one asterisk when using a name mask with the Element name. Be sure the asterisk is the last character coded in the field.
Reason:
You specified an Element using a wildcard when building a Package. This is not valid syntax.
Action:
Make the Element specification specific.
Reason:
You used a THROUGH ELEMENT clause when building a Package. This is not a valid syntax.
Action:
Respecify the request without the THROUGH ELEMENT clause.
Reason:
You used a FROM FILE (DDNAME) clause when building a Package. This is not valid syntax.
Action:
Respecify the request without the FROM FILE (DDNAME) clause.
Reason:
You used a wildcard to specify one or more of the parameters indicated in the message. This is not valid syntax for Package processing.
Action:
Respecify the request without wildcards.
Reason:
You used a TO FILE (DDNAME) clause when building a Package. This is not valid syntax.
Action:
Respecify the request without the TO FILE (DDNAME) clause.
Reason:
You used a wildcard to specify one or more of the parameters indicated in the message. This is not valid syntax for Package processing.
Action:
Respecify the request without wildcards.
Reason:
You specified both the BYPASS DELETE PROCESSOR and BYPASS ELEMENT DELETE options on an action request. These options are mutually exclusive.
Action:
Respecify the request.
Reason:
You specified a CLEAR FROM or CLEAR TO statement using incorrect syntax.
Action:
Correct the syntax.
Reason:
You specified both the SEARCH and NOSEARCH options on an action request. These options are mutually exclusive.
Action:
Respecify the request.
Reason:
You specified more than one of the options indicated in the message. These options are mutually exclusive.
Action:
Respecify the action request using only one of these options.
Reason:
You requested a Generate action and specified either SEARCH or NOSEARCH as an option. Neither option can be specified with this action.
Action:
Respecify the request without a search option.
Reason:
You requested a Transfer action to an archive file, with one of the options indicated in the message. These options cannot be used when the target of a transfer is an archive file.
Action:
Respecify the request without these options.
Reason:
You specified a List action using the SHOW TEXT option, but did not included a WHERE TEXT clause in the request.
Action:
Respecify the request to include a WHERE TEXT clause.
Reason:
You specified a WHERE COMPONENT clause with an initial value that is higher than the THROUGH value. This is invalid syntax.
Action:
Respecify the WHERE COMPONENT clause.
Reason:
You specified an ELEMENT clause with an initial value that is higher than the THROUGH value. This is invalid syntax.
Action:
Respecify the ELEMENT clause.
Reason:
You used invalid characters to specify a member name.
Action:
Respecify the name using the characters indicated in the message.
Reason:
You specified a member using wildcards. This is invalid syntax.
Action:
Respecify the member name without a wildcard.
Reason:
The current action does not allow the FROM MEMBER clause. The parsing routine generates a syntax error when it finds the FROM MEMBER clause.
Action:
Remove the FROM MEMBER clause from the action.
Reason:
The processor group cannot be a wildcarded name mask. It must be a fully qualified name. The parsing routine generates a syntax error when it finds a wildcarded processor group name.
Action:
Specify a fully qualified name on the OPTIONS PROCESSOR GROUP clause. Resubmit the request.
Reason:
The processor group option was specified, but the name of the processor group is blank.
Action:
Correct the SCL by adding the name of the processor group and reexecute the job.
Reason:
The WHERE component level clause was specified and the level number is missing or non-numeric.
Action:
Correct the SCL statement and reexecute the job.
Reason:
An attempt to acquire storage to build the user request block failed.
Action:
Increase the size of the region parameter on the JOB card and reexecute the job.
Reason:
Update and Noupdate cannot be active at the same time.
Action:
Change the Alter action option to either Update or Noupdate. If neither option is specified, the default is Noupdate.
Reason:
The Alter action requires that SMF recording be activated.
Action:
Enable SMF recording in your C1DEFLTS table. Set the SMFREC# parameter to specify the SMF record number to use for recording Endevor actions. You must also turn on SMF activity recording using the SMFACT parameter for each Environment where you use the Alter action. For more information about the SMFREC# and SMFACT parameters, see the Administration Guide.
Reason:
You must include a Replace clause in the Alter action.
Action:
Change the Alter action to include a valid Replace clause.
Reason:
You must use an explicit Environment name when using the Search option.
Action:
Change the action to include an explicit Environment name or remove the Search option.
Reason:
You must use a valid From value.
Action:
Change your Alter action to remove invalid characters, invalid name-masking characters, or embedded spaces not enclosed in single or double quotation marks.
Reason:
You must use a valid With value.
Action:
Change your Alter action to remove any invalid characters, invalid name-masking characters, or embedded spaces not enclosed by single or double quotation marks.
The User Data start position, the length value, or both are either outside the range of 1 to 80 or the combined numeric value of the start position and length exceeds 80.
Action:
Change your Alter action User Data start position, the length value, or both so that the combined value is within the range of 1 to 80.
Reason:
You must specify a User Data length greater than or equal to the With value length.
Action:
Increase the User Data length value equal to or greater than the length of the specified User Data With to-value.
Reason:
You must specify a pad character if the length value is greater than the length of the to-value.
Action:
Change your Alter action to include a pad character in the User Data With clause or change the length value to be equal to the length of the text.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|