New Page 1

All current version ‘3’ Knozall Software, Inc. products use the same engine to interpret and distribute jobs, it consists of an Admin Agent, Server Task Agents, and DOS Task Agents.

The Admin Server is your point of control for licenses, and security of all Server Task Agents and DOS Task Agents, and all jobs are created and scheduled on the Admin Server. All Windows executables, required files, and configuration information are located on the Admin Server.

FileWizard uses an Admin Server and Server Task Agents. All Reports and Graphs are generated at the Admin Server, and each Server Task Agent will maintain it’s own database for all of it’s available volumes.

Security Considerations

Loading Server Agents MConsole.INI Config. file Bindery Services vs. NDS Debug option SAP Filtering CLIB Version SFT NetWare Support Windows95/NT information ROOT Mapped drives FileWizard 3 space requirements Setting Default Server Utilization FileWizard 3 Reports & Graphs Scripting in KSI Basic Migration Utility Communication Errors

When installing Knozall products, the username in the Work Server Passwords must be Supervisor Equivalent security for NetWare 3.x (and Admin equivalent for 4.x) and be allowed at least 10 connections.

Work Server Passwords are used to allow the NLM’s to log into other servers. Logins must be provided for the Admin Agent and Server Agents, also for other servers that you wish to access.

If other users without Supervisor Equivalency are to use the product they must be granted Read, Write, Scan, and Create (RWFC) access to the "SYS:\System\Knozall" and "SYS:\System\MXCFW3" directories.

The Task Agent Security option is used by the NLMAuto Pro and NLMerlin to determine which tasks can be executed by a script, for increased security you may wish to disable some functions, but for troubleshooting check all boxes for all security levels. Passwords for each security level are optional.

Loading Server Agents

To Install NLMerlin and FileWizard on other fileservers, you must first make sure you have your server agents mapped to a drive letter, then use the option on your installation disks to install the agent, and register the serial number with the Administrative Server .

To start FileWizard on NLMerlin " load MAdmin" at the Administrative Server then type "load MAgent" on the other server(s). When you have more than one Administrative Server on your network, the Server Agent will need to specify which Administrative Server to connect to with the syntax " LOAD MAgent /m=<Admin Server> ", see manual for more details.

MConsole.INI Configuration file

The MConsole.INI file contains configuration information for the NLMAuto Pro and NLMerlin windows applications. The file is created during installation. If your Novell drive mappings have changed or if the application screen does not show correct information, you may need to edit the file and correct the pathnames for the executables.

Bindery Services vs. NetWare Directory Services (NDS)

NLMerlin, NLMAutoPro & FileWizard support Bindery or Directory Services on NetWare v4.x servers. If you have Bindery Services disabled we will start in NDS mode otherwise all modules will use Bindery Services.

The following modules support the " /N " command line switch to force Novell Directory Services even when Bindery Services are enabled: MAdmin.NLM, MAgent.NLM, and AutoPr.nlm. The syntax is "Load MAdmin /N" .

When using Directory Services your login must use the syntax " .LoginName.Domain " or " .cn=LoginName.o=Domain " wherever a NetWare login is required.

(NOTE the Dot before the LoginName and Domain )

Debug option

Version 3.20 of Merlin, NLMAutoPro & FileWizard have a Debug option. All commands and identifiers are called from other NLM libraries, for example all MXC file command are located in MXCLIBF.NLM. Check the Scripting Guide for a complete reference to other commands.

If you are experiencing problems with MXC:Xcopy , "unload MXCLIBF" then reload it with the debug option "load MXCLIBF /D".

Run your copy command again, all login attempts, pathnames, and filenames will be displayed on the server console.

To record this "load Conlog" run your copy job then "unload Conlog" this will create the file "sys:\etc\CONSOLE.LOG", Print and fax or e-mail it to Knozall Support. This will allow use to better understand why it may have failed.

SAP Filtering

Using Merlin & FileWizard Server Agents or DOS client agents when SAP filtering is enabled.

The Merlin Object type advertised is [ x0473 ] and the sockets used are [ x8528 , x8736 , x8619 ]

CLIB version

In order for your product to work correctly, you must be using the following versions installed on all fileservers being used.

CLIB version 3.12j dated 12-20-95 or later for Novell v3.x or version 4.11 dated 6-10-97 or later for Novell v4.x.

You can check the date of your current CLIB by typing DIR CLIB.NLM at the DOS prompt of the SYSTEM directory of your server or by typing "Modules" at the server console screen.

If your date is later than these dates, then use the CLIB that you currently have installed. You may download the latest CLIB from NetWare, Go NetWare on CompuServe, or http://www.novell.com on the Internet.

SFT NetWare

Problems have been reported while using SFT NetWare on Novell v3.x.

No problems have been reported while using SFT NetWare on Novell 4.x servers.

Windows 95/98/NT/2000/XP

