Frequently Asked Questions
If you have any questions not mentioned within this document, please send us a mail or select the Contact button at the top of the public area pages to get our address and fax number.
Keywords used within this document (Please use search facility of your browser):
| 3 | 3GL // 390 |
| A | ADABAS license // ADABAS SVC // address // After action; Userexit |
| B | Backout // Backout/Backin // Base // Batch // Before action; Userexit // Browse // buffer flush // Build Package action |
| C | C1DEFLTS // C1G0216E // Changes in NATURAL sources // Check // CICS // CommandNATURAL // Communication // compare // Comparison // Compatibility // Component list // Conversion of names element/member // CSP |
| D | database; multiple // Database is currently not active // DBID // DDM // Definition // Delete // Delta // Demo // Disk // Display // Display of message dataset // DSNAME OR FILE SPECIFIED IS INVALID OR NOT FOUND // DUMMY // Dynalloc failed... |
| E | E/NAT system file // edit // Editor // Element // e-mail address // ENABLE BACKOUT // Environment // Execution error |
| F | Fax // from |
| G | GENERATE |
| I | I0911 // I0914 // Internet |
| L | length // Library // Line numbers // lock // Logon |
| M | MAXCL // MCT // Member // Member Conversion Table // Message dataset // Mix of 3GL and NATURAL // MOVE; across ADABAS SVCs; across system files // Multiple databases // MVS |
| N | N000nnn // Name restrictions // NAT0082 // NAT0856 // NAT1029 // NAT3022 // NAT3148 // NATURAL buffer pool // NATURAL commands // NATURAL for DB2 // NATURAL for VSAM // NATURAL mixed with 3GL // NATURAL nucleus // NATURAL parameter // NATURAL sources; Changes; Editing; Storing; Version supported // NATURAL Version supported // NDVKZBF // NDVMSGS |
| O | Operating system // OPRB // OS/390 |
| P | Package // Package processing // parallel edit // PATH // Performance // Phone // PREDICT Ids longer than 10 characters; necessary to use E/NAT // PREDICT Active References // PREDICT XREF // Processor // Product information |
| R | Region size // RETRIEVE // Run |
| S | Security // Some panel variables are missing // steplib // support // SVC // System file |
| T | Test installation // TF // to // Too many NATURAL program calls // TP monitor // TSO NDVMSGS // TSO region size // TYPE |
| U | Upward compatibility // Userexit // UserId // userid.ENAT.DUMMY // USRnnnnN |
| V | Version // Version comparison // Version of NATURAL source // Version of NATURAL system // VIO |
| W | Windows 95 // Windows NT // World Wide Web // WWW |
Keys: Demo, Disk, Windows 95, Windows NT
An E/NAT demo disk for Windows is available. This disk contains a PowerPoint demo of E/NAT Version 2.2. The PowerPoint projector (runtime) is not included. Free download is available at http://www.microsoft.com.
If you have Powerpoint 4.0 or 7.0 or the viewer available you may download the zipped PPT file here.
Keys: Product information, Internet, WWW, World Wide Web
Yes. A PI sheet for E/NAT Version 2.2 is available in English upon request. Via the World Wide Web you can access the English and a German version using the following address:
Product Information (English) Produkt Information (German)
To print and/or view it in high quality you may download the PDF version
Keys: Test installation
Yes. Contact us. Please prepare the following information needed:
Please use our request form.
Keys: Communication, Phone, Fax, e-mail, support, address
If you have any question not answered here please use one of the following ways to contact us:
Head office in Germany:
Keys: CICS, TP monitor, GENERATE, NATURAL sources; Editing, Editor, steplib
No. NATURAL sources will be edited under CICS (or any other TP interface e.g. TSO) within the original NATURAL editors.
Working with the TSO Interface:
You have to switch between CICS and TSO only when you have FINISHED your
development. You then use Endevor to ADD the NATURAL source to Endevor. You may use
DELETE INPUT SOURCE to delete the source in the NATURAL environment. GENERATE of
Endevor produces the NATURAL object module in the NATURAL library defined for the
Environment/Stage/System combination (usually a NATURAL steplib).
Working with the E/NAT TP
Interface:
E/NAT version 2.2 comes with the TP Interface (TPI). Using E/NAT TPI you are able
to perform Endevor actions from within your TP monitor (e.g. CICS). Simply enter
"ENAT" in the NATURAL command line to invoke the TPI with NATURAL's
look-and-feel.
This offers a wide range of the Endevor actions to the NATURAL application
programmers. In addition to the TSO and batch interfaces you will get interfaces for all
TP monitors supported by NATURAL on MVS. See E/NAT Product Information for more details.
Keys: NATURAL sources; Editing, Editor, Check, Run
Because NATURAL offers more than only an editor for developers. They may "check" and "run" their programs. This is a major difference to 3GL sources. It makes therefore no sense to edit NATURAL sources outside NATURAL.
Using the TP Interface, there will be no need to use QuickEdit for NATURAL sources.
Keys: NATURAL sources; Storing, Base, Delta, Version comparison, Comparison
Base and Deltas reside within Endevor (like 3GL). This offers the complete functionality like comparison of versions and compression.
Keys: NATURAL sources, Version of NATURAL source
E/NAT supports all version 2, version 3 and version 4 sources of NATURAL ("reporting mode" and "structured mode"). NATURAL sources in version 1.x format should be SAVEd before ADDing them to Endevor (to get the directory information of NATURAL version 2 or higher).
Keys: NATURAL version, Version of NATURAL system
E/NAT runs with all NATURAL versions supported by Software AG. NATURAL 2.3 or later is necessary to execute E/NAT 2.2. The sources of NATURAL objects may be stored in any NATURAL 2, 3 or 4 format.
Keys: NATURAL sources; Changes, Changes in NATURAL sources, NATURAL sources; Storing, Line numbers, Browse, Upward compatibility, Compatibility
E/NAT sources are stored in Endevor in two ways: a readable format and in an internal format. The readable format does not contain any line numbers so that you can see source changes line by line (renumbering does not lead to a lot of changes).
Each NATURAL source is stored twice but as one element within Endevor. The first part is for browsing purposes and the second one for technical handling (the second part is used by E/NAT to ensure upward compatibility with future NATURAL versions). The two source formats are delimited by three lines.
Keys: Component list, PREDICT XREF, PREDICT Active References, Userexit
No. Component lists are not stored within Endevor / E/NAT. What we offer is the usage of the PREDICT Active References to select dependent NATURAL and/or PREDICT members. PREDICT XREFs are maintained in all environments (within PREDICT).
A customer in Germany builds component lists within Endevor by using E/NAT userexits to execute special routines.
Keys: NATURAL for DB2, NATURAL for VSAM, ADABAS license
In principle yes. The major problem
is, that in general NATURAL DB2 users have only a limited ADABAS license. To store NATURAL
sources in the NATURAL system file and to hold E/NATs tables in the E/NAT system file a
full ADABAS license is necessary. With a full ADABAS license NATURAL DB2 (and NATURAL
VSAM) can be used together with E/NAT.
In case your site currently owns a limited ADABAS license only, please contact
us to assist you in getting special pricing from Software AG.
The generation of DBRMs using the SYSDB2 application is possible. Simply use the flexible processors and our NATURAL command handler. If you need more details, please contact E/NAT support.
Keys: PREDICT;necessary to use E/NAT, DDM
No. If you have no need to manage PREDICT objects (including DDMs) you do not need PREDICT.
Keys: Name restrictions, PREDICT; Ids longer than 10 characters, DDM, MCT, Member Conversion Table
No. A conversion table is available which enables you to convert long PREDICT names (ids) into short element names for Endevor and vice versa. Within Endevor you'll see the converted short names (max. 10 characters). Using this Member Conversion Table (MCT) you'll be able to handle all PREDICT objects. The table may be unloaded, loaded and maintained online using comfortable functions. If a PREDICT object is added for which no entry in MCT exists, the user is prompted to enter a short name. The short name entered is stored in the MCT which ensures that no further user entry will be necessary for this element. In addition, import/export utilities and an API are available.
Keys: Multiple databases, SVC, ADABAS SVC, E/NAT system file, System file
If you intend to install E/NAT on different databases you need to install the E/NAT NATURAL modules on each database. If you use the same FUSER system file for all databases, this is not necessary. If you use the same ADABAS SVC you need only one single E/NAT system file, if you use different ADABAS SVCs you need one system file per SVC. Each system file must contain the same information. Using Entire Network from Software AG allows you to manage all your logical and physical machines with one single E/NAT system file. Please contact us for special pricing by Software AG, in case you want a license of Entire Network limited to the use with E/NAT only.
Keys: PATH, definition
The PATH is used to put a name on the
FUSER/FDIC database id and file number settings. This is useful
because now you can enter
the path "DEV" or "PROD" and so on, instead of specifying all these
numbers when executing ADD / RETRIEVE actions.
In short: the PATH describes the system files to be used.
If an application programmer needs a source he usually knows that he wants the
"PROD" version but not the FUSER/FDIC settings. Same problem when UPDATE is
performed. He knows that he needs to add it to "DEV" or "TEST".
Another advantage is, that there is no chance to use the correct FUSER but the wrong FDIC.
This is important when using the "XREF" functions. If the FUSER and FDIC are not
corresponding, a user will not recognize this (he gets his correct source but the wrong dependencies if he for example uses FUSER dbid/fnr for "DEV" but FDIC dbid/fnr
for "PROD".
********************
* Env/Stage/System *-------------+
******************** | ****************
V +----->* FUSER DBID/FNR *
******************* | ****************
* E/NAT ID *------+
******************* | ****************
^ +----->* FDIC DBID/FNR *
******************** | ****************
* PATH *-------------+
********************
|----- User -------|------------------ Administrator --------------------|
Keys: NATURAL Security
No, you will not loose any functionality. The only difference is that you have to install E/NAT in library SYSTEM (or the library associated with *STEPLIB) instead of a dedicated E/NAT library (default "EN").
Keys: NATURAL commands, processor
Yes. Within a processor you may
execute additional NATURAL commands using the active NATURAL copy. There is no need to
start NATURAL within an additional step. E/NAT supports the setting of FUSER and FDIC to a
specific environment or PATH (using SET PATH PATH=DEV). You
may use Endevor variables for these settings (for example SET ENV
ENV=&C1EN STAGE=&C1S# SYSTEM=&C1SY).
To execute a simple NATURAL command ("LIST *")
following the GENERATE process you would code the following lines within the processor:
GENERATE
COMMAND NATURAL
LIST *
In case you need to execute additional NATURAL commands in a different step, this is possible, too. This will cause no performance overhead, because the built-in features of E/NAT enable you to use the same active NATURAL copy within the same job in different steps.
Keys: NATURAL source, lock, edit, parallel edit
Sources are stored in
Endevor and
are (usually) available to NATURAL users if they use Endevor functions (RETRIEVE) only.
Endevor sets a SIGNOUT flag to prevent from unintended parallel changes. Within the
NATURAL environment there is no lock mechanism added by E/NAT. We propose to develop
NATURAL objects in user libraries (protected by NATURAL Security) instead of shared
application libraries. Otherwise you should use NATURAL ISPF to lock sources and to
prevent from parallel EDITs.
Outside NATURAL the sources are controlled by Endevor. We suggest to use the
built-in SIGNOUT/SIGNIN technique of Endevor and to delete the sources from the NATURAL
user library during ADD/UPDATE using the Endevor option DELETE INPUT SOURCE. By doing
this, there will be no need to lock sources in NATURAL.
In case of parallel development, the Endevor PDM option will assist you in
merging versions or variants of a NATURAL source.
Keys: NAT0082, N000nnn, USRnnnnN, Execution error
If you get errors like N0082 from within NATURAL on module names like N000... or USRnnnnN please check if there are old NATURAL system modules located in NATURAL library SYSTEM (*STEPLIB), any steplib defined to NATURAL security, library EN or any library you are working with during action processing.
Ensure that only the newest versions of the NATURAL user exit modules (as described in the Installation Manual) are active when using E/NAT.
Keys: I0911, Dynalloc failed..., Execution error, TSO region size, region size
If you get this error please check if your TSO region size is set to at least 6MB (6144). E/NAT requires a minimum of 6 MB region size. However, if you are working in split screen mode and for example editing a large member on the other logical screen, you may need to increase the region size again.
Keys: I0914, Some panel variables are missing, NDVKZBF, CSP, C1DEFLTS, Execution error
If you get this error please check if you have installed the Endevor CSP interface. Check C1DEFLTS if there is a password active for CSP (even if not needed) and remove it. E/NAT is not working together with the CSP interface.
Keys: C1G0216E, DSNAME OR FILE SPECIFIED IS INVALID OR NOT FOUND, DUMMY, userid.ENAT.DUMMY, Execution error, VIO
Please ensure that you are not using UNIT=VIO for this dataset. Change it to UNIT=SYSDA.
Keys: Environment panel, E/NAT parameters, selection 4.N
Check if you have activated the Endevor exits using example job BC1JXITS and that this definition is located in the corresponding Endevor library. Ensure that enough TSO region size is allocated.
Keys: Multiple databases, SVC, ADABAS SVC, E/NAT system file, System file, DBID, Environment, TF
Actually this special situation can be handled in the following way only:
Add the NATURAL parameter "(TF=(250,250,enatdbid,enatfnr)" as dynamic parameter for each entry in the table of physical environments (selection 2), or use the NTTF macro to apply this seeting. Replace enatdbid and enatfnr with the valid ids of the database and file number of the E/NAT system file for each physical environment.
Note: the TF parameter must be the last entry for the dynamic parameters.
Keys: NAT3148, Database is currently not active , Execution error
If you get this error sometimes during action processing when working with different ADABAS SVCs please see: How can I define different Environments with different ADABAS SVCs and different DBIDs of the E/NAT system file to E/NAT.
Keys: NAT3022, Database is currently not active, Execution error
If you get this error sometimes during action processing when working with different ADABAS SVCs please see: How can I define different Environments with different ADABAS SVCs and different DBIDs of the E/NAT system file to E/NAT.
Keys: NAT1029, Too many NATURAL program calls, Execution error, MAXCL, NATURAL parameter
Increase the NATURAL parameter MAXCL or set it to 0.
Keys: Backout/Backin, ENABLE BACKOUT, Execution error
If you use Endevor version 3.7.1 it is currently not possible to process packages with ENABLE BACKOUT set to "Y". This error is caused by Endevor because no information is passed to Endevor exit 7 (package processing). The latest problem number is 5220312. Some more problem numbers exist. This problem was fixed with Endevor 3.7.2.
Keys: panel, garbage, Execution error
Apply the following PTFs (IBM) to fix the problem and re-IPL your system:
Keys: Batch, UserId, NAT0856, Execution Error
E/NAT always starts a Natural session with AUTO=ON. When a batch job is executed, Natural is getting the Jobname as the UserId. This may lead to the error message NAT0856, since the user "Jobname" is not defined in Natural Security.
To solve this problem: Edit the NATOS module and include the USERID=YES in NTOS macro. Now the userid for batch job is being taken from RACF.
Keys: MVS, Operating System, OS, 390
Yes. E/NAT runs on MVS version 4.2.2 and above and on OS/390 release 1.1 and above.
Keys: TYPE, length, compare, from, to
The Endevor types have to be defined using the following element options:
| Source length | 255 |
| Compare from | 1 |
| Compare to | 255 |
| Source length | 5000 |
| Compare from | 1 |
| Compare to | 5000 |
Keys: Delete, source, OPRB
NATURAL 2.2 ONLY: In case the sources of a DELETE or MOVE action are not deleted
from the NATURAL FUSER system file and no error is returned, please check
if the parameter OPRB is set to NOOPEN. OPRB=NOOPEN must be set as NATURAL
parameter and - if installed - in the --> NATURAL Security profile of
the libraries affected.
Otherwise NATURAL Security will issue OPen commands to ADABAS during execution
of LOGON commands. In this case, the first OP command gets a response code 9
with subcode 63 from ADABAS (user not at ET status). Due to a problem in NATURAL
Security, this response code is NOT reported to the application, but all data
(including the already deleted records) is implicitly backed out from the
database. This problem was reported to Software AG in Germany. Please refer to
SAG-D request #331550 for more details.
Keys: NDVMSGS, Display of message dataset, Message dataset; Display, TSO NDVMSGS
Enter "TSO NDVMSGS". If necessary you may define a PF key with this string.
Keys: Userexit, Logon, Library, Security, Before action; Userexit, After action; Userexit, Command; NATURAL, NATURAL commands, Conversion of names element/member, Member, Element
E/NAT offers some userexits (NATURAL subprograms) which are executed in the following situations:
In addition it is possible to execute NATURAL commands (or programs) from within a processor (DELETE / GENERATE).
These features enable users to include their own application logic when processing NATURAL and/or PREDICT elements. The before and after action userexits may be used to execute NATURAL code for 3GL or other types too.
When using E/NATs userexits most of the information provided by the Endevor userexits is available within parameter data areas.
Keys: Performance, system file, NATURAL nucleus, MOVE; across system files, database; multiple
No. Because of the optimized logic of E/NAT there is no need to end and restart the NATURAL nucleus when moving elements from one system file to another.
Keys: Performance, System file, NATURAL nucleus, MOVE; across ADABAS SVCs, SVC, ADABAS SVC
Yes. In this situation NATURAL is
ended and restarted element by element with the new parameters. This decreases performance
and backout functionality is not available (because it is not possible to access both
ADABAS SVCs at the same time). To bypass this you may define a pre-stage on the target SVC
and move from there to the final stage e.g. using MOVE or TRANSFER actions. Now backout
functionality is available for the final stage.
As an alternative, you might use Entire Network to move elements across SVCs,
LPARs or physical machines.
Keys: Mix of 3GL and NATURAL, 3GL, NATURAL mixed with 3GL, Package
Yes. There is no restriction in mixing 3GL, NATURAL and other objects within one single package.
Keys: Mix of 3GL and NATURAL, 3GL, NATURAL mixed with 3GL, Package, Backout, ENABLE BACKOUT
Yes. Mixed packages are possible and may be specified with the ENABLE BACKOUT option of Endevor. E/NAT stores backout information in the system file and allows to backout all changes made. Please note, that backout functionality is not available for PREDICT objects.
Keys: NATURAL buffer pool, buffer flush
Yes, E/NAT performs a buffer flush in case of a backout. To get full advantage of this feature you should use a global buffer pool. The buffer flush is done for each single backed out member. Your NATURAL modules not affected by this backout (not included in this package) remain active in the buffer pool.
Keys: Package, Backout
The backout is prepared during package
processing with ENABLE BACKOUT set to Y. If a processor (DELETE, GENERATE, MOVE) is
executed E/NAT automatically saves the old version of each object in the target
environment before overwriting or deleting it.
If you decide to backout this package, each NATURAL member (object) to be backed out is
saved again (to allow later backin) and the original status is rebuilt (the old module is
restored or the new one is deleted if it did not exist before). During this process (which
is very fast) each single element is flushed from the NATURAL buffer pool.
If you decide to backin the package later this is supported, too.
Note: BACKOUT/BACKIN does not regenerate (CAT, STOW) your NATURAL modules.
It exchanges actual object versions by saved object versions only. This process is very
fast and save. It prevents from any trouble that would be caused by regeneration of old
NATURAL objects (e.g. syntax checker enhancements, SIZE problems and so on). You will not
loose any flexibility when performing a backout. You may decide to restore the new status
again. This could be repeated as often as you want.
Keys: PREDICT XREF, PREDICT Active References
Using ADD/UPDATE functions of Endevor there is a new option "INCLUDE PREDICT XREF" available. If you choose to automatically include all referenced objects using the information stored in the PREDICT Active References data you will get included all objects depending on the selected one automatically.
Example:
If you select a GDA to be added, all NATURAL members referencing
this GDA are included
automatically. The GENERATE process ensures that all affected programs are
recataloged.
Keys: Version, RETRIEVE
Yes. All versions stored in Endevor may be selected and RETRIEVEd back to NATURAL / PREDICT. For PREDICT objects, this functionality is limited to the backward compatibility of the SYSDICBE utility.