CA IDMS IUA EIUA

Re:question on QUED

  • 1.  Re:question on QUED

    Posted 09-21-2010 10:48 AM
    i have a very active read-only CV - however it does update Queues (being
    r/o journals are very small)

    although several applications have been subset - the jobs that write to
    these queues are still active- so i execute QUED prompt
    I note then when a journal fills and the info message is written

    DC205030 V75 T53649733 LID=4179105942 PROG=RHDCRUAL SUBS=IDMSNWK7
    BFOR=438KB

    rhdcrual is the program - interestingly - even though i exit qued -
    condensing does not free up the journal space

    is this because a pre-defined (RHDCRUAL) run unit is considered still
    active and as such the BFORS cannot be removed?

    the DCMT D RUNUNIT shows:

    TYPE QUEUE
    DRIVER TASK ID 0000000002
    SUBSCHEMA IDMSNWK7
    NODE
    DICTNAME/DBNAME SYSTEM
    IDLE INTERVAL OFF
    PREDEFINED RUN UNITS 2
    RUN UNIT ALLOCATIONS 162
    RUN UNIT FREES 162
    OVERFLOW RUN UNITS 0
    AREA NAME DDLDCRUN
    USAGE MODE SHARED UPDATE
    TYPE BOUND IN-USE ALLOCS OWNING TASK
    PERM YES NO 161
    PERM YES NO 1


    Chris Hoelscher
    IDMS/DB2 System & Database Architect
    Humana Inc
    502-476-2538
    choelscher@humana.com

    I refuse to repeat gossip - so listen carefully the first time




    The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
    "
    IDMS Public Discussion Forum
    IDMS-L@LISTSERV.IUASSN.COM
    SMTP
    IDMS-L@LISTSERV.IUASSN.COM
    IDMS-L@LISTSERV.IUASSN.COM
    SMTP








    Normal

    Normal
    Re: question on QUED
    "I think your problem is that the QUED task was unable to write an ABRT checkpoint record, so was unable to rollback.

    The ""normal"" RHDCRUAL run units should behave similar to any other run unit that takes a COMMIT, locks are freed and journal images are available for offloading.

    In the case of QUED, it (evidently) takes no COMMITs, so unless you can hold all the BFOR/AFTR images in your journals, you'll exhaust all your journals.

    Just a hypothesis.

    Don Casey