NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE:  NN30D.EXE; NetWare Navigator 3.0-Update D
README FOR:  NN30D.EXE

NOVELL PRODUCTS and VERSIONS:
NetWare Navigator 3.0

ABSTRACT:

NetWare Navigator 3.0D (NN) provides enhancements and fixes to
the 3.0 release. Since the 3.0D release is cumulative, it
includes all enhancements and fixes in the previous NetWire
releases.  Follow all of the steps listed under INSTALLATION
INSTRUCTIONS.  Installation requires distributing packages to
Distribution Servers, Staging Servers and clients. IMPORTANT:
NN30D.EXE is only for Navigator 3.00, it is NOT for Navigator
3.01.




-----------------------------------------------------------------
 DISCLAIMER
 THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO
NOVELL.  NOVELL
 MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. 
HOWEVER, THE
 INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION
ONLY.  NOVELL
 MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS
INFORMATION.

-----------------------------------------------------------------


SYMPTOM:

1. Distributions from the Distribution Server to a Staging Server
might not occur if the Staging Server was not responding at the
time the distribution attempt was made.

 2. Unable to multi-select items in the Distribution List Editor
and Contents List Editor, at the Administration Console.

 3. An OS/2 client could not receive a file from a Pull
Distribution if a Target Directory, other than the Navigator
default Receive Path, was specified.  Also, the following message
could be received at the Distribution Server: SJOBDMGR: Receiving
errors from <clientname> - <x> files.  (No problem with Push
Distributions)

 4. Scripts were executed twice (if a contents list was not
included) at DOS and OS/2 client workstations on Push
distributions, regardless of their success or failure.

 5. An error message stating that there was a failure to connect
from DJOBSCHD or SJOBDMGR. (also indicated in Status information
for the distribution job on the Navigator Administration console)

 6. Feedback on problem jobs were not seen at the Administration
Console
 (Status/Problem Jobs), and the Distribution Server NLMs reported
an error trying to open REPORTS.DAT.

 7. If a package was distributed with a script and then the
script was mistakenly deleted at the target, the target could not
change to a status of complete.

 8. No feedback was reported to the Administration Console, if
the Distribution Server was not responding at the time that
feedback was being reported.

 9. Modifying OS/2 scheduled events at the command line did not
always modify the events correctly.

 10. The file parameter for the OS/2 NNEXTRCT command was
ignored.

 11. In some cases, jobs distributed without a script were unable
to change to a Completed Jobs status.

 12. NWSDSYS appeared to connect numerous times, or a
"connections exhausted" message received.

 13. If the Distribution Server Name was more than 8 characters,
job status at the Administration Console did not receive the
feedback message that a package was received at a client.

 14. System Error SYS3175, when trying to add the eighth event to
the OS/2 Scheduler.

 15. Script log details could only be viewed at the
Administration Console for the default polling time of the
Staging Server (8 minutes).  The script log details were
overwritten when the Administration Console received the feedback
that a package was distributed. This symptom ONLY pertains to
packages distributed with the Pull Distribution Method.

 16. When playing back DOS keystrokes, erroneous ASCII characters
could be inserted into the keystroke file.

 17. If there was a sever name with less than 8 characters, the
script log details displayed at the Administration Console were
incomplete.

 18. When the same file was explicitly specified as both the
infile and the outfile (using the /i and /o options) for the
NNEDT command, and the workstation was running DR DOS, editing
files with the NNEDT command removed all other contents of the
edited file.

 19. Feedback from package script execution not returning to the
Administration Console.

 20. Windows applications that were scheduled as events from a
package script, using the NNWIN SCHED command, did not execute.
 (Because, Windows events were being flagged incorrectly to use a
command processor that is not used for Windows applications.)

 21. Using the "No Replace" option for Push distributions to
client workstations deleted the existing file on the workstation.


 ENHANCEMENTS
 ------------
 1. Buffer size increased to improve performance on transfers
from Staging Servers.

 2. Online Help now includes status code information for a "disk
full"  condition.

 3. Distributions from the Distribution Server to multiple
Staging Servers can now occur in parallel.  For example, if a
distribution is scheduled to go to 6 Staging Servers, the
distribution to the Staging Servers can now be performed at the
same time.  Previously, the distribution to the first Staging
Server had to complete before the distribution to the second
Staging Server could have started, and so on.

 Each thread requires approximately 19K (extra) of server memory. 
