IBM Security Z Security

Expand all | Collapse all

option serialization(enq(sysdsn),wait,maxwait(10)) in CKQSPECL

  • 1.  option serialization(enq(sysdsn),wait,maxwait(10)) in CKQSPECL

    Posted Wed August 05, 2020 09:50 AM

    I have a couple of questions regarding CKQRADAR parameter member CKQSPECL.  

    option serialization(enq(sysdsn),wait,maxwait(10))

    I have 2 questions:

    1) will this parameter be honoured not only at startup, but also during the life of the CKQRADAR STC ? That is if we increase to : maxwait(20) , will this fix our issue ? 

    our issue....
    we run a daily CKFREEZE & UNLOAD file create job  (starting at 1;30 am) that takes approximately 17 minutes to complete. 
    during that time we see the following msgs: 

    starting at 1;30 am ..
    S=SYSTEMS SYSDSN TS.D9K.ZSECURE.TCSF.CKFREEZE
    SYSNAME JOBNAME ASID TCBADDR EXC/SHR STATUS
    TCSF P9KFRTCS 01E9 007F8680 EXCLUSIVE OWN
    TCSF P9KQRADR 0072 007E9430 SHARE WAIT


    The enqueue does not clear up until Job P9KFRTCS completes (P9KFRTCS - ENDED - TIME=01.47.23), by that time STC P9KQRADR (our version of CKQRADAR)  stopped since it could not obtain an exclusive enqueue on dataset TS.D9K.ZSECURE.TCSF.CKFREEZE in an allowable time.

    at approx 1:40 am STC P9KQRADR ends ..

    CKR0911 00 ISGENQ RC=04 hex RSN=090B0403 hex for SYSDSN-SYSTEM TS.D9K.ZSECURE.TCSF.CKFREEZE: resource not immediately available
    CKR0911 00 ISGENQ RC=04 hex RSN=090B0403 hex for SYSDSN-SYSTEM TS.D9K.ZSECURE.TCSF.UNLOAD: resource not immediately available
    CKR0913 04 Serialization starts waiting for ENQs
    CKR1698 00 *** Elapsed/CPU 0.003491/0.000419 total 0.087525/0.013450 msg CKRM977 ****
    CKR0913 16 Serialization could not obtain all ENQs

    2) is there any negative impact to coding a maxwait(20) to STC P9KQRADR ?

    Please advise



    ------------------------------
    Marco Passaretti
    ------------------------------


  • 2.  RE: option serialization(enq(sysdsn),wait,maxwait(10)) in CKQSPECL

    Posted Wed August 05, 2020 11:23 AM
    Hi Marco
    Changing the MAXWAIT value  in CKQSPECL would work, the CKQRADAR task will sleep much longer before terminating.  However:
    During the wait time, SMF records are not retrieved from the buffers so if you use CKQEXSMF you have to ensure that the buffer space (NUMBUFS and BUFSIZEMB in member CKQEXSMF) is large enough.   Also, if your SIEM expects real-time SMF records, it should not complain when those records are delayed up to the MAXWAIT time.
    It would be a better idea to synchronize your Collect/Unload job P9KFRTCS with the refresh interval in CKQRADAR, such that you job starts shortly after the hourly restart of he SMF processing task.  You might want to open an RFE, asking that CKQRADAR issues an optional WTO at these times.

    ------------------------------
    Rob van Hoboken
    ------------------------------



  • 3.  RE: option serialization(enq(sysdsn),wait,maxwait(10)) in CKQSPECL

    Posted Wed August 05, 2020 11:49 AM
    Thanks Rob for your response !

    Note: we are using SMF via logstream on almost all our systems, so we use INMEM (2G in size) .  On those systems I don't believe there would be a concern regarding CKQEXSMF NUMBUFS & BUFSIZEMB.  

    Please advis eif my understanding is correct.

    Thanks,

    Marco



    ------------------------------
    Marco Passaretti
    ------------------------------