WRITEQ TD

WRITEQ TD

Summary

Writes the data to transient data queue. WRITEQ TD writes data to a predefined symbolic destination queue.

Syntax -

WRITEQ TD Syntax

Options -

FROM(data-area) -

Specifies the data area that is to be written to the transient data queue.

LENGTH(data-value) -

data-value is a halfword binary value. Specifies the length of the data to be written.

QUEUE (name) -

Specifies the symbolic name (1 - 4 characters) of the queue to be written to. The queue must have been defined to CICS.

SYSID (system-name) -

Option is for remote systems only. Specifies the system name (1 - 4 characters).

Error Conditions -

Below are the list of error conditions may occur in combination. If more than one occurs, only the first is passed to the application program.

Error ConditionRESP2, Description & SolutionSystem Action
1 ERROR
Occurs for any other condition that does not raise.
Solution -This might be the case which is not handled. Debug the program to find the issue and resolve it.		 Task abnormally terminated
84 DISABLED
Occurs when the queue has been disabled.
Solution -Enable the queue in the CICS region. If you have no access, contact system administrator to enable the queue.		 Task abnormally terminated
16 INVREQ
Occurs if WRITEQ names an extra-partition queue that has been opened for input.This condition cannot be raised for intra-partition queues.
Solution -The WRITEQ operation should not be performed on the queue opened for input. If WRITEQ operation required to perform on the same queue, open the queue in the output mode. 		Task abnormally terminated
17 IOERR
Occurs when an input/output error and the data record in error is skipped.
Solution -This condition occurs if writing the queue when the queue can’t be written and a QZERO condition occurs in this situation. Check the Queue opened mode before issuing a write command. This condition can also occur if the FREE=CLOSE operand has been used in the data set definition for an extra-partition queue and the queue has been closed and reopened. Reopen the file to resolve the issue. 		Task abnormally terminated
22 LENGERR
Occurs in either of the following situations -
  • WRITEQ names an extra-partition queue and does not specify a length consistent with the RECORDSIZE and associated formations specified in the TDQUEUE resource definition.
    Solution -Specify the RECORDSIZE and associated formations in TDQUEUE resource definition. If you have no access, contact system administrator to do the same.
  • WRITEQ names an intra-partition queue and does not specify a length consistent with the control interval defined for the intra-partition data set.
    Solution -Specify the length with the control interval for TDQUEUE resource definition. If you have no access, contact system administrator to do the same.
 Task abnormally terminated
70 NOTAUTH
A resource security check has failed on QUEUE (name).
Solution -Contact system administrator team to check whether the appropriate access added for the user or group. It will resolve the problem. 		Task abnormally terminated
44 QIDERR
Occurs if the symbolic destination to be used cannot be found.
Solution -This happens due to the Queue already might get deleted or queue name provided might wrong. Debug the application program flow and correct the logic. 		Task abnormally terminated
53 SYSIDERR
Occurs when the SYSID option specifies a name that is neither the local system nor a remote system.
Solution -The specified SYSID name is not related to any system. Correct it.

Occurs when the link to the remote system is closed.
Solution -This might be due to the remote system is not up and running. Contact remote system support team. 		Task abnormally terminated
18 NOSPACE
Occurs if no more space exists on the intra-partition or extra-partition queue, or the relative byte address (RBA) for an intra-partition queue would exceed 2 GB.
Solution -This issue because of storage issues. Contact system administrator to resolve the issue.		 Task abnormally terminated
19 NOTOPEN
Occurs if the destination is closed.
Solution -This might happen due to the queue is closed. Open the queue to resolve the issue. 		Task abnormally terminated