For example, if the maximum 8 threads is used, the NLM will
consume 152K of server memory in ADDITION to the amount of memory
required by the NLM in single thread mode. 
 The default is single threaded mode.     

 To use the capability of parallel distributions or
"multi-threading", an NLM (DJOBSCHD) must be loaded with the
thread parameter.  First, unload DJOBSCHD.NLM at the Distribution
Server, and then load the NLM by typing the following command:  
LOAD DJOBSCHD THREADS=<n>
 Where <n> is the number of threads from 1 to (and including) 8 .

 You may wish to edit AUTOEXEC.NCF on the Distribution Server to
ensure that Navigator automatically restarts with your specified
thread number.

 NOTE:
 Consider your network resources, the number of Staging Servers
you typically distribute to, your specific network management
needs, etc., in order to specify the optimum number of threads.

 4. Navigator can now be installed on any volume (formerly
restricted to SYS:).

 Insert the following step on page 2-7 in the "NetWare Navigator
Administration Guide."  (Online Help has been updated to include
Help for the new "Volume Selection" dialogue box.)
 |  2f. At the Volume Selection dialogue box, select the volume
where  you  want to
 |  install NetWare Navigator and select OK.

      NetWare Navigator will install on the volume you select.


 5. Administrators can now cancel a distribution job, providing
that it has not begun distribution.
 NOTE: Because access to the job queue is restricted to the
Administration Console user, it is not possible for anyone
without Navigator Administrator rights to cancel a job.  (Online
Help has been updated to include Help for the new "Cancel Job"
dialogue box.)

 To cancel one or more distribution jobs, perform the following
steps:

-----------------------------------------------------------------
----
 A. At the Navigator Administration Console, choose "Cancel
Job..." from the "File" menu.

 The "Cancel Job" dialogue box displays, listing all the jobs
still in the queue and their scheduled distribution times.  If
any jobs are scheduled to begin distribution during the time the
"Cancel Job" dialogue box is displayed, they will be held in the
queue until an action is completed at the "Cancel Job" dialogue
box.

 For example, if a job is scheduled to be distributed at 8:05AM
on a certain date, and the "Cancel Job" dialogue box is opened at
8:04 a.m. on the same date, the job is held in the queue until an
action is taken at the "Cancel Job" dialogue box.  If the action
taken is to cancel the job, the job is canceled.  If the action
taken is NOT to cancel the job, when the dialogue box is closed,
the job begins distribution (provided that the scheduled
distribution time has passed).

 B. Select one or more jobs from the list and select "OK."  (To
select more than one job, press and hold the <Shift> key while
using the mouse to select the jobs in the list.)

 The "Confirm" pop-up box displays the following message: "Do you
want to cancel the selected distribution jobs?"  If a job has
already begun distribution, it cannot be canceled, and you
receive the following error message "ERROR ACCESSING QUEUE:
queue_name".

 C. Select "Yes" to cancel the jobs at the confirmation box. 

 The "Cancel Job" dialogue box closes, returning you to the
NetWare Navigator Administration Console. 

 (If you select "No", the jobs are not canceled and the "Cancel
Job" dialogue box closes.  If you select "Cancel" the jobs are
not canceled, but you remain at the Cancel Job" dialogue box so
you can select other jobs.)

 To view the status of Canceled Jobs
 -----------------------------------
 Perform the following steps (you may want to add these steps to
page 3-38 in the "NetWare Navigator Administration Guide"):

 A. At the NetWare Navigator Administration Console, choose
"Completed Jobs..." from the "Status" menu. 

 The "Completed Jobs" screen displays.  For the jobs you
canceled, in the Node Status field area, the number of failed
attempts to distribute the job is equal to the number of targets
in the distribution list.  The number of successful attempts is
zero.

 B. Select the "Details" button.  The "Completed Job Details"
screen displays. 
 For the jobs you canceled, the feedback message is "Canceled."

SOLUTION: 

SOLUTION
 Install NN30D

 The Enhancements section of NN30D.EXE contains specific
