A fix is available
APAR status
Closed as program error.
Error description
The customer was running Generation Data Group (GDG) data sets and forgot to change the GDG number from (+1) to (0) for the XRST job pointed to an empty output data set. The XRST job ended normally but some records were missing. If the XRST job is on an empty output data set, it will issue a message DFS1000I IMS111 ABEND U0102 MODULE=DFSZD210 LABEL=C4C30001 R14=800208CA
Local fix
Description During XRST processing, GSAM determined that the output data set being repositioned was empty. To successfully resubmit the XRST job: 1. Issue a /STA command for the PSB stopped by the abending job. 2. Correct the DD statement for the GSAM output data set to point to the same data set in use when the abend requiring an XRST occurred. 3. Resubmit the XRST job.
Problem summary
**************************************************************** * USERS AFFECTED: All IMS V10 users of GSAM XRST (Extended * * Restart) with GDG (Generation Data Group) * * data sets. * **************************************************************** * PROBLEM DESCRIPTION: Data loss occurs when pointing to an * * empty GSAM output dataset during an * * XRST call. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** Currently, GSAM expects the output data set for XRST to be the same data set as the one created by the abending job, and will allow XRST to complete successfully with a valid empty data set. Data loss can occur when a user accidentally points to an empty data set that was not created by the abending job. This situation can occur when the user is running with GDG data sets and does not change the GDG number from (+1) to (0) in the XRST job. In this situation, XRST will be performed with a new (empty) data set. After the XRST call all subsequent ISRT (insert) calls will result in an I/O error trying to reposition to an empty data set. If this is not recognized by the user immediately after the job ends and subsequent jobs are run, then data loss can occur. This APAR will recognize this error condition and the XRST job will be abended and the problem clearly identified.
Problem conclusion
GEN: KEYWORDS: *** END IMS KEYWORDS *** THE FOLLOWING TEXT DESCRIBES THE DOC CHANGES: Messages and Codes Reference, Volume 1: DFS Messages DFS1000I message add DFSZDC00 under section Module: Messages and Codes Reference, Volume 3: IMS Abend Codes In the U0102 abend section, following the 'For DFSZSR10' table, the following table should be added: For DFSZDC00: Key Label Description Reg2=C4C30001 C4C30001 During XRST processing, GSAM determined that the output data set being repositioned was empty. To successfully resubmit the XRST job: 1. Issue a /STA command for the PSB stopped by the abending job. 2. Correct the DD statement for the GSAM output data set to point to the same data set in use when the abend requiring an XRST occurred. 3. Resubmit the XRST job. NOTE: Probably the most common cause of this problem is associated with the use of Generation Data Group (GDG) data sets. After the initial job fails, the XRST job is submitted, but the user fails to change the generation number on the GSAM output data set from (+1) to (0). As a result, XRST repositioning is performed on a new (+1) data set, not the current(0) copy of the data set (at abend time). CAUTION: If an XRST job is executed specifying the wrong restart data set, XRST completes successfully but valid data is overwritten. ************ * DFSZDC00 * ************ Code was added to GSAM XRST logic to check for an empty GSAM output data set. If the empty data set is not a valid condition (the abending job had opened the output data set but had never inserted any segments into it), then the DFS1000I message will be issued and the job will abend with a U0102 abend, reason code x'C4C30001'. This condition is detected when GBCRTNCD is equal to x'44'. ************ * DFSZD210 * ************ Obtain the DSAB, DSCB and JFCB blocks in the PNTRTN routine to check if the data set is empty during an XRST call. When this condition is detected an internal GSAM return code, GBCRTNCD, is set to x'44' to indicate that an error condition exists. GBBLKRF0 flag is set in routine GUREQ during an XRST call when GBBLKREF is equal to zero. This flag indicates a valid case of an empty data set during an XRST call. An addressability issue has also been corrected in this module. Relative branching is used to solve this issue. ******** * IGLI * ******** Two flags were added in IGLI macro in the GB DSECT. One flag represents a valid case of an empty data set during an XRST call. This flag name is GBBLKRF0 and equates to a x'02' in the GBDEVT1 byte. The second flag represents an invalid case of an empty data set during an XRST call. This flag name is GBCRTN44 and equates to a x'44' in the GBCRTNCD byte.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PK89932
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
2009-06-26
Closed date
2010-02-25
Last modified date
2010-04-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK54697
Modules/Macros
DFSZDC00 DFSZD210 IGLI
| GC18971402 | GC18971202 |
Fix information
Fixed component name
IMS V10
Fixed component ID
5635A0100
Applicable component levels
R010 PSY UK54697
UP10/03/04 P F003
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:
03 April 2010