Cobol - unable to retrieve data from cics start

Author

unable to retrieve data from cics start

progrmmr

2005-04-18, 8:55 pm

Started a CICS transaction with:

EXEC CICS START
TRANSID(WS-TCODE)
FROM(WS-DATA)
LENGTH(WLEN)
RESP(RESPONSE-CODE)
END-EXEC.

When trying to retrieve data with:

EXEC CICS RETRIEVE
INTO(WS-DATA)
LENGTH(LEN)
RESP(RESPONSECODE)
END-EXEC.

I get ENDDATA. What gives?
Looked at many numerious examples, but
this looks pretty straighforward. Do I have
to allocate/deallocate a special queue name?

Help anybody?

Arnold Trembley

2005-04-19, 3:55 am

progrmmr wrote:
> Started a CICS transaction with:
>
> EXEC CICS START
> TRANSID(WS-TCODE)
> FROM(WS-DATA)
> LENGTH(WLEN)
> RESP(RESPONSE-CODE)
> END-EXEC.
>
> When trying to retrieve data with:
>
> EXEC CICS RETRIEVE
> INTO(WS-DATA)
> LENGTH(LEN)
> RESP(RESPONSECODE)
> END-EXEC.
>
> I get ENDDATA. What gives?
> Looked at many numerious examples, but
> this looks pretty straighforward. Do I have
> to allocate/deallocate a special queue name?
>
> Help anybody?

ENDDATA means there is no outstanding message to be retrieved. Your
CICS commands look correct.

You might try adding the WAIT option to the RETRIEVE command, but that
implies that your started task will be long-running, or conversational
rather than pseudo-conversational. It is not possible to get an
ENDDATA condition on a RETRIEVE with WAIT. Your started task simply
goes into a wait state until there is a message to RETRIEVE.

I assume you had a good EIBRESP on your START command. Is the task
that issues the START command in the same CICS region as the task
being started? Or are you trying to start a task in another region
using IRC or ISC?

You cannot allocate a temp storage queue for the start message being
passed to the started task. CICS handles that for you.

Can you tell us a bit more about your program set up?

--
http://arnold.trembley.home.att.net/

progrmmr

2005-04-19, 3:55 pm

The systems people told me it was a CICS setting.

It works now.

Thanks.

Sponsored Links