home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
ip20561.3d1
/
READ.ME
< prev
next >
Wrap
Text File
|
1995-12-06
|
26KB
|
632 lines
ADSTAR(*) Distributed Storage Manager OS/2 client - READ.ME
───────────────────────────────────────────────────────────────
Version 2, Release 1, Level 0.2
Welcome to ADSM OS/2(*) client.
This READ.ME file contains information you need for installing
ADSM OS/2(*) Client, as well as information that was not available
for our printed publications.
┌──────────────────────────────────────────────────────────────────────┐
│ IMPORTANT NOTE: Once you have started using a Version 2 client on a │
│ particular node, you will NOT be able to use a Version 1 client on │
│ that node. Data backed up with Version 2 clients cannot be │
│ restored by Version 1 clients, regardless of the server version. │
└──────────────────────────────────────────────────────────────────────┘
========================================================================
This READ.ME file is divided into the following categories:
o Before You Install ADSM OS/2(*) Client
o Getting Help
o Installing ADSM OS/2(*) Client
o Late-Breaking News
- Limitations
- Document Updates
- General Information
- Known Problems
- Fix Information
o Trademarks
=====================================================================
Before You Install ADSM OS/2(*) Client
──────────────────────────────────────
Software Requirements
─────────────────────
- OS/2(*) 2.0 or later
Hardware Requirements
─────────────────────
- Any appropriately configured Intel(**) 80386 or higher hardware
platform with at least 10MB of disk storage and 12MB of memory.
=====================================================================
Getting Help
────────────
To receive service and technical support for ADSM
─────────────────────────────────────────────────
o Contact your ADSM administrator. This should be your first
step when having problems with ADSM.
o Your ADSM administrator will know how to contact IBM for
Technical Support on your behalf.
o For the latest information about ADSM, visit the ADSM home page
on World Wide Web. The URL is:
http://www.storage.ibm.com/storage/software/adsm/adsmhome.htm
To participate in user discussions of ADSM:
o Subscribe to IBM's officially supported ADSM forum on CompuServe(**).
This is located in the IBM Storage Systems Forum (GO IBMSTORAGE ADSM)
The general discussion section is ADSTAR(*) Distributed Storage Manager,
Section 1. Information files and fixes are in the ADSTAR(*) Distributed
Storage Manager Library, library 1.
o Subscribe to an Internet listserv forum for ADSM
This is not officially supported by IBM, but IBM support people
do participate in the discussions, along with other ADSM users.
You can subscribe by sending a note to listserv@vm.marist.edu
that contains the following command in the message body:
SUBSCRIBE ADSM-L yourfirstname yourlastname
Posts can then be sent to: adsm-l@vm.marist.edu
Anonymous FTP server
────────────────────
IBM also supports an anonymous FTP server where you can find
PTF maintenance and other ADSM-related materials. Three other
anonymous servers are unofficially maintained by non-IBM volunteers.
These servers are:
index.storsys.ibm.com (primary - California, IBM)
ftp.rx.uni-karlsruhe.de (mirror - Germany)
ftp.wu-wien.ac.at (mirror - Austria)
ftp.cac.psu.edu (mirror - Pennsylvania)
=====================================================================
Installing ADSM OS/2(*) Client
──────────────────────────────
For V2R1L1 or V2R1GA customers
──────────────────────────────
- The OS/2(*) ADSM client contains 5 diskettes.
- Place the first diskette into drive A.
- Open an OS/2(*) window
- Type in A:\INSTALL
- One of following choices may be performed
1) Select "Update the currently installed product" option to update
the code to V2R1L2 PTF level
-- or --
2) - Select "Delete the installed product and re-install" option to delete
the previous V2 code
- Select-All components to be deleted
- Exit from the main panel
- Type in A:\INSATLL to reinstall the client
Please note: due to Software Installer v1.3 upgrade, the re-install
option does not work automatically first time after the delete.
- Follow the instructions given
- Create a dsm.opt file in the Executable directory
- Reboot to activate DSM_CONFIG and DSM_DIR environment variables
For V1 customers
────────────────
- The OS/2(*) ADSM client contains 5 diskettes.
- Place the first diskette into drive A.
- Open an OS/2(*) window
- Type in A:\INSTALL
- Follow the instructions given
- Create a dsm.opt file in the Executable directory
- Reboot to activate DSM_CONFIG and DSM_DIR environment variables
The installation for Version 2 OS/2(*) client creates an "ADSM Client"
folder on the desktop, and all of the client executables are created
inside of this folder.
Start the client by double-clicking on the "ADSM Client" folder, then
- for the Backup GUI Client
. Double-click on the "ADSM Backup" icon
(Can also be started by typing DSM in an OS/2(*) window)
- for the Backup Command Line Client
. Double-click on the "ADSM Backup Command Line" icon
(Can also be started by typing DSMC in an OS/2(*) window)
- for the Client Scheduler
. Double-click on the "ADSM Scheduler" icon
(Can also be started by typing DSMC SCHED in an OS/2(*) window)
To start the ADSM Scheduler without having to be prompted for
the password, click on "Settings" notebook on ADSM Scheduler
icon, in Optional Parameters entry field, add -PASSWORD=xxxx
after SCHED parameter, where xxxx is your password. You may
then drag this ICON into the Startup folder to automatically
start ADSM Scheduler with OS/2(*).
- for the Administrator GUI Client
. Double-click on the "ADSM Administrator" icon
(Can also be started by typing DSMADM in an OS/2(*) window
- for the Administrator Command Line Client
. Double click on the "ADSM Administrator Command Line" icon
(Can also be started by typing DSMADMC in an OS/2(*) window
Please see the ADSM Installing the Clients for complete details
on how to install the product and set up the configuration files.
See ADSM Using the OS/2(*) Backup-Archive Client for information on
using this product.
See readme.api file (double-click on the "ADSM API Read Me" icon) for
more information on the ADSM OS/2(*) Application Programming Interface.
System Monospaced Font is recommended for viewing the documentation
icon in the ADSM Client folder.
=======================================================================
Late-Breaking News
──────────────────
Limitations
───────────
For the Administrator GUI Client, there are the following limitations:
- in the Database Add Mirrored Volumes window, you must add one volume
at a time; attempting to add two mirrored volumes simultaneously
(when they are both copies of the same volume) will result in an
ANR2433E error message.
- Due to Presentation Manager limitations, the maximum number of
open notebooks is 35.
Backup of LAN Server 4.0 Directory Limits for 386 HPFS drives are
not currently supported.
──────────────────────────────────────────────────────────────────────
Document Updates
──────────────────
- NEW OR CHANGED MESSAGE DOCUMENTATION:
. ANS4261E Session requires a NODENAME.
Please add a NODENAME option and retry the command.
Explanation: Session requires a nodename.
System Action: Processing stopped.
User Response: Add a NODENAME option and retry the command.
. ANS4119W FILE filename EXCLUDED BY INCLUDE/EXCLUDE LIST
Explanation: You tried to back up or migrate a file
that was specified to be excluded from backup.
System Action: ADSM did not back up or migrate the file.
User Response: Specify the file using the Include option and
retry the operation.
. ANS4353E SESSION REJECTED: UNKNOWN OR INCORRECT ID ENTERED
Explanation: The node name you entered is not known by the server,
or you are attempting to access a file migrated to
different node.
System Action: ADSM canceled the current operation. You are not
allowed to connect to the server until your node
name is registered with the server. If attempting
to access a migrated file, your nodename must be
the same node which migrated the file.
User Response: Ensure that you entered your ADSM node name correctly.
If yes, see your system administrator. Verify that
Verify that the server is using closed registration
and that your node name is registered with the server.
. ANS2159E SYSTEM MEMORY ERROR
Explanation: An OS/2 memory allocation/deallocation error occurred.
Error can be caused by a large number of entries
in a file list.
System Action: Processing stopped.
User Response: Run a smaller operation by reducing the number of
entries selected at a time, or invoke command line
client (dsmc) to run the entire operation.
. ANS2985W LIST BOX FULL. SOME ENTRIES MAY BE MISSING, OPERATION CONTINUING
Explanation: List box limit reached. Some data may not be displayed.
System Action: The OS/2 Toolkit List box limit has been reached.
Operation continues.
User Response: Run a smaller operation by reducing the number of
drives selected at a time, or invoke command line
client (dsmc) to run the entire operation.
. ANS2994W THE DRIVES FOR RESTORE/RETRIEVE LIST BOX IS FULL.
SOME ENTRIES MAY NOT BE DISPLAYED, OPERATION CONTINUING
Explanation: The list memory limit of 64K is reached for Drives for
Restore/Retrieve. Some entries can not be displayed.
System Action: Processing continues for displayed data.
User Response: Invoke the command line client (dsmc) to work with
the entire list of Drives For Restore/Retrieve.
--------------------------------------------------------------------------
- NEW OPTIONS:
. -FROMTIME and -TOTIME used on RESTORE, RETRIEVE, QUERY ARCHIVE
and QUERY BACKUP command line commands.
NOTE: These options cannot be used in the options file.
-FROMTime (with -FROMDATE)
Used in conjunction with the FROMDATE option to specify
a beginning time on the specified date.
For example, with FROMTIME and FROMDATE, you can request that
ADSM restore files beginning with those that were backed up
on or after 6:00 AM on June 1, 1995.
The default for FROMTIME is 00:00:00.
NOTE: If you want ADSM to use a value you specify for FROMTIME,
you must also include FROMDATE with the command.
Otherwise, ADSM ignores FROMTIME.
-TOTime (with -TODATE)
Used in conjunction with the TODATE option to specify
an ending time on the specified date.
For example, with TOTIME and TODATE, you can request that
ADSM list only files that were backed up on or before
11:59 PM on June 15, 1995.
The default for TOTIME is 23:59:59.
NOTE:If you want ADSM to use a value you specify for TOTIME,
you must also include TODATE with the command.
Otherwise, ADSM ignores TOTIME.
You can also use TOTIME and TODATE with FROMTIME and
FROMDATE to request that ADSM restore or retrieve or list
only those files that were backed up or archived within
a particular window of time.
For example, you could request that ADSM list only
files that were archived between 6:00 AM on June 1, 1995
and 11:59 PM on June 15, 1995.
The time must be in the format you select with
the TIMEFORMAT option.
For example, if TIMEFORMAT is set to the default of 1,
the time must be in the format 23:00:00.
If you include the TIMEFORMAT option with the
command, it must precede the FROMTIME and TOTIME options.
. PASSWORDACCESS and PASSWORDDIR
Click on ADSM Options Documentation icon of the ADSM Client folder
(or edit options.doc file) for complete details on the parameters
for these two options.
PASSWORDACCESS
Use the PASSWORDACCESS option to specify how you want to handle the
password for your client node if one is required.
PASSWORDDIR
Use the PASSWORDDIR option to specify the directory in which you want
ADSM to store a file that contains your encrypted password. Use this
option only when you specify Generate for the PASSWORDACCESS option.
──────────────────────────────────────────────────────────────────────────
General Information
───────────────────
- MIGRATING FROM EARLIER VERSIONS OF ADSM
ADSM Version 2 backup-archive clients store files in a different format
than the Version 1 clients. The Version 2 clients can back up and restore
data to a Version 1 or Version 2 server. If you have an ADSM Version 1
server and you install a Version 2 client, you can use the two within the
following rules:
* A Version 1 client can back up and restore or archive and retrieve to
a Version 2 server.
* A Version 2 client can back up and restore or archive and retrieve to
a Version 1 server.
* If a Version 2 client backs up data to a Version 2 server, that data
cannot be restored by a Version 1 client.
* A Version 2 client can back up and restore data that has previously
been backed up by a Version 1 client.
* A Version 1 client cannot back up or restore data that has previously
been backed up by a Version 2 client.
* A Version 2 administrative GUI can administer Version 1 servers, but
invoking Version 2 functions causes an error message.
* All command line administrative clients can administer either Version
1 or Version 2 servers.
* HSM clients can only work with Version 2 servers.
Once you start to use a Version 2 client you cannot switch back to a
Version 1 client. If a Version 1 client tries to restore Version 2 data
or perform a incremental backup after a Version 2 backup, an Unknown
format message is displayed.
Because the Version 2 clients store files in a different format than the
Version 1 clients, ADSM updates the attributes for each active file on the
ADSM server during the first incremental backup after you install the
Version 2 client.
--------------------------------------------------------------------------
- Support for IBM OS/2(*) Lan Server:
ADSM has full support for the 386 HPFS file system.
386 HPFS is an option of the IBM OS/2(*) Lan Server 3.0 - Advanced
product. ADSM will back up and restore Access Control Lists
(ACLs) on an individual file and directory basis of local 386
HPFS drives. ADSM must be installed on the OS/2 Lan Server
workstation and have administrator authority.
ACL data for files and directories will not be saved on
drives attached with the NET USE command. Drives must
be local.
ACL data for non-386 HPFS drives, which includes IBM OS/2(*) Lan
Server 3.0 - Entry and earlier version of the IBM OS/2(*) Lan
Server, is stored in the NET.ACC file. ADSM can back up and
restore this file; but ADSM will not back up and restore ACL
data on an individual file or directory basis.
-----------------------------------------------------------------
NEW INTERMEDIATE AND FINAL STATISTICS AFTER RESTORE OR RETRIEVE:
ADSM command line clients now report final statistics after a
RESTORE or RETRIEVE operation, similar to the backup statistics.
In addition, after every 50 files have been restored or
retrieved, a line is displayed that shows the total number of
files that have been restored or retrieved to that point.
Example of new final output:
Total number of objects restored: 62
Total number of bytes transferred: 4,667.6 KB
Data transfer rate: 551.00 KB/sec
Total failures: 0
Elapsed processing time: 0:01:13
-----------------------------------------------------------------
DOUBLE BUFFER READS MAY IMPROVE PERFORMANCE ON SOME PLATFORMS:
ADSM clients now use double buffers to read from the
TCP/IP, IPX, NETBIOS, and SNA LU6.2 communication buffers.
This may enhance performance on some client platforms
using these communication methods, and may reduce network
traffic in some cases.
──────────────────────────────────────────────────────────────────────
Known Problems
──────────────
- Pressing CTRL-C from the DSMADMC -CONSOLE client command and using
3270 communications causes a SYS3175 error message.
Currently, simply select OK on the error message and continue. OS/2(*)
will clean up from this error.
- ADSM does not backup ACL data from a LAN Server V3.0 entry level
client. This is because ADSM uses the HPFS386 file system to notify
itself as to the contents of the ACL data. The entry level of LAN
Server V3.0 does not contain HPFS386 or the API's needed to obtain
this ACL data.
- Message code ANS2628E (Transaction Processing Stopped) is issued
from time to time while doing an incremental backup and using APPC
communications.
──────────────────────────────────────────────────────────────────────
Fix Information
───────────────
------------------------------------------------------------------
APARs Fixed since the last Version 1 Release 2 maintenance release
------------------------------------------------------------------
IC07906 - ADSM does not recognize when ACL are changed during
incremental backup.
IC08872 - When redirecting dsmc restore with -pick option to
a file, SYS3175 SYS1811 occurs with the output file > 100K.
IC09038 - OS/2 client backup/restore GUI does not show the
restore/retrieve drive's label information when viewed as ICON.
IC09111 - OS/2 GUI client does not log the failing filenames
in dsmerror.log file.
IC09374 - ANS4095I should be ANS4095E, need message number for
archive failure in command line and schedule mode clients.
IC09551 - Client options for schedule lost on Admin GUI
IC09672 - Commandline client schedule log no statistics written
in quiet mode.
IC09857 - Elapsed time is incorrect when backups take more
than 24 hours.
IC09862 - When Viewing Events Log with the Admin GUI,
if dsmadm.cfg has invalid filter data, the user cannot change
the values for the invalid fields.
IC10131 - TRAP D on bad EA data during incremental backup
---------------------------------------------------
PTF IP20500(ENG) - Version 2, Release 1, Level 0.1
PTF IP20527(JPN) - Version 2, Release 1, Level 0.1
PTF IP20528(SVE) - Version 2, Release 1, Level 0.1
PTF IP20529(DEU) - Version 2, Release 1, Level 0.1
PTF IP20530(ESP) - Version 2, Release 1, Level 0.1
PTF IP20531(ITA) - Version 2, Release 1, Level 0.1
PTF IP20532(FRA) - Version 2, Release 1, Level 0.1
---------------------------------------------------
IC10795 - Fix for deletion of the local copy of a file during a
prompted restore dialog, "show prompt" for GUIs or rep=prompt
for command line clients, when the file exists on the
workstation and a communication timeout occurs.
IC10823 (IC10340) - backup terminates when EA data is close to
64K on a directory or file, system error 151 is displayed.
IC10877 (IC10183) - transfer rate value is not correct when
NUMBERFORMAT option is specified as 2/3/4/5/6.
---------------------------------------------------
PTF IP20561(ENG) - Version 2, Release 1, Level 0.2
PTF IP20562(JPN) - Version 2, Release 1, Level 0.2
PTF IP20563(SVE) - Version 2, Release 1, Level 0.2
PTF IP20564(DEU) - Version 2, Release 1, Level 0.2
PTF IP20565(ESP) - Version 2, Release 1, Level 0.2
PTF IP20566(ITA) - Version 2, Release 1, Level 0.2
PTF IP20567(FRA) - Version 2, Release 1, Level 0.2
---------------------------------------------------
IC10814 - SAGUI stgpool destination for migrated files
should be grayed out for type of space management when
none is specified.
IC10924 - A storage pool has a device class of cartridge
or tape and MAXSCRATCH is set to 100,000,000. The ADMIN-
client shows a negative number or a wrong positive number
for the estimated capacity.
IC10925 - In SAGUI, if you do a help for MAXSCRATCH VOLUME
field, it should say the limits are 0 - 100,000,000.
IC10950 - SAGUI should have functionality to change the
number of migration processes.
IC11063 - Scheduler cannot reconnect after password changed.
IC11126 - GUI problem in MediaWait window when restoring from tape.
IC11147 - SYS3175 issued by ADSM API when more than 50
filespaces exist on the ADSM server for the given node.
IC11172 - MAXSCRATCH VOLUME field is missing when updating a
storage pool copy in SAGUI.
IC11184 - ADSM cannot backup volumes on D/T3995-A23 optical drives.
IC11193 - ADSM Notes Backup Agent abends (SYS3175) during
restore of selected documents, if one of the things selected
from the view for restore is a category. The abend happens
after the failure to restore a category.
IC11198 - Getting SYS3175 on ADSM OS/2 client when running
incremental backup on local HPFS386 drives.
IC11222 - When specifying anything other than the default
DATEFORMAT, the GUI will crash when opening the Sequential
Volume History Delete or Include windows.
IC11228 - Restore stalls (slow) when restoring large number
of files.
IC11235 - Access violation exception in client GUI when
backing up from diskette and with 145+ filespaces already
existed on server.
IC11259 - Error message ANS4228E & ANS4119E produced when file
is excluded, causing schedule to log failure.
IC11268 - When using NETBIOS to logon to ADSM V2R1, dsmadm
is NOT working. SYS3171 is returned.
IC11278 - Misleading "Restore processing finished" message
issued for restore session when communications failure occurs.
IC11303 - In Admin GUI under Activity Log include window,
include criteria (ie search string) will be truncated at the
first blank.
IC11321 - OS/2 client does not have PASSWORD GENERATE
IC11363 - OS/2 client GUI's LOGO appeared to be corrupted
because the Drive Window is painted too early.
IC11430 - RESTORE -INA -PICK -FROMDATE -TODATE gives wrong
list of files.
IC11460 - OS/2 Admin GUI gives wrong result when sorting
on Percent Reclaimable of Storage Volume List
IC11484 - CID install of V2 OS/2 client results in message
"EPFIE212:The requested action could not be performed unattended"
being logged to ADSMINST.ERR file.
IC11552 - When using set access and the file does not exist on
the system, ADSM will change the filename to a directory.
IC11629 - SAGUI In the Storage Pool properties and add
notebooks, the range of the high migration threshold
should be 0-99, instead of 1-99.
IC11690 - SAGUI get SYS3171 when using NETBIOS in the GUI, under
STORAGEPOOL Volume
IC11814 - Internal APAR for new features and defects found internally:
New features:
. New options -TOTIME and -FROMTIME on RESTORE, RETRIEVE,
QUERY ARCHIVE, and QUERY BACKUP command line cmds
. Final statistics at end of RESTORE and RETRIEVE command line
. Double buffers used internally for reading from NETBIOS,
TCP/IP, IPX, and SNA LU6.2, possibly helping performance
on some platforms
. Client will now try to establish a new session with the
server three times on Restore if session times out.
To Cancel Session now from server during client Restore:
Disable server, Cancel session#, Enable server
. SAGUI User Name field for owner name in the Sessions container
Defects:
. OS/2 ADSM About (logo) window unreadable on 640x480
. OS/2 List File button cut off on 640x480 screens
. SAGUI Server Activity log defaults problem
. Command line Backup or Archive quits if tapeprompt prompt
is not quickly answered and the server times out
IC11871 - CID install of OS/2 client from an net used drive, receives
message - EPFIE187: A product specifc error occurred.
IC11981 - Client using IPXSPX communication method gets invalid
option specified when a valid IPX address is used with option
IPXSERVERADDRESS (any address that has a hex value of '63' imbedded
in it).
========================================================================
Trademarks
──────────
(*) Trademark or Registered Trademark of International Business Machine
Corporation
The following are registered trademarks or trademarks (**) of the indicated
company: Intel: Intel Corporation, CompuServe: Compuserve.