RPID report initialization errors
If the RPID report fails validation when you attempt to start the RPID ISPF interface with the RPID report, an error message is issued and the RPID ISPF interface does not start.
The following sections describe initialization errors that might cause the RPID report validation to fail.
Physical file characteristics
- Short message: Unsupported LRECL
- Long message: File being processed has Data_Width=nnn. Data_Width greater than 256 is not supported.
Make sure that the pre-allocated data set in which you save the RPID report is set to a data width of up to 256 bytes (LRECL=256 for FB, or LRECL=260 for VB), and then generate another RPID report. If the problem persists, contact IBM® Software Support.
Title, section, and page headings
The RPID ISPF interface processes and presents composite information that is extracted from the RPID report sections with the following title and headers.
IMS DATABASE FACILITY EXTENDED FUNCTIONS RECOVERY POINT ID REPORT
-> Invocation Parameters:
--> Recovery Time Spans Common to All Entries in the DBLIST:
--> Recovery Time Spans for Individual Entries in the DBLIST:
--> Recovery Points (Utility End Times) for Individual Entries in the DBLIST:
If the title or headings cannot be located in the report that is being processed, the RPID interface stops, and an ISPF error message is displayed. To avoid this error, rerun the RPID function to generate another RPID report, and do not delete any titles or headers from the report.
Common time spans
The RPID ISPF interface examines the common time spans that are defined in the RPID report. If no common time spans are contained in the report, the following panel is displayed.
No Common Time Spans
There are no Common Time Spans in the current
RPID report.
The report was run on 02/08/2021 at 19:26.
Press ENTER to continue without Common Time Spans.
Press END to exit.
If you want to generate a common time span, use the Recovery Point Creation function.