A fix is available
APAR status
Closed as program error.
Error description
If a Type47 log record contains a UOR entry that has residual data, then the Batch Backout Utility may request previous log data sets while attempting to locate the start of the UOR.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All IMS V10 users * **************************************************************** * PROBLEM DESCRIPTION: The Batch Backout Utility may fail with * * message DFS2298A and RC64 even though * * it has all log data for every active * * application. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** DFSBACK0 assumed that every entry in a TYPE47 record represented an active work unit. When it found an entry for an inactive PST, it would pick up the residual UOR and find no subsequent log records for that PST. It would issue DFS2298A requesting earlier log data so that it would have the log data for this apparently active work unit.
Problem conclusion
AIDS: RIDS/UTIL RIDS/DBS DBS/UTIL DEP: NONE GEN: *** END IMS KEYWORDS *** DFSBACK0 has been modified to test each TYPE47 record entry for its status. Each entry contains a copy of PSTSWR so DFSBACK0 will test for PSTSWR2. Only entries for active PSTs will be recorded. It was also noted that DFSBACK0 assumed that a single TYPE47 record would contain all active PST information, but there may be a group of TYPE47 records if one record cannot contain enough entries. DFSBACK0 needed to be able to detect a complete TYPE47 record group. For this reason a new flag, CAPRCD1, was added to the TYPE47 record to indicate the first of a group of TYPE47 records. DFSRCP10 will set this flag in the first TYPE47 record and both DFSBACK0 and DFSULG60 will use it to verify that a complete active UOR list has been obtained.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PK42406
Reported component name
IMS V10
Reported component ID
5635A0100
Reported release
010
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2007-04-01
Closed date
2007-04-20
Last modified date
2008-04-30
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK24231
Modules/Macros
DFSBACK0 DFSLOG47 DFSRCP10 DFSULG60
Fix information
Fixed component name
IMS V10
Fixed component ID
5635A0100
Applicable component levels
R010 PSY UK24231
UP07/04/25 P F704
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCVRBJ","label":"System Services"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
30 April 2008