IBM Support

PI50149: EXPORT DEFN TARGET(REPO) COMMAND NOT SUCCESSFUL BUT RETURNS COMPLETION CODE (CC) 0

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A EXPORT DEFN TARGET(REPO) command was issued while an EXPORT
    command was already in progress.  This occurred while running
    two Batch SPOC jobs at the same time.  It could occur whenever
    a second EXPORT command is issued before the first EXPORT
    command has completed.
    .
    The unsuccessful EXPORT command returns information similar to
    this:
    .
    Return code . . . : 0200000C
    Reason code . . . : 00003008
    Reason text . . . : None of the clients were successful.
    Command master. . : IMS1
    .
                 Return     Reason
     MbrName     Code       Code       Reason text
     --------    ------     ------     -----------
     IMS1        0000000C   00003004   No requests were successful
    .
    MbrName  Messages
    -------- -----------------------
    IMS1     DFS3407E EXPORT COMMAND COMPLETE FOR NONE,
                      RC=0300000C, RSN=00001504
    .
    Response for: EXPORT DEFN TARGET(REPO) TYPE(PGM) NAME(PGM1)
    Name     Type     MbrName    CC
    ---------------------------------------
    IMS1     LIST     IMS1        0
    PGM1     PGM      IMS1        0
    .
    This shows CC 0 even though previous codes indicate the EXPORT
    was not successful.  The CC should have been set to 1D4 and the
    response output should look like this:
    .
    Response for: EXPORT DEFN TARGET(REPO) TYPE(PGM) NAME(PGM1)
    Name     Type     MbrName    CC CCText
    -------------------------------------------------------
    IMS1     LIST     IMS1      1D0 NOT DONE DUE TO ERROR
    PGM1     PGM      IMS1      1D4 REPOSITORY MEMBER IN USE
    

Local fix

  • Do not issue a second EXPORT command until the first command
    completes.
    .
    Do not run two Batch SPOC jobs at the same time.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMS V13 users of                         *
    *                 EXPORT DEFN TARGET(REPO) command.            *
    ****************************************************************
    * PROBLEM DESCRIPTION: EXPORT DEFN TARGET(REPO) not            *
    *                      successful but returns completion       *
    *                      code (CC) 0.                            *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    Completion code 1D4 REPOSITORY MEMBER IN USE error is not
    returned when EXPORT DEFN TARGET(REPO) command is issued.
    EXPORT DEFN TARGET(REPO) command is not successful but the
    error cc response returns completion code (cc) 0.
    The code in module CSLRRU10 fails to populate the response
    cc with the error reason code returned from EXPORT request.
    This type of error occurs when:
    Two or more units of work try to access the
    same repository member. For example, the EXP DEFN TARGET(REPO)
    NAME(PGM1) command is sent to IMS1 and IMS2 at the same time.
    IMS1 makes a request to RM to update the definition for PGM1.
    RM gets the request, starts a unit of work, locks the repository
    member for PGM1 and the reads the member so that it can be
    updated. If IMS2 calls RM to update the member at the same time,
    it too starts a unit of work, attempts to lock the member and
    read it. If the lock is already held by IMS1, the lock request
    will fail and this should result in the
    1D4 REPOSITORY MEMBER IN USE error.
    However a CC=0 is being returned incorrectly instead of the
    error.
    

Problem conclusion

  • GEN:
    KEYWORDS:
    
    *** END IMS KEYWORDS ***
    The code in module CSLRRU10 has been modified to populate the
    response completion code (cc) and response reason code when
    the lock request is not successful.
    Logic is also added to wait and retry the lock request for
    6 times if the lock is not obtained before an error is
    returned.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI50149

  • Reported component name

    IMS V13

  • Reported component ID

    5635A0400

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-10-07

  • Closed date

    2015-11-13

  • Last modified date

    2015-12-03

  • APAR is sysrouted FROM one or more of the following:

    PI48998

  • APAR is sysrouted TO one or more of the following:

    UI32953

Modules/Macros

  • CSLRRU10
    

Fix information

  • Fixed component name

    IMS V13

  • Fixed component ID

    5635A0400

Applicable component levels

  • R300 PSY UI32953

       UP15/11/19 P F511

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"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"300","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
14 December 2020