======================================================================== IBM ADSM for Windows NT Version 3 Read1st File Including Enterprise Management Information (c) Copyright IBM Corporation, 1997-1998 | Last Updated: 3.1.2.13 (includes fixed uninstall) ======================================================================== | Welcome to the ADSTAR(*) Distributed Storage Manager. This is service | level 3.1.2.13 for the ADSM for Windows NT server, Version 3 Release 1. This is divided into the following sections: I. ADSM SERVER | o EMERGENCY FIX for APAR IX85298 | o THIS UPDATE ALSO INCLUDES THE FIX for APAR IX85125 o Overview of new function in this Server | o New server security option | o New Licensing information o Notice for WEB browser users | o Notes for use of the SNMP sub-agent (dsmsnmp) o Migration by age limitation | o Drive Cleaning support for SCSI tape libraries | o CHECKIN and LABEL command changes o Information on Data Errors in prior levels of ADSM Version 3 | o Clarification of fix to APAR IX79626 o Version 3 Release 1 APARS fixed by prior service levels | o Version 3 Release 1 APARS fixed by this service level II. ADSM CLIENT | o Before You Install Your ADSM Client | o Installing the ADSM Client | o Late-Breaking News. | o APARs Fixed in this PTF III. ADSM INFORMATION o Where to find Documentation o Getting Help o Trademarks | Items in this README which have been added or changed since the last | EMERGENCE FIX or Normal service level are marked with change bars | ('|') in the left column. *====================================================================== * I. ADSM SERVER *===================================================================== ********************************************************************** * EMERGENCY FIX for APAR IX85298 * ********************************************************************** | The version control for backup objects is not properly | maintaining the versions exists attribute for the copygroup | managing a given file. The error is that the versioning | algorithm is not marking files to be eligible for expiration | when the count of the number of versions for a given file | exceeds the versions exists value. Consequently, more files | are being kept in the server and the files are not being | expired when they should. | | Please note that the error is that the server is NOT expiring | data when it should actually be expiring it. ********************************************************************** * THIS UPDATE ALSO INCLUDES THE FIX for APAR IX85125 * ********************************************************************** | The ADSM V3 server can automatically make a drive unavailable if | it detects that there is a problem with it in some way. To allow | ADSM to use that drive again (after any problems with it have | been resolved) an ADSM Admin needs to issue 'UPDATE DRIVE' with | 'online=yes'. Under certain conditions the update process can | deadlock. The condition that can lead to deadlock is heavy | tape/drive utilization by the server such that mountpoint | processing is occuring at the same time that the update drive is | issued. *====================================================================== * Overview of new function in this Server *===================================================================== This section provide a brief description of the function that has been added to this Enterprise Management server. For more information, please refer to the manuals that were provided on the server CD. * NOTE * NOTE * NOTE * NOTE * NOTE * NOTE * NOTE * NOTE * NOTE * This server provides enhanced recovery log fault-tolerance and new database entries to support enhanced functions. If you start this server over an existing ADSM database, you will not be able to remove this server program and run the older server over the existing database/recovery log. * NOTE * NOTE * NOTE * NOTE * NOTE * NOTE * NOTE * NOTE * NOTE * Central Console The administrative WEB interface to the server has been enhanced for ease of use in navigation and the administration of multiple servers from a single interface. This interface is available from a Netscape version 4+ or Internet Explorer Version 4 browsers. The Netscape browser will require a patch from Netscape to support the JDK 1.1 function in the Java applets in the interface. Please see the section entitled "Notice for WEB browser users" for more information on this. Security for the WEB conversation has been enhanced through the option use of secure sockets layer (SSL) encrypted conversations. Please refer to the section entitled "Generating SSL certificates" for more information. The SSL encryption is not yet available for the MVS server. Central Configuration The central configuration function allows you to establish a server as the master configuration server for your enterprise, and then have others servers automatically inherit their configuration information (such as policy definitions) from the master configuration server. Central Commands The central command function provides a means for you to route server commands for execution across multiple server in your enterprise. The results from the routed commands are displayed at the screen from which the command was specified. Central Logging The event logging function provided in version 3 has been enhanced to support logging client and server events to a central server. This central server can then forward the events to other receivers such as SNMP or Tivoli, store the events in the server database, or log them to the console for monitoring by operations personnel. The Windows NT server has been enhanced to support sending client/server events to the Windows NT event log so they can be displayed by the event viewer. The data structure for the FILE and USER EXIT event receivers has been modified. A description of the data structure for an event can be found in the user exit sample (userExitSample.h). Because of the change, the version field has been updated to 2. You will need to recompile your existing user exit to utilize this new data structure. Server automation Server automation has been enhanced with command scripts that are stored in the server database, allow conditional logic based on command return codes, and can be scheduled for execution using the server's administrative command scheduler. Database and recovery log policy can now be established to automatically add space and extend the database/log when specified utilization is encountered. This frees the administrator from having to monitor database/log utilization on a regular basis. Central Reporting/Monitoring A number of sample SQL queries have been developed and provided to you in the form of command scripts to assist in obtaining useful information from the ADSM server. The SNMP MIB interface now allows you to execute command scripts from SNMP, returning the results from the script. Overflow storage pools To ease the management of automated libraries, this function allows you to checkout volumes from a library based on last use date so that slots can be used for new volumes. Prepare output on another server The prepare function has been enhanced as part of the Disaster Recovery Manager (DRM) feature to store recovery plan files directly on another ADSM server in the enterprise. This information can be queried and retrieved interactively through the WEB administrative interface. Prepare output can only be stored on other 3.1.2 servers, not on 3.1.1 servers. NEW/CHANGED COMMANDS: COPY SERVERGROUP COPY PROFILE DEFINE EVENTSERVER DEFINE GRPMEMBER DEFINE SCRIPT DEFINE PROFASSOIATION DEFINE PROFILE DEFINE SERVER DEFINE SERVERGROUP DEFINE SPACETRIGGER DEFINE SUBSCRIBER DELETE EVENTSEREVR DELETE GRPMEMBER DELETE SCRIPT DELETE PROFASSOCIATION DELETE PROFILE DELETE SERVER DELETE SERVERGROUP DELETE SPACETRIGGER DELETE SUBSCRIBER DELETE SUBSCRIPTION DELETE VOLHISTORY DISABLE EVENTS ENABLE EVENTS LOCK PROFILE MOVE GRPMEMBER NOTIFY SUBSCRIBERS PING PREPARE QUERY ENABLED QUERY EVENTRULES QUERY EVENTSERVER QUERY LICENSE QUERY PROFILE QUERY RPFILE QUERY RPFCONTENT QUERY SERVER QUERY SERVERGROUP QUERY SPACETRIGGER QUERY SUBSCRIBER QUERY SUBSCRIPTION QUERY VOLHISTORY RENAME SCRIPT RENAME SERVERGROUP RENAME STGPOOL RUN SET CONFIGMANAGER SET CONFIGREFRESH SET CROSSDEFINE SET DRMRPFEXPIREDAYS SET SERVERPASSWORD SET SERVERHLADDRESS SET SERVERLLADDRESS SET SERVERURL UNLOCK PROFILE UPDATE SCRIPT UPDATE PROFILE UPDATE SERVER UPDATE SERVERGROUP UPDATE SPACETRIGGER ********************************************************************** * NEW SERVER SECURITY OPTION * ********************************************************************** ADSM has been updated to provide additional control related to the administrative authority required to issue selected commands that cause the ADSM server to write information to an external file. A new server option REQSYSAUTHOUTFILE has been added to control this processing. REQSYSAUTHOUTFILE YES: Specifies that system authority is required for administrative commands that cause the server to write to an external file. The commands and associated parameters that are controlled by this option are: - MOVE and QUERY DRMEDIA when the CMD parameter has been specified - MOVE and QUERY MEDIA when the CMD parameter has been specified - BACKUP VOLHISTORY when the FILENAMES parameter has been specified - BACKUP DEVCONFIG when the FILENAMES parameter has been specified - TRACE BEGIN when a file name has been specified - QUERY SCRIPT when the OUTPUTFILE parameter has been specified REQSYSAUTHOUTFILE NO: Specifies that system authority is not required for administrative commands that cause the server to write to an external file (i.e. there is no change to the privilege class required to execute the command). The default is REQSYSAUTHOUTFILE YES. In addition, when REQSYSAUTHOUTFILE NO has been specified, authorization changes have been been made to select QUERY commands that cause the ADSM server to write information to an external file. The commands and their associated authorization changes are: - QUERY DRMEDIA or QUERY MEDIA with the CMD parameter require operator, unrestricted storage or system authority. - QUERY SCRIPT with the OUTPUTFILE parameter require, operator, policy, storage or system authority. The explanation for ANR2035E has been updated to indicate that this message can be issued as a result of the server option REQSYSAUTHOUTFILE YES. Note, it is assumed that proper access controls are in place for the server options file dsmserv.opt. Authorization to change or delete an ADSM command script have changed. The UPDATE SCRIPT and DELETE SCRIPT command, have the following additional controls in place: - An ADSM administrator with system privilege can change or delete any script - If an ADSM administrator does not have system privilege, the administrator must have previously created or updated the script. For scripts created after the application of this maintenance, only a system administrator or the administrator that created the script will be allowed to update or delete the script. A new message ANR1493E will be issued if the administrator is not authorized. ********************************************************************** * NEW LICENSING INFORMATION * ********************************************************************** The following functions are licensed as a separate Enterprise Administration feature in this server: Central Configuration Central Logging Central Commands To enable the "Enterprise Administration" license, use a text editor to cut out the following lines from this readme file into a license certificate file named 'entadmin.lic' : *------------------------- cut here ----------------------------------- (LicenseCertificate) CheckSum=1C88F172ED60F14D3A0796C685041A8A TimeStamp=896968609 PasswordVersion=4 VendorName=IBM Corporation VendorPassword=uw7jvac4k3umq VendorID=6fb1ea8d2ebc.a3.89.a3.25.04.00.00.00 ProductName=ADSM Enterprise Admin ProductID=21364 ProductVersion=3.1 ProductPassword=nv7d2xagpibikab2raaxnaa ProductAnnotation= LicenseStyle=nodelocked LicenseStartDate=06/03/1998 LicenseDuration=14457 LicenseEndDate=12/31/2037 LicenseCount=1 MultiUseRules= RegistrationLevel=3 TryAndBuy=No SoftStop=No TargetType=ANY TargetTypeName=Open Target TargetID=any DerivedLicenseStyle= DerivedLicenseStartDate= DerivedLicenseEndDate= DerivedLicenseAggregateDuration= *------------------------- cut here ----------------------------------- To register the license on the server, use the REGISTER LICENSE command to read the license information into the server: REGISTER LICENSE FILE=ENTADMIN.LIC | DRM Licensing - Clarification | The DRM license on the source server is the only license required to | store a recovery plan file on another server (i.e. the VIRTUAL VOLUMES | license is not required on the source and target servers, and the | NETWORK license is not required on the target server). ********************************************************************** * NOTICE FOR WEB BROWSER USERS * ********************************************************************** The web interface for administrative functions requires that your browser have jdk 1.1 support. the following instructions detail how to get this support for Netscape 4.0. Internet Explorer 4.0 has this support: Java 1.1 support is required for using the newly enhanced web interface. Below are instructions on how to upgrade your browser. Netscape Communicator Verify that you are currently running Netscape Navigator 4.03 or better. If you need to upgrade, go to http://home.netscape.com/download/ and follow the instructions to upgrade your current browser. For Windows NT/95 users, go to http://help.netscape.com/filelib.html#smartupdate and press the JDK Update Button (third button under the Win32 heading). This will start an automatic update of your browser. During installation you will be prompted to Grant or Deny a request to install software. Grant the request so installation can occur. Follow the instructions provided. When installation is complete, close Netscape Navigator and reopen the application. To verify that a proper installation has occurred, select Java Console from the Communicator menu. The first line of the Java Console should read Netscape Communications Corporation -- Java 1.1.4. For UNIX users, go to http://developer.netscape.com/software/jdk/download.html#UNIX_INSTALL . Here you will find information on how to download and install the patch for various flavors of UNIX. Internet Explorer You will need Internet Explorer 4.01 or higher for Java 1.1 support. To obtain the latest version of IE 4.0 go to http://www.microsoft.com/ie/download. Follow the provided instruction to install the product. HELP WINDOWS Due to a Javascript support problem in Netscape, if you resize the panel help window the 'close' button may not function correctly. If this should happen, you can always close the window by using the window's close icon. ********************************************************************** * NOTES FOR USE OF THE SNMP SUB-AGENT (dsmsnmp) * ********************************************************************** ADSM 3.1.2 servers cannot be used with versions of the SNMP subagent ( dsmsnmp ) prior to 3.1.2 and vice versa; Command output from SNMP subagents which run scripts on ADSM servers is truncated to 4026 characters. This is a limitation of SNMP agents. | The following files are updated for service level 3.1.2.1: | | dsmsnmp | aix.adsm.defs | mib2adsm.tbl | adsmserv.mib | | Two MIB variables have been added for control of text output from the | SNMP subagent; These variables allow control over column delimiters and | line delimiters. The two variables are: | | ibmAdsmServerLineDelimiter | and | ibmAdsmServerValueDelimiter | | These variables default to 0, which operates the same as the original | dsmsnmp, i.e., lines are delimited by carriage return/line feed | sequences and columns are delimited by blanks. | | Each variable is an enumerated type ranging from 1-5 and 1-3 | respectively (the enumerations are documented in the MIB ). | | If ibmAdsmServerValueDelimiter is non-zero, the output in | ibmAdsmM1ReturnValue works as the administrative command line client | -commadelimit and -tabdelimit parameters, separating commas by either | commas or tabs. These are for values 1 and 2 respectively. A value of | 3 may be used to delimit by a blank. In these cases, column headings are | suppressed. | | For ibmAdsmServerLineDelimiter, the following values are allowed: | | crlf (1) - output as the default with carriage return/line feed | separating lines | lf (2) - output with only a line feed between lines | comma (3) - output with only a comma between lines | tab (4) - output with only a tab between lines | blank (5) - output with only a blank between lines ********************************************************************** * DOCUMENTATION UPDATES * ********************************************************************** Problem: Routed commands using the serverlist: command syntax cannot be used within scripts. If a routed command using this syntax is used in a script, the command will run on the issuing server, not the targeted server. Solution: A new, additional syntax for routing commands is available. Routed commands can also be indicated by the following syntax: (serverlist) command Example: To route the command QUERY VOLUMES to the defined servers JOE and CHARLIE enter either of the following command: (JOE,CHARLIE) QUERY VOLUMES JOE,CHARLIE: QUERY VOLUMES The rules for the list of server names are the same with the new syntax as with the original. The new syntax can be used inside scripts to route commands. Example: To create and run a script CHECK_VOLUMES that routes the command QUERY VOLUMES to the defined servers JOE and CHARLIE enter the following commands: DEFINE SCRIPT CHECK_VOLUMES '(JOE,CHARLIE) QUERY VOLUMES' RUN SCRIPT CHECK_VOLUMES Updates to the Command Routing information: Administrators can route commands to one server, a server group or a list that contains multiple servers, multiple server groups or a combination of servers and server groups. Each server or server group in a list must be separated with a comma, without spaces. The server, server group, or list must be followed immediately by a colon or enclosed in parentheses, and followed by the command to be processed. Spaces are allowed between the end colon or parentheses and the command to be routed. The end parenthesis or the colon after the server name indicates the end of the routing information. Updates to the UPDATE and DEFINE SCRIPT command, and the information on using scripts: Command routing in a SCRIPT must be done using the parentheses. If command routing is done using the colon syntax, the command will not be routed when the RUN command is issued, and will instead run on the server where the RUN command is issued. ******************************************************************************** * Migration by age limitation * ******************************************************************************** Migration by age from disk will not be available in service level 3.1.2.0 The MIGDELAY and MIGCONTINUE parameters on the storage pool definition are only operational for sequential storage pools and not for disk storage pools at this time. These parameters will be enabled for disk storage pools in a later service level. ******************************************************************************** * Drive cleaning support for SCSI tape libraries * ******************************************************************************** | ADSM 3.1.2.1 includes ADSM-controlled cleaning of tape drives in a | SCSI library and partial support in stand-alone (manual) libraries. | | This support is intended to be used ONLY for those scsi libraries that | do NOT have their own automatic cleaning in the device hardware. | Automatic cleaning is included in such libraries as the STK 9710 and | IBM 3570 and 3575, and ADSM is not aware or involved with it in any | way. ADSM-controlled cleaning is not as tightly integrated with the | device hardware as a library's own automatic cleaning and may actually | conflict with it. The default for ADSM-controlled cleaning is NONE, | which means cleaning is up to the library hardware or a human | operator. | | The automatic cleaning included in some SCSI libraries interferes with | ADSM's use of the library and drives. If this is the case with your library, | turn off the built-in automatic cleaning and use ADSM-controlled cleaning. | ** ATTENTION ** | | Use of ADSM-controlled cleaning involves checking a cleaner cartridge | into the library's volume inventory. Be careful when using the | CHECKIN, CHECKOUT, LABEL, and AUDIT LIBRARY commands to ensure that a | cleaner cartridge is not inadvertently loaded into a drive instead of | a data cartridge. Details on how to prevent mistaking a cleaner | cartridge for a data cartridge are provided below. | | | Overview for SCSI Libraries | | You set up ADSM-controlled drive cleaning with the following three | steps: | | 1. Define the drives in a library with the new parameter that | defines the frequency of cleaning. | | 2. Check a cleaner cartridge into the library's volume inventory. ADSM | mounts the cleaner cartridge in a drive when it needs cleaning. | | 3. When needed, issue or schedule the new command, CLEAN DRIVE. Use | this command when you want ADSM to immediately load a cleaner cartridge into | a drive regardless of the cleaning frequency. | Details on these steps follow. | -------------------------------------------------------------------------------- | 1. Defining the drives with frequency of cleaning | | A new parameter, CLEANFREQUENCY, is added to the DEFINE DRIVE command. | The following is the new DEFine/UPDate command syntax: | | >>-DEFine/UPDate DRive--libname--drivename--DEVIce-=-devicename-> | | .-ONLine--=--Yes------. | >---+---------------------+--+----------------------------+-----> | '-ONLine--=--+-Yes-+--' | | | '-No--' '-ELEMent--=--elementaddress-' | | '-CLEANFREQuency-=-+-NONE------+ | >---+------------------------------+--------------------------->< | '-CLEANFREQuency-=-+-NONE------+ | |-ASNEEDED -| | | '-value-----' | | For the CLEANFREQUENCY parameter, possible values are: | - NONE, meaning ADSM does not track the need for device cleaning. | This is the default. Use for libraries that have their own automatic | cleaning. | - ASNEEDED, meaning that only when a drive reports a cleaning-needed | indicator to the device driver does ADSM load the drive with a | checked-in cleaner cartridge. | - A value from 1 to 9999 that specifies how much data in Gigabytes | should be processed on the drive before ADSM loads the drive with a | cleaner cartridge. ADSM also responds to cleaning-needed indicators | from a drive with this option, as for the ASNEEDED option. | | When the drive indicates that it needs to be cleaned or the | GBytes-processed threshold is exceeded, the drive finishes processing | the volume that is mounted on it. As part of the dismount processing, | ADSM loads a cleaner cartridge into the drive (provided that one is | checked into the library inventory) and resets the GBytes-processed | counter. | | 2. Check a cleaner cartridge into the library's volume inventory | Use the CHECKIN LIBVOL command to check a cleaner cartridge into the | library. The following is the CHECKIN LIBVOL command syntax showing | the new STATUS value of CLEANER and the new CLEANINGS parameter: | | >>-CHECKIn LIBVolume--libraryname--volname----------------------> | | .-CHECKLabel--=--Yes--------------. | >---STATus--=--+-PRIvate-+--+---------------------------------+-> | |-SCRatch-| '-CHECKLabel--=--+-Yes---------+--' | '-CLEaner-' +-No----------+ | '-Barcode-----' | | .-SWAP--=--No-------. | >----+-------------------+--VOLRange--=--+-volname1-+-----------> | '-SWAP--=--+-No--+--' '-volname2-' | '-Yes-' | | .-MOUNTWait--=--60---------------. | >---+--------------------------------+--------------------------> | '-MOUNTWait--=--mountwaitvalue---' | | .-SEARCH--=--No------------. | >----+--------------------------+-------------------------------> | '-SEARCH--=--+-No-------+--' | +-Yes------+ | '-Bulk-----' | | >----+-----------------------+--------------------------------->< | '-CLEANINGS--=--1..1000-' | | The STATUS=CLEANER parameter value designates the volume as a cleaner | cartridge and not a data cartridge. Check in a cleaner cartridge | separately from data cartridges using STATUS=CLEANER. | | The CLEANINGS parameter is required for cleaner cartridges. Set the | value to the recommended number of uses for the cleaner cartridge | (usually indicated on the cartridge). | The volume name is arbitrary, because the name is never read from the | cleaner. However, if the cleaner has a barcode label, use that value | as the volume name. | | CHECKLABEL=YES is invalid for checking in a cleaner. | Although you can check in cleaner cartridges using SEARCH=YES, it is | recommended that you check them in one at a time. | | If you check in more than one cleaner cartridge, ADSM uses only one | cartridge until that cartridge is used the number of times indicated | by the CLEANINGS value. ADSM then selects another cleaner cartridge, | and you can check out and discard the first cartridge. When a cleaner | cartridge has five or fewer cleanings left, ADSM issues a warning with | each use. | | You cannot update the status of a volume from CLEANER to SCRATCH or PRIVATE, | and vice versa. If you have checked in a volume with the wrong status, you | must check the volume out and check it back in again with the correct status. | This process helps to prevent changing a cartridge to the wrong status. | When you check out the volume, use the REMOVE=YES option of the CHECKOUT | command, so that you can verify the type of cartridge. | | You can change the CLEANINGS value by using the UPDATE LIBVOLUME command with | the STATUS=CLEANER parameter. | | 3. When needed, issue or schedule the new command, CLEAN DRIVE. | | The syntax of the command is: | | >>-CLEAN--DRIVE--libraryname--drivename---------------------->< | | This command is valid only in a SCSI library that has a cleaner | cartridge checked into its inventory. This command marks the drive as | needing to be cleaned. If the drive is not busy at the time, ADSM | loads the cleaner cartridge into the drive immediately. If the drive | is busy, ADSM loads the cleaner cartridge when the drive is unloaded. | | | Determining How Often A Drive Should Be Cleaned | | Consult the manuals that accompany the drives for cleaning | recommendations. In some cases, the manuals describe the cleaning | frequency in terms of hours of use. In this case, use the drive's | bytes per second speed rating to determine a GBytes per hour value for | the drive. Then multiply the GBytes/hour by the recommended hours of | use between cleanings. Use the result as the CLEANFREQUENCY to be set | on the drive definition. Alternatively, you can set the | CLEANFREQUENCY to ASNEEDED to allow the drive to signal when it needs | to be cleaned. In some cases, however, this alternative is not | reliable. | | | Preventing Problems When Using A Cleaner Cartridge in a SCSI library | | When a cleaner cartridge is checked in to the library, ADSM cannot | verify that the cleaner cartridge is in fact a cleaner. Various | ADSM-supported drives and libraries differ in how they handle | cleaners, how they report the presence of cleaners in a drive, and how | the device drivers on different platforms are able or are not able to | open a drive that may contain a cleaner at the time. This variability | means that ADSM cannot uniformly detect a cleaner cartridge. For this | and other reasons, ADSM does not intentionally load the cleaner | cartridge into a drive until the drive needs to be cleaned. | | Because of ADSM's limited ability to recognize a cleaner, ensure that | you do not check in a data cartridge with STATUS=CLEANER, and that you | do not check in a cleaner with STATUS=SCRATCH or PRIVATE. For | instance, when running a CHECKIN or LABEL command with SEARCH=YES, do | not allow a cleaner to be placed in a slot that will be detected by | that search process. TO DO SO WILL PRODUCE A NUMBER OF ERRORS, | including I/O errors and long delays on drive loads and unloads, which | may be on the order of 15 minutes. | | Cleaners that are already checked in are not a problem when checking | in data cartridges with SEARCH=YES, provided that the cleaners are in | their correct home slots. To help you verify that cleaners are in | their correct home slots, the QUERY LIBVOL command now provides the | element ID of the home slot for all library volumes. Visually verify | the correct storage slots for cleaners before using a search process | to check in volumes or before auditing a library. PLEASE NOTE: | Because AUDIT LIBRARY does not audit a slot that has a cleaner | cartridge checked into it, visually verifying a cleaner's home slot is | especially important before running an AUDIT LIBRARY command. | | If a drive needs to be cleaned, ADSM runs the cleaning operation after | dismounting a volume. If the cleaning operation fails or is | cancelled, or if no cleaner is checked in that has any cleanings left, | then the indication that the drive needs cleaning is lost. Monitor | cleaning messages for these problems. If necessary, clean the drive | either by issuing a CLEAN DRIVE command or by manually loading a | cleaner into the drive. | | | Drive Cleaning Without Checking a Cleaner Into the Library | | You can specify a cleaning frequency for a drive without checking a | cleaner cartridge into the library. When a drive needs to be cleaned | based on the clean frequency criteria, ADSM issues this message: | | ANR8914I Drive in library needs to be cleaned. | | The message is issued whether or not a cleaner is checked into the | library. You can use that message as a cue to manually insert a | cleaner into the drive. You may want to do this if you do not want to | deal with the constraints of having a cleaner checked into the | library's inventory. There is, however, no support for a QUERY | command to indicate that a drive is in the needs-cleaning state. ADSM | cannot determine from the drive that the drive has been cleaned so | that such an indicator could be turned off after cleaning. | | | Drive Cleaning in a Manual Library | | This support is the same as in "Drive Cleaning without Checking in a | Cleaner." There is no library inventory in a manual library, but the | ANR8914I message is issued when a drive needs to be cleaned. The | operator must monitor for these messages and load a cleaner cartridge | into the drive when needed. ******************************************************************************** * CHECKIN and LABEL command changes * ******************************************************************************** | | A new parameter VOLLIST has been added to the CHECKIN and LABEL LIBVOLUME | commands to allow the user to specify a list of volumes for the process. | | VOLList=volumespec | | Specifies the volume names that are to be used by the CHECKIN or LABEL | commands. volumespec can be a list of volume names or a file that a | list of volume names. | | VOLList=vol1,vol2,vol3 ... | specifies the names of the volumes. Each volume name is separateed by | a comma with no intervening spaces. For example: | VOLL=TAPE01,TAPE02,TAPE03 | | VOLList=FILE:filename | Specifies the path and name of the file that contains a list of volumes. | In the file, each volume name must be on a separate line. Blank lines | and comment lines that begin with an asterisk are ignored. | For example, to use TAPE01, TAPE02 and TAPE03, create a file called | TAPEVOL that contain these lines: | TAPE01 | TAPE02 | TAPE03 | and specify the parameter as follow: | VOLL=FILE:TAPEVOL | | The path and filename are case sensitive. | This parameter is optional. However, if specified the | SEARCH=YES option must also be specified. In addition, if specified, the | existing VOLRrange parameter must not specified. | This parameter is supported for SCSI, 3494 or ACSLS libraries. | | | | CHECKOUT command: | ----------------- | | To support the bulk volume checkout function from a ACSLS library, two parameters, | VOLRANGE and VOLLIST have been added to the CHECKOUT LIBVOLUME command to | allow the user to specify a list of volumes or a range of volumes. If either | VOLRANGE or VOLLIST is specified, the existing "volname" for the single volume | checkout function must not specified. | | VOLRANGE and VOLLIST are not supported for the 3494 and SCSI libraries. When | specified, REMOVE=BULK is treated the same as REMOVE=YES. REMOVE=BULK is not | supported for single volume checkout for the ACSLS library. | | | VOLRange=vol1,vol2 | | Specifies the volume range for this command. The volume format can be | any combination of alphanumeric characters. Basically, it contains prefix, | incremental and sufix areas. | The prefix and sufix areas are optional. If they are used, they are | identical alphanumeric characters between vol1 and vol2. Prefix area | begins at the first character and ends at the first "non-compare" numeric | character. The incremental area are numeric characters which begins after | the prefix area and ends at the next alpha character, if any. The incremental | numerics of vol2 must be greater than the numerics of vol1. The sufix area, | optional, begins at the end of the incremental area and are all alpha | characters. | | The possible combination for volume range are: | AnA, nA, An, n or A | "A" means the prefix or sufix area where the alphanumeric characters of | vol1 and vol2 are identical. "n" is the incremental area. | For example: | VOLR=ABC123,ABC234 | VOLR=123456,123567 | VOLR=123ABC,234ABC | VOLR=A123BC,A234BC | | This parameter is optional. However, if specified the VOLLIST parameter | must not specified. | | | VOLList=volumespec | | Specifies a list of volume names to be used by the CHECKOUT command. | volumespec can be a list of volumes or a file that contain a list of volumes. | | VOLList=vol1,vol2,vol3 ... | specifies the names of the volumes for the process. Each volume name | is separated by a comma with no intervening spaces. For example: | VOLL=TAPE01,TAPE02,TAPE03 | | VOLList=FILE:filename | Specifies the path and name of the file that contains a list of volumes. | In the file, each volume name must be on a separate line. Blank lines | and comment lines that begin with an asterisk are ignored. For example, | to use TAPE01, TAPE02 and TAPE03, create a file called TAPEVOL that | contain these lines: | TAPE01 | TAPE02 | TAPE03 | and specify the parameter as follow: | VOLL=FILE:TAPEVOL | | The path and filename are case sensitive. | This parameter is optional. However, if specified the VOLRANGE parameter | must not specified. ******************************************************************************** * Information on Data Errors in prior levels of ADSM Version 3 * ******************************************************************************** ADSM Version 3 AIX servers prior to service level 3.1.1.5 and non-AIX servers prior to service level 3.1.1.3 have experienced data errors during movement/reclamation of files stored on sequential-access media. Information regarding these problems has been distributed in several different forms. To reduce confusion, this package updates, summarizes, and simplifies information about these problems. The ADSM organization has gone to great lengths to ensure that problems involving data errors are addressed in a forthright and aggressive manner. While some problems are not likely to be seen by customers, we have nonetheless issued warnings and provided fixes as soon as possible to eliminate the remote possibility of affecting customer data. We have developed commands to identify and manage affected files. Once identified, these files can be recovered from valid copies the server has made, or the files can be deleted so that new backups are produced. NOTE to non-AIX platforms: This PTF contains an updated set of utilities that checks for any data errors that might have been introduced while the server was running at the 3.1.1.3 level. Although data errors at the 3.1.1.3 service level have only been observed on AIX, we are providing the updated utilities on all platforms as a precaution. The updated utilities contain an abbreviated audit that checks for any problem files. FREQUENTLY ASKED QUESTIONS -------------------------- * What is the nature of the data errors? The ADSM server performs various internal operations that move or copy data from one storage location to another. In certain situations, when a file is transferred from a sequential-access volume to another location, the target file may be invalid. * Is my ADSM server affected by these problems? Version 3 servers at levels prior to 3.1.1.5 may contain files with invalid data. * Are Version 1 or Version 2 ADSM servers affected by these problems? No. * Can files be affected that have never been stored on sequential-access storage pool volumes? No. * Weren't these problems corrected prior to 3.1.1.5? In April 1998, PTFs were distributed for all server platforms to correct the original data movement/reclamation problem. The service levels of these PTFs were 3.1.0.2 (MVS) and 3.1.1.1 (non-MVS platforms). More recently, a different Version 3 reclamation problem has been identified. To date, customers have reported this problem only on AIX servers, but we have not excluded the possibility that Version 3 servers on other platforms might also be affected. At this time, we have been unable to recreate the problem in our lab on any server platform, but are continuing to investigate. Service level 3.1.1.5 eliminates this most recent problem and is now available on AIX. * I upgraded from a Version 1 or Version 2 server to Version 3. Will files stored on the early server versions be affected by these problems? In PTF 3.1.0.2 (MVS) and 3.1.1.1 (non-MVS), a problem was corrected that could cause data errors in files that were stored to a Version 1 or 2 server and later moved or copied using a Version 3 server. If you used a Version 3 server that did not contain this fix, it is possible that Version 1 or Version 2 files could be affected. * Can space-managed files be affected by any of these problems? In PTF 3.1.0.2 (MVS) and 3.1.1.1 (non-MVS), a problem was corrected that could cause data errors in space-managed files. If you used a Version 3 server prior to this fix, it is possible that space-managed files were affected. * Is the 3466 Network Storage Manager affected by these problems? The Network Storage Manager may be affected if it has ever operated with ADSM Version 3 at a service level prior to 3.1.1.5. * I am using the ADSM Version 3 server. What can I do now to ensure that data errors are not introduced during data movement/reclamation operations? To avoid possible loss of data, you should apply the latest service level to your Version 3 servers as soon as possible. For AIX, service level 3.1.1.5 is now available and corrects all known data movement/reclamation problems. For all other platforms, service 3.1.1.3 is the latest level and corrects all problems that are known to exist on these platforms. * Why is service level 3.1.1.5 currently available only on AIX? Delivery of this service level was expedited on AIX to correct the recently discovered problem with data errors during reclamation on AIX servers. Although this problem has not been observed on other server platforms, a future PTF will be provided on each platform to eliminate the possibility of similar errors. * I'm still on ADSM Version 2. Is it safe for me to migrate to Version 3? The ADSM development and support groups are confident that it is safe and prudent to migrate to ADSM Version 3, provided that the most current level of maintenance is applied after installation. ADSM Version 3 provides many features that customers have requested and will be a valuable part of your installation. * I'm on ADSM version 2. How do I migrate to Version 3 without being affected by these problems? Install the base ADSM version 3 package and upgrade the database (this is done as part of the install on some platforms). Then install the PTF for level 3.1.1.3 (all server platforms except AIX) or 3.1.1.5 (AIX servers). You are now at the requisite level. For non-AIX servers, a future PTF will contain an updated set of utilities that checks for any data errors that might have been introduced while the server was running at the 3.1.1.3 level. Although data errors at the 3.1.1.3 service level have only been observed on AIX, we will provide the updated utilities on other platforms as a precaution. The updated utilities will contain an 'abbreviated' audit that checks for any problem files. * I do not currently use ADSM, but want to begin. What version should I use? We recommend that you use ADSM Version 3 because it provides many attractive features that are not found in previous versions. However, it is important that you apply the current maintenance level. For AIX servers, this is level 3.1.1.5. For other platforms, the latest service level is 3.1.1.3. For non-AIX servers, a future PTF will contain an updated set of utilities that checks for any data errors that might have been introduced while the server was running at the 3.1.1.3 level. Although data errors at the 3.1.1.3 service level have only been observed on AIX, we will provide the updated utilities on other platforms as a precaution. The updated utilities will contain an 'abbreviated' audit that checks for any problem files. * Can anything be done to deal with files that have already been affected by these problems? A set of utilities has been developed to identify and handle files that have been affected by these problems. These utilities are included in the latest Version 3 PTF. The utility functions are run by issuing commands on the ADSM console or from an administrative client. The utilities have been updated in service level 3.1.1.5 and later. The updated utilities check for all known types of data errors caused by data movement/reclamation, including the most recent problem. * What do the utilities do? The utilities include an audit command which identifies and gathers information about any files that are affected by these problems. An SQL SELECT command can then be used to view this information. Existing commands can be used to restore affected files from a copy storage pool, if valid copies are stored in the copy pool. A delete command is also provided for deleting database references to affected files. * Rather than using the reclamation utilities, can I use the AUDIT VOLUME command to detect any files that have been affected by these problems? No. The reclamation utilities are the only dependable way to detect these problems. * I have already run the utilities that were included with service level 3.1.1.2 or 3.1.1.3. Is there anything else I should do? In July 1998, the utilities were modified to detect files that have been affected by the reclamation problem that has recently been observed on AIX servers. AIX servers should be upgraded to 3.1.1.5 as soon as possible to eliminate the possibility of additional data errors because of this problem. You should then re-run the utilities, using the "abbreviated" audit mode. Although this reclamation problem has only been observed on AIX, a fix will be provided in the next PTF for other servers to ensure that they are not affected by a similar problem. When the next PTF becomes available on your server platform, you should apply this service. As a precautionary measure, after you have applied this PTF, we recommend that you run the updated utilities using the 'abbreviated' audit mode. * I have started using the utilities included with service level 3.1.1.2 or 3.1.1.3, but have not yet finished and issued the CLEANUP RECLAIM command. What should I do? You should finish running the utilities, including the CLEANUP RECLAIM command. Then apply the PTF with the updated utilities and run these utilities with the 'abbreviated' audit mode. * Specifically, what utilities are provided to help manage files that may have been affected by these problems? o An AUDIT RECLAIM command checks the ADSM database for files that may be affected and stores information about those objects in a RECLAIM_ANALYSIS table. o After the audit, the RECLAIM_ANALYSIS table can be queried using the SQL SELECT command. It may be possible to restore valid copies of these files from a copy storage pool. Alternatively, the files can be restored/retrieved to the client for examination or they can simply be deleted. o A DELETE RECLAIM command can be used to delete logical files in the RECLAIM_ANALYSIS table from the ADSM database. For backup files that still exist on the client machine, the next incremental backup should then store a new copy of the deleted file on the ADSM server. o A REMOVE RECLAIM command allows you to delete the entry for an individual logical file from the RECLAIM_ANALYSIS table. Optionally, the file itself can be deleted from the ADSM server database. o A CLEANUP RECLAIM command deletes all entries from the RECLAIM_ANALYSIS table and sets values in the ADSM database to show that the utilities have been completed. * What is the "abbreviated" audit mode mentioned above? The utilities were updated in July 1998 to check for files affected by the most recent reclamation problem. The revised utilities include an audit with two modes of operation. The first mode is the 'complete' mode or normal mode. This mode is intended for customers whose servers may have been exposed to the original data movement/reclamation problem. This includes all Version 3 servers that have run at any level prior to 3.1.0.2 (MVS) or 3.1.1.1 (non-MVS). For these servers, the 'complete' audit should be performed, unless an earlier version of the utilities has already been run. The updated utilities in 'complete' mode will examine client files for the original data movement/reclamation error as well as checking for the most recent reclamation problem. The second mode is the 'abbreviated' mode and should be used by customers whose servers are not affected by the original data movement/reclamation problem or who have already run the utilities to manage files affected by this problem. This mode only checks for the most recent data movement/reclamation problem and typically runs faster than the complete audit. * Can the utilities be executed while other ADSM processes are running? The AUDIT RECLAIM command can yield inaccurate or incomplete results if it runs at the same time as certain other processes. To avoid this situation you must make sure that the following operations are not running while the AUDIT RECLAIM command is running: Inventory expiration Storage pool migration Reclamation of sequential volumes MOVE DATA command BACKUP STGPOOL command RESTORE STGPOOL command RESTORE VOLUME command DELETE FILESPACE command DELETE VOLUME with DISCARDDATA=YES AUDIT VOLUME * Does the AUDIT RECLAIM command require that tapes be mounted? The reclamation audit examines information in the ADSM database to detect files that have data errors caused by the data movement/reclamation problems. The audit does not access files in your storage pools and therefore does not require the mounting of tapes. * How long will it take to run the reclamation audit? This will depend primarily on how many physical files are stored on your server. If the audit is long-running, it can be cancelled and restarted where it left off. This allows you to interleave audit processing with other server operations. * My server stores mostly backup files. Is there a simple procedure to identify and delete any files with errors so they can be backed up during the next incremental backup? The following basic steps can be used. 1. Issue the following command and wait for the background process to complete AUDIT RECLAIM 2. To display information on any files that the audit detected as having data errors, issue the following case-sensitive SQL query from an administrative client SELECT * FROM RECLAIM_ANALYSIS 3. Issue the following command and wait for the background process to complete DELETE RECLAIM FILETYPE=BACKUP 4. Issue the following command CLEANUP RECLAIM * I regularly back up files to a copy storage pool. If my primary storage pools contain files that have been affected by these problems, is it possible to recover the files from a copy storage pool? The following basic steps can be used. 1. Issue the following command and wait for the background process to complete AUDIT RECLAIM EXAMINECOPIES=YES This command marks affected files as damaged if a good copy is found in a copy pool. 2. To display information on any files that the audit detected as having data errors, issue the following case-sensitive SQL query from an administrative client SELECT * FROM RECLAIM_ANALYSIS 3. Use the RESTORE STGPOOL command to restore files that were marked as damaged in the previous step. For example, to restore files residing in primary storage pool TAPEPOOL, you could issue the following command RESTORE STGPOOL TAPEPOOL 4. Issue the following command and wait for the background process to complete DELETE RECLAIM This command deletes any files that could not be restored in the previous step. 5. Issue the following command CLEANUP RECLAIM * Where can I get more detailed information about the utilities? A detailed document describing the utilities is available in the PTF readme file. For your convenience, this document is provided below. * Where can I get more information about how to use the SQL SELECT command? The detailed utilities document provides additional examples of SQL queries for obtaining information about affected files. This document is provided below. DOCUMENTATION FOR RECLAMATION UTILITIES --------------------------------------- Following information was updated July 1998 >>> In early 1998, ADSM Development discovered and reported a problem with data movement/reclamation processing on Version 3 servers. Subsequently, Development distributed a set of utilities that could be used by ADSM customers to identify and handle client files that may have been affected by this error. Please refer to information APAR II11170 to determine whether the utilities should be run to deal with files affected by this error. In July 1998, the utilities were modified to cover APAR IX79165. This APAR involves a problem which allows aggregate reconstruction to produce files with an incorrect size. The utilities now identify client files that have been affected by this problem. The updated utilities are able to detect ALL files affected by IX79165, regardless of how many reconstructions might have been performed. To date, IX79165 has only been observed on AIX Version 3 servers; however, we recommend that the updated utilities be run on all Version 3 servers as a precautionary measure. The modified utilities include an audit with two modes of operation. The first mode is the 'complete' mode or normal mode. This mode should be used by customers who should run the utilities for the original data movement/reclamation problem (see APAR II11170), but have not yet done so. The updated utilities in this mode will examine all client files for problems referenced in both II11170 and IX79165. The second mode is the 'abbreviated' mode and should be used by customers whose servers are not affected by the problem described in II11170 or who have already run the utilities to manage files affected by this problem . The abbreviated audit will typically run faster than the complete audit . Please see the section titled 'AUDIT RECLAIM COMMAND' for the syntax and an explanation of the two audit modes. All other commands described in this document are the same regardless of which audit mode is used. Important note to customers who have begun using the utilities without the July 1998 update, but have not yet finished running the entire set of utilities: If you have not already applied this PTF, please finish running the entire set of utilities (including the CLEANUP RECLAIM command) to completion before applying the PTF; you can then apply this PTF and run the updated utilities using the MODE=ABBREV option. Alternatively, if you have already applied this PTF, you should run the updated audit with the MODE=COMPLETE and FORCEREANALYSIS=YES options. The remainder of this document describes the utilities that are provided to assist an administrator in managing client files affected by both II11170 and IX79165. <<< End of July 1998 update PROBLEM DESCRIPTION ------------------- ADSM Version 3 introduced a new storage mechanism to improve performance and reduce overhead. During client backup and archive operations, small files are automatically packaged into larger objects, called "aggregates," for management on the ADSM server. As expiration deletes files from the server, vacant space can develop within aggregates. For data stored on sequential media, this vacant space is removed during reclamation processing. The procedure for removing vacant space within aggregates during reclamation is called "reconstruction," because it entails rebuilding an aggregate without the empty space. ADSM Development recently discovered an error in the Version 3 server that can result in invalid data after an operation in which data is moved/copied from a sequential-access storage pool volume. Initially, it was believed that this error occurred only during reconstruction of file aggregates. Accordingly, updated servers were made available to prevent the problem by temporarily disabling reconstruction of aggregated files during reclamation processing. Subsequently, ADSM Development determined that the problem can actually be introduced during other operations in which files are moved or copied from sequential-access volumes on a Version 3 server. These operations include o Reclamation o Move data from a sequential-access volume o Migration from a sequential-access storage pool o Backup of a sequential-access storage pool o Restore volume or restore storage pool from a copy storage pool The error can potentially affect backup, archive, or space-managed files on Version 3 servers, including files that were initially stored on a Version 1 or Version 2 server and later move/copied from a sequential-access volume on a Version 3 server. Many customers initially store files in a disk storage pool and back up the files to a copy storage pool before allowing the files to migrate to a sequential-access pool. In this scenario, both copies of the file are valid at the time of the storage pool backup. If either the primary or copy pool file later becomes affected by one of the operations listed above, it is likely that the other copy still contains valid data. Please see APARs IX74458 and IX76734 for information about the data movement/reclamation problems and APAR II11170 for information about the specific Version 3 server levels that are affected. WARNING: Using export and import to transfer file data from one server to another may result in transfer of files that have invalid data due to data movement/reclamation on the source server. These problem files would not be detectable on the target server. We recommend that export and import not be used to transfer file data among Version 3 servers until you have finished using the utilities to manage the data move/reclamation problem. OVERVIEW OF THE UTILITIES ------------------------- The utilities obtain the information they need from the ADSM database. They do not access files in the ADSM storage hierarchy, and therefore do not require mounting of storage pool volumes. The following utilities are provided o An AUDIT RECLAIM command checks the ADSM database for logical files that may be affected by this problem and stores information about those objects in a RECLAIM_ANALYSIS table. o After the audit, the RECLAIM_ANALYSIS table can be queried using the SELECT command. It may be possible to restore valid copies of these files from a copy storage pool. Alternatively, the files can be restored/retrieved to the client for examination or they can simply be deleted. o A DELETE RECLAIM command can be used to delete logical files in the RECLAIM_ANALYSIS table from the ADSM database. For backup files that still exist on the client machine, the next incremental backup should then store a new copy of the deleted file on the ADSM server. o A REMOVE RECLAIM command allows you to delete the entry for an individual logical file from the RECLAIM_ANALYSIS table. Optionally, the file itself can be deleted from the ADSM server database. o A CLEANUP RECLAIM command deletes all entries from the RECLAIM_ANALYSIS table and reactivates reconstruction processing (if reconstruction has previously been disabled). The utilities are the only dependable way to identify files that are affected by this problem. In general, the AUDIT VOLUME command does not detect affected files and may actually undermine the utilities by marking files as undamaged that have previously been marked damaged by the utilities. Once you begin using the utilities by issuing the AUDIT RECLAIM command, you should not use the AUDIT VOLUME command until you have completed analysis of this problem and have run the CLEANUP RECLAIM command. WARNING: Do not run the CLEANUP RECLAIM command until you have handled all files that are suspected to contain errors. Once you issue the CLEANUP RECLAIM command, you will not be able to use the other utilities. HOW THE AUDIT WORKS ------------------- The audit utility works by examining information about physical files (aggregates and non-aggregates) in the ADSM database. By analyzing this file information, the audit identifies physical files that have been affected by the data movement/reclamation problem and determines which logical files have invalid data. When it detects such a logical file, the audit stores information about the file in the RECLAIM_ANALYSIS table for use by the other utilities. In most cases, the audit can determine with certainty whether a particular logical file is affected. However, there are situations, described in the following paragraphs, in which detection of problem files may be inaccurate or impossible. The audit detects all aggregates that have data errors because of the LAST reconstruction procedure for that aggregate. However, if an aggregate has been reconstructed more than one time, the analysis cannot determine whether the aggregate was affected during a previous reconstruction. As described in the next section, the audit provides an option for identifying files that may be affected by multiple reconstructions. If problem files are transferred from one Version 3 server to another using export/import, any problem files that existed on the source server would not be detectable on the target server. If an HSM client has migrated a file to the server and that same file is later backed up or archived, the backup/archive copy is created by duplicating the space-managed file that is already stored on the server . Even if the space-managed file is valid, it is possible that the new backup/archive could be invalid if a data movement problem occurs during duplication operation. In this situation, the invalid backup/archive file would not be detected by the audit. This situation should not occur commonly, since the default value for the MIGREQUIRESBKUP management class attribute is YES, meaning that the backup copy must exist before a file can be migrated from an HSM client to the server. Dealing with Possible Multiple Reconstructions ---------------------------------------------- In almost all cases, the audit can definitively detect logical files that are affected by the data movement/reclamation problem. However, the server does not have enough information to determine which aggregates have been reconstructed more than one time (during separate reclamations) and which of these aggregates might have incurred a problem during a reconstruction other than the most recent. Because of this uncertainty, the AUDIT RECLAIM command provides a LASTONLY option that allows the administrator to specify how the audit should handle the possibility of multiple reconstructions of the same aggregate. The default option, LASTONLY=YES, for the AUDIT RECLAIM command causes the audit to ignore the possibility of errors from reconstruction operations other than the most recent. With this option, the audit identifies logical files that were affected by data movement/reclamation operations other than reconstruction and creates an entry in the RECLAIM_ANALYSIS table for each of these logical files; each of these entries is assigned a category of DEFINITE, meaning that the file is definitely affected by the problem. With this option, the audit also identifies logical files that were affected by the last reconstruction and categorizes these logical files as DEFINITE in the RECLAIM_ANALYSIS table. However this option does not report any aggregates that contain invalid data because of reconstruction operations prior to the most recent reconstruction. You can also specify LASTONLY=NO when you run the AUDIT RECLAIM command. If you do this, the audit identifies the same logical files that would be identified with the LASTONLY=YES option, and categorizes these logical files as DEFINITE in the RECLAIM_ANALYSIS table. In addition, the LASTONLY=NO option identifies any logical files that might have been affected by earlier reconstructions and stores information about these files in the RECLAIM_ANALYSIS table with a category of POSSIBLE. Because the server does not have enough information to absolutely determine which logical files were affected by earlier reconstructions, it makes a set of worst-case assumptions. The result is that AUDIT RECLAIM LASTONLY=NO will identify all logical files that could possibly have been affected by multiple reconstructions. However, most of the logical files so identified will not have errors. If you use this option, the number of logical files categorized as POSSIBLE will be MUCH larger than the number of logical files categorized as DEFINITE. Handling Problem Files ---------------------- The AUDIT RECLAIM command also provides an EXAMINECOPIES option that allows you to specify what should be done when definite or possible problem files are identified. With the default option, EXAMINECOPIES=NO, suspect logical files are merely entered in the RECLAIM_ANALYSIS table and given a state of IDENTIFIED. This option should be used if you have NOT been using the BACKUP STGPOOL command to back up your storage pool data. You can also specify an option, EXAMINECOPIES=YES, that causes the audit to look for additional copies of any primary physical file with a definite or possible error; by doing so, the audit may locate a copy that is not affected by the problem. In searching for copies of aggregates, the server uses the criteria dictated by the LASTONLY parameter discussed above. The EXAMINECOPIES=YES option should be used if you intend to restore affected primary files for which a good copy exists. When the EXAMINECOPIES=YES option is used, additional processing described below is performed when a definite or possible problem file is found. This processing causes the audit to run longer, but may allow files to be regenerated from good copies in other storage pools using the normal storage pool backup and storage pool restore operations. If EXAMINECOPIES=YES is used and a physical file with definite or possible problems is detected, the server's response will depend on whether the affected file is a copy, cached, or primary file. If a physical file in a copy storage pool is found to contain invalid data, the copy is deleted. Similarly, if a cached copy has errors, the cached copy is deleted. Deletion of a copy pool file or cached file does not affect the corresponding primary physical file. If a primary physical file is found to have a possible or definite error, the server checks for an unaffected copy of the physical file in a copy storage pool. If a good copy is found, the entire primary physical file is marked as "damaged" and can later be restored using the RESTORE STGPOOL command. For such physical files, an entry in the RECLAIM_ANALYSIS table is also created for each possible or definite problem logical file. The entry records the state of the logical file as MARKED_DAMAGED, indicating that the corresponding physical file has been marked as damaged. If a primary physical file contains invalid data and the server is unable to locate a copy that is unaffected by the problem, an entry in the RECLAIM_ANALYSIS table is created for each possible and definite problem file in the physical file. In this case, the entry records the state of these logical files as IDENTIFIED. AUDIT RECLAIM COMMAND --------------------- This command analyzes the database and identifies logical files that are suspected to contain invalid data as a result of the Version 3 data movement/ reclamation problem. For each such logical file, information is stored in the RECLAIM_ANALYSIS table for later processing. This command runs as a background process that can be cancelled with the CANCEL PROCESS command. You can display information about this process using the QUERY PROCESS command. IMPORTANT: The AUDIT RECLAIM command can yield inaccurate or incomplete results if it executes at the same time as certain other processes. To avoid this situation you must make sure that the following operations are not performed while the AUDIT RECLAIM command is running. Inventory expiration Storage pool migration Reclamation of sequential volumes MOVE DATA command BACKUP STGPOOL command RESTORE STGPOOL command RESTORE VOLUME command DELETE FILESPACE command DELETE VOLUME with DISCARDDATA=YES AUDIT VOLUME If you cancel the audit process, it can be restarted and will resume where it left off during the previous audit. This allows you to interleave audit processing with other server operations. However, if you run AUDIT RECLAIM with the EXAMINECOPIES=YES option, you should not use the AUDIT VOLUME command until you have run the CLEANUP RECLAIM command. If you do so, the AUDIT VOLUME command may mark files as undamaged that have already been marked damaged by the AUDIT RECLAIM command. For more information regarding this command, read the previous section entitled "HOW THE AUDIT WORKS." Privilege Class: Requires system privilege. Syntax: AUDit RECLAIM |--FORCEreanalysis=No---| |--LASTonly=Yes--| AUDit RECLAIM >---------------------------------------------> |--FORCEreanalysis=Yes--| |--LASTonly=Yes--| |--FORCEreanalysis=No--| |--LASTonly=No--| |--EXAMinecopies=No---| |--MODE=COMPlete--| >------------------------------------------------< |--EXAMinecopies=Yes--| |--MODE=ABBRev--| |--EXAMinecopies=No---| |--MODE=COMPlete--| Parameters FORCEreanalysis=forcevalue Indicates whether information from a previous reclaim audit should be discarded and the audit repeated. This parameter is optional. The default value is NO. Yes Specifies that previous reclaim audit results will be deleted from the database and a new audit will be started. Database information on logical files with possible or definite errors will be discarded and regenerated by auditing all physical files again. No Specifies that if a reclaim audit has previously been performed, the existing audit results will be preserved. This allows a previous audit, which was cancelled or which failed before completion, to be resumed without the need to audit physical files that have already been audited. To avoid inconsistent data in the RECLAIM_ANALYSIS table, if you resume a previous reclaim audit, you should use the same choices for the LASTONLY and EXAMINECOPIES parameters as were used during the previous audit. LASTonly=lastvalue Specifies whether the audit should consider reconstruction operations prior to the most recent reconstruction for each aggregate. This parameter is optional. The default value is YES. Yes Specifies that the audit will only consider the most recent reconstruction of each aggregate. With this option, logical files that were affected by data movement/reclamation operations other than reconstruction will be entered in the RECLAIM_ANALYSIS table with a category of DEFINITE. Logical files that have invalid data from the last reconstruction procedure will also be entered in the RECLAIM_ANALYSIS table with a category of DEFINITE. This option will not detect logical files that have invalid data from earlier reconstructions. No Specifies that the audit should consider the possibility that aggregates may have been reconstructed more than one time. With this option, the audit will identify files that definitely have invalid data from the last reconstruction procedure or which were affected by other data movement/reclamation operations; these logical files will be entered in the RECLAIM_ANALYSIS table with a category of DEFINITE. A worst-case set of assumptions will also be used to identify files that could have invalid data from earlier reconstructions; these files will be entered in the RECLAIM_ANALYSIS table with a category of POSSIBLE. With this option, the audit will identify all logical files that could possibly be affected by the reconstruction problem, but most of the logical files categorized as POSSIBLE will not actually have invalid data. EXAMinecopies=examinevalue Specifies whether the audit should examine other copies of physical files that have invalid data. This parameter is optional. The default value is NO. Yes Specifies that the audit will examine other copies of any physical files that it identifies as having possible or definite errors. A detailed description of this option is provided in the section entitled "Handling Problem Files." This option marks affected primary physical files as damaged if a restorable copy can be found. You should not use this option unless you intend to restore the damaged files using the RESTORE STGPOOL command. No Specifies that the audit will not examine other copies of any physical files that it identifies as having possible or definite errors. The logical files in the affected physical file will be entered in the RECLAIM_ANALYSIS table with a state of IDENTIFIED. Following information was added July 1998 >>> MODE=mode Specifies the mode in which the audit will be run. This parameter is optional. The default value is COMPLETE. COMPlete Specifies that the audit will be run in complete mode. This mode should be used on servers that may be affected by the original data movement/reclamation problem (see APAR II11170) unless the utilities have already been run to completion. When run in complete mode, the audit will examine all client files for problems referenced in both II11170 and IX79165. ABBRev Specifies that the audit will be run in abbreviated mode. This mode should be specified if server is not affected by the original data movement/reclamation problem (see APAR II11170) or if the utilities have already been run to deal with this problem. When the audit is run in abbreviated mode, it checks only for the error IX79165. In abbreviated mode, the audit only examines aggregates and will typically run faster than in complete mode. NOTE: Options MODE=ABBREV and LASTONLY=NO cannot both be specified, since the abbreviated audit checks for an error that can be detected even if multiple reconstructions have been performed. <<< End of July 1998 addition NOTE: Options LASTONLY=NO and EXAMINECOPIES=YES cannot both be specified, since this combination would result in deleting copy pool files and marking primary files as damaged, even though these files only have possible errors. VIEWING AUDIT RESULTS --------------------- The SQL SELECT query can be used to display the contents of the RECLAIM_ANALYSIS table. The SQL language provides a high degree of flexibility in sorting, consolidating and analyzing the contents of the table. For detailed analysis, you may want to refer to a book or manual on the SQL SELECT language. Some very brief examples will be used below to illustrate the functions that can be performed. The information in the RECLAIM_ANALYSIS table is also accessible through the ADSM ODBC driver for analysis with product such as Lotus Approach or Microsoft Access. Each row in the RECLAIM_ANALYSIS table represents a client file that has been identified by the AUDIT RECLAIM process. The following columns, or fields, are defined for each file. Information about these columns can also be displayed using the following SQL query: SELECT * FROM COLUMNS WHERE TABNAME='RECLAIM_ANALYSIS' Columns in the RECLAIM_ANALYSIS table ------------------------------------- CATEGORY Identifies the degree to which the audit has determined that the file is affected by the data movement/reclamation problem. This column can have one of two possible values. A value of 'DEFINITE' is associated with files that are certain to contain invalid data. A value of 'POSSIBLE' is associated with files that are not known to have invalid data, but which may have been affected by reconstruction operations other than the most recent. NODE_NAME Identifies the name for the client node from which the file was backed up, archived, migrated. FILESPACE_NAME Identifies the name of the filespace on the client to which the file belongs. ENTRYTYPE Identifies the type of file on the server. This column can have one of three possible values: 'Archive' - indicates that the object was archived from the client 'Backup(Active)' - indicates that this copy is the latest backup copy that was sent from the client (the ACTIVE backup copy) 'Backup(Inactive)' - indicates that this is an inactive backup copy of the object 'Space Managed' - indicates that the file was migrated from an HSM client HL_NAME Identifies the high-level name for the client object LL_NAME Identifies the low-level name for the client object OBJTYPE Identifies the type of object. Two possible values can be displayed for this column: 'FILE' - the object is a client file 'DIR' - the object is a client directory ID Specifies the identifier for the client file. This identifier can be used to remove individual files with the REMOVE RECLAIM command. AUDIT_STATE Identifies the audit state for the object. This column can have one of two possible values: 'Marked Damaged' - indicates that the object was marked damaged during the audit process because an unaffected copy can be restored using the RESTORE STGPOOL command. 'Identified' - indicates that the object was identified but not marked damaged during the audit Example Queries --------------- This section will illustrate how the SQL SELECT statement can be used to obtain information about client files identified by the AUDIT RECLAIM process. The SQL SELECT command can be issued from any administrative command line client. It cannot be issued from the server console. The general format for a simple SELECT query is the following: SELECT columnlist FROM RECLAIM_ANALYSIS The columnlist is a comma-separated list of the columns that should be displayed from the descriptions above. An asterisk (*) can be used to indicate that all columns should be displayed in the order defined above. Other 'aggregate' functions can also be specified. Please refer to your SQL documentation for more details. A predicate may involve a comparison or evaluation based on column contents to determine which rows are to be displayed from the table. The examples below should clarify the basics. The simplest command displays all columns and all rows in the RECLAIM_ANALYSIS table: SELECT * FROM RECLAIM_ANALYSIS To display all rows that contain information on files that are definitely affected by the data movement/reclamation problem, the following query could be used: SELECT * FROM RECLAIM_ANALYSIS WHERE CATEGORY='DEFINITE' To display the filespace name, high-level name, and low-level name for each ARCHIVE file belonging to node SMITH that was definitely affected by the data movement/reclamation problem, the following query could be used: SELECT FILESPACE_NAME,HL_NAME,LL_NAME FROM RECLAIM_ANALYSIS WHERE CATEGORY='DEFINITE' AND NODE_NAME='SMITH' To display all archive or active backup files that were identified by the audit, the following query could be used: SELECT NODE_NAME,FILESPACE_NAME,HL_NAME,LL_NAME FROM RECLAIM_ANALYSIS WHERE ENTRYTYPE='Archive' or ENTRYTYPE='Backup(Active)' To display a count of the files that are definitely affected by the problem, the following query could be used: SELECT COUNT(*) FROM RECLAIM_ANALYSIS WHERE CATEGORY='DEFINITE' To display a count of the files that were POSSIBLY affected by a reconstruction, the following query could be used: SELECT COUNT(*) FROM RECLAIM_ANALYSIS WHERE CATEGORY='POSSIBLE' DELETE RECLAIM COMMAND ---------------------- This command is used to delete logical files stored on the server that may have errors due to the data movement/reclamation problem. These files must have been previously identified using the AUDIT RECLAIM command. Logical files are deleted only if they have an entry in the RECLAIM_ANALYSIS table and satisfy the filter criteria specified for the DELETE RECLAIM command. Once the files have been deleted, clients will no longer be able to access these files using ADSM. Deletion of active backup files for a client will cause the files to be backed up again during the next incremental backup operation for that client, provided that the files still reside in the client's file system. As logical files are deleted from the server, the corresponding entries in the RECLAIM_ANALYSIS table are also deleted. If the DELETE RECLAIM command processes a file whose state is MARKED_DAMAGED and the corresponding primary physical file is no longer marked damaged, the deletion process removes the entry from the RECLAIM_ANALYSIS table, but does not delete the logical file. In such a situation, the delete process assumes that the physical file has been restored from a copy storage pool and now contains valid data. To determine which files will be deleted if this command is issued, you should use the equivalent SELECT command to view information about the files you plan to delete. The command generates a background process that can be queried with the QUERY PROCESS command. The command can be cancelled with the CANCEL PROCESS command. Privilege Class: Requires system privilege. Syntax: DELete RECLAIM ---nodename-----------------------------------> |--FILESpace=filespacename--| |--FILEType=ALl-----------| |--CATegory=DEFINITE--| >-----------------------------------------------------------> |--FILEType=ALl-----------| |--CATegory=ALl-------| |--FILEType=ARchive-------| |--CATegory=DEFINITE--| |--FILEType=Backup--------| |--CATegory=POSSible--| |--FILEType=BACKUPActive--| |--FILEType=ALLActive-----| |--FILEType=INactive------| |--FILEType=SPacemanaged--| |--STate=IDENTified-----| >----------------------------+ |--STate=ALl------------| |--STate=IDENTified-----| |--STate=MARKEDdamaged--| nodename Specifies a list of client node names for which files are to be deleted. The items in the list are separated by commas, with no intervening spaces. Pattern-matching expressions can be used to specify the names. This parameter is required. FILESpace=filespacename Specifies a list of filespaces for which files are to be deleted. The items in the list are separated by commas, with no intervening spaces. Pattern-matching expressions can be used to specify the names. This parameter is optional. If not specified, files for all filespaces are deleted. FILEType=type Specifies the type of logical files that should be deleted. This parameter is optional. The default value is ALL. ALl Specifies that archive and backup files with entries in the RECLAIM_ANALYSIS table should be deleted. Space-managed files are not deleted. ARchive Specifies that only archived files should be deleted. Backup Specifies that only backup versions, whether active or inactive, should be deleted. BACKUPActive Specifies that only active backup versions should be deleted. ALLActive Specifies that all archive copies and active backup versions should be deleted. Space-managed files are not deleted. INactive Specifies that only inactive backup versions should be deleted. SPacemanaged Specified that only space-managed files should be deleted. CATegory=category Specifies the category of logical files that should be deleted. This parameter is optional. The default value is DEFINITE. ALl Specifies that files with all categories should be deleted. DEFINITE Specifies that only files with a category of DEFINITE should be deleted. These are files that are known to contain invalid data. POSSible Specifies that only files with a category of POSSIBLE should be deleted. These are files that do not contain known errors but which could contain invalid data due to a reconstruction operation other than the last reconstruction, should the aggregate have been reconstructed more than once. STate=state Specifies the state of logical files that should be deleted. This parameter is optional. The default value is IDENTIFIED. ALl Specifies that files with all states should be deleted. However, files with state of MARKED_DAMAGED are not deleted unless the primary physical file is still marked damaged. IDENTified Specifies that only files with a state of IDENTIFIED should be deleted. These are files that were identified, but not marked damaged, during the reclaim audit. MARKEDdamaged Specifies that only files with a state of MARKED_DAMAGED should be deleted. These are files that were marked damaged during the reclaim audit because they can be restored using the RESTORE STGPOOL command. These files are not deleted unless the primary physical file is still marked damaged. If you are not using the BACKUP STGPOOL command to make backup copies of your files, or if you used EXAMINECOPIES=NO on the AUDIT RECLAIM command, you will not have any files in the RECLAIM_ANALYSIS table in this state. REMOVE RECLAIM command ---------------------- This command is used to remove the entry for a single client file from the RECLAIM_ANALYSIS table. The table entry must have been created during a previous AUDIT RECLAIM operation. Optionally, this command also deletes all other references to the logical file from the server. Privilege Class: Requires system privilege. Syntax: |--DELObject=No---| REMove RECLAIM --identifier----------------------+ |--DELObject=No---| |--DELObject=Yes--| Parameters: identifier Specifies an identifier for the file to be removed from the database. This identifier can be obtained by using the SELECT command to view the contents of the RECLAIM_ANALYSIS table. The identifier consists of two numeric parts, separated by a period. This identifier is obtained from the ID column in the RECLAIM_ANALYSIS table. DELOject=value Specifies whether the object should be removed from the server. This parameter is optional. The default value is NO. No Specifies that the entry for the specified object will be removed from the RECLAIM_ANALYSIS table, but the object itself will not be deleted from the server. Yes Specifies that the specified object will be deleted from the server, and its entry will be removed from the RECLAIM_ANALYSIS table. CLEANUP RECLAIM COMMAND ----------------------- This command is used to remove the RECLAIM_ANALYSIS table that was created by the AUDIT RECLAIM command. This command should only be issued if you are satisfied with the recovery actions that you have taken, and do not plan to execute any other reclaim analysis utilities. Once you issue the CLEANUP RECLAIM command, you will not be able to run the other reclaim analysis utilities. The command generates a background process that can be queried with the QUERY PROCESS command. The command can be cancelled with the CANCEL PROCESS command. Privilege Class: Requires system privilege. Syntax: CLEANup RECLAIM------< POSSIBLE PROCEDURE FOR USE OF UTILITIES --------------------------------------- Various approaches can be used to manage files that may be affected by the data movement/reclamation problem. The utilities described above can be used to identify files with invalid data so that as many files as possible can be handled using normal storage pool backup and restore operations. Following is a possible procedure for resolving the data movement/reclamation problem: 1) Install this corrective level of the ADSM Server on your server platform. 2) Decide whether you want the audit to ignore the possibility of errors from reconstruction operations other than the most recent reconstruction for each aggregate. In making this decision, consider factors such as how often files are deleted through expiration, whether it is likely that the same data could have been reclaimed multiple times, and how critical it is to identify every logical file that could possibly be affected by reconstruction errors. Also keep in mind that a server fix was provided to disable reconstruction in late January; if your Version 3 server usage prior to applying this fix was minimal, your exposure to possible reconstruction errors should be low. These considerations should help you to select the value of the LASTONLY option for the AUDIT RECLAIM operation. In most cases, the default option of LASTONLY=YES should be used to avoid identifying an unmanageable number of files with possible reconstruction errors. 3) Decide whether you want the audit to merely identify logical files affected by the problem or whether it should examine other copies that might not be affected. Consider whether your primary storage pools are backed up to one or more copy storage pools, whether the backup is usually performed from a disk or a sequential-access pool, and the feasibility of obtaining copy pool tapes from an offsite location. These considerations should help you to select the value for the EXAMINECOPIES option for the AUDIT RECLAIM operation. 4) Use the AUDIT RECLAIM command to audit physical files stored on your server. If errors occur or if the audit has to be cancelled, the audit can be continued from the point at which it left off. 5) Use the SQL SELECT query on the RECLAIM_ANALYSIS table to determine which files may have been affected by the problem. 6) If you have used the EXAMINECOPIES option, restore your primary storage pools to replace physical files that have been marked as damaged. Then use normal storage pool backup to create new copies of any physical files that were deleted from your copy storage pools. 7) Issue the following command to delete backup files with entries in the RECLAIM_ANALYSIS table. This command deletes all backup files that were not successfully restored with the RESTORE STGPOOL operation. For files that are deleted, incremental backup will again store those files that still reside on the client. DELETE RECLAIM STATE=ALL FILETYPE=BACKUP 8) For remaining files in the RECLAIM_ANALYSIS table, attempt to locate the files on the client or retrieve the files and examine the file for possible errors. If the original file still resides on the client, store it again to the server. Otherwise, we recommend that you do not delete it from the server because the whole file may not have been affected, or the file may not be affected at all (e.g., if the file is in the POSSIBLE category). 9) When you are satisfied with the action you have taken to recover from this error, use the CLEANUP RECLAIM command to remove all entries from the RECLAIM_ANALYSIS table. This command also reactivates aggregate reconstruction, if it has been disabled. When in doubt, please contact your service representative for assistance with these procedures. ********************************************************************** * Clarification of fix to APAR IX79626 * ********************************************************************** Service aids "delete archd " and "delete object force=yes" and online and offline audit tools were provided in service level 3.2.1.0. The root cause of the problem, serialization, is fixed by this PTF. It has been recently discovered that the audit tools are not working properly. The fix was not available in time to meet the delivery date for this PTF so both the online and offline audit tools have been disabled. ******************************************************************************** * Version 3 Release 1 APARS fixed by prior service levels * ******************************************************************************** IX79245 DSMSERV AUDITDB PARAMETERS ARE NOT WORKING AS DOCUMENTED FILE=xx parameter on DSMSERV AUDITDB not directing output to V2 file. IX79248 SESSION NUMBER GREATER 99999 WILL NOT BE DISPLAYED PROPERLY IX75336 SELECT OCCUPANCY ... OUTPUT DOES NOT MATCH QUERY OCCUPANCY OUTPUT The SQL SELECT FROM OCCUPANCY does not display filespace information correctly for nodes with multiple filespaces. IX74446 Server incorrectly reporting missed schedules ANR2478I MESSAGE IS GENERATED WHEN THE SCHEDULE DOESN'T FINISH WITHIN START WINDOW. THIS MESSAGE SHOULD ONLY BE ISSUED IF SCHEDULE HAS NOT STARTED WITHIN START WINDOW. IX75715 Tivoli event receiver needs hostname slot ADSM did not pass the HOSTNAME slot to Tivoli. IX75962 Excessive ANR8216W messages with Tivoli event logging The Tivoli event receiver did not properly detect when the Tivoli event server went down. IX76138 QUERY SESSION hangs the server when it has much output When issuing a QUERY SESSION command from an admin client, and the number of sessios is so large that the entire output from the command cannot fit in a single buffer (over 150 sessions), the server can hang due to deadlock contention of the Session Mutex. IX76147 WEB ADMIN DOES NOT SEE DEFINED DRIVES, AND IN CUSTOMER'S CASE, HIS 3494 LIB. SQL queries and Web Admin pages return Not Found instead of no space available when there is insufficient database space for SQL temporary tables. This will occur when a Q DB shows 0 in the Maximum Reduction field. IX76494 Archive performance degredation archive query/retrieve performance is degraded from V2 IX76472 SELECT * FROM VOLUMEUSAGE DOES NOT LIST ALL VOLUMES WHICH CONTAIN DATA. entries are missing from 'select * from volumeusage' output IX76739 ANR2751I ISSUED WHEN ANR2756I IS APPROPRIATE IX76854 OPTICAL SUPPORT. DUE TO BAD SECTOR OR HARDWARE RELATED ISSUES ADSM WILL NOT ACCESS REST OF THE FILES AND MARK THEM ALL BAD The problem is that any single I/O error from the drive on a read operation prevents any other access to that side of the platter until the platter is dismounted. This impacts the AUDIT VOL and MOVE DATA commands from being able to access otherwise good files on the platter because one file had a bad sector in it. IX77291 THE DRM -> PREPARE ICONS ON THE WEBADMIN WILL RECOGNISE ONLY THE FIRST STGPOOL GIVEN IN A LIST. The PREPARE panel for the Web administrative interface incorrectly displayed partial storage pool information in the COPYSTGPOOL and PRIMSTGPOOL fields. IX77477 AIX ADSM SRV 3.1. GETS ANR8355E,ANR8311E WHEN TRYS TO MOUNT THE STORAGE TEK (ACSLS 5.1.1) TAPES WITH HEADER TYPE 1. prelabelled tapes do not have the HDR2 which ADSM expects IX77638 ADSM ADMIN COMMANDS THAT DO NOT REQUIRE SPECIAL ADMIN AUTHORIZATION CAN BE ISSUED THROUGH WWW INTERFACT WITHOUT AUTHENTICATION. The '/HELP/' path link in the server URL for the WEB admin interface will allow non-administrators to issu query commands. Commands the require an ADSM administrative authority above GENERAL will fail. IX77714 TRYING TO RUN A SCRIPT THAT RUNS AN ADMIN SCHEDULE. WORKED IN V2 DOES NOT WORK IN V3. Cannot Schedule Device and Library related Administrative cmds. IX77766 QUERY OPTION doesn't show AUDITSTORAGE option NOAUDITSTORAGE OPTION DOES NOT APPEAR IN ADSM SERVER QUERY OPTION OUTPUT EVEN THOUGH PARM IS SPECIFIED IN DSMSERV.OPT IX77783 ANR9999D PSPURROPT.C 1049) OPTICAL DISK NOT VALID FOR THIS PRODUCT RECEIVED WHEN RUNNING LABEL LIBVOL FOR OPTICAL PLATTER when ADSM labels an optical platter, it first tries to read the existing label to ensure that it is not being overwritten. If no existing label is found, the ANR9999 error message is issued, which is extraneous since this condition would be expected. IX77865 RESTORED FILE ACCOUNT IS WRONG IN ACCOUNTLOG. RESTORED WITH NO PROBLEM, BUT DISPLAYED "RESTORED FIL =ZERO". accounting info not updated for restored files IX78021 AFTER STARTING 'UPDATE DEVC' DURING 'QUERY CONTENT' WORKING , SERVER HANGS. IX78125 DSMFMT -G RESULTS IN OUT OF SPACE MESSAGE The GB value was processed incorrectly. IX78196 DB Dump was not dumping all pages When running the dumpdb comand, one or more of the following messages are issued: ANR9999D dldump.c(2361): Logical page xxx corrupted - data string packed structure invelid for record 0 IX78320 Unpredictable crash during Query Backup unpredictable core dump occurs during query backup IX78433 ANR9999D XIBF.C(1161):UNKNOWN RESULT CODE (23) FROM BFCREATE CAN BE A RESULT OF V3 SERVER FILLING UP DISK STGPOOL DURING IMPORT With a version 3 server when a disk storage pool becomes full during an import and didn't get the chance to migrate the data to tape, it will fail with ANR9999D XIBF.C(1161):UNKNOWN RESULT CODE (23) FROM BFCREATE. IX78702 QUERY CONTENT causes other commands to hang After starting 'update devc' during 'query content' working, server hangs, when 'query content' command take a big time to work (large output). After system waits (hangs) the message ANR0481W Session ??? for node ????? terminated - client did not respond within ?? seconds. After admin session with 'query content' command is terminated, then sessions with 'update devc', 'q devc' commands unhangs and worked properly. IX78829 Memory leak when creating mutexes (AIX Only) Every time a mutex is created in the server, an unspecified amount of memory is leaked. Over time this can cause excessive paging activity and/or server crash. IX79016 ADSM SRV 3101, AIX 4.2.1, DRIVE-POLLING THREAD DON'T MARKS THE DRIVE OFFLINE ADSM DB, ONLY IN DRIVE DESCRIPTOR. The problem occurs when a drive in the 3949 library has an error and ADSM begins to poll the drive. If the user marks the drive offline via the UPDATE DRIVE command, then when the polling thread finds out the drive is now accessible, the drive is marked online. However, the drive should still be marked offline according to earily commands issued. IX79165 ANR9999D AFERASE.C(493):INVALID LOGSIZERATIO INF Customer runs through RECLAMATION UTILITIES. Encountered errors on DELETE RECLAIM and later on RECLAMATION or EXPIRATION: ANR9999D aferase.c(493): Invalid logSizeRatio INF (logSize= 0.1240,size=0,0,aggrSize=0.21045) for aggregate 0.21279102 IX79191 REMOVE=BULK WILL NOT RETURN WITH AN INVALID OPTION WHEN USED WITH AN ACSLS LIBRARY. CHECKIN LIBVOL ... REMOVE=BULK ... is not supported by ACSLS libraries and should return an error if attempted. IX79350 SCHEDULER ISN'T PROCESSING 2/29/2000 CORRECTLY. Leap year not handled correctly for Y2K. IX79366 WHILE ADSM IS COMING UP, TAPES IN AN ACSLS LIBRARY SYSTEM WHICH ARE NOT FOUND WILL BE CHECKED OUT RESETTING THE 'LOCK' BIT. While ADSM is coming up, tapes in an ACSLS library system which are not found will be checked out resetting the 'lock' bit. By resetting the lock bit, we may be allowing the tape to be picked up by another application using the ACSLS library. IX79368 MAXSIZE ROUNDED FOR DISPLAY OF Q STGPOOL IX79394 ADSM SERVER CHECKIN LIBVOLUME SEARCH=YES AND LABEL LIBVOLUME SEARCH=YES CAUSE 3995 TO UNLOAD DRIVES FOR STATUS CHECKING the IES command that is issued by Checkin and Label commands with the search option causes any mounted volumes to be ejected from the drives IX79470 A WRITE PROTECTED TAPE IN AN ACSLS LIBRARY SYSTEM WILL BE REMOUNTED REPEATEDLY FOR SCRATCH OPERATIONS. A write protected tape in an ACSLS library system will be remounted repeatedly for scratch operations. Other tapes may be mounted durring this processing, as well, including a usable scratch tape being selected occationally. IX79566 Q ACTLOG WITH SEARCH OPTION DOESN'T DISPLAY ALL OCCURENCES OF THE STRING EXPRESSION ON 3.1.1.3 SERVERS. When doing a QUERY ACTLOG with SEARCH parameter, messages originating from clients or other servers were not always included. IX79579 ANR8449E WHEN TRYING TO MOUNT A SCRATCH VIRTUAL VOLUME. The name generation routine for scratch names was not appropriately checking to see if a volume by that name already existed. IX79727 EXPORT DOES NOT WRITE THE DATASET NAME IN THE HDR1 FIELD IF THE VOLUME HAS BEEN PREVIOUSLY USED BY ADSM The problem arises on the MVS side when importing data that was exported from a UNIX or NT. The error states that the data set name was incorrect. IX79815 AN ANR8311E I/O ERROR MESSAGE WITH RC OF 6 OR 28 IS ERRONEOUSLY GIVEN WHEN THE VOLUME BECOMES FULL AND END OF TAPE IS REACHED ADSM erroneously generates an: ANR8311E AN I/O ERROR OCCURRED WHILE ACCESSING DRIVE FOR WRITE OPERATION; ERRNO = 6 (or ERRNO=28) ANR8341I - END OF VOLUME REACHED FOR VOLUME . when using a library defined with LIBTYPE=EXTERNAL and the volume becomes full (i.e. reaches the end of media/end-of-tape/ EOT). This message sequence is not indicative of a true error. IX79974 IF A MOVE FROM DISK OPERATION IS CANCELED OR PREEMPTED, ADSM COULD ABEND WITH A TMTXN008 An abend can at time occur during the movement of data from a disk storage pool to another pool and a cancel is issued or the operation is preempted. This problem is more likely to happen if I/O errors are experienced and the move operation is retrying the move. IX80345 WHEN USING THE SQL SELECT STATEMENT WITH ORDER BY PARM AND THERE IS MORE THAN ONE COLUMN DISPLAYING DECIMAL,INTERVAL OR DATETIME SQL queries using the order by clause, with more than one column with decimal, date/time or interval data can have incorrect data displayed. IX80431 WEB ADMIN INTERFACE DOES NOT DISPALY OBJECTS FIELD INFORMATION IF MULTIPLE SET OS QUOTES ARE USED. Strings that contain double quotes (") do not preserve the double quotes when entered from the Administrative WEB interface. An example is the objects/options fields in the DEFINE/UPDATE schedule command. IX80461 DRIVER FOR 7206-110 12 GIG TAPE DRIVE Drive fails to configure using adsm driver but will configure using the native AIX driver. IX80531 ADSM DOESN'T RETURN AN ERROR WHEN THE MOVE MEDIA COMMAND AND CHECKLABEL=NO OPTION ARE USED TOGETHER. The users use an undocumented parameter CHECKL with the MOVE MEDIA command. If CHECKLABEL, instead of CHECKL, is used with the MOVE MEDIA command, ADSM reports the error. IX80875 DOCUMENTATION UPDATE REQUEST TO INCLUDE -SERVERNAME OPTION IN LIST OF IGNORED OPTIONS FOR DEFINE SCHEDULE COPMMAND IX80940 ANR9999D PKSHMEM.C(310): INVALID ATTEMPT TO FREE MEMORY: CALLED FROM 10201E54 (CSQUERYEVENT). Specifying "Query Event * type=admin nodes=" leads to attempts to free memory which has not yet been obtained. The use of type=admin and nodes= is not compatible. IX81008 IF A TIVOLI SERVER GOES DOWN AND IS BROUGHT BACK UP ADSM NO LONGER CAN COMMUNICATE WITH IT. TIVOLI went down, and ADSM did not attempt to reconnect and continue sending events to the TIVOLI Event Console. IX81130 TCP/IP IS CLOSED WHEN ERROR NUMBER 72 IS RECEIVED FROM TCP/IP If a session request is aborted in a very small window and ECONNABORTED is returned by AIX, the server will stop listening for TCP/IP sessions. IX77690 THE MESSAGE "ANRNNNNW UNABLE TO CLEAR THE LOG BELOW XX% OF THE TRIGGER VALUE. THE RECOVERY LOG IS NOW YY% FULL" SHOULD DISPLAY The server does not issue a message when running in roll-forward mode and a database backup does not clear the recovery log below the percentage specified by the database backup trigger. IX79262 HIGH CPU UTILIZATION DURING SCHEDULE MANAGER INITIALIZATION. When the ADSM server is starting, the schedule manager may take a long time to initialize if there is a large number of schedled events defined (i.e. lots of clients associated with one or more schedules). During schedule manager initialization, you may see one or more of these symptoms: - High CPU utilization - Clients will not be able to connect - No response to administrative commands Once the schedule manager starts (message "ANR2560I Schedule manager started.") ADSM will operate normally. IX76101 ADSM ADMIN GUI ERROR MESSAGE ANR2606E INVALID START DATE WHEN CODING 29/02/2000 IN THE START TIME BOX FOR SCHEDULED BACKUP Customer was doing year2000 testing and discovered that coding 29/02/2000 in the admin GUI schedule start time box caused ANR2606E invalid start date but 29/02 IS a valid date for year 2000. IX81433 VOLUME LOCATION FIELD ERASE BY SERVER LEVEL 3 . QUERY VOLUME F=D for cartridges reveal that the field LOCATION DIAPPEAR , after the cartridge has been used by server level 3. The volume was defined at server level 2 , and when its been use by server level 3 , the LOCATION field of the volume LOST. IX79264 DELETE MULTIPLE FILESPACES ANR0104E ARCHIVE.DESCRIPTIONS If the user deletes multiple filespace for a node at the same time, that is the deletes are running concurrently on the server, one of more of the delete filespace background threads may terminate with the following messages: . ANR0104E IMARINS(1301): Error .... deleting row from table "Archive.Descriptions". ANR0987I Process ... for DELETE FILESPACE running in the BACKGROUND processed .... items with a completion state of FAILURE at .... ------ IX76241 WAIT HANG SESSION VERSION 3 A client session on a ADSM V3 server may hang doing a long split on a database page during backup processing. Externally, there are no unique symptoms to this problem other than eventually all client sessions most processes will hang. IX79265 ABEND0C4 IN ADSM PROC TMABORT+'8E' RUNNING ADSM V3 SERVER. The adsm MVS V3 server gets an abend0c4 in TMPROC+'8E'. The is processing a transaction abort from a client but there was no session started causing this abend. IX79294 ANR9999D ADMNODE(6648): INVALID NODE TYPE 0 FOR NODE ... This APAR is to document this message and let customers know that this message may be ignored. This message is issued as a result of code added in level 3.1.0.2 and 3.1.1.1 to correct a problem where server nodes were counted against the number of clients licensed. ANR9999D is a diagnostic message which should only be issued when there is a problem which requires further diagnosis or corrective action by ADSM Service. In this case, it is an inappropriate use of the message because the server is actually correcting an existing problem and no further action or diagnosis is required. IX79295 ABEND0C4 ORMADM.C+42CE ENDMOVEDRMEDIATHREAD()+48E REG07 MOVe DRMedia background thread terminates with ABEND0C4 in load module DSMSERV (ANRSERV) source module ORMADM.C at offset +42CE, stmt 2926, in function EndMoveDrmediaThread() at offset +48E. EndMoveDrmediaThread() calls FreeStorage() to free the storage used by the move drmedia thread. The last thing that FreeStorage() frees is the ormDesc structure. Upon return from FreeStorage(), EndMoveDrmediaThread() attempts to call pkExitThread() using a pointer in the freed ormDesc structure as an argument. IX78196 DUMPDB INCORRECTLY REPORTING ANR9999D DLDUMP(2361) After upgrading from V2 to V3, customer is finds that DUMPDP is incorrectly reporitng ANR9999D DLDUMP(2361): logical page corruption --- BACKUP DB does not report and errors and show tblscn report no errors. IX79381 UNABLE TO CONNECT MORE THAN 200 CLIENT SESSIONS FOR BACKUP. HARD CODED LIMIT IN TCPCOMM.C FOR HPNS_MAX_SESSIONS IX79387 SQL ERROR IN THE WEB SHELL ADSM ADMINISTARTION DURING REQUESTING THE POOL VOLUMES INFO IF POOL NAME LONGER THAN 18 CHARACTERS. Error using the Web Admin displaying an object with a long name, when a dependent object is selected for display. An example: When displaying a storage pool with a long name select the volumes icon to display the volumes in that storage pool. IX79388 PARSING ERROR FROM TIVOLI WHEN IBMADSM_SERVER_EVENT CONTAINS DOUBLE QUOTATION MARKS When reporting ADSM SERVER events to Tivoli, a parsing error occurs if the message to log contains double quotation marks. IX79389 HANG OR WAIT OF ADSM SERVER WHEN USING WEBADMIN CLIENT The ADSM server can hang when using the WEBADMIN client if there are TCP/IP problems causing the send of data to hang in TCP/IP. The problem is in the HTTP communications path that the SMVARS mutex is being held while sending data. A SHOW THREADS will show most threads waiting on the same MUTEX. A Q SESSION will show an HTTP session in a SENDW state for a long time. IX80115 Q AUDITOCCUPANCY FROM MVS ADSM 3.1.1.3 DISPLAYS INCORRECT DATA. Query Auditoccupancy shows storage values for nodes which have no filespaces. IX79919 NETWARE & WIN32 3.1.0.3 CLIENTS RESTORE FILES WHEN -DIRSONLY OPTION IS SPECIFIED IF THE DATA IS STORED ON SEQUENTIAL MEDIA. When the DIRSONLY option is used with a restore from a client, files are sometimes sent from the server to the client. The will happen if: - The No-Query Restore protocol is used - Directories to be restore have extended atributes that reside on sequential media in ADSM. IX80959 WEB ADMIN CLIENT RECONNECTS TO SERVER WITHOUT AUTHENTICATION When an administrator sign-on times out, the user can gain access to the server by pressing the cancel button on the authentication pop-up screen. IX79282 AUDIT LIBRARY aborts the server If the SCSI driver is not started on the NT server and I run an AUDIT LIBRARY, the server will take a dump IX79537 Incorrect text response SD-3CC and FORMAT=DRIVE fix for ECART ********************************************************************** * APARS fixed by this service level (3.1.2.1) * ********************************************************************** | IX79626 WHEN ARCHIVE OBJECTS ARE BEING EXPIRED IF CORRESPONDING DESCRIPTION | ENTRY IS MISSING, EXPIRATION FAILS FOR THAT OBJECT. | | The archive descriptions tables were created to enhance | performance for the V3 GUI, archive/retrieve functions. | "Conversion" to the tables occurs on a per node basis: | - when a node attempts to archive a file using the V3 GUI | interface, the node is prompted if it will wait for the | conversion. If OK, entries are created in the archive | description tables. | | Errors have been reported when subsequent insertions, updates, | or deletions are made in these tables. Insertion errors are | reported by customers that use tools (e.g. shell scripts) to | generate multiple, concurrent archive sessions for the same | node name. Deletion errors also occur for nodes with large | numbers of archived data. | The errors were due to a serialization problem with the archive | description tables. The locking scheme was changed to fix. | | IX77733 WEB ADMIN LOOKS FOR SCHEDULE TO UPDATE ONLY BY NAME IGNORING DOMAIN | | The UPDATE SCHEDULE form for updating client schedules through | the WEB interface dose NOT always reference the selected | schedule if schdules having the same schedule name exist in | multiple policy domains. | | IX78290 ANR0729E SYNTAX ERROR WHEN IMPORTING A NODE ASSOCIATED TO CLIENT | OPTION SET | | During IMPORT of client optionsets, client option value needs | to be surrounded by quotes in order to keep the INCLEXCL option | value as one long string. | | IX79415 SELECT ALL* FROM STGPOOLS COMES BACK W/EST_CAPACITY_MB: 0.0 | WHEN A STORAGE POOL IS LARGER THEN A TERABYTE. | | EST_CAPACITY_MB does not handle terabytes in | "select ... from stgpools" | | IX79925 QUERY CONTENT FAILS AGAINST OPTICAL VOLUMES WHICH HAVE AN UNDERSCORE | IN THEIR NAME | | The LABEL LIBVOLUME command now allows optical volumes to | contain underscores. The QUERY CONTENT command attempt to | resolve the optical volume the underscore in its name and | did not allow underscores. The QUERY CONTENT failed. | | IX80363 ANS1314E (RC14) WHEN DOING PARTIAL OBJECT RETRIEVE WITH OFFSET > 0 | AND LENGTH = 0 (STG=TAPE) | | When applications retrieving through the ADSM api | perform a partial object retreive with only the | offset (length=0) the retrieve failed. This was | due to an invalid calculation in the retrieval | code. | | IX80786 TBUNDO096 ASSERT FAILURE RESTORE.OBJECTS TABLE | | If a Restartable Restore session is cancelled early on, it | is possible to receive an assert failure during transaction | processing: | ANR9999D TBUNDO(207): Error 2 on delete from table | Restore.Objects for undo. | | IX80900 ADSM RELCAMATION PERFORMANCE RUNS SLOW ON V3 SERVER, | ESPECIALLY WHEN SLOWER DEVICES ARE USED | | When ADSM server reconstructs an aggregate with empty | space, it currently requires a position to the beginning | of the frame before retrieving each file. With large | buffers and small files this severly effects performance | as we have to rewind the tape for each retrieval. | | IX81040 AIX ADSM 3.1.1.3 "CHECKI LIBV LIB_NAME STAT=SCR CHECKL=NO | VOLR= XXXX,XXXX SEARCH=Y DEVT=XXXX"DOESN'T CHECKIN ALL QUALIFIED VOLS | | a linked-list traversal was accessing the wrong list | element (volume) at the time of checkin. This also can | cause volume not in the range to be checked in, as well as | omit volumes that are in the range. | | IX81426 ADSM SERVER V3.PTF3 ON NT, LIBRARY ADIC SCALAR 458. | MOVE MEDIA WITH REM=BULK: DOOR IS LOCKED WHEN THE PROCESS HAS COMPLETED. | | When checking out a tape in this library using the remove=bulk | option, the library door is quickly unlocked and locked. The | problem is that the door is never unlocked, so the customer | is unable to remove a tape(s) from the entry/exit slot. Effects | HP, SUN, AIX and NT platforms | | IX81655 FILES DOES NOT REBIND WHEN MANAGEMENT CLASSES CHANGE DURING BACKUP. | | If a client file is assigned to a new management on the client, | this causes the server to perform a re-bind operation. This | re-bind operation assigns the existing files this client | backed-up to a new management class. | | However, the re-binding algorithm was not re-binding all | possible files in the case where the new management class | had a retversions of NO_LIMIT. | | IX81674 WHEN DOING A CLASSIC RESTORE OF A LARGE FILE SYSTEM, | THE SERVER RUNS OUT OF MEMORY OBTAINING LOCKS. | | During a large restoration, the following error(s) are seen: | ANR9999D Memory allocation error. | Warning: insufficient memory to buffer output data; data discard | ANR9999D pkthread.c(528): Insufficient memory available to alloc | "tmLockHolder" object of (40) bytes, Thread 44, File tmlock.c, L | If you are doing a classic restore of a very large filespace, | the server can exhaust its memory during the "query" phase | because locks aren't being released until the entire query | phase is done. | This problem is not witnessed with a NoQueryRestore. | | IX81952 RESTORE OR RETRIEVE PROCESSING DEGRADED WHEN DISK STORAGE | POOL UNAVAILABLE, RESTORE ORDER LIST NOT OPTIMAL | | During restore or retrieve processing from a client, the server | does not optimize the retrieve order for the files if the | files: | | 1) Reside in a disk storage pool | 2) And one or more of the following conditions exists | for the disk storage pool where the data resides: | - the disk storage pool is set to ACCESS=UNAVAILABLE | - a needed disk volume is not varied on-line | - a given file is marked as damagedin the disk storage pool | | IX81990 FILES NOT EXPIRING DURING EXPIRATION | | Inactive files are not expiraing according to the copy group | definition for retain extra versions. This may cause excessive | tape usage and the db to grow. | | IX82029 EXPORT THREAD HANGS. | | The server can deadlock if file data for a particular node is | exported at the same time as a backup, archive, or space- | management session is storing files for the same node. This | problem is caused by contention for the same database lock by | the export and storage operations. | | IX82032 ADSM SERVER HANG ON NO QUERY RESTORE | | The ADSM V3 server may hang while doing a no query restore | (NQR). A query session shows the hung session is in the run | state. | | IX82190 RECLAMATION VOLUME SELECTION UNPREDICATBLE. | | The current reclamation volume selection algorithm is not | ordered in a predictable manner. Based on many customer | requests, the algorithm will now first choose the eligible | volume which has the largest percentage of reclaimable | space. | | IX82308 ADSM MESSAGES MANUAL AND HELP OUTPUT INDICATES THAT THE NODENAME | AND NOT THE IP ADDRESS SHOULD BE DISPLAYED IN ANR8214W MESSAGE | | There is a documentation error in the on-line help and the | messages manual for message ANR8214. This message should refer | to "IP Host Address" instead of "node name". | | IX82320 SELECT COMMAND DISPLAYING THE PENDING_DATE MAY REPORT INCORRECT DATA. | | | IX82401 STORAGE VALIDATION AREA OVERWIRTTEN WITH USER DATA CAUSING | (server) TO LOOP | | In certain rare circumstances during a restartable restore | (No-Query Restore) a memory overlay condition could take | place causing a loop or abend. The circumstance | identified is when a file is backed up with a given | management class name. Since the time of backup the | file is re-bound to a new management class name which | is shorter in the number of characters. The failure | can happen during a restartable restore involving the | file. | | IX82436 WHEN UPDATING A MGMTCLASS NOT LISTED ON TOP OF THE LIST, THE WEB | ADMIN WILL DISPLAY THE INCORRECT MGMTCLASS DESCRIPTION. | | When updating a mgmtclass not listed on top of the list, the web | admin will display the incorrect mgmtclass description. When a | domain have several management classes and when an update is | performed on a management class that is not on top of the list, | the web admin will display the management class description that | belongs to the management class on top of the list. | | IX82528 SQL ERROR AND SERVER HALT WHEN ADSM WEB ADMIN CLIENT QUERY FILESPACE | WITH 'DEL' (0X7F) CHARACTER IN FILESPACE NAME | | IX82562 ADSM SERVER CORE DUMPS ON WEBADMIN URL PROCESSING (ANR7837S MEM0 001) | | The server abends when parsing a url that has been truncated | from the web browser. | | IX82629 9740 max drive should be 10 | | IX82739 ADSM V3 SERVER DOES NOT DISPLAY HELP FOR CLIENT ADMIN MESSAGES. | DOC NEEDS CLARIFICATION ON WHAT ADMIN COMMANDS WILL HAVE HELP. | | The server on-line help did not include the information | necessary for providing help for ANS messages to the | ADSM Command Line Administrative Client. | | IX83014 ANR0422W ERROR. NODE NAME IS CHANGING ON IT'S OWN UNDER CERTAIN | CIRCUMSTANCES. | | The ADSM server may corrupt string values it is processing. | An example is a node name appears incorrect. | | IX80101 SELECT * FROM CONTENTS OUTPUT MAY HAVE GARBAGE FILESPACE_NAME FIELD | | When "select * from contents" is issued, garbage is | sometimes displayed for the filespace name. | | IX81330 CANNOT DEFINE CLIENTACTION WHEN THE OBJECTS FIELD CONTAINS A DIRECTORY | WHICH HAS A SPACE IN THE DIRECTORY NAME. | | CANNOT DEFINE CLIENTACTION WHEN THE OBJECTS FIELD CONTAINS A | DIRECTORY WHICH HAS A SPACE IN THE DIRECTORY NAME. | For example: | Able to define a schedule with the following syntax and the | schedule runs successfully: | DEF SCH DOMAIN_NAME SCHED_NAME ACTION=ARCHIVE | OBJECTS='"f: my documents *'" | But cannot apply the same syntax for the objects field when | defining clientaction: | DEF CLIENTA NODENAME DO=DOMAIN_NAME ACTION=ARCHIVE | OBJECTS='"f: my douments *"' | This will error with ANR202E DEFINE SCHEDULE: | Invalid parameter - F: MY. | Tried objects="f: my documents *". The server accepted the | command but the schedule fails. Tried combinations of syntaxes | but all failed. | | IX83680 ANR8300E DURING A LABEL LIBVOL OPERATION USING THE | SEARCH=BULK PARAMETER((OP=00006C04, CC=320, KEY=FF, ASC=FF, ASCQ=FF). | | IX77909 ANE14--- MESSAGES ARE DISPLAYED ON SERVER INSTEAD OF ANE4---X | | Events such as ANE4007W are displayed as ANE14007. Because of | this, these events cannot be forwarded to an external event | handler. | | IX83398 DSMSERV CAN COREDUMP WITH IMIXN008 DURRING SERVER TO SERVER COMMUNICATIONS. | | Code was added at the 3.1.2.0 level of ADSM which allowed | multiple volume names to be picked within the same second. | Since the volumenames used in Server to Server communications | contain the time to the second, this would allow multiple | volumes of the same name. When this condition is discovered, | the transaction ends up being aborted twice, creating the | TMTXN008 condition. | | IX83777 PROBLEM W/ EXTERNAL LIBRARY MANAGER WHEN ISSUING QUERY DRMEDIA | | When running 3.1.2.0 Server code, issuing a QUERY DRMEDIA or a | MOVE DRMEDIA command will fail with the following errors: | | ANR9999D mmsdrm.c(135) error starting external library | batch process. | ANR2032E Q DRMedia failed - internal error detected. | | IX84204 ANR1171W MESSAGE CONTAINS MISSPELLED WORD ON ADSM V3.1.1.2 SERVER | | ANR1171W message contains misspelled word, "QUERY OPTIONS" should | read "QUERY OPTION". | *====================================================================== * II. ADSM CLIENT *===================================================================== | ************************************************************************* | Before You Install Your ADSM Client | ************************************************************************* | | WARNINGS | -------- | - ************* If your current client version is 3.1.0.3 or lower, | * IMPORTANT * existing filespace names will be migrated from volume | ************* label names to Universal Naming Convention (UNC) names. | While the migration is transparent, it will affect the | way filespace names are specified, especially from the command line | Backup-Archive client. It is IMPORTANT that you review the specifics of | this change in the README.OLD file before installing and/or using this | level of the client for the first time. | | - If you have file names with international characters (umlats, accents, etc.) | then the following client option MUST be in effect: | | USEUNICODEFILENAMES NO | | Otherwise the file names will be backed up with junk characters in the name, | and it will appear as if the prior problems with international characters | (APARs IC22005, IC21933, IC21926, IC21764) remain. | | Note that the default value is NO for all languages except English. | | - In order to back up Mac volumes on NT, you must have the following client | option set: | | USEUNICODEFILENAMES YES | | Yes, as you would imagine, this presents a problem if you have file names | with international characters, and you also have Mac volumes on NT. | Unfortunately this will remain a restriction until such a time that a fully | unicode-enabled Win32 client were to become available in a future version or | release. (Please note that this is NOT an announcement.) | | A circumvention for this problem is to use two nodes to back up the NT | system: One node that has USEUNICODEFILENAMES YES to back up only Mac | volumes, and another with USEUNICODEFILENAMES NO to back up the regular | files. | | Note that the default value is NO for all languages except English. | | - Prior to installing this package, you MUST shut down any existing ADSM | applications that may be running. This includes (but is not limited to) | the following: | | - ADSM Scheduler Service | - ADSM Client Acceptor Service | - ADSM Remote Client Agent Service | | If you try to install this package while the ADSM Scheduler Service is | running, you will get a message stating that a read-only file was | encountered. The program will ask if you want to replace anyway. If you | say yes, the install will fail as the files cannot be overwritten while | they are in use. If you say no, you run the risk of not having current | versions installed. | | If you try to install this package while the ADSM Client Acceptor Service | and/or ADSM Remote Client Agent Service is running, the installation will | hang. | | The services may be stopped via the NET STOP command from an MS-DOS command | prompt or via the Services applet (located in the Control Panel). | | - You must have Windows NT Administrator authority to install the ADSM | Scheduler, ADSM Client Acceptor, and ADSM Remote Client Agent services on | Windows NT. | | - If you uninstall any or all of the ADSM components, you MUST reboot the | system before attempting to install any or all of the ADSM components. | | - Clients installed into the same directory must be uninstalled together; you | cannot independently uninstall the backup-archive or administrator clients | in this case. | | - To install from the '\adsmcli\win32' directory on the CD-ROM, you need | approximately 30MB of free space in the Windows TEMP environment path and 2 | MB of free space in the Windows SYSTEM directory. If the TEMP directory is | on the same partition as the SYSTEM directory, you need 32MB of free space on | that partition. The Install program checks for free space when it starts and | exits with a message to the user if there is a problem. | | - If you are installing the ODBC component, you need an additional 1M of | SYSTEM directory space. The install program checks for this amount of space, | and lets the user know if there is a problem. | | - Some of the API installation directories have changed with this PTF. | Please refer to the API.TXT file if you use API applications. | | - If you use the Lotus SmartCenter feature of Lotus SmartSuite, make sure | you exit/stop this feature prior to installing. | | - Once the Window 32-bit Version 3 client has backed up or archived a file, | all active files for that client cannot subsequently be restored or | retrieved by a Version 2 client, regardless of the ADSM server version. See | the Migration Section in the README.OLD file for more details. | | - Shell Extension Conflict (Windows NT 4.0 platform only) | | There is a rare possibility that during installation a message will be | displayed indicating a Shell extension conflict. This is a result of a bug | in the installation software used on most Windows 32-bit platforms. | | One product that we know encounters this conflict is IBM AntiVirus V2.5.2. | The problem string will be displayed in the Warning message. The install | then exits. | | There are a couple of ways to circumvent this conflict with the install: | | 1) Get a fixed level of the offending product and install it prior to | installing ADSM. | | Example: If IBM AntiVirus Version 2.5.2 is the conflict, first install | IBM AntiVirus Version 3 (or later), then install ADSM. | | 2) Uninstall the offending product (e.g. IBM AntiVirus Version 2.5.2), | then install ADSM Version 3, then re-install the offending product. | | - Japanese characters are not displayed properly by the installation program. | Use English characters for directory path and folders. | | - If a previous version is detected the path to that version becomes the | default installation directory. | | - A warning is displayed if you install an additional copy of ADSM into a | location other than the previous copy. | | - If a client has never been installed but there is an existing component it | will be the default installation directory. | | - If the installation program detects existing ADSM environment variables | which may conflict with the installation, a warning dialog is issued. | | - During installation you now have the choice to uninstall previous versions | of the 32-Bit Windows client including files and program folders. | | - To completely UN-INSTALL a manual cleanup of options files that were | generated by the clients is required after uninstall. These default files | are located in the baclient and/or saclient directories. | | - The ADSM installation program creates one of two "sentinel" files following | the completion of the installation program. The file will be created in the | "base" directory of the ADSM installation (usually c:\win32app\ibm\adsm). If | the installation completes successfully, then the file: "adsm.ok" is | created. If the installation completes unsuccessfully, then the file | "adsm.err" is created. Other programs may watch for creation of this file to | determine if "silent" installations have completed. | | - View the README.OLD file for advanced installation considerations, including | information on how to perform "silent" installs. | | | Client Components | ----------------- | The table below indicates the components that are included with the ADSM | Version 3 Client for Win32. The YES/NO column indictes whether the component | is included. The CLI column indicates whether a Command Line Interface | exists, and the GUI column indicates whether a Graphical User Interface | exists. An 'x' under the CLI or GUI column indicates that the component has | that kind of interface. For example, the Administrative Client CLI is | available on both Intel and DEC Alpha platforms, while the GUI interface is | available only on for Intel. | | +----------------------------------------------------------------------------+ | | | INTEL | DEC ALPHA | | | COMPONENT NAME | YES/NO CLI GUI | YES/NO CLI GUI | | +----------------------------------------------------------------------------+ | | Backup-Archive Client | YES x x | YES x x | | | | | | | | Administrative Client | YES x x | YES x | | | | | | | | Application Programming | YES | YES | | | Interface (API) | | | | | | | | | | Web Client | YES x | NO | | | | | | | | ODBC | YES | NO | | +----------------------------------------------------------------------------+ | | See the text file PACKING.LST, located in directory \ADSMCLI\WIN32\, | for a list of installed client files. | | | Software Requirements | --------------------- | The ADSM Win32 Backup-Archive Client requires one of the following operating | systems: | | - Windows 95(**) | - Windows 98(**) | - Windows NT(**) 3.51 (SP5 is recommended) | - Windows NT(**) 4.0 (SP3 or higher is recommended) | | | Hardware Requirements | --------------------- | Any appropriately configured Intel(**) 80386 or higher hardware platform with | at least 32MB of disk storage and 16MB of memory to do a full install of the | ADSM for Windows 32-bit client package. A compact install only needs 18MB of | disk space. | | | Migration Information from Version 2 to Version 3 | ------------------------------------------------- | See historical readme file README.OLD. | | | Enterprise Management Web Backup-Archive Client | ----------------------------------------------- | See readme file WEBCLI.TXT. | | | Application Program Interface (API) | ----------------------------------- | See readme file API.TXT. | | | ************************************************************************* | Installing the ADSM Client | ************************************************************************* | | Installing the Client | --------------------- | 1. Run setup.exe from the '\adsmcli\win32\' directory on the CD-ROM. | | 2. You may now specify a directory to install ADSM. | | 3. You may now choose a Compact, Custom or Typical install: | | a. Compact: installs the Backup-Archive client and the Web client. This | installation option requires 18MB of disk space. | | b. Custom: installs the components you select. | | c. Typical: installs the following: | - Backup-Archive Client | - Administrative Client | - Web Client | - Scheduler and Web Client services (NT only) | - ODBC support | - HTML help | - Multimedia | | A Full install (all components) requires 33MB of disk space. | | 4. If you select Custom install, you can select which ADSM language support | files to install. | | 5. Select the Program Folder you wish to install. | | 6. If you have chosen to install both the backup-archive client and the | administrative client, you will be given the option to install both | clients into a single directory or separate directories. If you choose to | install into a single directory then the clients will share an options | file. Clients installed into a single directory must be uninstalled at the | same time; you cannot independently uninstall the backup-archive or | administrative clients, unless they are in separate directories. | | Note: Existing options files are preserved and the new options file | is saved in the appropriate directory with a name of dsm.new. | | | Additional Setup Considerations | ------------------------------- | - APPC support requires Microsoft SNA Server Version 3. Note that Microsoft | SNA Server Version 3 requires an intermediate Windows NT server. See | diagram below: | | +---------------+ +------------+ +--------+ | | MS SNA client |______________| Windows NT |____________________| ADSM | | | (ADSM client) | | Server | | Server | | +---------------+ TCPIP, +------------+ SNA LU 6.2 +--------+ | IPX/SPX, | Named Pipes, | or Banyan Vines | | Refer to the Microsoft SNA Server documentation for information on how to | configure your system for SNA LU 6.2 communications. | | - A Windows NT user must possess the following rights to backup/restore files: | | Backup Files | Restore Files | Manage Auditing and Security Logs | | - When accessing domain resources such as network drives and UNC names, the | ADSM service must log on using a domain account that has the above rights. | | - Please view DSMCUTIL.TXT for instruction on installing/configuring ADSM | services on Windows NT. | | | Uninstalling the Client | ------------------------ | From the "ADSM for Windows NT" menu item, click "Uninstall ADSM Components". | This will allow you to choose which components to uninstall. | | For a completed automated, silent uninstall, run the uninstal.exe program | found in the "shared" directory with the /silentall command-line parameter: | | UNINSTAL /SILENTALL | | WARNING: This feature automatically stops all running ADSM services, and | removes all previously installed versions of ADSM found in the registry. | Uninstalling commences immediately upon execution; there are no confirmation | prompts. | | WARNING: After uninstalling ADSM components, you MUST reboot the system before | attemtping to install any ADSM components. | | | ************************************************************************* | Late-Breaking News. | ************************************************************************* | | What's New | ---------- | - There has been a change in what appears in ADSM READMEs with Version 3. The | Late-Breaking News and APAR sections of this README file contain only | information that is new with this particular PTF. Please see the README.OLD | file for important information that was in these sections of README files | from previous PTFs. In an effort to reduce the size of the current README | files, the README files will no longer be cumulative. This should make it | easier to find the most current information. | | - The Enterprise Management Web Backup-Archive client is now available for | installation with this PTF. This client allows you to backup, archive, | restore, and retrieve files on this workstation from any workstation that | has a Web Browser that supports JDK 1.1.5 (Netscape 4.06, Microsoft Internet | Explorer 4.01 or higher). This client replaces the Webshell client that was | previously available for OS/2, AIX, and Windows NT. Please see WEBCLI.TXT | for more information. | | - The ADSM manual 'Using the Microsoft Windows Backup-Archive Client' is | included in this package. For more information, see section "Getting Help" | below, sub-section "Client Documentation". | | - The maximum line length of the command line interface's online help has been | increased from 72 to 78 characters. See section "Known Problems" below if | this causes problems. | | | Documentation Updates | --------------------- | - A new option has been added to the command line Administrative Client | called "-DISPLAYMODE". Prior to this PTF, the output from Administrative | QUERY commands was displayed in a tabular format or a list format, depending | on the column width of the operating system's command line window. This made | it difficult to write scripts that parsed the output from the QUERY commands | as the output format was not predictable. | | The -DISPLAYMODE option allows you to force the QUERY output to tabular or | list format regardless of the command line window column width. | | The option is specified when invoking the Administrative Command Line | Client, and has the following syntax: | | >>--- -DISPLaymode=-+-LISt--+--->< | | | | '-TABle-' | | If you do not specify the -DISPLAYMODE option, the default behavior is to | format the QUERY output in list or tabular form, depending on the number of | columns in the operating system's command line window. | | Example 1: | | dsmadmc -id=storman -password=adminpw -displaymode=list | query domain > qdomain.out | | The file qdomain.out contains: | | ADSTAR Distributed Storage Manager | Command Line Administrative Interface - Version 3, Release 1, Level 0.6 | (C) Copyright IBM Corporation, 1990, 1997, All Rights Reserved. | | Session established with server BABYLON_5: Windows NT | Server Version 3, Release 1, Level 1.3 | Server date/time: 11/15/1998 04:18:18 Last access: 11/15/1998 04:12:35 | | ANS8000I Server command: 'q do' | | Policy Domain Name: STANDARD | Activated Policy Set: STANDARD | Activated Default Mgmt Class: STANDARD | Number of Registered Nodes: 14 | Description: Installed default policy domain. | | | ANS8002I Highest return code was 0. | | Example 2: | | dsmadmc -id=storman -password=adminpw -displaymode=table | query domain > qdomain2.out | | The file qdomain2.out contains: | | ADSTAR Distributed Storage Manager | Command Line Administrative Interface - Version 3, Release 1, Level 0.6 | (C) Copyright IBM Corporation, 1990, 1997, All Rights Reserved. | | Session established with server BABYLON_5: Windows NT | Server Version 3, Release 1, Level 1.3 | Server date/time: 11/15/1998 04:18:26 Last access: 11/15/1998 04:12:35 | | ANS8000I Server command: 'q do' | | Policy Activated Activated Number of Description | Domain Policy Default Registered | Name Set Mgmt Nodes | Class | --------- --------- --------- ---------- ----------------- | STANDARD STANDARD STANDARD 14 Installed default | policy domain. | | ANS8002I Highest return code was 0. | | - See README.OLD for information on updates from previous PTFs. | | | Known Problems and Limitations | ------------------------------ | - The maximum line length of the command line interface's online help has been | increased from 72 characters to 78 characters in this PTF. If you experience | word wrapping or splitting when using the online help, increase the width of | your command line window to 80 columns (or more), then redisplay the help | text. If your operating system allows you to set a default command line | window size, it should be set to display a minimum of 80 columns. | | - On Windows NT 3.51, the Administrative Client GUI can fail when switching | back and forth between selections in the "Show Media Information" dialog. | | - See the README.OLD file for known problem and limitations from prior ADSM | Version 3 PTFs. | | | ************************************************************************ | APARs Fixed in this PTF | ************************************************************************ | For APARs fixed in previous maintenance releases, see README.OLD. | | PTF IP21494 - Version 3, Release 1, Level 0.6 | --------------------------------------------- | IC19830 - Set access with NT GUI fails with: filespace not | known to the server | | IC19977 - V3 SA GUI built incorrect value for FORCE parameter | with DEFINE CLIENTOPT command. | | IC21080 - GUI option optfile is not recognized. | | IC21502 - Files are expired after communication failure and | session restart | | IC21559 - DSCFRA.TXT does not have the correct character | | IC21581 - SAGUI Include date for viewing Backup/Archive events | does not reset to default if modified in dialog | | IC21606 - The message "Unknown abort #38 from the server" | isn't explained in DSMERROR.LOG. | | IC21680 - PostNschedulecmd option is not working on Win NT | | IC21727 - Restoring a file to the same location with CLC | PTF 5 will sometimes show the restore destination | | IC21749 - The GERMAN ADSM 'DSM' executable for NT dumps on | startup | | IC21764 - Files previously backed up using Unicodefilenames | are left active with new backups. | | IC21780 - Archive beginning at a directory below the root | receives error skipping unreadable directory | | IC21865 - 'Access Denied' message received during restore on Windows 95 | | IC21882 - ANS4012E 'file already exists' occurs when restoring | OS/2 file with EA or ACL data to NT | | IC21926 - Files with filenames containing special characters | (such as umlauts) are always backed up during | incrementals, even if unchanged, when MEMORYEFFICIENT=YES | | IC21933 - Query output on non-English clients is incorrect | if files have special characters like umlauts | | IC21937 - Restore -IFNEWER volumspace:\* does not replace | an existing file if the backup is newer then the | existing file. | | IC21938 - SAGUI Include date for viewing backup/archive events | does not reset to the default after being changed. | | IC21949 - Help Button in restore/archive/retrieve window of GUI | client calls wrong help screen | | IC21950 - Status bar in GUI is too small. | | IC21951 - Restore window ADSM NT BACLIENT GUI : Action field | not updated | | IC21952 - WinNT CLI Client has parsing/buffering problem | when REGBACK ENTIRE or REGREST ENTIRE or | EVENTBACK ENTIRE or EVENTREST ENTIRE is | attempted after q ba - the message "ANS1433E | Extraneous argument 'xxx' after keyword 'xxx'" is issued. | | IC21959 - NT client 3.1.0.5 uses NODENAME to create filespace during | incremental backup if the old style domain option | specified in dsm.opt file. | | IC22005 - Unable to select a file in the GUI Restore window if | it is under a directory whose name has an accent | | IC22037 - Unable to backup Mac files stored on Windows NT | | IC22093 - Incorrect password for scheduler service fills log | | IC22192 - SAGUI COMMAND CURRENTLY ACTIVE WILL NOT SET TO YES | | IC22283 - ADSM registry backup on Windows 95 fails with message | ANS1435E. | | IX78268 - GUI doesn't report backup statistics after tape mount | | IX79203 - ADSM GUI under Windows NT doesn't restore information | to the "Following location" if drive for restore has | no folders. | | IX79511 - Using quotes to specify a wildcard within | a filespecification 3 consecutive times within | a session may error with ANS1102E. | | IX79636 - Exclude statement is affected during archive | processing and could skip managment class | definition done by include statement. | mounted | | IX80983 - QUERY ARCHIVE doesn't work in MBCS environment | | IX81345 - Using the -COMMADELIMITED or -TABDELIMITED option | can cause the output of admin client to be truncated | and can also cause the session to hang. | | IX82209 - If length of string of option value is longer than | 200 for POSTSCHEDULECMD or PRESCHEDULECMD, it whould | generate the coredump by executing DSMC SCHED command *====================================================================== * III. ADSM INFORMATION *====================================================================== *====================================================================== * Where to Find Documentation *====================================================================== The BOOK CD contains the ADSM Version 3 Release 1 Server and Client ESP/Beta books, in PDF format, for AIX, MVS, Windows NT, Sun Solaris, and HP-UX. This CD contains the following: readme.txt (this file) ar32e301.exe (Adobe Acrobat Reader installation file for Windows 95, Windows NT) aro2e30.exe (Adobe Acrobat Reader installation file for OS/2) adsmesp.pdf (main pdf file with links to books in the pdfs directory) pdfs (a directory which contains all 28 product pdf files) To install the Adobe Acrobat Reader on your platform, run the appropriate installation file, and follow the on-line installation instructions. Additional platform and language Adobe Acrobat Reader installation files are available at the following web site: http://www.adobe.com/prodindex/acrobat/readstep.html Use the Adobe Acrobat Reader to view the adsmesp.pdf file. This file contains links to the 28 product pdf files. Click on the book title you want to view. To navigate back to the adsmesp.pdf file, press and hold the right mouse button, move the cursor to the "Go Back" selection, and release the mouse button. *====================================================================== * Getting Help *====================================================================== - To receive technical support for ADSM: + Contact your ADSM administrator. This should be your first step when having problems with ADSM. + Your ADSM administrator will know how to contact IBM for Technical Support on your behalf. + For the latest information about ADSM, visit the ADSM home page on World Wide Web. The URL is: http://www.storage.ibm.com/software/adsm/adsmhome.htm - To participate in user discussions of ADSM: + 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.rz.uni-karlsruhe.de (mirror - Germany) ftp.wu-wien.ac.at (mirror - Austria) ftp.cac.psu.edu (mirror - Pennsylvania) - Performance Tuning for ADSM: The ADSM V3 Performance Tuning Guide will be available on the ADSM home page. Point your web browser to this address: http://www.storage.ibm.com/adsm - Frequently Asked Questions: For the latest list of ADSM Frequently Asked Questions (FAQ) please point your web browser to the following URL: http://www.storage.ibm.com/storage/software/adsm/adfaq.htm *====================================================================== * Trademarks *====================================================================== (*) Trademark of the IBM Corporation in the United States and other countries.