RPID output
The output of the RPID function is written to the RPTRPID DD.
If you do not specify the RPTRPID DD in the JCL, it is dynamically allocated to SYSOUT=*. You can write the RPID report output to SYSOUT or to a data set. The characteristics of the output are RECFM=FBA,LRECL=133. You can write the report to the IMS Tools Knowledge Base repository by specifying the REPORT(ITKBOUT(YES)) keyword and parameter.
The default is REPORT(ITKBOUT(YES)).
The RPID report consists of three report sections. The following figure shows the first two sections of the RPID report:
IMS DATABASE FACILITY EXTENDED FUNCTIONS V2.1.0 (5655-V86)
IMS DATABASE FACILITY EXTENDED FUNCTIONS RECOVERY POINT ID REPORT Run Time: 10/08/2021 19:26
********************************************************************************
-> Invocation Parameters:
********************************************************************************
Time Format : UTC
Time Range : 19.283 14:15:40.1+0000 to 21.364 14:15:40.1+0000
********************************************************************************
-> Database List
********************************************************************************
DATABASE AREA/PART DD TYPE DSN PART-TYPE OLR-PARTNER
-------------------------------------------------------------------------------------------------------------------------
DBOHIDK5 POHIDKA POHIDKAA HALD IMSTESTS.DBOHIDK5.A00001 DATA POHIDKAM
DBOHIDK5 POHIDKA POHIDKAB HALD IMSTESTS.DBOHIDK5.B00001 DATA POHIDKAN
DBOHIDK5 POHIDKA POHIDKAL HALD IMSTESTS.DBOHIDK5.L00001 ILE
DBOHIDK5 POHIDKA POHIDKAM HALD IMSTESTS.DBOHIDK5.M00001 DATA POHIDKAA
DBOHIDK5 POHIDKA POHIDKAN HALD IMSTESTS.DBOHIDK5.N00001 DATA POHIDKAB
DBOHIDK5 POHIDKA POHIDKAX HALD IMSTESTS.DBOHIDK5.X00001 INDEX POHIDKAY
DBOHIDK5 POHIDKA POHIDKAY HALD IMSTESTS.DBOHIDK5.Y00001 INDEX POHIDKAX
DBOHIDK5 POHIDKB POHIDKBA HALD IMSTESTS.DBOHIDK5.A00002 DATA POHIDKBM
DBOHIDK5 POHIDKB POHIDKBB HALD IMSTESTS.DBOHIDK5.B00002 DATA POHIDKBN
DBOHIDK5 POHIDKB POHIDKBL HALD IMSTESTS.DBOHIDK5.L00002 ILE
DBOHIDK5 POHIDKB POHIDKBM HALD IMSTESTS.DBOHIDK5.M00002 DATA POHIDKBA
DBOHIDK5 POHIDKB POHIDKBN HALD IMSTESTS.DBOHIDK5.N00002 DATA POHIDKBB
DBOHIDK5 POHIDKB POHIDKBX HALD IMSTESTS.DBOHIDK5.X00002 INDEX POHIDKBY
DBOHIDK5 POHIDKB POHIDKBY HALD IMSTESTS.DBOHIDK5.Y00002 INDEX POHIDKBX
DBOHIDK5 POHIDKC POHIDKCA HALD IMSTESTS.DBOHIDK5.A00003 DATA POHIDKCM
DBOHIDK5 POHIDKC POHIDKCB HALD IMSTESTS.DBOHIDK5.B00003 DATA POHIDKCN
DBOHIDK5 POHIDKC POHIDKCL HALD IMSTESTS.DBOHIDK5.L00003 ILE
DBOHIDK5 POHIDKC POHIDKCM HALD IMSTESTS.DBOHIDK5.M00003 DATA POHIDKCA
DBOHIDK5 POHIDKC POHIDKCN HALD IMSTESTS.DBOHIDK5.N00003 DATA POHIDKCB
DBOHIDK5 POHIDKC POHIDKCX HALD IMSTESTS.DBOHIDK5.X00003 INDEX POHIDKCY
DBOHIDK5 POHIDKC POHIDKCY HALD IMSTESTS.DBOHIDK5.Y00003 INDEX POHIDKCX
DBOHIDK5 POHIDKD POHIDKDA HALD IMSTESTS.DBOHIDK5.A00004 DATA POHIDKDM
DBOHIDK5 POHIDKD POHIDKDB HALD IMSTESTS.DBOHIDK5.B00004 DATA POHIDKDN
DBOHIDK5 POHIDKD POHIDKDL HALD IMSTESTS.DBOHIDK5.L00004 ILE
DBOHIDK5 POHIDKD POHIDKDM HALD IMSTESTS.DBOHIDK5.M00004 DATA POHIDKDA
DBOHIDK5 POHIDKD POHIDKDN HALD IMSTESTS.DBOHIDK5.N00004 DATA POHIDKDB
DBOHIDK5 POHIDKD POHIDKDX HALD IMSTESTS.DBOHIDK5.X00004 INDEX POHIDKDY
DBOHIDK5 POHIDKD POHIDKDY HALD IMSTESTS.DBOHIDK5.Y00004 INDEX POHIDKDX
DBOVLFPC VLOSAM01 VLOSAM01 FF DBOVLFPC.XABCD01O
DBVHDJ05 PVHDJ5A PVHDJ5AA HALD IMSTESTS.DBVHDJ05.A00001 DATA
DBVHDJ05 PVHDJ5A PVHDJ5AB HALD IMSTESTS.DBVHDJ05.B00001 DATA
DBVHDJ05 PVHDJ5A PVHDJ5AL HALD IMSTESTS.DBVHDJ05.L00001 ILE
DBVHDJ05 PVHDJ5B PVHDJ5BA HALD IMSTESTS.DBVHDJ05.A00002 DATA
DBVHDJ05 PVHDJ5B PVHDJ5BB HALD IMSTESTS.DBVHDJ05.B00002 DATA
DBVHDJ05 PVHDJ5B PVHDJ5BL HALD IMSTESTS.DBVHDJ05.L00002 ILE
DBVHDJ05 PVHDJ5C PVHDJ5CA HALD IMSTESTS.DBVHDJ05.A00003 DATA
DBVHDJ05 PVHDJ5C PVHDJ5CB HALD IMSTESTS.DBVHDJ05.B00003 DATA
DBVHDJ05 PVHDJ5C PVHDJ5CL HALD IMSTESTS.DBVHDJ05.L00003 ILE
DBVHDJ05 PVHDJ5D PVHDJ5DA HALD IMSTESTS.DBVHDJ05.A00004 DATA
DBVHDJ05 PVHDJ5D PVHDJ5DB HALD IMSTESTS.DBVHDJ05.B00004 DATA
DBVHDJ05 PVHDJ5D PVHDJ5DL HALD IMSTESTS.DBVHDJ05.L00004 ILE
DEDBDD01 DD01AR0 DD01AR0 FP DD01AR0
DEDBJN24 DB24A000 DB24A000 FP DB24A000
DEDBJN24 DB24A001 DB24A001 FP DB24A001
DEDBJN24 DB24A239 DB24A239 FP DB24A239
DHVNTZ02 HIDAM HIDAM FF DHVNTZ02.FKXXI01E
DHVNTZ02 HIDAM2 HIDAM2 FF DHVNTZ02.FKXXI02E
DIVNTZ02 DBHVSAM1 DBHVSAM1 FF DIVNTZ02.FJXXS01K
DIVNTZ02 DBHVSAM2 DBHVSAM2 FF DIVNTZ02.FJXXS01E
DXVNTZ02 XDLBT04I XDLBT04I FF DXVNTZ02.FKXXSIXK
D2XHDJ05 P2XHDJA P2XHDJAA HALD IMSTESTS.D2XHDJ05.A00001 DATA
D2XHIDK5 P2XIDKA P2XIDKAA HALD IMSTESTS.D2XHIDK5.A00001 DATA
The RPID report contains the following sections:
- Invocation Parameters
- This section of the report shows the options that RPID used for
its processing.
- Time Format
- This field indicates whether the timestamps that are displayed in the report are in Local or UTC (Coordinated Universal Time) format. Specify this parameter on the REPORT keyword by using the TIMEFMT() parameter.
- Time Range
- This field displays the formatted time range that you specified on the RPID RANGE() parameter.
- Database List
- This section of the report shows the databases that were processed
in this RPID run.
- DATABASE
- This column specifies the name of the database that was processed.
- AREA/PART
- This column specifies the area name for fast path databases or the partition name for HALDB databases that were processed. This column is blank for full function databases.
- DD
- This column specifies the DD name that is associated with this area, partition, or full function database.
- TYPE
- This column specifies the type of database that was processed. Valid values are FF for full function databases, FP for fast path areas, and HALD for HALDB partitions.
- DSN
- This column specifies the data set name that is associated with this area, partition, or full function database.
- PART-TYPE
- For HALDB partitions, this column specifies the type of data set that was processed. Valid values are INDEX for the index portion of the HALDB, ILE for the index list element (or ILDS) portion of the HALDB, or DATA for the data portion of the HALDB.
- OLR-PARTNER
- For HALDB partitions that are IMS Online Reorganization (OLR) capable, this column specifies the OLR partner DD name that is associated with the partition.
- Recovery Time Spans and Points for Time Stamp Recovery
- The next section shows the following information:
- Recovery Time Spans that are common to all database entries
- Recovery Time Spans for Individual database entries
- Recovery Points (Utility End Times) for individual database entries
********************************************************************************
-> Recovery Time Spans and Points for Time Stamp Recovery
********************************************************************************
--> Recovery Time Spans Common to All Entries in the DBLIST:
19.283 14:15:40.100000+0000 to 21.139 10:54:27.712196+0000
21.139 11:10:19.946777+0000 to 21.364 14:15:40.100000+0000
--> Recovery Time Spans for Individual Entries in the DBLIST:
DBD=POHIDKA DDN=POHIDKAN DB_Type=HALDB-Part Partner_DD=POHIDKAB Master_DB=DBOHIDK5
19.283 14:15:40.100000+0000 to 21.139 10:59:31.214366+0000 Last_IMSID=n/a
21.139 11:00:17.329938+0000 to 21.139 11:00:38.972179+0000 Last_IMSID=IMS1
21.139 11:10:19.562406+0000 to 21.364 14:15:40.100000+0000 Last_IMSID=IMS1
DBD=POHIDKA DDN=POHIDKAM DB_Type=HALDB-Part Partner_DD=POHIDKAA Master_DB=DBOHIDK5
19.283 14:15:40.100000+0000 to 21.139 10:59:31.192224+0000 Last_IMSID=n/a
21.139 11:00:17.329938+0000 to 21.139 11:00:38.951749+0000 Last_IMSID=IMS1
21.139 11:10:19.478393+0000 to 21.364 14:15:40.100000+0000 Last_IMSID=IMS1
DBD=POHIDKA DDN=POHIDKAB DB_Type=HALDB-Part Partner_DD=POHIDKAN Master_DB=DBOHIDK5
19.283 14:15:40.100000+0000 to 21.139 10:59:31.214366+0000 Last_IMSID=n/a
21.139 11:00:17.329938+0000 to 21.139 11:00:38.972179+0000 Last_IMSID=IMS1
21.139 11:10:19.562406+0000 to 21.364 14:15:40.100000+0000 Last_IMSID=IMS1
DBD=POHIDKA DDN=POHIDKAA DB_Type=HALDB-Part Partner_DD=POHIDKAM Master_DB=DBOHIDK5
19.283 14:15:40.100000+0000 to 21.139 10:59:31.192224+0000 Last_IMSID=n/a
21.139 11:00:17.329938+0000 to 21.139 11:00:38.951749+0000 Last_IMSID=IMS1
21.139 11:10:19.478393+0000 to 21.364 14:15:40.100000+0000 Last_IMSID=IMS1
DBD=POHIDKB DDN=POHIDKBN DB_Type=HALDB-Part Partner_DD=POHIDKBB Master_DB=DBOHIDK5
19.283 14:15:40.100000+0000 to 21.139 10:59:23.973009+0000 Last_IMSID=n/a
21.139 11:00:17.329938+0000 to 21.139 11:00:42.276666+0000 Last_IMSID=IMS1
21.139 11:10:19.690115+0000 to 21.364 14:15:40.100000+0000 Last_IMSID=IMS1
--> Recovery Points (Utility End Times) for Individual Entries in the DBLIST:
DBD=POHIDKA DDN=POHIDKAN DB_Type=HALDB-Part Partner_DD=POHIDKAB Master_DB=DBOHIDK5
DBD=POHIDKA DDN=POHIDKAM DB_Type=HALDB-Part Partner_DD=POHIDKAA Master_DB=DBOHIDK5
DBD=POHIDKA DDN=POHIDKAB DB_Type=HALDB-Part Partner_DD=POHIDKAN Master_DB=DBOHIDK5
21.139 10:58:40.700316+0000 -- Batch-IC
21.139 11:11:19.946777+0000 -- Batch-IC
21.139 11:11:32.500000+0000 -- 21.139 11:11:32.500000+0000 Full-Recovery
21.139 11:12:26.800000+0000 -- 21.139 11:12:26.800000+0000 Full-Recovery
DBD=POHIDKA DDN=POHIDKAA DB_Type=HALDB-Part Partner_DD=POHIDKAM Master_DB=DBOHIDK5
21.139 10:58:39.740236+0000 -- 00.000 00:00:00.000000+0000 Batch-IC
21.139 11:11:19.946777+0000 -- Batch-IC
21.139 11:11:32.500000+0000 -- 21.139 11:11:32.500000+0000 Full-Recovery
21.139 11:12:26.800000+0000 -- 21.139 11:12:26.800000+0000 Full-Recovery
21.130 11:12:26.812300+0000 -- 21.130 11:12:26.800000+0000 Concurrent-IC
DBD=POHIDKB DDN=POHIDKBN DB_Type=HALDB-Part Partner_DD=POHIDKBB Master_DB=DBOHIDK5
DBD=POHIDKB DDN=POHIDKBM DB_Type=HALDB-Part Partner_DD=POHIDKBA Master_DB=DBOHIDK5
DBD=POHIDKB DDN=POHIDKBB DB_Type=HALDB-Part Partner_DD=POHIDKBN Master_DB=DBOHIDK5
21.139 10:58:42.471480+0000 -- 00.000 00:00:00.000000+0000 Batch-IC
21.139 11:11:32.500000+0000 -- 21.139 11:11:32.500000+0000 Full-Recovery Alloc-Overlap
21.139 11:12:26.800000+0000 -- 21.139 11:12:26.800000+0000 Full-Recovery Alloc-Overlap
DBD=POHIDKB DDN=POHIDKBA DB_Type=HALDB-Part Partner_DD=POHIDKBM Master_DB=DBOHIDK5
21.139 10:58:41.545885+0000 -- 00.000 00:00:00.000000+0000 Batch-IC
21.139 11:11:32.500000+0000 -- 21.139 11:11:32.500000+0000 Full-Recovery
21.139 11:12:26.800000+0000 -- 21.139 11:12:26.800000+0000 Full-Recovery
DBD=POHIDKC DDN=POHIDKCN DB_Type=HALDB-Part Partner_DD=POHIDKCB Master_DB=DBOHIDK5
DBD=POHIDKC DDN=POHIDKCM DB_Type=HALDB-Part Partner_DD=POHIDKCA Master_DB=DBOHIDK5
The Recovery Time Spans and Points for Time Stamp Recovery report contains the following sections:
- Recovery Time Spans Common to All Entries in the DBLIST:
- This section of the report lists all of the recovery time spans
(RTSs) that are common for all of the databases in the DBLIST. The
RTSs that are shown are based on allocation ranges bounded by the
RANGE parameter input. If more than one common RTS is found, each
one is listed. If no common RTS was found, no lines are printed under
this heading. Each entry shows the beginning and ending timestamp
that is associated with the common recovery time span.
When you review an RTS, any timestamp can be used on a Time Stamp Recovery job for recovering any and all of the databases on the DBLIST, including the beginning and the ending of the RTS. When you review this information, if it appears that the RTSs are more limited than what you expected, you can find the reasons for the limitation in the Utility End Times section of the report. For example, if any of the databases were reorganized and no image copy was taken after the reorganization, the end of the RTS will be the time immediately before the reorganization job started.
- Recovery Time Spans for Individual Entries in the DBLIST:
- This section of the report lists the RTSs for individual databases
in the DBLIST, which are based on allocation ranges bounded by the
RANGE parameter input. The last IMSID to allocate the database just
before the beginning of the RTS is also listed.
If you recognize the Last_IMSID field as a DL/I batch job, the time to the left of the two dashes (--) is the log start time for the batch job, and the time to the right of the two dashes (--) is the log end time for the batch job.
If the database is a HALDB partition, the partner partition, and HALDB master database name are listed.
Any timestamp that is bounded by and includes the beginning and ending timestamps of the RTS is a valid recovery TSR time for the individual database. When RPID calculates the Common Recovery Time Spans, it assumes that if one of the HALDB partners is allocated the other HALDB partner is also allocated. And so, a TSR that is using a recovery point can recover both of the partner partitions.
- Recovery Points (Utility End Times) for Individual Entries in the DBLIST:
- This section of the report lists the subsequent recovery points
(that is, the utility run and end times within the RANGE specification
for individual entries in the DBLIST).
The following table lists the utility information that can be displayed:
| What is displayed in the report | Meaning |
|---|---|
| Batch-IC | Batch image copy |
| Concurrent-IC | Concurrent image copy |
| User-IC | User image copy |
| SMS-IC-DB-Exclusive | SMS image copy – database exclusive |
| SMS-IC-DB-Shared | SMS image copy – database shared |
| Full-Recovery | Full recovery |
| Partial-Recovery | Partial recovery |
| Offlin-REORG+SubseqIC | Offline reorganization and subsequent image copy |
| Offlin-REORG-SubseqIC | Offline reorganization and no subsequent image copy |
| Online-REORG+IC | Online reorganization and image copy |
| Online-REORG-IC | Online reorganization and no subsequent image copy |
| Full-Rcvr+SubseqIC | Full recovery and subsequent image copy |
| Full-Rcvr-SubseqIC | Full recovery and no subsequent image copy |
| Partial-Rcvr+SubseqIC | Partial recovery and subsequent image copy |
| Partial-Rcvr-SubseqIC | Partial recovery and no subsequent image copy |
| Complete-Change-Accum | Complete change accumulation |
RPID ISPF interface for viewing RPID reports and generating JCL statements
The RPID ISPF interface plays an important role for viewing RPID reports and generating JCL for a recovery. The RPID ISPF interface allows you to easily select database components and recovery times. After specifying database components and recovery times, you can use the RPID ISPF interface to generate IMS Database Recovery Facility control statements. For viewing RPID reports and generating control statements, you must have an understanding of the IMS Recover Point Identification ISPF interface.