# ADADCU utility - File Created in EBCDIC for format is not compatible

**URL:** <https://techcommunity.softwareag.com/t/adadcu-utility-file-created-in-ebcdic-for-format-is-not-compatible/204219>\
**Category:** Forum\
**Tags:** Adabas-Natural, Adabas, Adabas-Basics-on-Linux-Unix-Windows, Adabas-on-Windows-UNIX, Adabas-on-Linux, Adabas-Natural-Cloud\
**Created:** [June 18, 2019, 1:02pm UTC](https://techcommunity.softwareag.com/t/adadcu-utility-file-created-in-ebcdic-for-format-is-not-compatible/204219 "2019-06-18T13:02:06Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sindhu\_Jose](https://avatars.discourse-cdn.com/v4/letter/s/f0a364/32.png) [@Sindhu\_Jose](https://techcommunity.softwareag.com/u/Sindhu_Jose)\
**Post date:** [June 18, 2019, 1:02pm UTC](https://techcommunity.softwareag.com/t/adadcu-utility-file-created-in-ebcdic-for-format-is-not-compatible/204219/1 "2019-06-18T13:02:06Z")

</div>

Hello Team,

Was trying to create a mainframe file using Adabas Manager 8.4, the file seems to be not completely in EBCDIC format. Steps Followed.

1. Downloaded community edition of ADABAS and Natural for Docker.
2. Executed ADAULD utility for the sample EMPLOYEES file i.e DBID=12, FILE=11.
3. Executed ADADCU utility with the options  
RECORD\_STRUCTURE=RDW,TARGET\_ARCHITECTURE = (EBCDIC, IBM\_370\_FLOATING, HIGH\_ORDER\_BYTE\_FIRST).

The Copy of the output file is attached. It contains Alphanumeric Characters in addition to EBCDIC ones.

Pleas guide

[MFEmp.txt](https://techcommunity.softwareag.com/uploads/short-url/kvj7d31jDVvjZrz9wTyHCFWJCEa.txt) (1.15 MB)

---

<div class="post-metadata">

**Author:** ![Marbod\_Mueller1](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/marbod_mueller1/32/97_2.png) [@Marbod\_Mueller1](https://techcommunity.softwareag.com/u/Marbod_Mueller1)\
**Post date:** [June 18, 2019, 1:48pm UTC](https://techcommunity.softwareag.com/t/adadcu-utility-file-created-in-ebcdic-for-format-is-not-compatible/204219/2 "2019-06-18T13:48:22Z")

</div>

Hello Sindhu,  
Specifying EBCDIC in TARGET\_ARCHITECTURE only concerns ALPHA format fields (A). The Wide character fields (W) will not be converted to EBCDIC. Simlilarly, numeric fields with the exception of format U.

There are two sample EMPLOYEES files. The older one does not have W fields and the alphanumeric data happens to be stored in upper case.  
When looking at the attached file it seems that you have used the new file.

Bear in mind that the record is formatted depending on the Field description (FDT) of the file.

Please also note that the Adabas Mainframe distribution also includes both sample Employees files.

Kind regards,  
Marbod Mueller

---

<div class="post-metadata">

**Author:** ![Sindhu\_Jose](https://avatars.discourse-cdn.com/v4/letter/s/f0a364/32.png) [@Sindhu\_Jose](https://techcommunity.softwareag.com/u/Sindhu_Jose)\
**Post date:** [June 18, 2019, 2:03pm UTC](https://techcommunity.softwareag.com/t/adadcu-utility-file-created-in-ebcdic-for-format-is-not-compatible/204219/3 "2019-06-18T14:03:25Z")

</div>

Thanks a lot Marbod Mueller for the quick response !!!

So is there a way to Convert “W” fields also to EBCDIC ?

Regards,  
Sindhu

---

<div class="post-metadata">

**Author:** ![Marbod\_Mueller1](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/marbod_mueller1/32/97_2.png) [@Marbod\_Mueller1](https://techcommunity.softwareag.com/u/Marbod_Mueller1)\
**Post date:** [June 18, 2019, 2:27pm UTC](https://techcommunity.softwareag.com/t/adadcu-utility-file-created-in-ebcdic-for-format-is-not-compatible/204219/4 "2019-06-18T14:27:42Z")

</div>

You can do this with ADACMP on the mainframe.

There are parameters that tell how the alpha or wide field is encoded in the input. If the output encoding of ADADCU for W fields is UTF-8 you can use UACODE=4091 and FACODE=37 for EBCDIC Alpha fields.  
But it is possible that W fields contain non-Latin characters that will result in non-translatable character replacement in the mainframe database.  
But you will have to adapt the LUW-FDT and change the W fields to A for the mainframe FDT.

Preferably you would keep the W fields and specify UWCODE=4091 and FWCODE=4095 and get the W fields loaded in Unicode (UTF-16) encoding on the mainframe.

[http://techcommunity.softwareag.com/ecosystem/documentation/adabas/ada842mfr/util/adacmp-compress.htm#adacmp-compress\_optparm](http://techcommunity.softwareag.com/ecosystem/documentation/adabas/ada842mfr/util/adacmp-compress.htm#adacmp-compress_optparm)

Kind regards,  
Marbod Mueller

---

<div class="post-metadata">

**Author:** ![anon72918622](https://avatars.discourse-cdn.com/v4/letter/a/ecae2f/32.png) [@anon72918622](https://techcommunity.softwareag.com/u/anon72918622)\
**Post date:** [June 19, 2019, 9:50am UTC](https://techcommunity.softwareag.com/t/adadcu-utility-file-created-in-ebcdic-for-format-is-not-compatible/204219/5 "2019-06-19T09:50:52Z")

</div>

Hi,

Please keep in mind the Adabas Manager supports currently only Adabas on LUW.  
For Adabas on mainframe please use AOS (chargeable option) or the Adabas utilities.

Regards,  
Wolfgang

---

<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, 3:42pm UTC](https://techcommunity.softwareag.com/t/adadcu-utility-file-created-in-ebcdic-for-format-is-not-compatible/204219/6 "2021-04-02T15:42:58Z")

</div>


