Author: Bill O'Boyle
Subject: Reply to: How to find a CICS resource used in CICS ENQ command?
Posted: Fri Sep 30, 2016 6:43 pm (GMT 5.5)
When using an ENQ "RESOURCE" API, the named defined to this RESOURCE must be known by all programs that attempt access. For example, if you have a TSQ which is accessed/updated by several programs, to ensure data integrity, a given program MUST serialize TSQ access. This would be the purpose of the ENQ API. It is highly suggested when serialized access has completed and you're ready to allow access by the "next" waiting-task, rather than wait for task-termination, issue an explicit DEQ API.
I still prefer using the HANDLE CONDITION ENQBUSY (LABEL), but that's just my preference.
If a program has issued an ENQ on a shared RESOURCE and it's busy, the program logic will automatically wait at the LABEL defined in the HANDLE until it becomes available.
HTH....
_________________
Nothing in fine print is ever good news.![icon_wink.gif]()
!!!!!!!
ò ¿ ó
(~~)
Mr. Bill
Subject: Reply to: How to find a CICS resource used in CICS ENQ command?
Posted: Fri Sep 30, 2016 6:43 pm (GMT 5.5)
When using an ENQ "RESOURCE" API, the named defined to this RESOURCE must be known by all programs that attempt access. For example, if you have a TSQ which is accessed/updated by several programs, to ensure data integrity, a given program MUST serialize TSQ access. This would be the purpose of the ENQ API. It is highly suggested when serialized access has completed and you're ready to allow access by the "next" waiting-task, rather than wait for task-termination, issue an explicit DEQ API.
I still prefer using the HANDLE CONDITION ENQBUSY (LABEL), but that's just my preference.
If a program has issued an ENQ on a shared RESOURCE and it's busy, the program logic will automatically wait at the LABEL defined in the HANDLE until it becomes available.
HTH....
_________________
Nothing in fine print is ever good news.
!!!!!!!
ò ¿ ó
(~~)
Mr. Bill