N2O & N2O/3GL V5.0.1 |
Current Fix Level: | D |
Current Zap Level: | N/A |
Current Version: | 5.0.1 |
Fixes
Sample NDV userexit(NDV-UX01) to prevent editing when using
FIX
EXPLANATION
A
The Userview field is blank on the Select Userview screen when N2O is executed under PREDICT V4.X against a 3.4.X FDIC.
Allow the detection of PREDICT version when more than 12 SAG products are installed.
Enhancement - Report (N2OVCCC) to display objects that are checked out to multiple change control numbers.
Enhancement - A statistical report of the number of objects migrated for a specific change control number.
N2OVRFY returns an error screen with the message 'Not a valid database type'.
B
N2O9460N loops when more than 12 Software AG products are installed.
The reject message in N2OUE12N can not be modified when MODE is equal to B. The default message is 'Request Denied by N-2-O Security'
During DB2 DBRM batch JCL generation, N2ODBRM incorrectly places a // before the 40th create package step. This causes all steps after the // to be ignored.
Objects can be archived multiple times by an interrupted multiple target event.
No field level help is available for the Event processed by Date report.
The Change Control field is blank on the Archive Version Summary report.
Checkout/Checkin validation is incorrect when performing a Batch Migration of an Extract Event that renames Objects on the to (target) environment. The message 'cannot be processed due to Checkout/Checkin violations' may be encountered.
C
NATURAL V4.1.2 Support.
The BATCH remote source compare does not display non-matching
that occur at the end of an object.
The Recovery from Archive is not defaulting the event sequence
to 1 for N2OPURGE recoveries.
Versions exceeding the Archive retention value(s), are not
deleted by the Archive Purge for multiple environments using a
single Archive Definition.
Performing a batch submission from the Select an Event screen
returns the message 'No Records found for listing' instead of the
'JCL has been submitted'.
Chronology of Events report has the screen title of Administrative
Reporting instead of Event Reporting.
N2OUML creates duplicate master records if the new location
already contains master records.
N2O Archive purge returns a '**NOT ON ARC**' message when an
ADABAS End of File (RC 3) is encountered.
Setting the variable INTERNAL-ID-YES to FALSE in N2OUE14N does not
pass the parameter INTERNAL-ID=N to SYSDICBE for non-extract
PREDICT migrations.
A NAT936 error occurs in N2O1981N line 4540 when checking-out
a PREDICT Object using a wildcard.
Batch Recovery events are not shown on the History of an object
report.
The N2O Checkout Utility does not permit the checkout of a DDM
with a DBID of 0.
The BATCH remote source compare utility loops.
Multiple users are able to authorize the same event at the same
time.
User exit 5 reject message is not displayed on the Checkout
utility wildcard object selection screen.
Can not select the version of an object purged and archived by
N2OPURGE and backed up to an archive purge backup dataset using
the recovery from archive backup utility.
Source compare utility displays matching lines as non-matching
on the last lines of a data area.
New userexit (N2OUED0N) to enable Source only move events
to delete Object code. Refer to Section V.3 in the N2O
Administrator Manual for more information.
Multiple concurrent N2OPURGEs of an object are not displayed on
the N2O Archive Version Summary report.
N2O Batch remote source compare incorrectly displays the top
matching line of data areas.
Cannot cancel the checkout of a DDM without using a wildcard in
the name.
Autorecovery does not work when N2OUE00N is used to override the
userid.
Natural Object Listing utility returns 'No Objects Found' when
archive version is selected from an object archive version list.
The Autocompile field can be set to a value other than NO in a
Migration Profile with an archive target environment if the Copy
a Migration Profile function is used.
The object name, type and mode is blank on the first page of a
BATCH execution of the Documentation tools NATURAL Object
Listing report.
A NAT3047 occurs in N2OMODST on line 470 when using the Change
an Event Status utility to change an Event with a large number
of selected objects.
A NAT1301 occurs on line 7100 in N2O3112N when the Minimum number
of lines for a MATCHING Block is set to 9.
When using the Checked Out Objects report to display all objects
checked out to a specific user id, SYSERR checkouts are ignored.
N2O source compare does not compare objects beginning with a #.
A NAT1108 error occurs in N2O1112N line 0800 when using N2OAPI3N
to copy an event.
N2OAPI3N produces events with a status of O (open).
The Documentation Toolbox, view objects function does not display
N2OPURGE archived objects when selecting an archive version by
a date range.
D
Due to file size limitations on many e-mail servers, we are making product manuals available for download from the Treehouse Web site. Additionally, Treehouse will mail a documentation CD to sites upon request.
Natural for Windows in a NDV/SPOD environment.
Requires NDV Service Pack NDV212P001 or higher.
Refer to Section II.6 of the N2O Administrator Manual for details.
N2O Autocompile causes a NAT1106 error to occur in CATALL when
it is invoked by NATURAL for Windows in a NDV/SPOD environment.
Prevent the creation of a migration profile with a target archive
environment that is not the archive defined to the source
environment.
Ad-hoc N2O environment reports, APIs (N2OREPI) that customers can
use to inquire on Environment Security setup environment.
Refer to Section V.7.4 of the N2O Administrator Manual for details.
#LAST-CARD not set to TRUE in N2OUERJE when submitting a job
that contains mostly replacement variables.
N2OAPI3N does not get the EXTRACT setting from the master event.
A NAT936 error occurs in N2ODYM1P on line 710 when using the
Documentation Tools - Map Listing report to view an archived map.
New program(N2OREPD) to interface with the Events Processed by
Date Report. This new program will allow sites to setup a
regularly scheduled batch job that will generate a report of all
Events processed for the previous day. For details on running
Event reports in batch, refer to the N2O User Manual
Section IV.3.10 Event Reporting in Batch.