IBM Crypto Education Community

Expand all | Collapse all

KGUP jobstream ended with RC=0036

  • 1.  KGUP jobstream ended with RC=0036

    Posted Mon December 14, 2020 08:10 AM
    Hello ,

    I'm trying to generate operational key via ICSF menus (option 8.1 and so on ) and it ends with RC=0036 :


    KGUP jobstream used :

    //KGUP EXEC PGM=CSFKGUP,PARM=('NOSSM')
    //CSFCKDS DD DSN=SYSL.CSF.SY92.CSFCKDS,
    // DISP=OLD
    //CSFIN DD DSN=EXSYNM.ICSF.KGUP.CNTL(DES01),
    // DISP=OLD
    //CSFDIAG DD SYSOUT=*
    //CSFKEYS DD DSN=EXSYNM.ICSF.KGUP.KEY.OUTPUT,
    // DISP=OLD
    //CSFSTMNT DD DSN=EXSYNM.ICSF.KGUP.CSFSTMNT,
    // DISP=OLD



    CSFIN statement (example) :

    ADD TYPE(DATA) LENGTH(16),
    LAB(IRR.SSIGNON.SYS1.KEY2020)

    Is there something missing ? ( MKs loaded , CKDS initialized ,  all previous steps done )

    Thank you .



    ------------------------------
    Nordine
    ------------------------------


  • 2.  RE: KGUP jobstream ended with RC=0036

    Posted Mon December 14, 2020 12:08 PM
    From the ICSF Messages book, Chapter 5. CSFGnnnn messages (Key generator utility processing)

    CSFG0002 CRYPTOGRAPHIC KEY GENERATION - END OF JOB. RETURN CODE = retcode.
    Explanation
    The key generator utility program completed processing with a return code of retcode. The table lists all known
    return codes and their meanings.
    Note: Not all of the return codes listed will be communicated via the CSFG0002 message in the CSFDIAG data
    sets; some will only be generated by the KGUP JCL job.
    Return Code
    Meaning
    36
    State of special secure mode on the coprocessor is not the same as the state that is specified in the PARM
    field of the EXEC JCL statement.

    This means you have a mismatch between the JCL and ICSF state. In this case, you have "NOSSM" specified in the JCL but have ICSF running with SSM(YES).

    ------------------------------
    Eric Rossman
    ------------------------------