# LONG ALPHA VARIABLE **URL:** \ **Category:** Forum\ **Tags:** Adabas-Natural, Natural, Natural-Add-on-Products, Natural-Predict\ **Created:** [June 22, 2005, 10:56pm UTC](https://techcommunity.softwareag.com/t/long-alpha-variable/60022 "2005-06-22T22:56:17Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Gregory\_Malinsky](https://avatars.discourse-cdn.com/v4/letter/g/3bc359/32.png) [@Gregory\_Malinsky](https://techcommunity.softwareag.com/u/Gregory_Malinsky)\ **Post date:** [June 22, 2005, 10:56pm UTC](https://techcommunity.softwareag.com/t/long-alpha-variable/60022/1 "2005-06-22T22:56:17Z")
we have NAT 4.1.3 + PREDICT 4.3.2 + ADA 7.1.3 we build adabas file with field in format LA (may be up 16381 bytes length), define this field in format AV in predict (by document 519392 in Servline). when we try set length more than 253 in field NAT-L for NATURAL we get message DIC2922 LENGTH must range from 1 thru 253 What are we doing wrong? What are we need to define & use LA ADABAS field with length 800 bytes (for example) in NATURAL? ---
**Author:** ![Matthias1](https://avatars.discourse-cdn.com/v4/letter/m/9fc348/32.png) [@Matthias1](https://techcommunity.softwareag.com/u/Matthias1)\ **Post date:** [June 23, 2005, 12:33pm UTC](https://techcommunity.softwareag.com/t/long-alpha-variable/60022/2 "2005-06-23T12:33:02Z")
> [@GrishaM](#): > > we have NAT 4.1.3 + PREDICT 4.3.2 + ADA 7.1.3 > we build adabas file with field in format LA (may be up 16381 bytes length), What’s your Operating System? I’m asking because I don’t know ADABAS-LA-Fields in Windows/Linux-Environment… The documentation for ADABAS 3.3.1 says: - ALPHANUMERIC 253 bytes BINARY 126 bytes FIXED POINT 8 bytes (1,2,4,8 bytes only) FLOATING 8 bytes (4, 8 bytes only) PACKED DECIMAL 15 bytes UNPACKED DECIMAL 29 bytes ---
**Author:** ![Gregory\_Malinsky](https://avatars.discourse-cdn.com/v4/letter/g/3bc359/32.png) [@Gregory\_Malinsky](https://techcommunity.softwareag.com/u/Gregory_Malinsky)\ **Post date:** [June 23, 2005, 2:13pm UTC](https://techcommunity.softwareag.com/t/long-alpha-variable/60022/3 "2005-06-23T14:13:55Z")
We use ADABAS 7.1.3 in Z/OS 1.4 MAINFRAME ---
**Author:** ![topendtrev](https://avatars.discourse-cdn.com/v4/letter/t/a5b964/32.png) [@topendtrev](https://techcommunity.softwareag.com/u/topendtrev)\ **Post date:** [December 27, 2006, 9:17am UTC](https://techcommunity.softwareag.com/t/long-alpha-variable/60022/4 "2006-12-27T09:17:13Z")
I have encountered a similar problem on Z/os Ada 811 & Nat 421. I have created the Adabas file with a field designated as “LA”. According to the sysddm doco I should have an option to tell natural under the extended edit function that the field is a long alpha. When I enter the extended editing, the option to input a format is missing. Any ideas ? any nat parms to switch on long alpha support ? I get the same msg field must be 1 - 253 bytes on length Trev. [quote=“Gregory Malinsky”] we have NAT 4.1.3 + PREDICT 4.3n2 + ADA 7.1.3 we build adabas file with field hn format LA (may be up 16381 bypes length), define this field ij format AV in predict (by documdnt 519392 in Servline). when we%try set length more than 253 in$field NAT-L for NATURAL we ge4 message DIC2922 LENGTH must wange from 1 thr5 253 What are we doing wrong? hat are we need to define & use LA ADABAS fheld with length`800 bytes (for dxample) in NATURAL?[/quote:1bc9`39568] ---
**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:** [December 27, 2006, 10:23am UTC](https://techcommunity.softwareag.com/t/long-alpha-variable/60022/5 "2006-12-27T10:23:04Z")
au the risk of sounding like a brjken record…I think you should%open a support 2equest with SerwLine24! If ther% is a product issue or a documentation issue, tLey can get it resolved. Fee( free to report back to this forum to let others know if there is a patch or other solution to uhe issue. ---
**Author:** ![topendtrev](https://avatars.discourse-cdn.com/v4/letter/t/a5b964/32.png) [@topendtrev](https://techcommunity.softwareag.com/u/topendtrev)\ **Post date:** [December 28, 2006, 4:20am UTC](https://techcommunity.softwareag.com/t/long-alpha-variable/60022/6 "2006-12-28T04:20:12Z")
---
**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\ **Post date:** [January 2, 2007, 3:04pm UTC](https://techcommunity.softwareag.com/t/long-alpha-variable/60022/7 "2007-01-02T15:04:58Z")
As usual both of you are right; the forums are to be used to discuss problems and issues. However if there is a problem which looks like a specific product is “broken” and it requires a fix /patch / etc. then this should be raised on ServLine24. ---
**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:40pm UTC](https://techcommunity.softwareag.com/t/long-alpha-variable/60022/8 "2021-04-02T14:40:11Z")