instructions regarding the following enhancements.
 - Enhancement #3. Parallel Distribution
 - Enhancement #4. Installation on other than the SYS: volume.
 - Enhancement #5. Canceling a Distribution Job.

 Specifics Regarding Certain (Numbered) Symptoms

-----------------------------------------------------------------
----------
 S1. The Distribution Server will retry the connection to a
Staging Server if a Staging Server is not responding.  The
connection will be retried according to the setting in the Job
Retry field (set during the installation of Navigator).  The
retry will continue until the Job Retry Limit has been reached.

 S2. The Distribution List Editor and Contents List Editor
provide random and multi-select capabilities.  For example, to
randomly select files in the Contents List Editor, hold down the
"Alt" key and click on the desired files.

 S5. DJOBSCHD.NLM and SJOBDMGR.NLM have been updated to work with
the latest, as well as previous, SMS TSA NLMs.

 S6. The Administration Console will no longer lock the database
file (REPORTS.DAT).

 S7. The feedback mechanism for the Automated Script Processor
was changed to generate a code (9000 or above) for a package that
is missing a specified script.  When a code in this range is
received at the Administration Console, the job is considered
complete.

 S8. Feedback to the Distribution Server will now be retried
until the Distribution Server can respond.

 S9. The SCHEDULE MODIFY command has been changed to execute the
DATE and TIME fields correctly.

 S10. The NNEXTRCT command has been changed to include the
parameter for specifying a filename (FILE).  See page A-42 of the
"NetWare Navigator Administration Guide" for details on the
NNEXTRCT command.

 S12. SJOBFDBK.NLM was changed to store the restart information,
so that server connections will not be consumed inappropriately
when jobs are active and then reloaded.

 S13. The feedback NLM will now correctly handle cases where a
Distribution Server name has more than 8 characters.

 S14. The recursive action has been removed from the OS/2
Scheduler.
 (The recursive action was causing a stack overflow.  This stack
overflow occours when using the PM Interface for scheduling
events, and does not apply to scheduling events from the command
line.)

 S15. Feedback on a package distribution will now be returned to
the Administration Console before any feedback on script
executions.

 S16. Special keystroke functions, such as <WAITSEC nn>, will now
be handled properly.

 S17. Embedded NULLs have been replaced with spaces in the script
log file.

 S18. File contents will now be retained for files being edited
with the NNEDT command if the /i and /o options are specified.

 S19. Conflicts between DR DOS and VLM shells have been resolved
by upgrading the NetWare Client API.

 S20. The command processor is no longer used for scheduling
Windows applications.

 S21. When the No Replace option is used on Push distributions
the existence of a file will now be verified.

Self-Extracting File Name: nn30d.exe

Files Included     Size     Date      Time

..\
       NN30D.TXT     (This file)
       ERROR.TXT           32206         8-22-95     10:47:40 am
       NN30D.TXT           21831         8-23-95      5:51:42 pm
        ON41.TXT            5520         8-22-95     10:05:34 am
..\BIN\
         NNC.EXE          541184         8-11-94     10:59:48 am
     NNCHELP.HLP          250188         4-22-94     10:50:10 am
      NNCSTR.DLL           29733         2-17-94      4:28:16 pm
..\CODE\
      NNAUTO.SCF           16320          8-9-94     12:53:52 pm
       NNEDT.EXE           13977         10-4-93     11:20:02 am
      NNFDBK.EXE           32739         9-29-93      4:17:24 pm
    SCHEDRUN.COM           22528         12-6-93     11:57:02 am
..\NNINST\
     NNIHELP.HLP           83961         4-22-94     10:29:32 am
      NNINST.EXE          302080         4-20-94     12:39:56 pm
..\NNINST\NETNAV\
..\NNINST\NETNAV\BIN\
         NNC.EXE          541184         8-11-94     10:59:48 am
     NNCHELP.HLP          250188         4-22-94     10:50:10 am
      NNCSTR.DLL           29733         2-17-94      4:28:16 pm
..\NNINST\NETNAV\CODE\
      NNAUTO.SCF           16320          8-9-94     12:53:52 pm
       NNEDT.EXE           13977         10-4-93     11:20:02 am
      NNFDBK.EXE           32739         9-29-93      4:17:24 pm
    SCHEDRUN.COM           22528         12-6-93     11:57:02 am
..\NNINST\NETNAV\OS2CODE\
    NNEXTRCT.EXE           23181         5-16-94      2:54:22 pm
     NNFDBK2.EXE           15255         9-30-93     10:06:14 am
      NNFTLC.EXE           33455         7-13-94     10:23:24 am
    SCHEDULE.EXE           20944          6-2-94      2:51:02 pm
..\NNINST\NETNAV\WINCODE\
    NNWINAPP.EXE           29696         9-15-93      1:06:20 pm
..\NNINST\SYSTEM\
    DJOBFDBK.NLM           29371          9-2-94      4:05:50 pm
    DJOBSCHD.NLM           42022         9-19-94      9:02:36 am
    NWSDUPG1.NLM           27761         4-22-94      4:11:18 pm
    NWSDUPG2.NLM           19069         4-22-94      4:13:20 pm
    SJOBDMGR.NLM           94547          9-1-94      4:54:06 pm
    SJOBFDBK.NLM           12334          9-8-94      9:39:36 am
..\OS2CODE\
    NNEXTRCT.EXE           23181         5-16-94      2:54:22 pm
     NNFDBK2.EXE           15255         9-30-93     10:06:14 am
      NNFTLC.EXE           33455         7-13-94     10:23:24 am
    SCHEDULE.EXE           20944          6-2-94      2:51:02 pm
..\PACKAGES\
     DSUPDTD.JCF             531         9-14-94      3:16:56 pm
     DSUPDTD.SCF            2658         8-22-94      3:10:42 pm
     DWUPDTD.JCF             531         9-14-94      3:17:12 pm
     DWUPDTD.NNA            1440         9-14-94      3:11:32 pm
     DWUPDTD.SCF             886         9-14-94      3:16:24 pm
    O2CUPDTD.JCF             531         9-14-94      3:17:22 pm
    O2CUPDTD.NNA             866         8-22-94      3:28:30 pm
    O2CUPDTD.SCF             443        12-27-93      1:32:10 pm
    OS2CLINT.BAT             343        12-27-93      1:38:42 pm
     SSUPDTD.JCF             531         9-14-94      3:17:34 pm
     SSUPDTD.SCF            6202         9-14-94      3:15:16 pm
..\PACKAGES\DSUPDT\
    DJOBFDBK.NLM           29371          9-2-94      4:05:50 pm
    DJOBSCHD.NLM           42022         9-19-94      9:02:36 am
    NWSDUPG1.NLM           27761         4-22-94      4:11:18 pm
    NWSDUPG2.NLM           19069         4-22-94      4:13:20 pm
    SJOBDMGR.NLM           94547          9-1-94      4:54:06 pm
    SJOBFDBK.NLM           12334          9-8-94      9:39:36 am
..\PACKAGES\DWCUPDT\
    NNWINAPP.NEW           29696         9-15-93      1:06:20 pm
    SCHEDRUN.NEW           22528         12-6-93     11:57:02 am
..\PACKAGES\OS2CUPDT\
    SCHED-PM.NEW           47632        11-18-93      2:29:34 pm
..\PACKAGES\SSUPDT\
      NNAUTO.SCF           16320          8-9-94     12:53:52 pm
       NNEDT.EXE           13977         10-4-93     11:20:02 am
    NNEXTRCT.EXE           23181         5-16-94      2:54:22 pm
      NNFDBK.EXE           32739         9-29-93      4:17:24 pm
     NNFDBK2.EXE           15255         9-30-93     10:06:14 am
      NNFTLC.EXE           33455         7-13-94     10:23:24 am
    NNWINAPP.EXE           29696         9-15-93      1:06:20 pm
    NWSDUPG1.NLM           27761         4-22-94      4:11:18 pm
    NWSDUPG2.NLM           19069         4-22-94      4:13:20 pm
    SCHEDRUN.COM           22528         12-6-93     11:57:02 am
    SCHEDULE.EXE           20944          6-2-94      2:51:02 pm
    SJOBDMGR.NLM           94547          9-1-94      4:54:06 pm
    SJOBFDBK.NLM           12334          9-8-94      9:39:36 am
..\WINCODE\
    NNWINAPP.EXE           29696         9-15-93      1:06:20 pm


Installation Instructions:

