Skip to Main Content
Due to the recent acquisition by IBM, the Adabas & Natural Ideas Portal does not contain ideas from products ApplinX and EntireX any longer. Please refer to the IBM Ideas Portal for these products from now on (IBMid required). Existing content will be migrated during the next few weeks.
ADD A NEW IDEA

Natural (NAT)

Showing 23 of 359

Automatic verification of a zaps Pre-req.

Natural and other product zaps regularly have prerequisites for example; * *+ZAP:NA93002 * -------- (C) Software AG, Darmstadt/Germany, 2012 -------- * ---------------- Release Date: 01.Nov.2012 --------------- * PRODUCT: NAT823 * PREREQ. : NA9222...
Guest almost 4 years ago in Natural for z/OS / Natural (NAT) 1 Not in Plan

Allow for I8 datatype

OpenSystems hardware has it for a long time, z/Series has it for quite a while now, so by now there is no platform NOT natively supporting 64-bit arithmetic. So please introduce an I8 datatype into Natural - on all supported platforms (and NOC as ...
Wolfgang Winter almost 4 years ago in Natural for z/OS / Natural (NAT) / Programing Syntax (Cross platforms) 1 Future consideration

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 4 years ago in Natural for z/OS / Natural (NAT) 0 Not in Plan

Natural Buffer Pool (SYSBPM): TotalUC#2 new Use count field for depicting Level-1 executions of natural objects

Under Natural Buffer Pool (SYSBPM), we noticed while investigating a performance issue in production that when a Natural Object has multi-level, the TotalUC value for the primary object is a cumulative sum of all the sub-routines being called. Th...
Zaffer Khan about 1 year ago in Natural for z/OS / Natural (NAT) 4 Future consideration

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 4 years ago in Natural for z/OS / Natural (NAT) 1 Not in Plan

Natural RPC - Buffer pool closing procedure

Having defined a NTBPI macro with: GBP, SEQ=0 and LBP, SEQ=1, if GBP is closed while the Natural sesión is active, Natural attemps to connect the LBP. But for a Natural RPC it doesn't work in the same way. In our installation we have configured AL...
Jose Dario Rudz 5 months ago in Natural for z/OS / Natural (NAT) 1 Not in Plan

Enhance Hyperdescriptor Exit for Natural Mainframe Server to cover other areas too

With Natural 9.1.2 we introduced a hyperdescriptor exit NATHX15 to improve the performance when reading Natural object names on a Mainframe server.This exit was enhanced with Natural 9.2.1 to also fast read Natural library names. It should be cons...
Stefan Diehl 8 months ago in Natural for z/OS / Natural (NAT) / Natural Development Server (NDV) / Utilities 0 Planned

Create a user exit in SYSEXT to perform a SCAN across all FUSER or FNAT

Create a user exit in SYSEXT to perform a SCAN across all FUSER or FNAT .It can be similar to the existing SCAN tool. The replace function is not required and may be a bit dangerous. This way we can search all source code for a specific string, be...
Dana Sherbondy about 1 year ago in Natural for z/OS / Natural (NAT) / Utilities 2 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 4 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 4 years ago in Natural for z/OS / Natural (NAT) 1 Not in Plan