To Purge or Forcepurge a specific local task.
SET WORKREQUEST >>-SET WORKREQUEST(data-value)--+----------------+--------------> +-WORKTYPE(cvda)-+ +-IIOP-----------+ '-SOAP-----------' >--+-----------------+----------------------------------------->< +-PURGETYPE(cvda)-+ +-FORCEPURGE------+ '-PURGE-----------'
Conditions: INVREQ, NOTAUTH, NOTFND
This command is threadsafe.
The SET WORKREQUEST command allows you to purge a specific local IIOP task (terminate it abnormally) using the PURGE or FORCEPURGE option. These actions are not permitted for request receivers, any such attempts fail.
SET WORKREQUEST is only available for IIOP tasks.
Work Requests are identified by tokens. Each token is unique in the local system . It is expressed as an eight character field, where the characters are hexadecimal digits .
For additional background information about the SPI commands that handle Work Requests, see INQUIRE WORKREQUEST.
Purging a task at the wrong time can result in a loss of data integrity or, in some circumstances, can cause CICS to abend. CICS always defers purging until the task reaches a state where the system itself does not appear to be at risk, but you can specify whether CICS also should wait until data integrity can be ensured.
If CICS accepts a purge request, it returns a NORMAL response to SET WORKREQUEST. You can tell whether execution has been deferred by inspecting the RESP2 value. If RESP2 is zero, the purge has been completed; if RESP2 is 6, it has been deferred. CVDA values are: