IBM Support

OA67779: C2PAMALC GIVES ERROR MSG IKJ56712I INVALID KEYWORD WHEN USING A DA ALLOCATION

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • C2PAMALC gives error msg IKJ56712I INVALID KEYWORD when using a
    DA allocation
    
    If a customer wants to add a dataset to their C2PAMALC member
    instead of coding it in the JCL they will receive an error if
    the DSN exceeds 31 characters. Example using C2PAMALC and the
    SYSPRST1 DD follows.
    
    alloc dd(c2pdebug) sy(*) lrecl(255) recfm(v b)
    
    alloc dd(c2xprint) sy(*) lrecl(255) recfm(v b)
    
    alloc dd(c2ptsprt) sy(*) lrecl(255) recfm(v b)
    
    alloc dd(sysabend) sy(*) lrecl(1000) recfm(v b)
    
    alloc dd(sysprst1) lrecl(255) recfm(v b) space(32760,(10,10))
    shr -
           DA('CRMA.X.DATA.TVT2038.C2PACMON.SYSPRCON')
    
    
    Results in this error message in C2PTSPRT
    
    IKJ56712I INVALID KEYWORD,
    'CRMA.X.DATA.TVT2038.C2PACMON.SYSPRCON'
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of zSecure Access Monitor running its  *
    *                 started task with a OPTION ALLOCATIONMEMBER  *
    *                 argument or with a default C2PAMALC data     *
    *                 set that provides additional data set        *
    *                 allocation specifications.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: zSecure Access Monitor started task     *
    *                      might issue a MSGC2P0269E followed by   *
    *                      MSGIEC130I at startup.                  *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF provided.                      *
    ****************************************************************
    When a data set name name provided in the dynamic allocation
    member (either default C2PAMALC or specified by the OPTION
    ALLOCATIONMEMBER started task argument) has length exceeding 31
    characters, the zSecure Access Monitor started task issues a
    MSGC2P0269E which begins with the text "C2P0269E Invalid
    parameter..." followed by a MSGIEC130I which begins with the
    text "<dd name> DD STATEMENT MISSING".
    

Problem conclusion

  • zSecure Access Monitor has been modified, so that it accepts
    data set names whose length exceeds 31 characters provided in
    the dynamic allocation member (either default C2PAMALC or
    specified by the OPTION ALLOCATIONMEMBER started task argument).
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA67779

  • Reported component name

    ZSEC BASE,ADMIN

  • Reported component ID

    5655T0100

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-04-17

  • Closed date

    2025-05-23

  • Last modified date

    2025-05-24

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

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

    UJ97249

Modules/Macros

  • C2PPRSRC
    

Fix information

  • Fixed component name

    ZSEC BASE,ADMIN

  • Fixed component ID

    5655T0100

Applicable component levels

  • R310 PSY UJ97249

       UP25/05/24 I 1000

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":"BU048","label":"IBM Software"},"Product":{"code":"SSPQTM","label":"IBM Security zSecure Admin"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"310","Line of Business":{"code":"LOB70","label":"Z TPS"}}]

Document Information

Modified date:
24 May 2025