|
|
|
Messages issued by the Report Writer begin with the letters ERPT. Some Report Writer messages identify syntax errors in your history reporting job stream. These messages appear in the output from the Report Writer. Such messages identify syntax errors in the following way:
Syntax errors identified by messages of type E cause the Report Writer to terminate.
The following example shows how the Report Writer identifies a syntax error:
TAB DATE MVS CPU %BUSY AND,
MVS JOB CONT
$
ERPT204E ILLEGAL VARIABLE
END
RUN
ERPT202E 1 SYNTAX ERRORS ENCOUNTERED
ERPT229I RUN TERMINATED FOR ABOVE REASONS
In this example, MVS JOB CONT is identified as an illegal variable. The Report Writer terminates.
The following are the messages issued by the Report Writer.
Reason:
The Report Writer has begun or has completed running the reports you requested.
Indicates either INITIATED or COMPLETED.
Provides the version, release, and maintenance level of the Report Writer.
Provides the date and time at which the Report Writer has begun or has completed running the reports.
Action:
None.
Reason:
The program identified by program requested storage for the Report Writer to run, but not enough virtual storage is available.
Provides the offset within the program that requested storage.
Action:
Do one or more of the following:
Note: The need for virtual memory by the Report Writer is nearly proportional to the number of plot lines that are to print.
Reason:
The Report Writer has encountered n syntax errors.
Specifies the number of syntax errors.
Action:
Correct the syntax errors and resubmit the job.
Reason:
This message identifies a syntax error. The variable above the dollar sign ($) is invalid.
Action:
Correct the invalid variable.
Reason:
This message identifies a syntax error. The control statement above the dollar sign ($) contains an invalid command.
Action:
Correct the invalid command.
Reason:
This message identifies a syntax error. The command above the dollar sign ($) is a duplicate. You can use some commands only once in any given report. For instance, only one FROM or TO command can be used in a single report.
Action:
Remove the duplicate command.
Reason:
The Report Writer did not find enough operands to produce a report. The continuation character could be missing at the end of a line. The continuation comma tells the Report Writer that more operands follow on the next line. A dollar sign ($) underscores the last operand that the Report Writer found.
Action:
Either add more operands or place a comma after the last character on the line.
Reason:
This message identifies a syntax error. The operand above the dollar sign ($) is incomplete or invalid.
Action:
Correct the partial or invalid operand.
Reason:
This message identifies a syntax error. You exceeded the maximum number of operands the current command can accept. The operand above the dollar sign ($) is the first operand to exceed the maximum number.
Action:
Delete the excessive operands and rerun the report.
Explanation:
This message follows other syntax error messages and indicates that the current operand has been discarded. The Report Writer continues to look at the remainder of the operands to finish the error check and then terminates processing.
Action:
Correct the syntax error.
Explanation:
This message identifies a syntax error. You omitted a comma or parenthesis at the location above the dollar sign ($).
Action:
Insert a comma or a parenthesis.
Reason:
The EACH time value is greater than the PERIOD time value.
The EACH command defines the timespan represented by each detail line The PERIOD command defines the timespan covered by a Report Writer summary. Therefore, the EACH time value cannot be greater than the PERIOD time value.
Action:
Change the EACH or PERIOD value to correct the error. The default for the EACH command is one day.
Reason:
This message identifies a syntax error. You tried to issue a RUN command before issuing an END command to end the last report. A dollar sign ($) underscores the RUN command that you issued out of sequence.
Action:
Enter an END command to end the last report before using the RUN command.
Reason:
This message identifies a syntax error. The Report Writer ignored the current command and all of its operands. This error message follows other error messages that identify the specific problem. A dollar sign ($) underscores the part of the command that generated the error.
Action:
Correct the command and resubmit the report.
Reason:
An END command signaled the end of a report, but no report existed.
Action:
Specify a report before you issue the END command.
Reason:
The END command has signaled the end of a report, but the Report Writer did not find a primary command to begin the report.
Action:
Specify a primary command for the report.
Reason:
An internal error occurred.
Identifies the address where the error occurred.
Specifies the name of the CSECT.
Specifies is the offset into the CSECT.
Action:
Collect as much information about the problem as possible, including the listing of the run in which this error occurred and then contact Technical Support.
Reason:
End-of-file was reached, but the required END command was missing for the last report.
Action:
End this report and all other reports with the END command.
Reason:
This message occurs during report writing rather than during syntax checking. The Report Writer could find no data in the log file to match the following items you specified: the times, the identifiers, or the variables with non-zero activity.
The Report Writer considers zero activity for a given variable to be no activity.
For example, you requested a report on the variable TRANSACTION WAITS, and no waits existed for any transactions during the time you specified. You would then receive this message.
Action:
Either modify your commands to change the time boundaries for the report or make the identifier restrictions more general.
Reason:
You tried to execute the Report Writer but did not specify any report commands.
Action:
Specify one or more report commands.
Reason:
Because of the errors listed above this message, your reports were not printed.
Action:
Review the messages preceding this message and then take the appropriate action. If you need help, contact Technical Support.
Reason:
The Report Writer expects the date format identified by format, but your report includes dates in another format.
Specified as either dd/mm/yy or mm/dd/yy (where dd = day, mm = month, and yy = year).
Action:
Alter your dates to conform to the format the Report Writer expects. You can use the DATEFRMT operand of the OPTION command to specify the type of date format you want.
Reason:
This message identifies a syntax error. An ID option either has no identifiers or has no left parenthesis before its identifiers. The format for ID options requiring identifiers is a left parenthesis followed by one or more identifiers separated by commas, and a closing right parenthesis. One or more identifiers or a left parenthesis appear at the location above the dollar sign ($).
Action:
Supply the missing identifiers or parentheses.
Reason:
One of the following has occurred:
Action:
Submit only one report type for each END command, or include a SCALE operand when you use the EACH RECORD command with the HPLOT command.
Reason:
A QUIT command was encountered. The QUIT command stops syntax checking and halts the Report Writer without reading another command.
Action:
No action is required.
Reason:
The Report Writer terminated for the reasons listed above this message.
Action:
Correct the errors and resubmit the report.
Reason:
The Report Writer successfully completed the reports you requested.
Action:
None.
Reason:
The Report Writer finished parsing your commands and found no errors.
Action:
None.
Reason:
The Report Writer successfully opened the file identified by filename.
Action:
None.
Reason:
The Report Writer successfully closed the file identified by filename.
Action:
None.
Reason:
This message identifies a syntax error. The number of left parentheses in your job stream does not match the number of right parentheses. A parenthesis appears at the location above the dollar sign ($).
Action:
Balance the number of left and right parentheses.
Reason:
You are constructing a table with the TAB command, but the Report Writer has run out of space on the page for the columns you are requesting.
Action:
Remove some of the variables, decrease the size of the headings you selected with the HDR1 and HDR2 commands, or use the FORMAT variable option to reduce the number of columns used by each variable.
Reason:
The Report Writer did not find a variable after the AND operand. The cause of this error could be the lack of a continuation comma after the AND operand.
Action:
Either add more variables or place a comma after the AND operand.
Reason:
The Report Writer generates the statements that follow this message.
Action:
None.
Reason:
The cause can be either of the following:
Action:
Change the order of your variables or specify only variables that are logically related.
Reason:
An attempt to access the file identified by filename failed.
The VSAM request type.
Message ERPT240E follows this message.
Action:
Use the information in message ERPT240E to determine the problem.
Reason:
Your attempt to access the file identified by filename in message ERPT239E failed. code1 is the return code from register 15, and code2 is the error code.
Action:
Use the codes in the message to correct the error. For the meanings of these codes, see the IBM documentation containing VSAM messages and codes.
Reason:
The record that the Report Writer is currently processing is outside the limits set by the report parameters. The record is ignored.
Action:
None.
Reason:
The record read by the Report Writer has an invalid record format.
Action:
Verify that the records you have instructed the Report Writer to read have been correctly identified to the Report Writer. Verify that the associated INPUT commands are correct.
Reason:
This message identifies a syntax error. The identifier above the dollar sign ($) is invalid.
Action:
Correct the invalid identifier.
Reason:
An invalid date format was detected.
Action:
Correct the format of the DATEFRMT operand of the OPTION command so that it is either mm/dd/yy or dd/mm/yy.
Reason:
You have included more than one report with a flashback report.
Action:
Run each flashback report by itself.
Reason:
The number of input records read within the FROM/TO range exceeds the maximum value you set in the COUNT command. The reports you requested were printed, but the records exceeding the maximum value were ignored.
Action:
None.
Reason:
The Report Writer read a total of nnnnnn input records.
Action:
None.
Reason:
Provides the total number of input records read that passed the minimum FROM and maximum TO date and time criteria.
Action:
None.
Reason:
Provides the total number of input records read that passed all selection and range criteria.
Action:
None.
Reason:
An attempt to load the command table identified by table did not complete successfully. Processing of reports terminates immediately.
Provides the return code of the load request.
Action:
Record the return code and then take appropriate action. If you need help, contact Technical Support.
Reason:
End-of-file was reached for SYSIPT, and no RUN command was encountered.
Action:
Include the RUN command and resubmit the report.
Reason:
The Report Writer encountered one or more END commands, but did not find a following RUN command. The Report Writer terminates.
Action:
Add a RUN command after the last END command and resubmit the job.
Reason:
An error was detected in an internal program name.
Provides the name of a CSECT.
Action:
Contact Technical Support.
Reason:
The EACH and PERIOD commands were used with the VPLOT command. The quotient of the PERIOD value divided by the EACH value must be less than or equal to the number of available plot columns. The Report Writer found that the resulting VPLOT report does not meet this criterion.
Action:
Increase the EACH value, decrease the PERIOD value, or alter both values. Alter the values so that the quotient of these values is less than or equal to the number of columns your report has available. The default number of columns is 110.
Reason:
The Report Writer detected an invalid record type. type1 is the product type and type2 is the hexadecimal record type.
Action:
See whether you have an invalid or corrupt data file.
Reason:
The Report Writer allocated mmmmmK bytes of storage to report number nn.
The cause could be either of the following reasons:
If your storage is depleted, one of these messages appears for every report you tried to run, following message ERPT201, MAIN STORAGE EXHAUSTED.
Action:
None.
Reason:
The Report Writer finished reading input from the previous tape file and is asking you to mount the tape containing the next input file.
Provides the name of the next input file.
The Report Writer requests the file names in the same order that you specified them with the INPUT command.
Action:
No action is required.
Reason:
An attempt to load the message table identified by table did not complete successfully. Processing of reports terminates immediately.
Provides the return code of the load request.
Action:
Record the return code and then take appropriate action. If you need help, contact Technical Support.
Reason:
An attempt to load the user exit identified by name did not complete successfully.
Provides the return code of the load request.
Action:
Record the return code and then take appropriate action. If you need help, contact Technical Support.
Reason:
nnnnK of virtual storage is available at the end of the reporting process. This message is displayed if you specify the command OPTION(STORSTAT=YES).
Action:
None.
Reason:
You asked to see the report status by specifying the command OPTION(RPTSTAT=YES).
Provides the current input record count. The current input record is date-stamped mm/dd/yy and time-stamped hh:mm:ss.
Action:
No action is required.
Reason:
An attempt to load the module identified by module did not complete successfully. Processing of reports terminates immediately.
Provides the return code of the load request.
Action:
Record the return code and then take appropriate action. If you need help, contact Technical Support.
Reason:
The Report Writer requested an unknown or invalid internal utility.
Provides the name of the utility requested.
Action:
Contact Technical Support.
Reason:
The Report Writer attempted to read the flashback file (EXPxxxx) but failed because it could not locate the flashback control record.
Action:
Change the DLBL statement to point to a valid flashback file.
Reason:
The Report Writer successfully read nnnnnnnn physical records from the file identified by filename.
Action:
No action is required.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |