home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
lmu220d1.dsk
/
READ.ME
< prev
Wrap
Text File
|
1995-04-12
|
29KB
|
676 lines
*****************************************************************************
* IBM LAN NetView Management Utilities for OS/2 *
* 5622-153 (C) Copyright IBM Corp. 1991, 1995. All rights reserved. *
* *
* Corrective Service Diskettes (CSD) for the following: *
* *
* LAN NetView Management Utilities for OS/2 Version 1.0 (CSD LM00200) *
* LAN NetView Management Utilities for OS/2 Version 1.1 (CSD LM00210) *
* *
* Upon successful application of this CSD, the IBM LAN NetView Management *
* Utilities for OS/2 will be at CSD level LM00220. *
* *
*****************************************************************************
* *
* T A B L E O F C O N T E N T S *
* *
* Section I: How to apply the CSD *
* Section II: What's included in the CSD *
*****************************************************************************
*****************************************************************************
* *
* S E C T I O N I *
* *
*****************************************************************************
* *
* Part 1: *
* *
* Instructions on how to apply the CSD in an OS/2(TM), Windows(TM), *
* DOS, and NetWare(TM) server environments. *
* *
* Part 2: *
* *
* Considerations for applying this CSD via the Configuration, *
* Installation, and Distribution (CID) process. *
* *
*****************************************************************************
*****************************************************************************
* Section I Part 1: Applying the CSD *
*****************************************************************************
Updating LMU in an OS/2 environment:
-----------------------------------
1. In preparation for updating LMU, you must terminate all
active LMU functions. This may be done via the
following commands:
LMUQUERY /T * will inactivate all major LMU
components.
LMUFIND module-name /T will inactivate any long
running LMU utilities like
PERFCAP2, SRVWATCH, etc.
* If you are viewing any LMU books, you will need to close
any and all windows associated with them.
* If you are using AUEDRIVR.DLL as the alert user exit of
LAN Network Manager, you will need to terminate LNM or
inactivate the exit before updating LMU.
* If you are forwarding FFST alerts to LMU using EPWRT003.DLL,
you will need change the EPWROUT.EXE statement in CONFIG.SYS
and reboot before updating LMU.
* If you have loaded LMU2RX (via RxFuncAdd) in any REXX program
you will need to reboot before updating LMU.
Note: The LMU update program will replace ALL LMU source files.
Before starting, you may want to rename or back up
any LMU files that you have modified and not renamed.
2. To apply this update to LMU, insert CSD diskette 1 in the A: drive
and issue one of the following commands:
A:\LMUFIX To update the boot-drive:\LMU2 subdirectory
A:\LMUFIX /Tx To update the x:\LMU2 subdirectory,
where x is the disk drive where you have
installed LMU
Note: LMU must already be installed in the target subdirectory.
LMUFIX updates those LMU files that have already been
installed will be updated.
You will be prompted to insert LMU CSD diskettes 2 thru 5.
If this workstation does NOT have LMU Version 1.0 (CSD LM00200)
installed, go to step 5. In addition, if this workstation is NOT
a Managing System with Database, go to step 4.
3. Because a new column has been added to the BASE table to support
symbolic names, the current LMU database must be migrated or deleted.
To migrate your current database (add this column to your database):
- Run the database migration utility LMUDB200.CMD to add the new
column to an existing LMU database.
Note: You must be logged-on to the userid used to create the database.
The command syntax is: LMUDB200 [database_name]
To delete your current database:
- Erase the LMU database using QUERY MANAGER.
LMUSRV will build a new database when the system is restarted.
4. If this workstation does NOT have the LMU User's Guide or Messages
manuals installed, go to step 5.
If this workstation does have the LMU User's Guide or Messages
manuals installed, you must customize your workstation again.
To customize your workstation, run LMUCUST with the same options you
customized with the first time. (Refer to LMUSTART.CMD file in the
LMU2 subdirectory of your workstation if necessary).
5. Restart your computer.
***** !! Warning to OS/2 users !! *****
Users running the SNMP Proxy (LMUSNMPD) in conjunction with LAN NetView
View or LMU/6000 V1.1.1 must alter their LMUSTART.CMD file to invoke
LMUSNMPD with the +C option. Users that have already upgraded to
LMU/6000 V1.1.2 should invoke LMUSNMPD without the +C option.
Updating LMU in a Windows environment:
-------------------------------------
1. In preparation for updating LMU, you must terminate all
active LMU functions. This may be done by exiting Windows.
2. To apply this update to LMU, insert CSD diskette 5 in the A: drive
and issue the following command:
A:\LMUFIXW x: To update the x:\LMU2 subdirectory,
where x is the disk drive where you have
installed LMU
You will only need LMU CSD diskette 5.
3. Restart Windows.
Updating LMU in a DOS environment:
---------------------------------
1. To apply this update to LMU, insert CSD diskette 5 in the A: drive
and copy the following files to the subdirectory where LMU is installed.
o DOSVIRGA.COM
o QDOSVPD.COM
o LMUDOSHB.COM
o AUEDOSAL.COM
o DRWATCHD.COM
o CVT_VPD.EXE
o ADAPTERS.TBL
o ADAPTERS.SMP
o CRITFILE.SMP
o USERVPD.SMP
2. Restart your computer.
Updating LMU in a NetWare server environment:
--------------------------------------------
1. In preparation for updating LMU, you must terminate all
active LMU functions loaded on the NetWare server. This
can be done by UNLOADing any LMU NLMs that are running.
For example:
UNLOAD LMUCLI
UNLOAD VOLWATCH
UNLOAD NSVWATCH
UNLOAD NLMWATCH
2. Applying the CSD to a Netware server can be done by either
running LMUFIX OR copying the LMU files manually. Both are
done via the OS/2 requester.
Using LMUFIX (recommended)
--------------------------
Application of this CSD must be done via an OS/2 NetWare
Requester. To apply this update to LMU, on a NetWare server,
apply the corrective service to a network drive mapped to the
volume containing the LMU2 subdirectory.
Insert CSD diskette 1 in the A: drive and issue the following
command:
A:\LMUFIX /Tx To update the x:\LMU2 subdirectory,
where x is the network drive mapped to
the where you have installed LMU
Note: LMU must already be installed in the target subdirectory.
Only those LMU files that have already been installed will
be updated.
You will be prompted to insert LMU CSD diskettes 2 thru 5
Manually copying LMU files (for managed systems only)
-----------------------------------------------------
This process is designed for updating NetWare servers that are
LMU managed systems. It allows updates to be done via an OS/2,
DOS, or Windows NetWare Requester.
From an OS/2, DOS, or Windows NetWare Requester workstation,
copy the following modules from the LMU Diskette 5 to the server
station's NetWare partition:
All .NLM modules (*.NLM)
ADAPTERS.SMP
CRITFILE.SMP
LMUBIND.SMP
NLMWATCH.SMP
USERVPD.SMP
ADAPTERS.TBL
QDOSVPD.COM
3. At the NetWare server load the LMUVPDCS customization NLM.
This NLM will copy the updated QDOSVPD.COM and ADAPTERS.TBL
files to the DOS partition of your system.
Note: DOS must be present in the server.
4. Restart your computer.
*****************************************************************************
* Section I Part 2: CID Considerations *
*****************************************************************************
LMU provides the LMUCID command, which enables LMU to be installed,
customized, or upgraded using Configuration Installation Distribution
(CID) procedures. This procedure describes how to apply the LMU CSD to
a CID code server and how to build the LMUCID response file.
In order to CID-install this CSD, the LMU product must have already been
installed or copied to the CID code server. If this has not been done,
either use the LMUINST command to install (copy and unpack) the LMU files
from the LMU product diskettes or use the COPY command to copy (but not
unpack) all the LMU files from the LMU product diskettes to the CID code
server. Refer to the "LMU Installation and Customization" manual for
more detail on this process.
NOTE: Using LMUINST to install LMU is the recommended method of install.
Installing the LMU CSD onto the CID code server
-----------------------------------------------
The method used to install the original product diskettes, dictates the
procedure you will use to apply the CSD. If the original product
diskettes were LMUINSTed onto the CID code server, use procedure 1 to unpack
the new LMU files from the CSD diskettes and upgrade the unpacked version
of the code onto the server. If the original product diskettes were
COPYed onto the CID code server, use procedure 2 to store the new LMU
files onto the server into a new LMU2 subdirectory.
Procedure 1:
Applying this CSD to a previously LMUINSTed LMU on the CID code server
(LMU has been unpacked and stored in an LMU2 subdirectory on the server).
To update a previously LMUINSTed LMU on the CID code server, use
the following command:
LMUFIX /Tx:\path
where x:\path is the drive and path leading to, but not including,
the existing LMU2 subdirectory on the CID code server.
Example:
LMUFIX /Tx:\cid\img
unpacks and places all LMU files from the LMU CSD diskettes into the
x:\cid\img\LMU2 subdirectory on the CID code server (assuming the
x:\cid\img path exists, and LMU has been previously installed).
Procedure 2:
Applying this CSD to a previously COPYed LMU on the CID code server
(LMU stored in an LMU2 subdirectory on the server is still packed).
To add the LMU CSD to a previously COPYed LMU on the CID code server,
create a new LMU2 subdirectory.
Note: This new subdirectory MUST be different from the LMU2 install
subdirectory (so that LMUINST will continue to work).
Then, use the following command:
COPY A:\LMU2\*.* x:\csdpath
for each of the LMU CSD diskettes, where x:\csdpath specifies the
drive and complete path of the new LMU CSD subdirectory on the CID
code server.
Example:
COPY A:\LMU2\*.* x:\cid\csdimg\LMU2
copies packed LMU files from an LMU CSD diskette to the
x:\cid\csdimg\LMU2 subdirectory on the CID code server (assuming
the x:\cid\csdimg\LMU2 path exists).
Creating the LMUCID response file
---------------------------------
Regardless of how the LMU CSD is stored on the CID code server, the
process of applying the CSD onto the CID clients remains the same.
An LMUCID response file is required to apply the LMU CSD to CID clients.
The response file keyword to install this CSD is LMUFIX.
Sample LMUCID response file:
; LMUCID response file for LMU CSD
LMUFIX
;
The LMUFIX keyword overrides any previously specified (or defaulted)
LMUINST or LMUCUST keywords. LMUFIX should be the only keyword in the
response file.
The "/T:" LMUCID parameter allows for the specification of the target
drive on the CID client. The drive specified must have an LMU2
subdirectory with a previously installed version of LMU.
*****************************************************************************
* *
* S E C T I O N I I *
* *
*****************************************************************************
* *
* Part 1: *
* *
* List of APARs, sorted by number and module, included in this CSD. *
* *
* Part 2: *
* *
* Description of changes. *
* *
*****************************************************************************
*****************************************************************************
* Section II Part 1: APAR/fix list *
*****************************************************************************
Sorted by APAR number:
APAR Component/Module Description
------- ---------------- -------------------------------
IC08355 LMUGUI Hang and LMU7981E trap fixes
IC08436 QUERYVPD/QDOSVPD Serial number, Memory
IC08474 QUERYVPD/QDOSVPD Processor Speed
IC08554 Documentation Bookshelf; missing index file
IC08560 Fault Manager CM/2 alerts
IC08562 LMULNV Memory creep
IC08563 LMUGUI Saving font changes
IC08622 LMUGUI Execute commands enhancements
IC08680 LMUGUI Userid label and enhancements
IC08694 LMUSRV Change log alert
IC08722 LMUCUSTW Specify Windows directory
IC08723 LMUCLI.NLM Overdue after DOWN server
IC08761 QUERYVPD/QDOSVPD ThinkPad 720, 755
IC08788 LMUCID Popup if LMU2 subdirectory exists
IC08819 SHUTDOWN Trap on OS/2 2.x workstation
IC08863 QUERYVPD COMPAQ systems not recognized
IC08870 PERFCAP2 DSK * not collecting all disk
IC08939 LMUPAGER Change reset and init strings
IC08996 NSVWATCH Loop when polling length > 4
IC09260 LMUCLIWB Truncated workstation name
IC09273 QUERYVPD/QDOSVPD 9595-STB not recognized
IC09677 LMUPOPUP Times out early
IC09690 LMUSTEP List of times not recognized
Sorted by Component/Module:
Component/Module APAR Description
---------------- ------- -----------------------------
Documentation IC08554 Bookshelf; missing index file
Fault Manager IC08560 CM/2 alerts
LMUCID IC08788 Popup if LMU2 subdirectory exists
LMUCLI.NLM IC08723 Overdue after DOWN server
LMUCLIWB IC09260 Truncated workstation name
LMUCUSTW IC08722 Specify Windows directory
LMUGUI IC08355 Hang and LMU7981E trap fixes
LMUGUI IC08563 Saving font changes
LMUGUI IC08622 Execute commands enhancements
LMUGUI IC08680 Userid label and enhancements
LMULNV IC08562 Memory creep
LMUPAGER IC08939 Change reset and init strings
LMUPOPUP IC09677 Times out early
LMUSRV IC08694 Change log alert
LMUSTEP IC09690 List of times not recognized
NSVWATCH IC08996 Loop when polling length > 4
PERFCAP2 IC08870 DSK * not collecting all disk
QUERYVPD IC08863 COMPAQ systems not recognized
QUERYVPD/QDOSVPD IC08436 Serial number, Memory
QUERYVPD/QDOSVPD IC08474 Processor Speed
QUERYVPD/QDOSVPD IC08761 ThinkPad 720, 755
QUERYVPD/QDOSVPD IC09273 9595-STB not recognized
SHUTDOWN IC08819 Trap on OS/2 2.x workstation
*****************************************************************************
* Section II Part 2: Detailed description *
*****************************************************************************
Documentation (APAR IC08554):
-------------
BOOKMGR/READIBM is unable to verify bookshelf when
opening the LMU bookshelf (BK50BK01.BKS)
Fault Manager (APAR IC08560):
-------------
Substitution token -$t (detailed data) returns wrong data when
processing a CM/2 alert
Null text field in GUI event dialog (for CM/2 alert)
Null MIB object lmuAlertText (for CM/2 alert)
Sample fault table (AUEUSER.SMP) specified -$m instead of -$t for
CM/2 alerts (CM/2 alerts do not contain -$m subvector)
LMUCID (APAR IC08788):
------
LMUCID presents a popup when run on a system that already had
an LMU2 subdirectory. This would halt processing.
LMUCID would not accept semicolons (';') as a comment line.
LMUCLI.NLM (APAR IC08723):
----------
NetWare server managed system goes Overdue instead of Inactive
at managing system after NetWare server is DOWNed.
Other NLMs behave strangely after LOADing LMUCLI.NLM due to a
Novell bug with non-local semaphores.
LMUCLIWB (APAR IC09260):
--------
Workstation name truncated to 8 characters on an
IBM (NetBIOS) Windows managed system.
LMUCUSTW (APAR IC08722):
--------
LMUCUSTW unable to find Windows drive in PATH when
directory that Windows is installed in is not WINDOWS.
LMUGUI (IC08355, IC08562, IC08563, IC08622, IC08680):
------
Changes to the Font Name and Point Size in the Change
Miscellaneous Configuration dialog where ignored.
Changes to the Font Name and Point Size in the Change
Miscellaneous Configuration dialog where not written to
LMU.INI file.
Fields on the Change Miscellaneous Configuration dialog
where rearranged to allow for a larger Font Name field.
LMUGUI Execute Commands dialog now accepts a series of
substitution tokens that can be used anywhere in the
command string, and may be used more than once. The
following is a list of the valid tokens:
Token Description
----- --------------------------------------------------------
@$a Is replaced by the Node Address of the selected system.
@$c Is replaced by the current Status of the selected system.
@$d Is replaced by the Domain of the selected system.
@$m Is replaced by the Managing System of the selected system.
@$n Is replaced by the Name of the selected system.
@$s Is replaced by the Symbolic Name of the selected system.
@$t Is replaced by the Node Type of the selected system.
@$u Is replaced by the Userid of the selected system.
The proxy address field on the LAN NetView Version 1.0 Display
Attributes dialog has been expanded to include the host and
community names.
Added the ability to display the userid as the fourth
label for each managed or managing system.
Corrected a typo for the GUI_IGNORE_UNKNOWNS key in the
sample control file (LMUCTL.SMP). This typo also affected
the Ignore Unknowns option in LMUGUI. If this field was
modified and saved via the Miscellaneous Configuration dialog,
it will need to be changed/saved again.
Corrected an error with the "save" logic in the three change
configuration dialogs. Previously, when the Save button was
pressed, only the configuration fields that had been changed
in that invocation of the change dialog were saved (written
to the LMU.INI file).
LMUGUI would "lockup" the keyboard and mouse when it was left
running for long periods of time without user access. Other
processes in the machine (LAN Server, etc) where unaffected
(with the exception of no mouse or keyboard input). The
problem was traced to a failing Graphics View/2 API call.
That particular API call is no longer being used.
In certain situations, users where receiving LMU7981E error
messages indicating that some Graphics View/2 API call had
returned unexpected results and that processing would continue.
The GUI would then trap. The trap has been corrected. If the
user still receives LMU7981E error messages, they should redraw
the view by reselecting the current view or selecting Refresh
View from the View menu item.
A Product Information dialog has been added to the Help menu item.
This dialog details the GUI's Version, Release, and maintenance
levels.
LMULNV (IC08562):
------
Memory creep when running LAN NetView Version 1.0 View
interface program (LMULNV.EXE)
LMUPAGER (APAR IC08939):
--------
LMUPAGER had hard coded modem Reset and Initialization strings.
Many of today's modems rely on software configuration and no
longer have hardware switches to change the various settings.
This situation caused the following problems:
- Some modems will set and then drop carrier detect while
dialing. LMUPAGER could not distinguish this from a valid
loss of carrier and aborted.
- LMUPAGER would not work with modems that have a factory-set
Transmission Mode setting of anything other than Asynchronous
Transmission Mode (&Q0). For example, Hayes Accura modems
have a factory-set Transmission Mode setting of Error-control
Mode (&Q5).
- LMUPAGER failed to work with certain modems connected to
certain computers using 25-pin to 9-pin cables. For example,
a Hayes Accura modem would not work when connected to a Value
Point 466DX2/D using the cable supplied with the modem.
- Some modems defaulted to "high speaker volume".
Three new fields have been added to the end of the Paging System
file (PAGESYS.SMP) to allow for the customization of a 10-byte Reset
string, a 30-byte first Initialization string and a 30-byte second
Initialization string. If a given string is not coded for a given
data file entry, the default string will be used. If the modem rejects
any of the commands in the Reset or first Initialization strings, a
error message is displayed and the LMUPAGER processing is aborted.
If the modem detects errors in any of the commands in the second
Initialization string, processing continues.
The default strings have been changed as follows:
- Added &Q0 to force asynchronous mode communication
- Added L2 to set medium speaker volume
- Changed X4 to X3 to handle more 'smart' modems
- Changed &D2 to &D0 to handle modems that turn carrier
detect on/off/on during dialing
The original and updated Reset and Initialization strings are included
(as comments) in the sample Paging System file (PAGESYS.SMP).
Please consult the documentation supplied with your modem for a list
and description of the commands used to activate your modem's features.
Some users did not understand that the semicolon in the first column
of each entry in the PAGESYS.SMP and PAGEUSR.SMP sample files marked
those entries as comment lines that are to be ignored by LMUPAGER.
These users coded their entries with a semicolon in the first column
which resulted in invalid (ie, unknown) paging systems, userids, etc.
The two sample files have been modified to better explain the meaning
of a semicolon in the first column.
LMUPOPUP (APAR IC09677):
--------
LMUPOPUP timed out early when the specified time out value was
greater than 65.
LMUSRV (APAR IC08694):
------
The wrong fault table entry was processed for change log alert. The
key of change log alert was 5622153 02 A000 instead of 5622153 01 8000.
LMUSTEP (APAR IC09690):
-------
If a command was scheduled to execute at multiple times,
for example, at 10:00, 10:05, and 10:10 on a given day,
Only the first command was executed (at 10:00). This is
done by coding 0,5,10 for the minutes or Monday, Tuesday,
Friday for the day.
NSVWATCH (APAR IC08996):
--------
Infinite loop in NSVWATCH when polling length option (/L)
is specified with a value greater than 4.
PERFCAP2 (APAR IC08870):
--------
Requesting data collection for all disks (DSK *) resulted
in the collection for physical disks 1, 2, and 3. Data
collection for all disks will now record information for
all 24 disks.
Creation of a summary log file named "-" even though summary
log file creation had been suppressed.
QUERYVPD/QDOSVPD (APAR IC08436, IC08474, IC08761, IC08863, IC09273)
----------------
Displaying system vital product data (ie. system serial
number, planar serial number, planar part and FRU numbers)
on a micro-channel system with 8K NVRAM (eg. 9576i).
Failure to detect all memory on a micro-channel expansion
card (MC id = FDDF). Both expanded memory and total memory
values were incorrect.
Support for dynamic processor type and processor speed has
been enhanced to further distinguish various processors and
their speeds independent of system configuration. For
example a PS/VP 466DX2/D would have reported 80486/33MHz
rather than 486DX2/66MHz.
COMPAQ systems reported as OEM Machine rather than COMPAQ.
System identification of various IBM ThinkPad systems
including the Thinkpad 700, 720, 750, and 755.
QUERYVPD/QDOSVPD incorrectly identified a 9595-STB as
an IBM PS/2 Server 560. The 560 designation has been
dropped.
SHUTDOWN (APAR IC08819):
--------
SYS3170 (trap) after executing LMU shutdown on an
OS/2 2.x workstation