# Anyone know what to do when FNR associated with a file in ADABAS different than FNR in Natural **URL:** \ **Category:** Forum\ **Tags:** Adabas-Natural, Adabas, Adabas-on-Mainframes, Adabas-Basics-on-Mainframes\ **Created:** [November 10, 2016, 5:08pm UTC](https://techcommunity.softwareag.com/t/anyone-know-what-to-do-when-fnr-associated-with-a-file-in-adabas-different-than-fnr-in-natural/191470 "2016-11-10T17:08:14Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Sandy\_Spencer](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/sandy_spencer/32/1219_2.png) [@Sandy\_Spencer](https://techcommunity.softwareag.com/u/Sandy_Spencer)\ **Post date:** [November 10, 2016, 5:08pm UTC](https://techcommunity.softwareag.com/t/anyone-know-what-to-do-when-fnr-associated-with-a-file-in-adabas-different-than-fnr-in-natural/191470/1 "2016-11-10T17:08:14Z")
When I run the ADAREP utility, I see than file XXX-MIN8 is associated with FNR 250. From Natural, when I list all DDM’s in that same nucleous, it shows the file XXX-MIN8 is associated with FNR 640. Fortunately, this is our sandbox environment, but I would like to know how to clean this up. File XXX-MIN8 should be associated with FNR 640 ---
**Author:** ![Ralph\_Zbrog](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/ralph_zbrog/32/78_2.png) [@Ralph\_Zbrog](https://techcommunity.softwareag.com/u/Ralph_Zbrog)\ **Post date:** [November 10, 2016, 9:47pm UTC](https://techcommunity.softwareag.com/t/anyone-know-what-to-do-when-fnr-associated-with-a-file-in-adabas-different-than-fnr-in-natural/191470/2 "2016-11-10T21:47:46Z")
Before you “clean this up” make sure that you should. Write a Natural program to read one record from the file. From what you say, you should receive error code 3017 to indicate a bad file number. If you don’t get this error then a file number translation is happening under the covers, for example via the NTTF macro. To fix the problem, run the ADADBS utility. ```auto ADADBS RENUMBER FILES=250,640 ``` ---
**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:** [November 11, 2016, 2:24am UTC](https://techcommunity.softwareag.com/t/anyone-know-what-to-do-when-fnr-associated-with-a-file-in-adabas-different-than-fnr-in-natural/191470/3 "2016-11-11T02:24:34Z")
You can use the SYSEXT API USR1034 to see if the TF tables are being used in your Natural environment. They can be supplied dynamically in your parms, PROFILE or statically from the NATPARM as Ralph mentions. ---
**Author:** ![Sandy\_Spencer](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/sandy_spencer/32/1219_2.png) [@Sandy\_Spencer](https://techcommunity.softwareag.com/u/Sandy_Spencer)\ **Post date:** [November 15, 2016, 2:15pm UTC](https://techcommunity.softwareag.com/t/anyone-know-what-to-do-when-fnr-associated-with-a-file-in-adabas-different-than-fnr-in-natural/191470/4 "2016-11-15T14:15:41Z")
I tried running the ADABAS RENUMBER utility, but I get a S0C8 MODULE=\*UNKNOW ## Parameters: ADADBS RENUMBER FILES=250,640 A D A D B S: Error occurred during execution: ERROR-072, Unexpected nucleus response 148 ADABAS is not active I tried running this with the nucleus running, then tried running with the nucleus down and still get this error ---
**Author:** ![Sandy\_Spencer](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/sandy_spencer/32/1219_2.png) [@Sandy\_Spencer](https://techcommunity.softwareag.com/u/Sandy_Spencer)\ **Post date:** [November 15, 2016, 3:10pm UTC](https://techcommunity.softwareag.com/t/anyone-know-what-to-do-when-fnr-associated-with-a-file-in-adabas-different-than-fnr-in-natural/191470/5 "2016-11-15T15:10:56Z")
Finally noticed I had the wrong SVC coded in my parameters Now I have this error: ADADBS RENUMBER FILES=250,640 A D A D B S: Error occurred during execution: ERROR-072, Unexpected nucleus response 64 01- Invalid file number(s) ---
**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:** [November 16, 2016, 1:59am UTC](https://techcommunity.softwareag.com/t/anyone-know-what-to-do-when-fnr-associated-with-a-file-in-adabas-different-than-fnr-in-natural/191470/6 "2016-11-16T01:59:16Z")
is your database configured for file numbers greater than 255? Run an ADAREP REPORT NOFILE and look for "Maximum number of files = " in the general database information near the top of the report. ---
**Author:** ![Sandy\_Spencer](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/sandy_spencer/32/1219_2.png) [@Sandy\_Spencer](https://techcommunity.softwareag.com/u/Sandy_Spencer)\ **Post date:** [November 16, 2016, 8:42pm UTC](https://techcommunity.softwareag.com/t/anyone-know-what-to-do-when-fnr-associated-with-a-file-in-adabas-different-than-fnr-in-natural/191470/7 "2016-11-16T20:42:26Z")
Thank you Douglas! The database was configured with the default of MAXFILES=255. It took a while to figure out, but I was finally able to run an ADAORD REORDB on this region, reran the ADADBS RENUMBER FILES=250,640 and now: ## Parameters: ADADBS RENUMBER FILES=250,640 —\> File 250 renumbered to 640 A D A D B S Terminated normally 2016-11-16 14:35:58 ---
**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, 3:37pm UTC](https://techcommunity.softwareag.com/t/anyone-know-what-to-do-when-fnr-associated-with-a-file-in-adabas-different-than-fnr-in-natural/191470/8 "2021-04-02T15:37:18Z")