Skip to Main Content
ADD A NEW IDEA

Natural (NAT)

Showing 18 of 402

NAT: Numeric target operands in SEPARATE statement desired

Unfortunately it is not possible with the SEPARATE statement to assign numeric values directly to numeric target fields. Message: NAT0240 Operand format invalid. Format A, B or U expected. So, sometimes laborious redefinitions are necessary. It wo...
Guest almost 3 years ago in Natural for z/OS / Natural (NAT) 1 Not in Plan

Provide SIZEOF( dataitem ) to determine the storage size of dataitem

Natural defines a set of "Application Related System Variables". To give an example: *LBOUND() and *UBOUND()can be used to determine the lower and upper bound of an array. If you have to answer the question "how much bytes are used for a dataitem?...
Christian Held almost 3 years ago in Natural for z/OS / Natural (NAT) 1 Not in Plan

FIND NUMBER RECORDS ...

Background: Currently, Natural has no "generic" way to find the number of records loaded in an Adabas file. Natural must always use the name of a file-specific descriptor which is "known to be populated for every record". e.g. FIND NUMBER EMPLOYES...
Guest almost 3 years ago in Natural for z/OS / Natural (NAT) 1 Not in Plan

Introduce User-Defined Data Types

There is a SAG strategie (or statement)called "ADABAS & NATURAL 2050+" Based on this I would like to have "User-Defined Data Types". I assume that the audience is familiar with this concept. When NATURAL was introduced it was called a 4-GL lan...
Christian Held almost 3 years ago in Natural for z/OS / Natural (NAT) 0 Not in Plan

(Super Natural) Enhance to handle file updates in transactions

In Super Natural we have a large number of files defined. We are constantly updating those file definitions. We add/update/delete fields with new releases of our application. Currently there is no elegant way to get the updates into Super Natural....
Guest almost 3 years ago in Natural for z/OS / Natural (NAT) 1 Not in Plan

Filler notation for WRITE WORK FILE

Enhancement Request: Please consider allowing filler notation (nX) with the WRITE WORK FILE statement. Example: WRITE WORK FILE 1 VARIABLE #VAR1 2X #VAR2 5X #VAR3 Reason: Filler notation is intuitive and gives a consistent feel to the language syn...
Guest almost 3 years ago in Natural for z/OS / Natural (NAT) 1 Not in Plan

Allow Edit Masks to be named constants

Natural provide the "Edit Mask"-feature which is most useful. I would like to see an improvement in using this feature. Currently, the Edit Mask must explicitly specified when used. If you have big applications the used Edit Mask are dispersed in ...
Christian Held almost 3 years ago in Natural for z/OS / Natural (NAT) 1 Not in Plan

Allow Edit-Mask Left & Right on MOVE EDITED

MOVE EDITED only permits 1 Edit-Mask on the left or right hand side. It would save many lines-of-code if 2 Edit-Masks were allowed, left AND right.Effectively, MOVE EDITED is an Alpha Move:one side is alpha & the Edit-Mask reduces the other si...
Guest almost 3 years ago in Natural for z/OS / Natural (NAT) 0 Not in Plan