# Need Help running asynch

**URL:** <https://techcommunity.softwareag.com/t/need-help-running-asynch/91135>\
**Category:** Forum\
**Tags:** Adabas-Natural, Adabas, Adabas-on-Mainframes, Adabas-Utilities-on-Mainframes\
**Created:** [September 3, 2009, 7:11pm UTC](https://techcommunity.softwareag.com/t/need-help-running-asynch/91135 "2009-09-03T19:11:02Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hezi](https://avatars.discourse-cdn.com/v4/letter/h/a5b964/32.png) [@Hezi](https://techcommunity.softwareag.com/u/Hezi)\
**Post date:** [September 3, 2009, 7:11pm UTC](https://techcommunity.softwareag.com/t/need-help-running-asynch/91135/1 "2009-09-03T19:11:02Z")

</div>

Hi,

We have a cobol program that invoke natural asynch.  
Somehow, we always get “nt06 - send attempted without a terminal”.  
Probably, we do not get a valid terminal id fron natural.  
How can we fix it?

Hezi

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [September 4, 2009, 12:04pm UTC](https://techcommunity.softwareag.com/t/need-help-running-asynch/91135/2 "2009-09-04T12:04:33Z")

</div>

Async tasks are not allowed to issue terminal writes i.e. write/display/print to printer 0.

---

<div class="post-metadata">

**Author:** ![Aldo\_Teusch](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/aldo_teusch/32/87_2.png) [@Aldo\_Teusch](https://techcommunity.softwareag.com/u/Aldo_Teusch)\
**Post date:** [September 4, 2009, 12:12pm UTC](https://techcommunity.softwareag.com/t/need-help-running-asynch/91135/3 "2009-09-04T12:12:05Z")

</div>

Hi Hezi,

Normally programs running in asynch mode should not WRITE / DISPLAY to a terminal. Nonetheless output can be intercepted by redirecting it, p.ex. to a Cics transient data destination.

The manual says: "Make sure that appropriate SENDER and OUTDEST destinations are specified for an asynchronous Natural session; otherwise, any output (for example, unexpected error messages) will lead to an abnormal termination. "

At our site we set LOGDEST=NLOG in the NCIPARM member and we set SENDER=NLOG at start-up of asynchronous sessions. NLOG points to a CICS transient data destination.

Aldo

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 2:57pm UTC](https://techcommunity.softwareag.com/t/need-help-running-asynch/91135/4 "2021-04-02T14:57:27Z")

</div>