A. DECOMPRESS FILES

 1. Do you have Navigator 3.01.  If you do, STOP!  NN30D is only
for Navigator 3.00.

 2. Copy NN30D.EXE to the volume\NETNAV, where NN is installed on
the Distribution Server.

 3. Decompress NN30D.EXE by typing: NN30D  [enter]
 NOTE: overwrite all duplicate files.

 IMPORTANT:  Continue on to "Complete The Installation".

 B. COMPLETE THE INSTALLATION
 If you are running NetWare Navigator 3.0, 3.0A, or 3.0B OR your
Distribution Server is a NetWare 4x server running TSAs dated
11/5/93 or later, start with Step 1 of the installation
instructions.  If you are running NetWare Navigator 3.0C, start
with Step 4.

 WARNING - Before loading and unloading NLMs you must ensure that
there are no Active Jobs on that server.

 NOTE - Loading and unloading NLMs may be performed by using the
NetWare RCONSOLE utility.

 1. Unload the specified NLMs (SJOBDMGR, SJOBFDBK, DJOBSCHD,
DJOBFDBK) at the Distribution Server by typing:
      UNLOAD SJOBDMGR <enter>
      UNLOAD SJOBFDBK <enter>
      UNLOAD DJOBSCHD <enter>
      UNLOAD DJOBFDBK <enter>

 2. Copy the new NLMs (SJOBDMGR.NLM, SJOBFDBK.NLM, DJOBSCHD.NLM,
DJOBFDBK.NLM) from NETNAV\PACKAGES\DSUPDT to SYS:SYSTEM on the
Distribution Server.

 3. Restart the new NLMs at the Distribution Server by typing:   
NWSDRUN <enter>

 4. Using the NetWare Navigator Administration Console,
distribute the NetWare Navigator Distribution Server Update 3.0D
package to the Distribution Server.
 NOTE: If the Distribution Server is not in the list of available
targets, the Distribution Server was not installed as a Staging
Server. Refer to Page 2-14 of the "NetWare Navigator
Administration Guide" for information on installing Staging
Servers.
   
 5. Incorporate SCHED-PM.EXE into the required NNCLIENT.ZIP file
on the Distribution Server by typing: 
NETNAV\PACKAGES\OS2CLINT.BAT

 6. Before distributing the Staging Server update, you must
determine whether NetWare Navigator is installed on the SYS:
volume of the targeted Staging Servers.  If it is, skip to Step
6b; if not, perform Step 6a. (Installing NetWare Navigator on a
volume other than SYS is a new feature in NetWare Navigator
3.0C.)

 -- 6a. Using the Administration Console, edit the NetWare
Navigator Staging Server Update 3.0D package.  For each file in
the Contents List, add the file again but specify the Target
Directory with the desired volume.  After all files have been
added with the correct Target Directory, remove the files with
the incorrect Target Directory.
        Continue with Step 6b.

 --6b. Using the Administration Console, distribute the NetWare
Navigator Staging Server Update 3.0D package to a Distribution
List containing all the NetWare Navigator Staging Servers.

 NOTE: You must distribute a Staging Server Update package to
your Distribution/Staging server, as well as to any additional
installed Staging Servers.
       Continue with Step 7.

 7. Unload the specified NLMs (SJOBDMGR, SJOBFDBK) at each
Staging Server by
 typing:

      UNLOAD SJOBDMGR <enter>
      UNLOAD SJOBFDBK <enter>

 8. Restart the new NLMs at each Staging Server by typing: 
NWSDRUN <enter>

 9. Using the Administration Console, distribute the NetWare
Navigator DOS/Windows Client Update 3.0D package to a
Distribution List containing DOS client workstations.

 10. Using the Administration Console, distribute the NetWare
Navigator OS/2 Client Update 1.0 package to a Distribution List
containing OS/2 client workstations.

 11. New installations of staging servers or clients will not
require that this update be run, as long as SETUP is run from the
updated Distribution Server.

 12. ERROR.TXT is a list of System and Error Messages.  ON41.TXT
explains how to install Navigator on a 4.1 server.  You should
find them useful.



-----------------------------------------------------------------
 Any trademarks referenced in this document are the property of
their
 respective owners.  Consult your product manuals for complete
trademark
 information.

-----------------------------------------------------------------