Knozall NLM-based products work fine under all versions of Windows. That includes Windows 95/98/NT. The Windows-based products are 32-bit software and run fine on Windows 95/98/NT. (These 32-bit products do not run on 16-bit operating systems such as Windows 3.x).

ROOT Mapped drives

Novell Root mapped drives are NOT supported by our exclusive NLM-based products. For the Windows applications to work properly the Mconsole.exe and FileWiz3.exe must be located in the SYS:\System\Knozall directory, the FileWiz3.exe must be located in the SYS:\System\MXCFW3 directory.

If you are not sure please type MAP at a DOS prompt, it should display [ Drive U: = SERVER\SYS: \ ]

And your windows icon should display [ U:\SYSTEM\MXCFW3\FILEWIZ3.EXE ] for the Command line and [ U:\SYSTEM\MXCFW3\ ] for the working directory.

FileWizard 3 disk space requirements

FileWizard installation requires only 5.2 MB of disk space. The space required to maintain the database on your SYS: volume will take approximately 1 MB of disk space per 8000 files. For example, if vol sys: had 40,000 files and vol1 had 80,000 files, the space required on volume SYS: would be 15 MB. If you do a DBF dump it will require 1 MB of disk space per 2000 files, or 60 MB of disk space.

Setting default Fileserver Utilization

To avoid high fileserver utilization while using FileWizard we have included a means of limiting the FileWizard NLM and allowing other NLMs to process. By default, it is limited to an average utilization of 80%.

To set the maximum Fileserver utilization to 60%, edit the ASCII startup file "SYS:\System\Knozall\Knozall.AMX" and add the command line switch " MXCFW3.NLM /u=60 ". The MAdmin and MAgent NLM’s both use this Knozall.AMX file to load and unload other NLM’s that are required.

The Administrative NLM (MAdmin.NLM) and Agent NLM (MAgent.NLM) also limit fileserver utilization, 10% by default.

FileWizard 3 Reports & Graphs

FileWizard uses Crystal Reports to generate its reports. Other applications such as ArcServe also use it. One problem we have seen is a version conflict with their DLL files. The DLL’s in question include:

CRPE.DLL 04-04-94 & PDBXBSE.DLL 04-04-94

FileWizard uses Graphic Server to generate it’s graphs, DLL’s include:

GSWAG16.DLL 03-22-95 & GSWDLL16.DLL 03-22-95

If you are having problems with FileWizard Reports or Graphs please check your drives for other versions of these files, if you locate other versions that are newer than the ones shipped with FileWizard copy them into the FileWizard directory.

Scripting in KSI Basic

If a script fails with an error it places a copy of the job in the "SYS:\System\Knozall\MDEBUG" directory. If you open the file with Notepad it will show an error like <<Error [303] Offset [7]>> at the line that failed. Error codes and their cause are located in the back of the Scripting Guide. The scripts are not case sensitive.

If you receive Error 400, make sure that you have selected a Task Agent at the bottom of the Job Edit screen and/or set the $Tagent identifier (See Scripting Guide).

Each script holds its own schedule data, stored in the header of the file, if this header data is missing or corrupted, the script may cause an Abend on the fileserver if it is executed. So if you edit your scripts in another editor, cut & paste it into the Job Editor before running it.

Migration Utility

Version 3.20 of NLMerlin, NLMAutoPro & FileWizard support our new File Migration Utility. It requires Novel v4.x and Knozall on the server that is to be migrated from, the destination of the migrated files can be anything recognized as a NetWare Volume.

Basically the File Migration Utility will move set of files to another location and in place of the file a 0 bit or Sparse Tag File will exist, if a user tries to access the Tag File the migrated file it will immediately retrieved for the user.

When installed it loads KSIMIG.NLM in the servers Autoexec.ncf file, this is the NLM that will retrieve the migrated files. If the NLM is not loaded the migrated file will not be retrieved.

The MXCMIG.NLM is loaded in the Knozall.AMX file, it is used to migrate files to another location and create the Tag File.

Communication Errors

If you experience 400, 404, 407 Errors--or you are having problems copying to a Server Agent or DOS Task Agents, etc. , you may fix this by RESETTING your Routers (by typing RESET ROUTERS at a colon prompt--not DOS), and Running Bindfix for Bindery (NetWare 3.x) or DSRepair for Directory Services.(NDS 4.x)

(Note: Resetting your routers will not interfere with your users. Doing a Bindfix or DSRepair will not drop users, however, it will prevent anyone from logging in for about a minute while it is running..)

Also, if you are using NLMerlin or NLMAutoPro, and are getting a 400 Error ("Target Agent not responding to Send!") you can fix this by going to EDIT JOBS/ Load JOB-- and selecting the Target Agent from the box at the lower left corner of your screen. Make sure you have your JOB LOADED before selecting the Target Agent-- because it needs to be SAVED along with your JOB.