IBM Support

PK07916: DATASET-NAME USING 44 BYTES INSTEAD OF 41 BYTES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • OS Version (uname -a):      IBM Mainframe running z/OS
    ClearCase Version and Patch Level:   clearcase_p2003.06.00-17
    
    
    What is the problem? (Brief)
    
    RCCE-040
    A dataset allocation error occurred on MVS.
    DDName = 'SRCPL#'
    return code = '4'
    error code = '5896'
    info code = '2'
    Determine the cause of the error by matching the
    error codes with the documented svc99 codes in the
    'MVS System Programming Library: System Macros and
    and Facilities Volume 1'.
    The dataset attributes for the DDName specified
    in the MVS build script may have contributed to the
    problem.
    
    RCCI-011 Probable cause:
         Specified dataset could not be located.
    
    
    DSN=SCCM.U0000.T1.TEMP.D3738310.E0615F05.A1.PL#,DISP=SHR,RCCEXT=
    PL#,DSORG=PO
    
    
    
    FULL DESCRIPTION OF PROBLEM:
    
    Customer is using the ClearCase Mainframe Connector API. All
    descriptions below concern IBM Mainframe. While the API is
    parsing the Dataset-Names of the API Mapmember, customer gets an
    error when the Dataset-Name is using more than 41 bytes. The
    usual MVS Limit is 44 bytes. Customer would
    like/need to use the full 44 bytes. output below shows the error
    of the API
    
    Output of API
    ***********************************************************
    
    RCCE-040
    A dataset allocation error occurred on MVS.
    DDName = 'SRCPL#'
    return code = '4'
    error code = '5896'
    info code = '2'
    Determine the cause of the error by matching the
    error codes with the documented svc99 codes in the
    'MVS System Programming Library: System Macros and
    and Facilities Volume 1'.
    The dataset attributes for the DDName specified
    in the MVS build script may have contributed to the
    problem.
    
    RCCI-011 Probable cause:
         Specified dataset could not be located.
    
    
    DSN=SCCM.U0000.T1.TEMP.D3738310.E0615F05.A1.PL#,DISP=SHR,RCCEXT=
    PL#,DSORG=PO
    
    ************************************************************
    
    ClearCase version 2003.06.00 (Fri Apr 25 09:05:22 EDT 2003)
    clearcase_p2003.06.00-14 (Thu Dec 02 15:33:25 EST 2004)
    clearcase_p2003.06.00-15 (Wed Nov 24 11:03:49 EST 2004)
    clearcase_p2003.06.00-16 (Fri Dec 03 14:50:48 EST 2004)
    clearcase_p2003.06.00-17 (Thu Dec 09 08:20:07 EST 2004)
    @(#) MVFS version 2003.06.10 (Wed Nov  3 00:30:33 EST 2004)
    
    
    
    Please check defect RATLC00748792 which has been found inhouse.
    

Local fix

Problem summary

  • Mainframe Connectors:  Allocation error on data set name in
    MAP
    file while attempting low level API function.
    

Problem conclusion

  • Fixed in ClearCase 7.0.0.0
    MFX not properly handling data set name in MAP file when
    name is greater than 41 characters in length.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK07916

  • Reported component name

    CLEARCASE UNIX

  • Reported component ID

    5724G2901

  • Reported release

    60S

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2005-06-27

  • Closed date

    2006-06-09

  • Last modified date

    2006-06-09

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

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

Modules/Macros

  • na
    

Fix information

  • Fixed component name

    CLEARCASE UNIX

  • Fixed component ID

    5724G2901

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0.S","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
22 July 2020