SET WORKREQUEST

To Purge or Forcepurge a specific local task.

Read syntax diagramSkip visual syntax diagramSET WORKREQUEST
 
>>-SET WORKREQUEST(data-value)--+----------------+-------------->
                                +-WORKTYPE(cvda)-+
                                +-IIOP-----------+
                                '-SOAP-----------'
 
>--+-----------------+-----------------------------------------><
   +-PURGETYPE(cvda)-+
   +-FORCEPURGE------+
   '-PURGE-----------'
 

Conditions:  INVREQ, NOTAUTH, NOTFND

This command is threadsafe.

Description

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.

Options

WORKREQUEST(data-value)
specifies an 8-character token to identify the work request. Start of changeThe token is generated by CICS. Normal usage begins with an INQUIRE WORKREQUEST BROWSE command, to identify the token which is of interest. Then the specific token can be used to issue INQUIRE and SET commands that relate to the task in question.End of change
PURGETYPE(cvda)
specifies that CICS is to purge the task, and indicates conditions for doing so.

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:

FORCEPURGE
The task is to be terminated as soon as it is consistent with system integrity and without regard to data integrity.
Note:
CICS cannot always determine whether a forced purge is safe; it is possible to abend the system when you specify FORCEPURGE.
PURGE
The task is to be terminated as soon as both system and data integrity can be maintained.
Note:
You cannot purge a task with this CVDA value if the definition of the TRANSACTION it is executing specifies SPURGE=NO.
WORKTYPE(cvda)
specifies the type of work being performed:
Start of change
IIOP
Specifies that the work is being executed for an IIOP request.
SOAP
Specifies that the work is being executed for a Web service request.
End of change

Conditions

INVREQ
RESP2 values:
2
The attempted purge or forcepurge action is not valid.
5
The attempt to purge or forcepurge a local task failed.
6
The attempt to purge or forcepurge a local task is deferred.
7
PURGE is not permitted because SPURGE=NO has been set to protect the task.
8
The task is protected by CICS and is not eligible for modification with this command.
9
An attempt to purge or forcepurge a request receiver failed. Such actions are not allowed for request receivers.
NOTAUTH
RESP2 values:
100
The user of the issuing task is not authorized to use this command.
NOTFND
RESP2 values:
3
The specified WORKREQUEST is not present in this system.
[[ Contents Previous Page | Next Page Index ]]