home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
netdor3.zip
/
DISK_11
/
IMAGE10.ZIP
/
BOOK
/
maint.inf
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1994-11-25
|
20KB
|
702 lines
ΓòÉΓòÉΓòÉ 1. NetDoor Maintenance ΓòÉΓòÉΓòÉ
NetDoor Maintenance is a general purpose workstation update tool for users
running in the IBM NetWork Door environment. NetDoor Maintenance is used by
the NetDoor administrators to change the operation of your workstation when
something in the NetDoor or LAN environment is upgraded or changed.
Occasionally, it is necessary to update files on your machine to ensure its
continued operation in the NetDoor environment when these changes occur, and
NetDoor Maintenance makes this possible with little or no perceptible change to
the way your machine operates.
NetDoor Maintenance has two independent modes of operation (Select one for more
information); Automatic, and Continuous.
NetDoor Maintenance is usually started by OpenDoor when you logon to the
NetDoor environment. MAINT can also be started from an OS/2 command prompt, and
will accept any combination of 4 options: /AUTO or /NOAUTO, /CONT or /NOCONT,
/STATUS, and /OPTIONS.
If no options are specified, NetDoor Maintenance runs with the options you have
specified in the Options Window.
The /AUTO and /NOAUTO options will start NetDoor Maintenance with Automatic
Mode on or off respectively. If both are specified, they are processed in
order, so the last specified will be effective.
The /CONT and /NOCONT options will start NetDoor Maintenance with Continuous
Mode on or off respectively. If both are specified, the last will be
effective. You can use MAINT /NOCONT to turn NetDoor Maintenance off if it is
already running in Continous mode.
The /STATUS option will display the Status Window.
The /OPTIONS option will display the Options Window.
ΓòÉΓòÉΓòÉ 1.1. Automatic Mode ΓòÉΓòÉΓòÉ
When Automatic Mode is on, NetDoor Maintenance will automatically apply any
fixes that your workstation requires. When Automatic Mode is off, NetDoor
Maintenance will show you the Apply This Fix? Window for each fix that needs to
be applied, which will show you a brief description of each new fix, and allow
you to decide whether it should be applied or not.
It is recommended that you run NetDoor Maintenance with Automatic Mode on, and
Continuous Mode on, so that your machine is always up to date. Automatic Mode
can be turned off if you wish to have more control over your workstation.
ΓòÉΓòÉΓòÉ 1.2. Continuous Mode ΓòÉΓòÉΓòÉ
When Continuous Mode is on, NetDoor Maintenance runs continuously on your
workstation in the background and periodically checks the NetDoor environment
for fixes that need to be applied. When Continuous Mode is off, NetDoor
Maintenance will check the NetDoor environment for new fixes only once, apply
any that are necessary, and exit.
It is recommended that you run NetDoor Maintenance with Continuous Mode on, and
Automatic Mode on, so that your machine is always up to date.
ΓòÉΓòÉΓòÉ 2. Status Window ΓòÉΓòÉΓòÉ
The Status Window is shown when you type MAINT /STATUS on an OS/2 command line.
The status window has two sections: Continuous Mode, and Fixes.
Continuous Mode Section
The Continuous Mode Section shows if Continuous Mode is on or off. If
continuous mode is on, there will be an additional description of what NetDoor
Maintenance is doing at the moment.
Select one of the following for more information:
Continuous Mode
On Button
Off Button
Fixes Section
The Fixes section of the Status Window will show you the status of all the
available fixes.
Select one of the following for more information:
Fix List
Program Affected
Prerequisites
Description
Apply
Bypass
Cancel
ΓòÉΓòÉΓòÉ 2.1. On Button ΓòÉΓòÉΓòÉ
Press the On Button to turn Continuous Mode on.
ΓòÉΓòÉΓòÉ 2.2. Off Button ΓòÉΓòÉΓòÉ
Press the Off Button to turn Continuous Mode off.
ΓòÉΓòÉΓòÉ 2.3. Fix List ΓòÉΓòÉΓòÉ
The Fix List shows a list of all the fixes available to NetDoor Maintenance,
and whether or not they have been applied to your machine.
Each fix has an icon that tells you whether or not it has been applied. The
indicates that the fix has been applied successfully. The indicates that an
error occured when NetDoor Maintenance attempted to apply the fix. You should
have gotten an error message on your screen for this fix. The indicates that
the fix has not yet been applied. This will appear if you defer the fix from
the Apply This Fix? window, the fix has prerequisite fixes that haven't been
applied, the fix's start date has not yet arrived, or the NetDoor administrator
has specified the fix be deferred. The indicates that the fix was bypassed.
You can select a fix from the list to get more information about it. When you
select a fix from the fix list, the Program Affected, Prerequisites, and
Description fields are filled in for you to give you more information. You can
also apply or re-apply, or bypass the selected fix by pressing the Apply
Button, or Bypass Button.
ΓòÉΓòÉΓòÉ 2.4. Program Affected ΓòÉΓòÉΓòÉ
The Program Affected field is filled in when you select a fix from the Fix
List. This field will contain the names of the programs affected by this fix,
if any. Some fixes are designed to fix a specific program from the NetDoor
environment, and may not be useful to you if you don't use the particular
program.
ΓòÉΓòÉΓòÉ 2.5. Prerequisites ΓòÉΓòÉΓòÉ
The Prerequisites field is filled in when you select a fix from the Fix List.
This field will contain the names of fixes that must be applied before this fix
can be applied. Some fixes depend on the action performed by other fixes, and
can only be applied after those fixes.
ΓòÉΓòÉΓòÉ 2.6. Description ΓòÉΓòÉΓòÉ
The Description field is filled in when you select a fix from the Fix List.
This field will describe what the selected fix does.
ΓòÉΓòÉΓòÉ 2.7. Apply Button ΓòÉΓòÉΓòÉ
The Apply Button will apply the fix selected in the Fix List, or re-apply the
fix if it has already been applied. A message will inform you when the fix has
been applied successfully to your workstation, or if any error occurs trying to
apply the fix.
ΓòÉΓòÉΓòÉ 2.8. Bypass Button ΓòÉΓòÉΓòÉ
The Bypass Button will mark the fix selected in the Fix List as Applied without
actually running the fix program. This can be useful when a fix is designed
for a program on NetDoor that you never use.
ΓòÉΓòÉΓòÉ 2.9. Cancel Button ΓòÉΓòÉΓòÉ
The Cancel Button will close the Status Window.
ΓòÉΓòÉΓòÉ 3. Options Window ΓòÉΓòÉΓòÉ
The Options Window is shown when you type MAINT /OPTIONS on an OS/2 command
line.
The Options Window allows you to set options for how NetDoor Maintenance should
run.
Select one of the following for more information about each option:
Automatic mode
Continuous mode
Sleep interval
Retry fixes interval
Run priority
Make sure TIMEXEC.EXE is running
Run: Hidden and Minimized
Log TIMEXEC Activity
Log File
Log Overwrite and Append
Default
Undo
OK
Cancel
ΓòÉΓòÉΓòÉ 3.1. Automatic Mode Checkbox ΓòÉΓòÉΓòÉ
The Automatic Mode Checkbox specifies if NetDoor Maintenance should run with
Automatic Mode on or off as the default. This setting can be overriden by
running NetDoor Maintenance with the /AUTO or /NOAUTO options.
It is recommended that NetDoor Maintenance run with Automatic Mode on.
ΓòÉΓòÉΓòÉ 3.2. Continuous Mode Checkbox ΓòÉΓòÉΓòÉ
The Continuous Mode Checkbox specifies if NetDoor Maintenance should run with
Continuous Mode on or off as the default. This setting can be overriden by
running MAINT with the /CONT or /NOCONT options.
It is recommended that NetDoor Maintenance run with Continuous Mode on.
ΓòÉΓòÉΓòÉ 3.3. Sleep Interval Field ΓòÉΓòÉΓòÉ
The Sleep Interval Field specifies how long NetDoor Maintenance should sleep
between checks for new fixes when Continuous Mode is on. You should enter a
value between 1 and 60 minutes.
NetDoor Maintenance checks for new fixes to apply periodically. If you are
running on a slow machine, longer sleep intervals will prevent NetDoor
Maintenance from slowing down you machine.
ΓòÉΓòÉΓòÉ 3.4. Retry Fixes Interval Field ΓòÉΓòÉΓòÉ
The Retry Fixes Interval Field specifies how long NetDoor Maintenance should
wait before trying to apply fixes that failed or were deferred when Continuous
Mode is on. You should enter a value between 1 and 24 hours.
NetDoor Maintenance will attempt to apply any fixes that failed after this
interval has passed. If the error occurs again, the error message will be
redisplayed.
If Automatic Mode is off, NetDoor Maintenance will show you the Apply This Fix?
Window for each fix that failed or was deferred, after this interval has
passed.
ΓòÉΓòÉΓòÉ 3.5. Run Priority Field ΓòÉΓòÉΓòÉ
The Run Priority Field instructs OS/2 how much processor time to give to
NetDoor Maintenance in relation to other regular OS/2 applications. The run
priority must be in the range -31 to 31. A positive number means NetDoor
Maintenance should get more processor time, and a negative number means less
time, as compared to other normal applications.
It is recommended that the Priority Delta be set to 0, to give the NetDoor
Maintenance an equal chance at processor time as other applications. If you
have a noticeable slowdown when you run NetDoor Maintenance, you may want to
lower the run priority.
ΓòÉΓòÉΓòÉ 3.6. Make Sure TIMEXEC.EXE is Running Checkbox ΓòÉΓòÉΓòÉ
The Make Sure TIMEXEC.EXE is Running Checkbox allows you to have NetDoor
Maintenance automatically start TIMEXEC.EXE for you. (See Schedule in the IBM
NetWork Door/2 User's Guide or the IBM NetWork Door/2 Administrator's Guide for
more information about TIMEXEC)
This is useful if you have TIMEXEC set up, and you want to make sure it is
running all the time.
NetDoor Maintenance will only attempt to start TIMEXEC.EXE if it exists along
the PATH. If it is not found, no errors will be reported, and TIMEXEC.EXE will
not be started.
TIMEXEC.EXE can be started in one of two modes, which you can set with the
Hidden or Minimized buttons.
ΓòÉΓòÉΓòÉ 3.7. Run: Hidden and Minimized Buttons ΓòÉΓòÉΓòÉ
The Hidden and Minimized buttons allow you to specify how NetDoor Maintenance
should start TIMEXEC.EXE.
If the Hidden button is selected, NetDoor Maintenance will start TIMEXEC.EXE so
that the TIMEXEC.EXE window is hidden. The window will not appear on your
screen, so you will not be able to see it running.
If the Minimized button is selected, NetDoor Maintenance will start TIMEXEC.EXE
so that the TIMEXEC.EXE window is minimized. Depending on how you have set up
your system minimize option, the window will appear in the Minimized Window
Viewer, or on your desktop.
ΓòÉΓòÉΓòÉ 3.8. Log TIMEXEC Activity Checkbox ΓòÉΓòÉΓòÉ
When the Log TIMEXEC Activity Checkbox is checked, NetDoor Maintenance will
start TIMEXEC.EXE so that all it's ouput goes a file. You can specify the file
in the File Field.
ΓòÉΓòÉΓòÉ 3.9. File Field ΓòÉΓòÉΓòÉ
The File Field specifies the file to Log TIMEXEC output in if the Log TIMEXEC
activity checkbox is checked. You must specify the full path of the log file.
This file will be created if it doesn't already exist.
ΓòÉΓòÉΓòÉ 3.10. Overwrite and Append Buttons ΓòÉΓòÉΓòÉ
The Overwrite and Append buttons let you determine what should happen to the
TIMEXEC log file if it already exists.
When you have Log TIMEXEC Activity checked, the TIMEXEC output will go to the
specified file.
If you select Overwrite, when NetDoor Maintenance starts TIMEXEC, the file will
be erased if it exists, and a new file created for the output.
If you select Append, when NetDoor Maintenance starts TIMEXEC, the output will
be appended to the existing file, preserving the original contents.
It is recommended that you use Overwrite to save disk space from a continually
growing log file.
ΓòÉΓòÉΓòÉ 3.11. Undo Button ΓòÉΓòÉΓòÉ
The Undo Button will fill in the options with the last saved values. This is
useful if you make an unintentional change to the options.
ΓòÉΓòÉΓòÉ 3.12. Default Button ΓòÉΓòÉΓòÉ
The Default Button will fill in the options with the recommended values. The
recommended values are to start with Automatic Mode on, Continuous Mode on,
with a Sleep Interval of 10 minutes, Retry Interval of 1 hour, a Priority Delta
of 0, and Make Sure TIMEXEC.EXE is Running will be set, and will be set to
start Hidden. with Log TIMEXEC Activity on, logging to the TIMEXEC.LOG File in
your NetDoor Data directory. Logging will be set to Overwrite.
ΓòÉΓòÉΓòÉ 3.13. OK Button ΓòÉΓòÉΓòÉ
The OK Button will save the options and close the Options Window. The options
will take effect immediately.
ΓòÉΓòÉΓòÉ 3.14. Cancel Button ΓòÉΓòÉΓòÉ
The Cancel Button will close the Options Window without saving the options.
ΓòÉΓòÉΓòÉ 4. Apply This Fix? Window ΓòÉΓòÉΓòÉ
The Apply This Fix? Window will be displayed when you are running NetDoor
Maintenance with Automatic Mode off. It will show you a fix name and a brief
Description of what the fix does. You can apply, defer or bypass the fix by
pressing the Apply Button, Defer Button, or Bypass Button respectivly.
The Help Button will bring up this help window.
ΓòÉΓòÉΓòÉ 4.1. Description ΓòÉΓòÉΓòÉ
The Description is a short description of the purpose of the fix specified.
This will generally show you what files will be affected by the fix and what
program if any the fix affects.
ΓòÉΓòÉΓòÉ 4.2. Apply Button ΓòÉΓòÉΓòÉ
The Apply Button will apply the fix specified to your workstation. A message
window will appear telling you if the fix was applied successfully, or if an
error occurs.
ΓòÉΓòÉΓòÉ 4.3. Defer Button ΓòÉΓòÉΓòÉ
The Defer Button will mark the fix as Not Yet Applied and NetDoor Maintenance
will not apply it until the Retry Failed Fixes Interval specified in the
Options Window if Continuous Mode is on, or the next time NetDoor Maintenance
runs if Continuous Mode is off. This is useful if you don't want to apply the
fix, but may want to apply it at a future date.
ΓòÉΓòÉΓòÉ 4.4. Bypass Button ΓòÉΓòÉΓòÉ
The Bypass Button will mark the fix as Applied, but will not actually apply the
fix. This is useful if the fix is for a program that you never use.
ΓòÉΓòÉΓòÉ 5. Message Code Numbers ΓòÉΓòÉΓòÉ
All the messages and errors presented by Maint have a message number of the
form COUxxxx. Following is a list of messages in numerical order with some
explanation, and possible solutions for errors.
COU3008 An error occured trying to send a message to background process.
Maint was started from the command line and a background process
was already running, but the background process did not respond.
If this happens continuously, the background maint process may be
hung.
COU3009 Timed out waiting for background process to respond.
Maint was started from the command line and a background process
was already running, but the background process did not respond.
Most likely the background process is busy, and this will work
later. If this happens continuously, the background maint process
may be hung.
COU3010 Unable to access shared memory.
This is an internal or system error.
COU3012 Unable to open request semaphore.
This is an internal or system error.
COU3013 Unable to start background session.
Maint was run from the command line, but it could not start the
backround maint process. There may be too many sessions running on
the system. Maint will not continue to run when this error occurs.
COU3014 Unable to create semaphore.
This is an internal or system error.
COU3016 Unable to create semaphore.
This is an internal or system error.
COU3018 Unable to allocate shared memory.
This is an internal or system error.
COU3020 Unable to create a thread to start fixes.
This is an internal error. Maint will not continue to run when
this error occurs.
COU3022 Unable to allocate memory for fixes stack.
This is an internal error. Maint will not continue to run when
this error occurs.
COU3028 Unable to create termination queue.
This is an internal or system error. Maint will not be able to
apply any fixes when this message appears.
COU3030 Unable to set thread priority.
This is an internal error. Maint will continue to run normally,
but the Priority Delta option in the Options Window will be
ignored.
COU3032 An error occured creating a help instance. Help will be
unavailable.
Possibly caused by a missing MAINT.HLP file, or the MAINT.HLP file
is not along the HELP path. The MAINT.HLP file must be along the
HELP for help to work correctly.
COU3034 Unable to allocate memory to read fix files.
This is an internal error.
COU3036 Unable to allocate memory to read fix file.
This is an internal error.
COU3038 Unable to determine the NetDoor image directory.
An error was returned from COUENV.DLL. The NETDOOR.INI file may be
corrupt or missing. A re-installation of NetDoor may solve the
problem.
COU3048 Fix xxx is not intended for your class of machine. Apply anyway?
You attempted to apply a fix from the Status Window that was not
intended for your class of machine.
COU3049 The current date is not between the start and end dates for fix
xxx. Apply anyway?
You attempted to apply a fix from the Status Window before the
start date, or after the end date for the fix.
COU3050 The prerequisite fixes for fix xxx have not yet been applied.
You attempted to apply a fix from the Status Window that has
prerequisite fixes that have not been applied.
COU3051 Fix xxx has been applied successfully.
The fix was applied successfully.
COU3053 Fix xxx has been deferred.
The fix has been deferred.
COU3054 Fix xxx has been bypassed.
The fix has been bypassed.
COU3056 Fix File 'xxx' has a duplicate id tag. Contact your NetDoor
administrators.
There are two fixlist.* files that contain the same tag on the
first line. Maint is unable to load the indicated file because it
would cause a conflict in fix names. The fixlist.* file must be
modified by the adminstrator so that all fixlist.* files have
unique tags.
COU3058 The fix executable for fix xxx is missing.
The fix executable is missing or incorrectly specified in the
fixlist.* file.
COU3060 Unable to start a session to apply fix xxx.
This is an internal or system error. Possibly caused by too many
sessions running on the system.
COU3062 The prerequisite fix(es) specified for fix xxx do not exist.
The prerequisite fixes for this fix are missing or incorrectly
specified in the fixlist.* file.
COU3064 Error number xxx occured running fix xxx.
A fix returned an error code to Maint. The error number is shown.
This happens when the fix fails. The author of the fix should know
what the error code means.
COU3066 Attempted to run fix xxx, but it never returned. Contact your
NetDoor administrators.
If a fix program does not return within 1 hour of launch time,
Maint kills it and posts this error. Either the fix expected user
interaction and the user was not responding, the fix was in an
infinite loop, or waiting on an event that doesn't occur.
COU3068 Unable to determine if fix xxx completed successfully.
This is an internal or system error. Maint ran the fix, but was
unable to get the return code, so maint will assume the fix
failed, and run it again at the appropriate time.
COU3070 An unexpected error occured trying to update app 'xxx', COUCOPY
return code xxx. Contact your NetDoor aministrators for help.
An internal or system error trying to update local files. COUCOPY
documentation should be consulted to determine the cause of this
particular error.
COU3072 An error occured trying to read local file information, return
code xxx. Contact your NetDoor administrators for help.
An internal or system error trying to update local files. COUCOPY
documentation should be consulted to determine the cause of this
particular error.
COU3074 An error occured trying to read local file information for
application 'xxx', return code xxx. Contact your NetDoor
administrators for help.
Internal or system error trying to update local files. COUCOPY
documentation should be consulted to determine the cause of this
particular error.
COU3076 Unable to open the xxx file.
The fixlist file could not be opened for read. Possibly caused
when the file is in use by another process or a file system error
occurs.
COU3078 Unable to write to the NETDOOR.INI file.
Unable to write to the NETDOOR.INI file. Possibly caused by a
corrupt NETDOOR.INI file or the file is set as read-only.
COU3080 Unable to open the NETDOOR.INI file. Using default options.
The NETDOOR.INI file could not be opened. The NetDoor installation
may have failed, or the NETDOOR.INI file is corrupt. A re-install
of NetDoor may fix the problem.
COU3081 Unable to write to NETDOOR.INI file. One or more options were not
saved.
This may be caused by a corrupt NETDOOR.INI file or the file may
be set as read-only.
COU3083 Unable to open NETDOOR.INI file. Options could not be saved.
The NETDOOR.INI file could not be opened. The NetDoor installation
may have failed, or the NETDOOR.INI file is corrupt. A re-install
of NetDoor may fix the problem.
COU3085 Unable to create a semaphore thread.
This is an internal error. Maint will not continue to run when
this error occurs.
COU3087 Unable to allocate semaphore thread stack.
This is an internal error. Maint will not continue to run when
this error occurs.
COU3089 Unable to locate the NETDOOR.INI file.
The NETDOOR.INI file could not be found. Error returned by
COUENV.DLL. Possibly caused by a failed NetDoor installation, or
corrupt OS2.INI. A re-install of NetDoor may solve the problem.
COU3091 Unexpected error querying NetDoor environment. COUENV return code
xxx.
An error was returned by COUENV.DLL. COUENV documentation should
be consulted to determine the cause of this particular error.
COU3093 An error occured trying to update app 'xxx'. The stage directory
could not be created or setup correctly. Your disk may be full.
A COUCOPY.DLL error occured. Local files could not be updated.
Check for full disk, and COUSTAGE directory in NetDoor directory
for strange files or file attributes. Deleting the COUSTAGE
directory may help. A re-installation of NetDoor may help.
COU3095 An error occured trying to update app 'xxx'. Files could not be
backed up to old config directory. Your disk may be full.
A COUCOPY.DLL error occured. Local files could not be updated.
Check for full disk and existence of OLDCONFG directory in the
NetDoor directory. A re-installation of NetDoor may help.
COU3097 An error occured trying to update app 'xxx'. The config.sys file
could not be updated.
A COUCOPY.DLL error occured. Local files could not be updated. The
config.sys file may be locked or in use by another process. The
disk may be full.
COU3099 An error occured trying to update app 'xxx'. The NETDOOR.INI file
could not be found.
A COUCOPY.DLL or COUENV.DLL error occurred. Can be caused by a
failed NetDoor installation, or a corrupt OS2.INI file. A
re-installation of NetDoor may help.
COU3101 An error occured trying to update app 'xxx'. The NETDOOR.INI file
could not be opened.
A COUCOPY.DLL error occurred. The NETDOOR\SYSTEM directory may
have been deleted. Possibly caused by a corrupt NETDOOR.INI file
or a corrupt OS2.INI file. A re-installation of NetDoor may help.
COU3103 An error occured trying to update app 'xxx'. Unable to read from
the NETDOOR.INI file.
A COUCOPY.DLL error occurred. Possibly caused by a corrupt
NETDOOR.INI file.
COU3105 An error occured trying to update app 'xxx'. Unable to write to
NETDOOR.INI file.
A COUCOPY.DLL error occurred. Possibly caused by a corrupt
NETDOOR.INI or the NETDOOR.INI file is set as read-only.
COU3107 An error occured trying to update app 'xxx'. Files could not be
copied to the stage directory. Your disk may be full.
Check for a full disk. Check for unusual files in the COUSTAGE
directory in the NetDoor directory. Deleting the COUSTAGE
directory may help.
COU3109 An error occurred trying to determine the class of the machine.
Assuming CLIENT class.
May be caused by corrupt NETDOOR.INI file. A re-installation of
NetDoor may help. For 99% of machines, this message will not
affect the machine, because most machines are CLIENT's, but this
may be an indication of something else wrong.