# NAT0920 in CICS TS v31

**URL:** <https://techcommunity.softwareag.com/t/nat0920-in-cics-ts-v31/62089>\
**Category:** Forum\
**Tags:** Adabas-Natural, Natural, Natural-on-Mainframes, Natural-Database-and-TP-Monitor-Interfaces-on-Mainframes\
**Created:** [March 28, 2007, 5:10am UTC](https://techcommunity.softwareag.com/t/nat0920-in-cics-ts-v31/62089 "2007-03-28T05:10:04Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dana\_Duncan](https://avatars.discourse-cdn.com/v4/letter/d/eb8c5e/32.png) [@Dana\_Duncan](https://techcommunity.softwareag.com/u/Dana_Duncan)\
**Post date:** [March 28, 2007, 5:10am UTC](https://techcommunity.softwareag.com/t/nat0920-in-cics-ts-v31/62089/1 "2007-03-28T05:10:04Z")

</div>

We are a Natural v414 site under ADABAS v743 and CICS.

I have a Natural program doing a call to a third-party module written in C/C++ as follows:  
SET CONTROL ‘P=LS’  
CALL ‘SSAOPEN’  
#SSA-COMMON-PARMS  
When I run this in TSO, all is fine.

However, in CICS, I get:  
NAT0920 Program SSAOPEN cannot be loaded (FFFFFFFF).

We are a LE370=yes site.

There are a lot of details and I will be happy to supply any info that I can.

Can anyone help?

---

<div class="post-metadata">

**Author:** ![Daniel\_Wilson](https://avatars.discourse-cdn.com/v4/letter/d/94ad74/32.png) [@Daniel\_Wilson](https://techcommunity.softwareag.com/u/Daniel_Wilson)\
**Post date:** [March 28, 2007, 5:28am UTC](https://techcommunity.softwareag.com/t/nat0920-in-cics-ts-v31/62089/2 "2007-03-28T05:28:02Z")

</div>

Well, without know how your called program is expecting the parameter data to be passed, it hard to say, but I would try changing the SET CONTROL "P=LS’ to ‘P=C’ or ‘P=S’ to see which one works. The ‘P=S’ is for standard CICS linkages and the ‘P=C’ is for passing the values of the parameters instead of the address of the data.

If these don’t work, you can always write a small COBOL program that acts as an intermediate program between Natural and the C++ program. I have had to that in the past with some third party products.

---

<div class="post-metadata">

**Author:** ![Douglas\_Kelly](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/douglas_kelly/32/102_2.png) [@Douglas\_Kelly](https://techcommunity.softwareag.com/u/Douglas_Kelly)\
**Post date:** [March 28, 2007, 10:30am UTC](https://techcommunity.softwareag.com/t/nat0920-in-cics-ts-v31/62089/3 "2007-03-28T10:30:55Z")

</div>

a NAT0920 says that Natural can’t load the requested module from the operating system. I’m guessing this is not (yet) a problem of parameter passing (which is what the %P= option controls).

Is SSAOPEN a CICS module, callable using CICS conventions? If you are calling the same module from TSO, it is not using CICS conventions. Either

- you need to obtain the equivalent CICS module and ensure that it is in the DFHRPL library and has a PPT entry created for it, or
- link edit “SSAOPEN” with the Natural nucleus and use the CSTATIC option. This will use the MVS standard linkage conventions (BALR 14,15, parameters in R1).

Please check out the documentation on the %P= command  
[http://techcommunity.softwareag.com/ecosystem/documentation/natural/nat422mf/tcom/pcpeq.htm#pcpeq](http://techcommunity.softwareag.com/ecosystem/documentation/natural/nat422mf/tcom/pcpeq.htm#pcpeq)  
and the Natural support of LE environment:  
[http://techcommunity.softwareag.com/ecosystem/documentation/natural/nat422mf/ops\_mf/misc\_le.htm](http://techcommunity.softwareag.com/ecosystem/documentation/natural/nat422mf/ops_mf/misc_le.htm)

---

<div class="post-metadata">

**Author:** ![AlanPeterson](https://avatars.discourse-cdn.com/v4/letter/a/b19c9b/32.png) [@AlanPeterson](https://techcommunity.softwareag.com/u/AlanPeterson)\
**Post date:** [June 1, 2007, 6:04am UTC](https://techcommunity.softwareag.com/t/nat0920-in-cics-ts-v31/62089/4 "2007-06-01T06:04:36Z")

</div>

Dana,

Was there ever a solution found to solve the Nat0920?

Alan Peterson.

---

<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:** [July 18, 2007, 5:57pm UTC](https://techcommunity.softwareag.com/t/nat0920-in-cics-ts-v31/62089/5 "2007-07-18T17:57:11Z")

</div>

NAT0920 return code -1 indicates that Natural under CICS is NOT LE enabled.  
Pls follow the instructions of member #README, which is supplied in the NCI4.1 distribution source library to make NCI LE compliant in CICS.

---

<div class="post-metadata">

**Author:** ![Dana\_Duncan](https://avatars.discourse-cdn.com/v4/letter/d/eb8c5e/32.png) [@Dana\_Duncan](https://techcommunity.softwareag.com/u/Dana_Duncan)\
**Post date:** [October 10, 2007, 10:54pm UTC](https://techcommunity.softwareag.com/t/nat0920-in-cics-ts-v31/62089/6 "2007-10-10T22:54:09Z")

</div>

> [@AlanPeterson](#):
>
> Dana,
> 
> Was there ever a solution found to solve the Nat0920?
> 
> Alan Peterson.

Alan,  
To answer your question, my data center did not wnat to do the suggested steps to make Nat v41 LE enabled.  
We are now Nat v423 and I have traded my NAT0920 for an S0C1.

---

<div class="post-metadata">

**Author:** ![Dana\_Duncan](https://avatars.discourse-cdn.com/v4/letter/d/eb8c5e/32.png) [@Dana\_Duncan](https://techcommunity.softwareag.com/u/Dana_Duncan)\
**Post date:** [October 10, 2007, 10:54pm UTC](https://techcommunity.softwareag.com/t/nat0920-in-cics-ts-v31/62089/7 "2007-10-10T22:54:33Z")

</div>

> [@AlanPeterson](#):
>
> Dana,
> 
> Was there ever a solution found to solve the Nat0920?
> 
> Alan Peterson.

Alan,  
To answer your question, my data center did not wnat to do the suggested steps to make Nat v41 LE enabled.  
We are now Nat v423 and I have traded my NAT0920 for an S0C1.

---

<div class="post-metadata">

**Author:** ![Dana\_Duncan](https://avatars.discourse-cdn.com/v4/letter/d/eb8c5e/32.png) [@Dana\_Duncan](https://techcommunity.softwareag.com/u/Dana_Duncan)\
**Post date:** [October 10, 2007, 10:56pm UTC](https://techcommunity.softwareag.com/t/nat0920-in-cics-ts-v31/62089/8 "2007-10-10T22:56:14Z")

</div>

> [@AlanPeterson](#):
>
> Dana,
> 
> Was there ever a solution found to solve the Nat0920?
> 
> Alan Peterson.

Alan,  
To answer your question, my data center did not wnat to do the suggested steps to make Nat v41 LE enabled.  
We are now Nat v423 and I have traded my NAT0920 for an S0C1.

---

<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:41pm UTC](https://techcommunity.softwareag.com/t/nat0920-in-cics-ts-v31/62089/9 "2021-04-02T14:41:08Z")

</div>


