This section details messages generated by the Inventory Analyzer in the course of processing, along with possible causes and corrective actions to take in error situations.
Reason:
Informational message. This message appears in the Execution Report, and indicates that analysis of the program parameter is beginning. You receive this message only if you specified a program parameter in the JCL for the Inventory Analyzer.
Action:
None.
Reason:
The parameter format is invalid.
Action:
Correct the errors and retry execution.
SOURCE OPTIONAL REQUESTED, "FROM" DATA SETS NO LONGER REQUIRED
Reason:
Informational message. This message appears in the Parameter Syntax section of the Execution Report, and indicates that the SOURCE OPTIONAL parameter was coded. This option allows you to omit FROM data sets from your ANALYZE requests. If a FROM data set is omitted, analysis proceeds without any source analysis. You receive this message only if you specified the SOURCE OPTIONAL parameter in the JCL for the Inventory Analyzer.
Action:
None.
Reason:
Informational message. This message appears in the Execution Report, and indicates that a parameter was coded that overrides the default ddname associated with the output model definition. You receive this message only if you specified a ddname that overrides the ddname BSTMODEL in the JCL for the Inventory Analyzer.
Action:
Make sure that the DDname "BSTMODEL" is replaced in the jobsteps with the ddname identified in the message in order to read the output model definition.
Reason:
Informational message. This message appears in the Execution Report, and indicates that a parameter was coded that overrides the default DDname associated with the Execution Report.
You receive this message only if you specified a DDname that overrides the default DDname C1MSGS1 in the JCL for the Inventory Analyzer.
Action:
Make sure that the DDname "C1MSGS1" is replaced in the jobstream with the DDname identified in the message in order to obtain the Execution Report.
Reason:
Informational message. This message appears in the Execution Report, and indicates that a parameter was coded that overrides the default DDname associated with the input request data set.
You receive this message only if you specified a DDname that overrides the default DDname BSTIPT01 in the JCL for the Inventory Analyzer.
Action:
Make sure that the DDname "BSTIPT01" is replaced in the jobstream with the DDname identified in the message in order to read the input requests.
Reason:
Informational message. This message appears in the Execution Report, and indicates that a parameter was coded that overrides the default DDname associated with the input rule definitions.
You receive this message only if you specified a DDname that overrides the default DDname BSTRULES in the JCL for the Inventory Analyzer.
Action:
Make sure that the DDname "BSTRULES" is replaced in the jobstream with the DDname identified in the message in order to read the input rule definitions.
Reason:
Informational message. This message appears in the Execution Report, and indicates that a parameter was coded that overrides the default DDname associated with the Summary Report.
You receive this message only if you specified a DDname that overrides the default DDname C1SUMARY in the JCL for the Inventory Analyzer.
Action:
Make sure that the DDname (C1SUMARY) is replaced in the jobstream with the DDname identified in the message in order to obtain the Summary Report.
Reason:
Informational message. This message appears in the Execution and Summary Reports, and indicates the number of COND=SUCCESS members processed with output model directed to the DDname specified.
Action:
None.
Reason:
Informational message. This message appears in the Execution and Summary Reports, and indicates the number of COND=FAILURE members processed with output model directed to the DDname specified.
Action:
None.
Reason:
Informational message. This message appears in the Execution and Summary Reports, and indicates the number of actions selected for processing as well as the number of members associated with those actions.
Action:
None.
Reason:
Informational message. This message appears in the Execution and Summary Reports, and indicates the number of members in FROM data sets for which no corresponding output member in a USING data set was found.
Action:
Make sure that the USING data set list contains all of the associated output data sets to be used for analysis.
Reason:
Informational message. This message appears in the Execution and Summary Reports, and indicates the total number of members analyzed as well as the number of members that were successfully processed; that is, those members for which exactly one Type and processor group were established.
Action:
None.
Reason:
Informational message. This message appears in the Execution and Summary Reports, and indicates the number of members analyzed for which no Type and processor group were established.
Action:
Review the Execution Report. Either you need more information about the members or you may need to modify some rules.
Reason:
Informational message. This message appears in the Execution and Summary Reports, and indicates the number of members analyzed for which more than one Type and processor group were established.
Action:
Review the Execution Report. Either you need more information about the members or you may need to modify some rules.
Reason:
Informational message. This summary is provided at the end of the job listing the Types and groups for which members were successfully matched, and indicates how many matches occurred.
Action:
None.
Reason:
Informational message. This message appears in the Execution Report, and indicates that the next logical request will be read and parsed. Each logical request is assigned a statement number.
Action:
None.
Reason:
The member name clause, which must be specified, was omitted from the ANALYZE statement.
Action:
Correct the ANALYZE statement by adding a member name.
Reason:
A THROUGH clause was specified on an ANALYZE statement. The member specified has a greater value than the through member specified, resulting in no possible members in the range.
Action:
Correct either the member name or the through member name.
Reason:
The FROM data set clause, which must be specified, was omitted from the ANALYZE statement.
Action:
Specify the FROM data set name on the ANALYZE statement, or include a SET statement with the FROM clause in the request data set prior to the ANALYZE statement, or run with source, opt parameter.
Reason:
An attempt to obtain storage failed.
Action:
Increase the region size on the JOB or EXEC card.
Reason:
The member name field contains some invalid characters or an invalid sequence of characters.
Action:
Correct the member name. A member name can contain only the characters: A- Z, 0-9, @, #, and $. In addition, you can use a question mark (?) as a character placeholder and an asterisk (*) as a terminating wildcard. However, you cannot code any characters following an asterisk. Also, you cannot use embedded blanks
Reason:
Informational message. This message appears in the Execution Report, and indicates that the request data set was completely parsed.
Action:
None.
Reason:
Informational message. This message appears in the Execution Report, and indicates the next rule to be read and parsed. Each rule read is assigned a statement number.
Action:
None.
Reason:
The member name field contains an invalid sequence of characters.
Action:
Correct the field value. A question mark (?) can be used as a character placeholder, and an asterisk (*) can be used as a terminating wildcard.
Reason:
No WHEN clause was coded for this rule definition. A rule definition requires a WHEN clause.
Action:
Add a valid WHEN clause to the rule definition.
Reason:
A Format 1 expression was specified using an invalid qualifier. Valid qualifiers for this format are ANY and PRIMARY.
Action:
Correct the qualifier in the expression.
Reason:
A Format 3 expression was specified using an invalid qualifier. Valid qualifiers for this format are ANY and ONLY.
Action:
Correct the qualifier in the expression.
Reason:
A Format 2 expression was specified using an invalid operator. Valid operators for this format are EQUALS and CONTAINS.
Action:
Correct the operator in the expression.
Reason:
An expression was specified using an invalid qualifier. Valid qualifiers include ANY, ONLY, and PRIMARY.
Action:
Correct the qualifier in the expression.
Reason:
The current DEFINE statement contains a direct reference to the same category and entity name. That is, the statement is trying to define a category/entity relationship using that same category/entity as definition criteria.
Action:
Correct the recursive clause.
Reason:
A Format 1 expression contains an invalid component reference. Valid component references are as identified in the message.
Action:
Correct the component reference.
Reason:
An incomplete expression was encountered when a Boolean AND or OR expression is expected.
Action:
Correct the expression.
Reason:
After reading all rules, it was determined that references were made to categories and/or entities that do not exist.
Action:
Either correct the reference or add the appropriate definition.
Reason:
After reading all rules, it was determined that the initial category/entity contains an imbedded, recursive reference to the second category/entity. That is, a category/entity relationship was defined indirectly using this same category/entity as definition criteria.
Action:
Remove the recursive reference.
Reason:
After reading all rules, it was determined that the category/entity was defined but that no references exist.
Action:
None. This is a valid situation.
Reason:
An attempt to obtain storage failed.
Action:
Increase the region size on the JOB or EXEC card.
Reason:
A Format 3 expression contained a reference to an invalid category name. Category names cannot be greater than 8 characters
Action:
Correct the referenced category name.
Reason:
Comparison data exceeded the maximum allowable size for the field specified.
Action:
Change the comparison data identified so that it does not exceed the maximum length for the specified field.
Reason:
The data clause in a Format 2 expression contains an invalid column range specification. The column range must specify a beginning column number which is less than (or equal to) the ending column number.
Action:
Correct the column range specification.
Reason:
The data clause in a Format 2 expression contains an invalid column range specification. The column range must be at least large enough to contain the comparison data string. For example, if the string contains 10 characters, the column range must include at least 10 columns.
Action:
Correct the column range specification.
Reason:
The data clause in a Format 2 expression contains an invalid line range specification. The line range must specify a beginning line number which is less than (or equal to) the ending line number.
Action:
Correct the line range specification.
Reason:
The data clause in a Format 2 expression contains a confusing line range specification. The line range specified contains a mixture of relative line numbers and absolute line numbers.
Action:
None. This is a valid, although unusual, specification.
Reason:
The data clause in a Format 2 expression contains a confusing line range specification. The line range specified contains a mixture of relative line numbers and absolute line numbers.
Action:
None. This is a valid, although unusual, specification.
Reason:
The value indicated should be a valid numeric string, and may have a leading sign. The value specified is not a valid numeric string.
Action:
Correct the number.
Reason:
The value indicated should be a valid numeric string, and may have a leading sign. The value specified is not a valid numeric string.
Action:
Correct the number.
Reason:
The value indicated should be a valid numeric string, possibly containing a leading sign. The number may not exceed 15 digits.
Action:
Correct the number.
Reason:
The data clause in a Format 2 expression contains an inappropriate line range specification. The line range specified is a relative number, but is invalid unless contained within a WITH clause.
Action:
Correct the line range number.
Reason:
After reading all rules, it was determined that the category/entity was defined, but the only references that exist are directed to the category as a whole, not the entity.
Action:
None. This is a valid situation.
Reason:
After all rules were read, it was determined that this Type and processor group made no references to the specified category.
Action:
None. This is a valid situation.
Reason:
Informational message. This message appears in the Execution Report, and indicates that the rules data set was completely parsed.
Action:
None.
Reason:
Informational message. This message appears in the Execution Report, and indicates the next model definition input line to be read and parsed. Each line read is assigned a line number.
Action:
None.
Reason:
A data line was encountered prior to a model definition control card. This data card cannot be associated with any output DD statement.
Action:
Correct the positioning of this template data line.
Reason:
The DDname specified in this control card is not allocated. Output processing associated with this DD statement will not occur.
Action:
None. Make sure the DDname has been correctly specified.
Reason:
The DDname specified in this control card is invalid. DDnames cannot exceed 8 characters.
Action:
Correct the DDname specification.
Reason:
The DDname is a required operand on the output model definition control card.
Action:
Add the DDname specification.
Reason:
The DDname was specified and is followed by an unrecognizable operand. The only valid operand after the DDname is the COND clause.
Action:
Correct the control card specification.
Reason:
The COND clause is missing the operand value. The COND clause can be specified as one of the following:
Action:
Correct the COND clause specification.
Reason:
The COND clause contains an unrecognizable value. The COND clause can be specified as one of the following:
Action:
Correct the COND clause specification.
Reason:
An attempt to obtain storage failed.
Action:
Increase the region size on the JOB or EXEC card.
Reason:
Informational message. This message appears in the Final Request Interpretation section of both the Execution and Summary Reports. All applicable global parameters were merged with the request and each ANALYZE request is printed a final time. This message represents the beginning of an ANALYZE request that contains a single member specification, which may be wildcarded.
Action:
None.
Reason:
Informational message. This message appears in the Final Request Interpretation section of the Execution and Summary Reports. All applicable global parameters were merged with the request and each ANALYZE request is printed a final time. This message represents the beginning of an ANALYZE request that contains a member name range.
Action:
None.
Reason:
Informational message. This message appears in the Final Request Interpretation section of the Execution and Summary Reports. For each request, a complete set of symbolics is printed, along with their associated values. When more than one symbolic is associated with the request, message ANAL404I prints the additional symbolics.
Action:
None.
Reason:
Informational message. This message appears in the Final Request Interpretation section of the Execution and Summary Reports, and is a continuation of message ANAL403I.
Action:
None.
Reason:
Informational message. This message appears in the Final Request Interpretation section of the Execution and Summary Reports. For each request, a complete list of source (FROM) data sets is printed. When more than one source data set is associated with the request, message ANAL406I prints the additional data set names.
Action:
None.
Reason:
Informational message. This message appears in the Final Request Interpretation section of the Execution and Summary Reports, and is a continuation of message ANAL405I.
Action:
None.
Reason:
Informational message. This message appears in the Final Request Interpretation section of the Execution and Summary Reports. For each request, a complete list of output (USING) data sets is printed. When more than one output data set is associated with the request, message ANAL408I prints the additional data set names.
Action:
None.
Reason:
Informational message. This message appears in the Final Request Interpretation section of the Execution and Summary Reports, and is a continuation of message ANAL407I.
Action:
None.
Reason:
Informational message. This message appears in the Rule Interpretation section of the Execution Report, and represents a rule which is defining an entity within a category. The rule number matches the number assigned when the rule was originally read and parsed.
Action:
None.
Reason:
Informational message. This message appears in the Rule Interpretation section of the Execution Report, and represents a rule which is establishing a processor group for a Type. The rule number matches the number assigned when the rule was originally read and parsed.
Action:
None.
Reason:
Informational message. This message appears in the Rule Interpretation section of the Execution Report, and reflects the interpreted WHEN clause—with each operand, whether specified or assumed, explicitly stated. Each logical expression begins on a new line and may continue over several lines. All parentheses are shown.
Action:
None.
Reason:
Informational message. This message appears in the Execution Report, and indicates that the specified logical request will be processed.
Action:
None.
Reason:
Informational message. This message appears in the Execution Report, and indicates that member analysis is about to begin.
Action:
None.
Reason:
Informational message. This message appears in the Execution Report, and identifies the member being analyzed.
Action:
None.
FROM DSNAME 'data set-name'
Reason:
Informational message. This message appears in the Execution Report, and identifies the source (FROM) data set used for analyzing the member. If the member is found in multiple source data sets, this message identifies the member used for analysis. Message ANAL505I identifies the other source data sets in which the member is located.
Action:
None.
Reason:
Informational message. This message appears in the Execution Report, and identifies additional source data sets that contain occurrences of the member currently being analyzed. These occurrences are not used during the analysis. Message ANAL504I identifies the source data set which is used to analyze the member.
Action:
None.
Reason:
The member to be analyzed was found in at least one source (FROM) data set, but not found in any of the associated output (USING) data sets. Since the request contained a list of output data sets, an output member is required. The data sets examined for the output member are listed after this message, using message ANAL507I.
Action:
If the output member exists in an output data set, add that data set to the list of USING data sets. If no output exists for this member, place this member in a separate request with no USING data sets or run with source opt parameter.
Reason:
Informational message. This message appears in the Execution Report, immediately following message ANAL506E. This message identifies the output (USING) data sets searched for the member occurrence.
Action:
None. Refer to message ANAL506E.
Reason:
Informational message. This message appears in the Execution Report, and identifies the output (USING) data set used for analyzing the member. If the member is found in multiple output data sets, this message identifies the member used for analysis. Message ANAL509I identifies the other output data sets in which the member is located.
Action:
None.
Reason:
Informational message. This message appears in the Execution Report, and identifies additional output data sets that contain occurrences of the member currently being analyzed. These occurrences are not used during the analysis. Message ANAL508I identifies the output data set which is used to analyze the member.
Action:
None.
Reason:
Analysis for the member is terminated. This message follows message ANAL506E.
Action:
Refer to message ANAL506E.
Reason:
An attempt to obtain storage failed.
Action:
Increase the region size on the JOB or EXEC card.
Reason:
Allocation of the data set failed; the request is terminated.
Action:
Refer to the preceding allocation error messages.
Reason:
Validation of the data set failed; the request is terminated.
Action:
Refer to the validation error messages immediately preceding this message.
Reason:
Sequential data sets may not be used for analysis; the request is terminated.
Action:
Remove the sequential data set from the data set list.
Reason:
An attempt to read the data set directory failed; the request is terminated.
Action:
Refer to the error messages immediately preceding this message.
Reason:
Informational message. This message appears in the Execution Report when analysis for a member failed (message ANAL520E or ANAL522E). The member source is listed, using message ANAL529I, to assist in determining the reason behind the failure.
Action:
None.
Reason:
The user exit set a return code of 08, forcing member analysis to terminate.
Action:
None.
Reason:
Analysis of the member is unable to establish a Type and processor group combination. All information known about the member is formatted and printed following this message.
Action:
Review the module information and rule summary to determine whether any rule modifications should be performed. Make sure that the correct member source and outputs were used for the analysis.
Reason:
Informational message. This message appears in the Execution Report, and lists each Type and processor group that matched the member being analyzed.
Action:
None.
Reason:
Analysis of the member is unable to result in establishing a single Type and processor group combination. Several ANAL523I messages immediately follow this message, identifying the rules matched. All information known about the member is also formatted and printed.
Action:
Review the module information and rule summary to determine whether any rule modifications should be performed. Make sure that the correct member source and outputs were used for the analysis.
Reason:
Informational message. This message appears in the Execution Report, and lists each Type and processor group that matched the member being analyzed. Immediately follows message ANAL522E.
Action:
None.
Reason:
Informational message. This message appears in the Execution Report. After this message, you see a list of the load module attributes. This message immediately precedes message ANAL525I.
Action:
None.
Reason:
Informational message. This message appears in the Execution Report, and identifies all load module attributes. This message immediately follows message ANAL524I.
Action:
None.
Reason:
Informational message. This message appears in the Execution Report. After this message, you see a list of all CSECTs and translators. This message immediately precedes message ANAL527I.
Action:
None.
Reason:
Informational message. This message appears in the Execution Report, and identifies all CSECTs and translators. This message immediately follows message ANAL526I. The primary CSECT and translator is identified by an arrow.
Action:
None.
Reason:
Informational message. This message appears in the Execution Report, and identifies the linkage editor translator.
Action:
None.
Reason:
Informational message. This messages appears in the Execution Report, and lists the member source. This message immediately follows message ANAL518I.
Action:
None.
Reason:
Informational message. This message appears in the Execution Report. After this message, you see a list of all defined categories and entities. This message immediately precedes message ANAL531I.
Action:
None.
Reason:
Informational message. This message appears in the Execution Report, and identifies all defined categories and entities. There are three possible results: TRUE, FALSE, and UNRESOLVED. This message immediately follows message ANAL530I.
Action:
None.
Reason:
Informational message. This message appears in the Execution Report. After this message, you see a list of linkage editor identify data. This message immediately precedes messages ANAL533I and ANAL534I.
Action:
None.
Reason:
Informational message. This message appears in the Execution Report, and identifies all linkage editor identify data contained in a load module. This message immediately follows message ANAL532I and can be used in combination with message ANAL534I.
Action:
None.
Reason:
Informational message. This message appears in the Execution Report, and identifies all CSECT footprints contained in a load module. This message immediately follows message ANAL532I and can be used in combination with message ANAL533I.
Action:
None.
Reason:
This is a continuation of message ANAL534I.
Action:
None.
Reason:
Informational message. This message appears in the Execution Report. After this message, you see a list of all zap data. This message immediately precedes message ANAL537I.
Action:
None.
Reason:
Informational message. This message appears in the Execution Report, and identifies all zap data. This message immediately follows message ANAL536I.
Action:
None.
Reason:
An attempt to obtain storage failed.
Action:
Increase the region size on the JOB or EXEC card.
Reason:
This message is produced during the analysis phase, and indicates that no rules were established for any types.
Action:
Establish rules for types and groups.
Reason:
When loading the source member from the source data set, the member was not found. This should never occur since the member was validated prior to actually beginning member analysis.
Action:
Rerun the job.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|