======================================================================= Tivoli Storage Manager Server APAR History File -- Version 3.7.3.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 1999. All rights reserved. ======================================================================== Welcome to the Tivoli Storage Manager. Contents - APARS fixed by service level 3.7.0.0 - APARS fixed by service level 3.7.1.0 - APARS fixed by service level 3.7.2.0 - APARS fixed by service level 3.7.3.0 ====================================================================== APAR History ====================================================================*/ -------------------------------------------- - APARS fixed by service level 3.7.0.0 -------------------------------------------- IY03618 3.1.2.40 SERVER ABENDS WHEN ATTACHED TO A STK 9310 LIBRARY RUNNING ACSLS Server may crash with TMTXN008 ABEND if there is an error updating the inventory list during ACSLSL initialization. The release also includes fixes from the following device driver fixes. The device driver README files also include this information. IC24458 ILLEGAL REQUEST DURING READ ELEMENT STATUS AFTER STK 9710 FIRMWARE UPGRADE Additional data were returned from the Read Element Status command, causes incompatible storage allocation between the new firmware and the current ADSM device driver. The fix resolves the differences for 9710, 9714 and 9740 firmware upgrades. IY03314 ELAINT IS RECOGNIZED AS EXB8505 AND THEREFORE CANNOT LABEL TAPES WITH THE LABEL LIBVOL COMMAND The "Label Libvol" command fails with an I/O error when using Exabyte Eliant 820 drive. -------------------------------------------- - APARS fixed by service level 3.7.1.0 -------------------------------------------- IY03199 ADSM AIX SERVER 3.1.2.22 SERVER INCORRECTLY IDENTIFIES 3590E VOLUMES AS 4MM VOLUMES TO SUBSEQUENT SERVERS. ( Database Repair Command for 3590E early support customers ) ADSM development has discovered a problem in the 3.1.2.22 ADSM server where it incorrectly identifies 3590E volumes as 4MM volumes to subsequent servers. This problem only affects customers on 3.1.2.22 with 3590E drives. Subsequent servers will not recognize a 3590E volume introduced to a storage pool while running the 3.1.2.22 server. ADSM development is providing a special server command to repair the database so that customers can access the affected volumes. Although there is no loss of data, as a precaution, you should backup your ADSM database before performing the repair insructions below. 1. Backup your ADSM database. 2. Apply this server update (do not commit the update until you are satisfied that the repair is successfull.) 3. Add the option DISABLESCHEDS YES to your server options file. 4. Start the server. 4.1 Enter disable sessions at the ADSM prompt. 4.2 Delete the 3590E drive definitions. 4.3 Redefine the 3590E drives. 4.4 If the current format of the 3590 device classes is not DRIVE, update the format to DRIVE, 3590E-B, or 3590E-C. For example, UPDATE DEVCL <3590 device class> FORMAT= 4.5 Display a list of the affected volumes, by running the SHOW FORMATDEVCLASS command. For example SHOW FORMATDEVCLASS <3590 device class> 4.6 Repair the database, by running the SHOW FORMATDEVCLASS command again with the UPDATEFORMAT option. For example, SHOW FORMATDEVCLASS <3590 device class> UPDATEFORMAT 5. After the command completes, halt the server. 6. Remove DISABLESCHEDS YES from the options file. 7. Restart the server and continue running. PQ30157 EXPIRATION DM0001S TXNLOCK16 ABENDU0301 There is a possibility of the server crashing with a TXNLOCK15 or TXNLOCK16 message when a move data operation ( migration, reclamation, move data ) is run concurrently with a deletion operation ( expiration, delete filespace, delete volume ). -------------------------------------------- - APARS fixed by service level 3.7.2.0 -------------------------------------------- || ********************************************************************** || * APARS fixed by service level 3.7.2.0 * || * APARS may apply to both ADSM and Tivoli Storage Manager. * || * The APAR associated with Tivoli Storage manager will be indicated * || * by a suffix of "37". For example IC25588(SUN37) * || ********************************************************************** || || IC24035 WHEN UPDATING NODE WITH A WILDCARD, IF A NODE FAILS THE COMMAND || || SYSROUTES: IC25585(AIX37),PQ33700(MVS37),IC25586(NT37),IC25587(HP37), || IC25588(SUN37) || || Insufficient messages issued when an UPDATE NODE updating || multiple nodes fails because a node is in use. || || -------- || IC24676 ANR8829I REMOVE VOL FROM SLOT 30 OF LIBRARY || || SYSROUTES: IY05373(AIX),IC24676(NT),IC25135(HP),IC25136(SUN),IC25589(AIX37), || IC25590(NT37),IC25592(HP37),IC25591(SUN37) || || In the ANR8829I message, the ADSM server does not display || the element address of the Entry/Exit slot where it placed || the volume just checked out from the library with the || the CHECKOUT LIBVOLUME command and the REMOVE=BULK option. || The server reports the same element address (element address || of 30) each time. || || -------- || IC24886 FORCED PASSWORD CHANGE OPTION NOT WORKING IN ENTERPRISE MANAGEM || || SYSROUTES: IC25593(AIX37),PQ33702(MVS37),IC25594(NT37),IC25596(HP37), || IC25595(SUN37) || || The FORCEPWRESET attribute of an administrator was not being || passed from the configuration manager server to the managed || server. || || The FORCEPWRESET attribute of an administrator was not being || passed from the configuration manager server to the managed || server. || || -------- || IC25105 WHEN REMOVING A NODE NAME THAT WAS REGISTERED W/ USERID= PARM, || || SYSROUTES: IY07426(AIX),PQ34661(MVS),IC25910(NT),IC25911(HP),IC25912(SUN), || PQ34663(VM),IC25105(AIX37),PQ34664(MVS37),IC25913(NT37), || IC25914(HP37),IC25915(SUN37) || || When removing a node name that was registered with non default || administrator id no warning message is issued indicating || that the admin user id not removed. || || -------- || IX87208 SERVER MACRO CAUSES ACTLOG CORRUPTION, AND SOMETIME THE SERVER || || SYSROUTES: IX87208(AIX),PQ24308(MVS),IC23305(NT),IC23306(HP),IC23307(SUN), || IC25597(AIX37),PQ33703(MVS37),IC25598(NT37),IC25600(HP37), || IC25599(SUN37) || || A query actlog on an extra long command line failed. || Possible symptoms include hangs or traps. || || -------- || IX88345 THE FORMAT OF THE ANR8808E MESSAGE IS NOT BEING DISPLAYED CORRE || || SYSROUTES: IC25601(AIX37),PQ33706(MVS37),IC25602(NT37),IC25604(HP37), || IC25603(SUN37) || || The message ANR8808 had an imbedded tab character and other || incorrect spacing in the message. These errors in the || message cause it to not format correctly to the server || console or to an admin client. The formatting errors || do not prevent the message from being issued - it just || does not display well. || || -------- || IY00407_revOK Review Defect for Defect IY00407 || || SYSROUTES: || || -------- || IY00827 DEFINE SCHED OR UPDATE SCHED PARAMETER CMD='CHECKING LIBVOL...' || || SYSROUTES: IC25605(AIX37),IC25606(NT37),IC25607(HP37) || || Commands are not recognized as eligible for scheduling. || || -------- || IY02812 THE SET CONFIGREFRESH COMMAND FAILS TO CONTACT CONFIGURATION MA || || SYSROUTES: IC25678(NT37) || || ADSM Server Monitor thread was not properly initialized when || the Server is started as a Windows NT service. || || -------- || IY03035 ISSUING HELP COMMANDS FROM THE COMMAND LINE OF THE WEB ADMIN IN || || SYSROUTES: IC25608(AIX37),PQ33710(MVS37),IC25609(NT37),IC25611(HP37), || IC25610(SUN37) || || Issuing HELP commands from the command line of the WEB Admin || interface may cause the ADSM server to crash. || || -------- || IY03374 UNDER CERTAIN ERROR CONDITIONS WITH 3494, AN RC 11 IS RETURNED || || SYSROUTES: IY03374(AIX),IC25258(NT),IC25259(HP),IC25260(SUN),IC25612(AIX37), || IC25613(NT37),IC25615(HP37),IC25614(SUN37) || || This APAR documents a problem that occurs only on 3494 || libraries when the customer's USEREXIT forks a process. || || Background information leading up to the problem: || When ADSM calls close() to close a file handle to a drive, || the close() call returns a return code of 0 (success). || However, because the forked process inherited ADSM's open || file handles, the device driver never receives the close() || call. When ADSM calls open() to open a new file handle to || the same drive, the open() call returns a return code of 11. || || Description of the problem: || After receiving the errno=11, ADSM does not correctly || handle the error situation. As a result, ADSM may close || another process's file handle in error if there are at least || 11 open file handles. The number of open file handles depends || on the customer's environment and the amount of activity || at the time when the USEREXIT forked the new process. || || -------- || IY03390 SERVER HANG DURING BACKUP STORAGEPOOL IF WAIT=YES OPTION IS USE || || SYSROUTES: IC25629(AIX37),PQ33718(MVS37),IC25630(NT37),IC25632(HP37), || IC25631(SUN37) || || The processing for BACKUP STORAGEPOOL with the WAIT=YES || parameter may hang and/or abend the server. || || -------- || IY03519 DEFINES AND UPDATES MADE WITH THE WEB ADMIN DO NOT UPDATE THE D || || SYSROUTES: IC25617(AIX37),PQ33715(MVS37),IC25618(NT37),IC25621(HP37), || IC25619(SUN37) || || Using the web interface to update or define device related || information, the device configuration file is not updated. || || -------- || IY03614 ADSM NOT FREEING MEMORY (TCPSENDSSL) PROPERLY. || || SYSROUTES: IC25622(AIX37),PQ33717(MVS37),IC25623(NT37),IC25625(HP37), || IC25624(SUN37) || || Web Admin client does not free memory correctly || || -------- || IY03618 3.1.2.40 SERVER ABENDS WHEN ATTACHED TO A STK 9310 LIBRARY RUNN || || SYSROUTES: IY03618(AIX),IC25397(NT),IC25398(SUN),IC25626(AIX37),IC25627(NT37), || IC25628(SUN37) || || Server can core during initialization while initializing || the ACSLS library. Core will occur if an error occurs || while updating the inventory list. The core is || a TMTXN008 error. || || -------- || IY03818 ADSM UNNECESSARILY DISMOUNTS VOLUMES AT END-OF-TAPE PROCESSING || || SYSROUTES: IC25633(AIX37),PQ33719(MVS37),IC25634(NT37),IC25636(HP37), || IC25635(SUN37) || || During the storing of large client files, if the volume || became full the ADSM server would fail the mount of the || next volume because the mountwait flag from the client || had been reset to false; even though at the beginning || of the session the client had set the flag to true. || || -------- || IY04323 FORMAT=DETAILED DOES NOT WORK FOR CLEANUP ARCHDIR COMMAND, ONLY || || SYSROUTES: IC25637(AIX37),PQ33720(MVS37),IC25638(NT37),IC25640(HP37), || IC25639(SUN37) || || "clean archdir format=" accepts "detail" but not "detailed" || || -------- || IY04631 ERROR ADSM_DD_LOG2 (5680E405) LOGGED DURING TAPE DRIVE CLEANING || || SYSROUTES: IC25679(AIX37),IC25680(NT37),IC25682(HP37),IC25681(SUN37) || || ADSM_DD_LOG2 message is entered into the AIX error log || for a DD_CLEANER_INST condition. An ADSM_DD_LOG2 message || is a permanent hardware message type. This is incorrect. || || -------- || IY04652 ADSM CHECKIN LIBRARY VOLUME AND QUERY PROCESS CAN RESULT IN DEA || || SYSROUTES: IC25641(AIX37),IC25642(NT37),IC25644(HP37),IC25643(SUN37) || || Server deadlocks when query process is issued immediately || after a checkin, checkout, label, or audit || || -------- || IY04929 ANR4391I MESSAGES FLOODING THE ACTIVITY LOG RESULTING IN DATABA || || SYSROUTES: IY04929(AIX),PQ32928(MVS),IC25401(NT),IC25402(HP),IC25403(SUN), || PQ32929(VM),IC25756(AIX37),PQ33721(MVS37),IC25645(NT37), || IC25647(HP37),IC25646(SUN37) || || The problem is a status message, ANR4391, can flood the || server's activity log. This flood of messages then triggers a || backup database in the middle of expiration. || || -------- || IY05321 EXPIRATION PROCESS MAY HANG WHEN ATTEMPTING TO EXPIRE OBJECTS T || || SYSROUTES: IY05321(AIX),PQ32966(MVS),IC25420(NT),IC25421(HP),IC25422(SUN), || PQ32967(VM),IC25757(AIX37),PQ33722(MVS37),IC25648(NT37), || IC25650(HP37),IC25649(SUN37) || || During expiration processing, the server may hang. This hang || is only possible with expiration running. Typically, || clients will hang when connecting to the server because || of this and other server operations may also hang. || || -------- || IY05562 DEADLOCK SITUATION DURING EXPIRATION MAY OCCUR WHEN PROCESSING || || SYSROUTES: IY05562(AIX),PQ32968(MVS),IC25423(NT),IC25424(HP),IC25425(SUN), || PQ32969(VM),IC25758(AIX37),PQ33723(MVS37),IC25651(NT37), || IC25653(HP37),IC25652(SUN37) || || During expiration processing, the locking performed by the || algorithm to serialize access to server resources may not || be correct in cases where expiration is processing both || backup and archive files in the same deletion batch. This || can result in a "deadlock" on the server and the deadlock || detector will eventually detect this and end one of the || transactions involved. || || -------- || IY05678 ADSM AIX SERVER ISSUES CLOSE() AGAINST WRONG FILE HANDLE BECAUS || || SYSROUTES: IY05678(AIX),IC25437(NT),IC25436(SUN),IC25654(AIX37),IC25655(NT37), || IC25656(SUN37) || || Background information leading up to the problem: || When ADSM calls close() to close a file handle to a drive, || the close() call returns a return code of 0 (success). || However, because the forked process inherited ADSM's open || file handles, the device driver never receives the close() || call. When ADSM calls open() to open a new file handle || to the same drive, the open() call returns a return code || of 11. || || Description of the problem: || After receiving the errno=11, ADSM does not correctly handle || the error situation. As a result, ADSM may close another || process's file handle in error if there are at least 11 || open file handles. The number of open file handles depends || on the customer's environment and the amount of activity || at the time when the new process is forked. || || -------- || PQ26477 ABEND0C4 DEFINE UPDATE STGPOOL RECLAIMSTGPOOL VSPRINTF() || || SYSROUTES: IY05686(AIX),PQ26477(MVS),IC25267(NT),IC25283(HP),IC25284(SUN), || PQ32559(VM),IC25657(AIX37),IC25658(NT37),IC25660(HP37),IC25659(SUN37) || || ABEND0C4 DEFINE UPDATE STGPOOL RECLAIMSTGPOOL VSPRINTF() || || -------- || PQ27180 ABEND0C4 ANRAQMUT PROTOCOL VIOLATION ANR0444W || || SYSROUTES: IY05691(AIX),PQ27180(MVS),IC25272(NT),IC25724(HP),IC25725(SUN), || PQ32544(VM),IC25661(AIX37),IC25662(NT37),IC25664(HP37),IC25663(SUN37) || || occasional server crash || || -------- || PQ28443 INTERLINK FUNCTION NOT BEING INCLUDED AT LINK-EDIT TIME WXITCPE || || SYSROUTES: IC25665(AIX37),PQ33724(MVS37),IC25666(NT37),IC25668(HP37), || IC25667(SUN37) || || At execution of the TSO Admin Client module, an attempt to || connect to the Server results in a failure; return code || of -59 is noted in a message. When tracing is active with || the COMM option, the message "WXITCPER is NULL" is displayed || to indicate that a required function was not included when || the client was built. || || -------- || PQ28620 ADSM/MVS EXPIRATION RECLAMATION HANG || || SYSROUTES: PQ28620(MVS),PQ32550(VM),PQ33725(MVS37) || || During reclamation if expiration deletes all remaining || active data from a volume when the server goes to || reclaim the next volume the server may abend. || || During reclamation if expiration deletes all remaining || active data from a volume when the server goes to || reclaim the next volume the server may abend. || || -------- || PQ29705 ANR5083 IUCV CONNECTION TERMINATED - ERROR XX ACCEPTING CONNECT || || SYSROUTES: PQ29705(VM) || || Abend 12D during IUCV communication session with CMS client || || -------- || PQ29708 QUERY ACTLOG SEARCH= || || SYSROUTES: PQ33726(MVS37) || || An invalid character in the activity log causes a loop. || || -------- || PQ31373 ADSM/TSM DOC INDICATES ABBREVIATION FOR DEFINE MACHINE IS DEF M || || SYSROUTES: IC25669(AIX37),PQ33727(MVS37),IC25670(NT37),IC25672(HP37), || IC25671(SUN37) || || Server does not allow for using an abbreviation of MA for || the DEFINE MACHINE, UPDATE MACHINE, DELETE MACHINE or || QUERY MACHINE commands. MA is the abbreviation which is || documented in our command reference. || || -------- || PQ31769 ADSM SERVER NETWARE RESTORE ANR9999D SMNQR(235): INVALID OBJECT || || SYSROUTES: IC25673(AIX37),PQ33728(MVS37),IC25674(NT37),IC25676(HP37), || IC25675(SUN37) || || During no query restore operations, the restore may || fail with an ANR9999D SMNQR(235) Invalid Object Header || State in retrieve operation for session..... || A logic error occurred in the server did not reset || certain control information following a sink error. || As a result the above message was issued due to the || object header size being incorrect. || || -------- || PQ31959 LABELS ON EMPTY OUTPUT TAPES THAT ARE MOUNTED BUT NOT WRITTEN T || || SYSROUTES: PQ33731(MVS37) || || Tape label can be overwritten on unused tape volumes. || || -------- || IC25316 UPDATE SUMMARY TABLE STATISTICS NOT CORRECT. || || SYSROUTES: IC25316(AIX37),PQ34783(MVS37),IC25951(NT37),IC25952(HP37), || IC25953(SUN37) || || UPDATE SUMMARY TABLE STATISTICS NOT CORRECT. || || -------- || IC25327 CALLS MADE TO LOCALTIME LIBRARY ROUTINE ARE NOT THREAD SAFE: CA || || SYSROUTES: IY07602(AIX),PQ34867(MVS),IC25979(NT),IC25980(HP),IC25902(SUN), || PQ34868(VM),IC25981(AIX37),PQ34869(MVS37),IC25982(NT37), || IC25983(HP37),IC25327(SUN37) || || Enabling and starting a server trace could cause the server to || hang or abort. || || -------- || PQ31998 ANR9999D BDMVS(1540): ERROR 001C0A0C OCCURRED DURING I/O WHILE || || SYSROUTES: PQ31998(MVS37) || || Page fixing a batch of I/O buffers was specifying a batch size || of 1 rather than 16. This meant the first page of the I/O || page of the I/O buffers was fixed and the remaining 15 may || not be fixed. Code was added to the database backup component || to ensure a full batch size was specified on the page fix || request. || || -------- || PQ32470 ANR9999D PK390(2159): UNABLE TO OPEN IMAGES 'ADSM.V3R1M0.SANRIM || || SYSROUTES: PQ32470(MVS),PQ34331(MVS37) || || Web engine issues an ANR9999D message when a file is not found. || || || -------- || PQ32867 TIVOLI STORAGE MANAGER MVS SERVER DUMPDB PROCESSING FAILS WITH || || SYSROUTES: PQ3286(MVS37) || || -------- || IC25165 SERVER ABENDS WHEN RUNNING SERVER IN UTILITY MODE AND USING TAP || || SYSROUTES: IC25165(AIX37),IC25903(NT37),IC25904(HP37),IC25905(SUN37) || || The Tivoli storage manager can abend when running in utility || mode. Typically this has been found when restoring or loading || the server from the command line using the commands dsmserv || load or dsmserv restore. The problem occurs when using multiple || sequential volume to restore the database. The server abend || after the first volume is dismounted. || || || -------- || IC25166 SERVER ABENDS AFTER DISMOUNT FAILS DURING NORMAL SERVER OPERATI || || SYSROUTES: IC25166(AIX37),IC25817(NT37),IC25819(HP37),IC25818(SUN37) || || There is a chance that the TSM server can abend when a || volume is dismounted from a drive and the dismount fails. || This problem can be found if the stack trace back found || in a core file contains FinishMp with a call to || pkBroadcastSignal. The problem is that the signal || being broadcast is NULL and nobody is waiting on the || signal. || || || -------- || IC25167 SERVER DEADLOCKS ON A MOUNT/DISMOUNT OPERATION || || SYSROUTES: IC25167(AIX37),IC25906(NT37),IC25907(HP37),IC25908(SUN37) || || There is a potential that the server can deadlock || when one thread is requesting a mount point (you || will see a call to pvrAcquireMountPoint) and another || thread dismounting a volume is trying to signal the || ss mount queue (you will see a call to asNotifyMPAgent). || The problem is that the mount point thread is waiting || on the PVR mutex to be release and the dismount thread || is waiting on the SS mutex. The problem can be found || by looking at the output of a show threads command. || The server will appear to be hung out on sequential || volumes. || || -------- || IY05753 HIGH CPU USAGE CAN RESULT IN THE BUFFER PRE-FETCHER UTILIZING L || || SYSROUTES: IY05753(AIX),PQ34881(MVS),IC25988(NT),IC25989(HP),IC25990(SUN), || PQ34882(VM),IC25991(AIX37),PQ34883(MVS37),IC25992(NT37), || IC25993(HP37),IC25994(SUN37) || || Data base buffer prefetcher can use too much memory if the || thread servicing the prefetch requests can not service the || requests as fast as the other threads in the server can create || the requests. || || -------- || IY06424 ANR9999D ERROR POSITIONING SERVER VOLUME FOR VIRTUAL VOLUMES AF || || SYSROUTES: IY06424(AIX),PQ34665(MVS),IC25916(NT),IC25917(HP),IC25918(SUN), || PQ34666(VM),IC25919(AIX37),PQ34667(MVS37),IC25920(NT37), || IC25921(HP37),IC25922(SUN37) || || If the default management class on the target server for the || node representing the source server is changed, any data || for virtual volumes previously stored on the target server || will not be addressable. Specifically, the virtual volumes || on the source server will exhibit errors positioning on the || virtual volumes that have archive files bound to the previous || default management class. || || -------- || IY07203 RETRIEVING FILES THAT SPAN SIDES OF OPTICAL MEDIA FAILS. || || SYSROUTES: IY07203(AIX),IC25923(NT),IC25924(HP),IC25925(SUN),IC25926(AIX37), || IC25927(NT37),IC25928(HP37),IC25929(SUN37) || || When a file that is stored on optical media and spans sides || media there is a possiblity that retrieving the file may || fail. || || -------- || IY07274 SNMP SUBAGENT ONLY WORKS WHEN TRACING IS ENABLED || || SYSROUTES: IY07274(AIX),IC25909(AIX37) || || The SNMP subagent may not complete initialization unless || the -trace flag is used when invoking dsmsnmp. || This applies only to the AIX version. || || -------- || IY07355 PARTIAL OBJECT RETRIEVE MAY SEND LESS BYTES THAN REQUESTED || || SYSROUTES: IY07355(AIX),PQ34878(MVS),IC25985(NT),IC25986(HP),IC25987(SUN), || PQ34879(VM),IC25954(AIX37),PQ34790(MVS37),IC25955(NT37), || IC25956(HP37),IC25957(SUN37) || || Partial object retrieves would fail given certain offsets. || -------------------------------------------- - APARS fixed by service level 3.7.3.0 -------------------------------------------- $3 ********************************************************************** $3 * APARS fixed by service level 3.7.3.0 * $3 * APARS may apply to both ADSM and Tivoli Storage Manager. * $3 * The APAR associated with Tivoli Storage manager will be indicated * $3 * by a suffix of "37". For example IC25588(SUN37) * $3 ********************************************************************** $3 $3 IC23926 ADSM NT V3 DSMLABEL FAILS WITH ANR0000E ERROR READING MESSAGE R $3 $3 SYSROUTES: IC23926(NT) $3 $3 -------- $3 IC25316 UPDATE SUMMARY TABLE STATISTICS NOT CORRECT. $3 $3 SYSROUTES: IC25316(AIX37),PQ34783(MVS37),IC25951(NT37),IC25952(HP37), $3 IC25953(SUN37) $3 $3 UPDATE SUMMARY TABLE STATISTICS NOT CORRECT. $3 $3 -------- $3 IC25380 DIRECTORY FIELD IS LIMITED TO 30 CHARACTERS WHEN UPDATING THE F $3 $3 SYSROUTES: IC26087(AIX37),PQ35273(MVS37),IC25380(NT37),IC26088(HP37), $3 IC26089(SUN37) $3 $3 DIRECTORY FIELD IS LIMITED TO 30 CHARACTERS WHEN UPDATING THE $3 FILE DEV CLASS USING THE WEB ADMIN. $3 $3 -------- $3 IY03390 SERVER HANG DURING BACKUP STORAGEPOOL IF WAIT=YES OPTION IS USE $3 $3 SYSROUTES: IC25629(AIX37),PQ33718(MVS37),IC25630(NT37),IC25632(HP37), $3 IC25631(SUN37) $3 $3 The processing for BACKUP STORAGEPOOL with the WAIT=YES $3 parameter may hang and/or abend the server. $3 $3 -------- $3 PQ31486 ANR2578I MESSAGE ISSUED FROM MVS SERVER WHEN TRYING TO RUN SERV $3 $3 SYSROUTES: PQ31486(MVS),PQ36372(MVS37) $3 $3 Unable to successfully "ping" waiting clients when schedmode $3 is defined a "prompted". $3 $3 -------- $3 PQ31998 ANR9999D BDMVS(1540): ERROR 001C0A0C OCCURRED DURING I/O WHILE $3 $3 SYSROUTES: PQ31998(MVS37) $3 $3 Page fixing a batch of I/O buffers was specifying a batch size $3 of 1 rather than 16. This meant the first page of the I/O $3 page of the I/O buffers was fixed and the remaining 15 may $3 not be fixed. Code was added to the database backup component $3 to ensure a full batch size was specified on the page fix $3 request. $3 $3 -------- $3 PQ32867 TIVOLI STORAGE MANAGER MVS SERVER DUMPDB PROCESSING FAILS WITH $3 $3 SYSROUTES: PQ32867(MVS37) $3 $3 -------- $3 IC25329 WHEREPLATFORM OPTION FOR THE UPDATE NODE COMMAND DOES NOT WORK $3 $3 SYSROUTES: IY09210(AIX),PQ36722(MVS),IC25329(NT),IC26544(HP),IC26545(SUN), $3 PQ36723(VM),IC26546(AIX37),PQ36724(MVS37),IC26547(NT37), $3 IC26548(HP37),IC26549(SUN37) $3 $3 The WHEREPLATFORM option on the UPDATE NODE command did not $3 account for mixed case values (i.e. winNT). $3 $3 -------- $3 IC25438 SCRIPT IS LIMITED TO 2000 BYTES WHEN UPDATING WITH TSM 3.7.1.0 $3 $3 SYSROUTES: IY07365(AIX),PQ34574(MVS),IC25874(NT),IC25875(SUN),IC25876(HP), $3 IC25877(AIX37),PQ34576(MVS37),IC25878(NT37),IC25879(SUN37),IC25880(HP37) $3 $3 Scripts entered via the TSM Web Administrator interface are $3 limited to 2000 characters. $3 $3 -------- $3 IY05307 A COMBINATION OF EXCESSIVELY LONG MANAGEMENT CLASS NAMES OR ENT $3 $3 SYSROUTES: IY06918(AIX),PQ33961(MVS),IC25748(NT),IC25750(HP),IC25749(SUN),PQ33962(VM), $3 IC25751(AIX37),PQ33963(MVS37),IC25752(NT37),IC25753(SUN37),IC25754(HP37) $3 $3 A domain with an extremely long policy set will cause the $3 server to hang or abend when a backup/archive client connects. $3 The long policy set can be created by and extremely large $3 number of management classes, a large number of management $3 classes with long descriptions for the management classes or $3 copy groups. $3 $3 -------- $3 IC25793 Defunct processes on External Library Manager $3 $3 SYSROUTES: IY09270(AIX),IC25793(AIX37) $3 $3 On a heavily loaded system, defunct proceses sometimes appear. $3 $3 -------- $3 IY07274 SNMP SUBAGENT ONLY WORKS WHEN TRACING IS ENABLED $3 $3 SYSROUTES: IY07274(AIX),IC25909(AIX37) $3 $3 The SNMP subagent may not complete initialization unless $3 the -trace flag is used when invoking dsmsnmp. $3 This applies only to the AIX version. $3 $3 -------- $3 IY04693 ADSM SERVER DISPLAYS A MISLEADING ERROR MESSAGE WHEN ADSMSERV.L $3 $3 SYSROUTES: IY04693(AIX),IC26398(HP),IC26399(SUN),IC26347(AIX37),IC26348(HP37), $3 IC26349(SUN37) $3 $3 If the dsmserv.lock file is unable to be created, locked or $3 written to, the message indicates the server is already $3 running. There are other reasons for the failure such as $3 permissions, full filesystems, no inodes, etc. $3 $3 -------- $3 IY05753 HIGH CPU USAGE CAN RESULT IN THE BUFFER PRE-FETCHER UTILIZING L $3 $3 SYSROUTES: IY05753(AIX),PQ34881(MVS),IC25988(NT),IC25989(HP),IC25990(SUN), $3 PQ34882(VM),IC25991(AIX37),PQ34883(MVS37),IC25992(NT37), ##2 IC25993(HP37),IC25994(SUN37) $3 $3 Data base buffer prefetcher can use too much memory if the $3 thread servicing the prefetch requests can not service the $3 requests as fast as the other threads in the server can create $3 the requests. $3 $3 -------- $3 IY06424 ANR9999D ERROR POSITIONING SERVER VOLUME FOR VIRTUAL VOLUMES AF $3 $3 SYSROUTES: IY06424(AIX),PQ34665(MVS),IC25916(NT),IC25917(HP),IC25918(SUN), $3 PQ34666(VM),IC25919(AIX37),PQ34667(MVS37),IC25920(NT37), $3 IC25921(HP37),IC25922(SUN37) $3 $3 If the default management class on the target server for the $3 node representing the source server is changed, any data $3 for virtual volumes previously stored on the target server $3 will not be addressable. Specifically, the virtual volumes $3 on the source server will exhibit errors positioning on the $3 virtual volumes that have archive files bound to the previous $3 default management class. $3 $3 -------- $3 IY07203 RETRIEVING FILES THAT SPAN SIDES OF OPTICAL MEDIA FAILS. $3 $3 SYSROUTES: IY07203(AIX),IC25923(NT),IC25924(HP),IC25925(SUN), $3 IC25926(AIX37),IC25927(NT37),IC25928(HP37),IC25929(SUN37) $3 $3 When a file that is stored on optical media and spans sides $3 media there is a possiblity that retrieving the file may $3 fail. $3 $3 -------- $3 IY07233 WEB ADMIN SUGGESTS INCORRECT BEGINDATE WHEN SELECTING 'OBJECT V $3 $3 SYSROUTES: IY07233(AIX),PQ34863(MVS),IC25977(HP),IC25978(SUN),PQ34864(VM) $3 $3 Web admin suggests incorrect begin date when selecting $3 'object view' / 'server' / 'activity log'. $3 SQL queries involving the current date return the current $3 date plus one month. $3 $3 -------- $3 IY07355 PARTIAL OBJECT RETRIEVE MAY SEND LESS BYTES THAN REQUESTED $3 $3 SYSROUTES: IY07355(AIX),PQ34878(MVS),IC25985(NT),IC25986(HP),IC25987(SUN), $3 PQ34879(VM),IC25954(AIX37),PQ34790(MVS37),IC25955(NT37), $3 IC25956(HP37),IC25957(SUN37) $3 $3 Partial object retrieves would fail given certain offsets. $3 $3 During a backup/archive operation, it is possible for $3 the client session to hang if during the read operation $3 an error occurs. The session cannot be cancelled on $3 the server. $3 Partial object retrieves would fail given certain offsets. $3 $3 -------- $3 IY07446 ANR9999D MMSSCSI.C ELEMENT ADDRESS MISMATCH ADIC VLS 4MM. THE L $3 $3 SYSROUTES: IY07446(AIX),PQ36717(MVS),IC26530(NT),IC26531(HP),IC26532(SUN), $3 PQ36718(VM),IC26533(AIX37),PQ36719(MVS37),IC26534(NT37), $3 IC26535(HP37),IC26536(SUN37) $3 $3 ANR9999D MMSSCSI.C ELEMENT ADDRESS MISMATCH ADIC VLS 4MM. $3 $3 ANR9999D mmsscsi.c(4501): Element Address mismatch; slotInfo.ele $3 m =15, slotInv.addr = 0 $3 . $3 ADSM will allow the user to define the drives and library. Howe $3 ver, other drive related commands will fail with the above error $3 The problem is when ADSM / TSM issues a READ ELEMENT STATUS (b8) $3 type 0 the data comes back correctly. However if ADSM issues th $3 e (b8) type 2(storage slots) the drives,autochanger and e/e slo $3 t are excluded and the number of slots returned is 11 and not 15 $3 . $3 $3 -------- $3 IY07501 ADSM HANGS DURING EXPIRATION. $3 $3 SYSROUTES: IY07501(AIX),PQ36725(MVS),IC26550(NT),IC26551(HP), $3 IC26552(SUN),PQ36727(VM),IC26553(AIX37),PQ36729(MVS37), $3 IC26554(NT37),IC26555(HP37),IC26556(SUN37) $3 $3 The server may hang during expiration processing. This problem $3 occurs when any of the following messages are issued AND the $3 server has to evaluate different policy information for files $3 within the current selected group for expiration. The $3 messages that are seen than may indicate the hang are the $3 following: ANR0830W, ANR0831W, ANR0832W, ANR0833W, ANR0886E, $3 or ANR0887E. $3 $3 -------- $3 PQ30874 MESSAGE IS VERY CRYPTIC WHEN ADSM CANNOT OBTAIN FILE FOR RESTOR $3 $3 SYSROUTES: IY09212(AIX),PQ30874(MVS),IC26557(NT),IC26558(HP),IC26559(SUN), $3 PQ36730(VM),IC26560(AIX37),PQ36731(MVS37),IC26561(NT37), $3 IC26562(HP37),IC26563(SUN37) $3 $3 If a file fails retrieval from the server during either a $3 retrieve or restore operation, an ANR9999D message may be $3 received indicating the following: $3 $3 ANR9999D SMNQR.C(xxx): Bitfile xxxx not found for $3 retrieval. $3 $3 The restore/retrieve operation fails at this point and $3 no other information is given on the server. $3 $3 -------- $3 IC24852 ADSM AUDIT VOLUME DOES NOT CHECK THE IMBEDDED HEADER STORED WIT $3 $3 SYSROUTES: IY09061(AIX),PQ36539(MVS),IC24852(NT),IC26428(HP),IC26429(SUN), $3 PQ36540(VM),IC26432(AIX37),PQ36541(MVS37),IC26434(NT37), $3 IC26435(HP37),IC26436(SUN37) $3 $3 "audit volume" did not check object headers. $3 $3 -------- $3 IC25744 3.7.1.0 ADMIN WEB GUI DOES NOT GIVE YOU THE OPTION TO DEFINE OR $3 $3 SYSROUTES: IC26253(AIX37),IC26350(NT37),IC25744(SUN37) $3 $3 Users cannot define or update ACSLS libraries and drives $3 when using Web Admin interface. $3 $3 -------- $3 IC25769 GENERATE BACKUPSET CORE DUMPS IF MORE THAN 20 FILESPACES ARE PR $3 $3 SYSROUTES: IC25769(AIX37),PQ35612(MVS37),IC26191(NT37),IC26192(HP37),IC26193(SUN37) $3 $3 Tivoli Storage Manager server core dumps when generating a $3 backup set with more than 20 filespaces. $3 $3 -------- $3 IC25770 THE WEB ADMIN DOES NOT ACKNOWLEDGE THE 3494 LIBRARY ALL COMMAND $3 $3 SYSROUTES: IC25770(NT37) $3 $3 The user cannot define or update 349X libraries or drives $3 using the Web Admin interface $3 $3 -------- $3 IC25868 ADSM SERVER IGNORES THE SEARCH=BULK PARAMETER ON THE LABEL LIBV $3 $3 SYSROUTES:IY08917(AIX),IC26353(NT),IC26400(HP),IC26401(SUN),IC25868(AIX37), $3 IC26354(NT37),IC26355(HP37),IC26356(SUN37) $3 $3 For the LABEL LIBVOLUME command: $3 1) The SEARCH=BULK option only applies to SCSI libraries. $3 $3 The server does not correctly perform the following command $3 syntax checking for the CHECKIN LIBVOLUME command: $3 1) The SWAP parameter is only valid with the SEARCH=NO option. $3 2) The SEARCH=BULK option only applies to SCSI libraries. $3 3) The CHECKLABEL=BARCODE option only applies to SCSI libraries. $3 4) On SCSI libraries, the customer must specify CHECKLABEL=YES $3 or CHECKLABEL=BARCODE when using SEARCH=YES. $3 $3 For the LABEL LIBVOLUME command: $3 1) The SEARCH=BULK option only applies to SCSI libraries. $3 $3 -------- $3 IC25995 TSM SERVER DSMSERV RESTORE DB FAILS FROM VIRTUAL VOLUME OR SEQU $3 $3 SYSROUTES: IC26101(AIX37),PQ35314(MVS37),IC25995(NT37),IC26102(HP37),IC26103(SUN37) $3 $3 When performing a RESTORE DB to a point in time (specifying $3 TODATE and TOTIME on the command), the server can $3 cause a segmentation violation and crash. $3 $3 -------- $3 IC26005 LIBRARY CLIENT CAN NOT USE PRIVATE TAPES IN A SHARED LIBRARY $3 $3 SYSROUTES: IC26005(NT37),IC26352(SUN37) $3 $3 The problem is the attributes passed by the library client for $3 a private mount cause a problem with the library manager when $3 mounting a volume. $3 $3 -------- $3 IY03599 MANUAL DRIVES AND LIBRARIES DO NOT DISPLY IN THE WEB ADMIN WHEN $3 $3 SYSROUTES: IY03599(AIX),PQ35606(MVS),IC26184(NT),IC26185(HP),IC26186(SUN), $3 PQ35607(VM),IC26187(AIX37),PQ35608(MVS37),IC26188(NT37), $3 IC26189(HP37),IC26190(SUN37) $3 $3 'MANUAL' drives and libraries do not display in the WEB Admin $3 when server in French. $3 $3 -------- $3 IY04315 WHEN YOU USE LANGUAGE FRENCH, THE WEB ADMIN DOES NOT DISPLAY TH $3 $3 SYSROUTES: IY04315(AIX),PQ35176(MVS),IC26052(NT),IC26057(HP),IC26058(SUN), $3 PQ35177(VM),IC26059(AIX37),PQ35178(MVS37),IC26053(NT37), $3 IC26060(HP37),IC26061(SUN37) $3 $3 When server running with LANGUAGE other than English, some $3 values in SELECT commands and in some output views from $3 WEB Admin Client does not display. $3 $3 -------- $3 IY04825 LOGGING IN WITH INCORRECT PWD, AFTER PWD HAS EXPIRED, MESSAGE G $3 $3 SYSROUTES: IY04825(AIX),PQ36490(MVS),IC26407(NT),IC26408(HP),IC26409(SUN), $3 PQ36491(VM),IC26410(AIX37),PQ36492(MVS37),IC26411(NT37), $3 IC26412(HP37),IC26413(SUN37) $3 $3 Server tests for password expiration before authenticating $3 an admin. client. $3 $3 -------- $3 IY05795 UNDER RARE CONDITIONS DURING OFFSITE RECLAMATION PROCESSING THE $3 $3 SYSROUTES: IY05795(AIX),PQ36542(MVS),IC26443(NT),IC26444(HP),IC26445(SUN), $3 PQ36543(VM),IC26446(AIX37),PQ36544(MVS37),IC26447(NT37), $3 IC26448(HP37),IC26449(SUN37) $3 $3 There is a possibility that offsite reclamation may hang due $3 to a locking problem. This is unlikely to happen. In one $3 error path there are locks that could be obtained without $3 being released. $3 $3 -------- $3 IY06004 ANR9999D MESSAGE INCORRECT: EXPIRATION CONTINUES $3 $3 SYSROUTES: IY06004(AIX),PQ35316(MVS),IC26104(NT),IC26105(HP),IC26106(SUN), $3 PQ35317(VM),IC26107(AIX37),PQ35318(MVS37),IC26108(NT37), $3 IC26109(HP37),IC26110(SUN37) $3 $3 Expiration processing may issue an ANR9999D message $3 indicating that a given file could not be deleted if an $3 error was encountered while trying to delete the file. $3 There may also be ANR9999D messages issued from imutil.c $3 indicating that locks in the inventory could not be $3 obtained. In this case, expiration kept on processing $3 and completed. These messages are extraneous. $3 $3 -------- $3 IY06778 MULTITHREADED EXPIRATION RUNS VERY SLOWLY, BITFILES EXAMINED IN $3 $3 SYSROUTES: $3 $3 Expiration may run slowly when expiring ARCHIVE files. $3 $3 $3 -------- $3 IY07132 EXTERNAL LOG FILE CREATED BY DSMULOG SHOWS A 3 DIGIT DATE FORMA $3 $3 SYSROUTES: IY07132(AIX),IC26382(AIX37) $3 $3 The activity log output produced from dsmulog utility displays $3 dates after December 31, 1999 in incorrect format. $3 $3 -------- $3 IY07631 DSMLABEL DOES NOT WORK ON ACSLS DRIVE IDS GREATER THAN 3 $3 $3 SYSROUTES: IY07631(AIX),IC26584(NT),IC26583(SUN),IC26586(AIX37), $3 IC26588(NT37),IC26587(SUN37) $3 $3 The maximum number of drive as specified in the developer tool kit was 3. $3 However, as the STK library grow larger and more than 3 drive can be $3 placed into the library, this value is no longer valid. $3 $3 -------- $3 IY07663 SOME CLIENT SESSIONS BECOME 'STUCK' ON THE SERVER. THEY CAN NOT $3 $3 SYSROUTES: IY07663(AIX),PQ36810(MVS),IC26610(NT),IC26611(HP),IC26612(SUN), $3 PQ36811(VM),IC26613(AIX37),PQ36812(MVS37),IC26614(NT37), $3 IC26615(HP37),IC26616(SUN37) $3 $3 Clients performing backup/archive operations can hang $3 if an error occurs during a read verb opertion on $3 the server. $3 $3 -------- $3 IY07860 ANR9999D WHEN RUNNING AN AUDITDB $3 $3 SYSROUTES: IY07860(AIX),PQ36545(MVS),IC26450(NT),IC26451(HP),IC26452(SUN), $3 PQ36546(VM),IC26453(AIX37),PQ36547(MVS37),IC26454(NT37), $3 IC26455(HP37),IC26456(SUN37) $3 $3 Under certain circumstances, a database audit can fail and $3 produce messages such as the following. $3 ANR9999D bfaggrut.c(712):Unable to locate attributes for bitfile $3 ANR2184W bfaudit.c631: Transaction 0:110413 was aborted for $3 command AUDITDB. $3 ANR4142I AUDITDB: Database audit process terminated in error. $3 . $3 This problem occurs only when the audit is run with $3 FIX=YES and only when a specific combination of $3 referential-integrity errors is detected. The problem $3 is less likely to occur on Version 3.7 servers than on $3 earlier server levels. $3 $3 -------- $3 PQ31537 ANR0104E ASTXN(1256): ERROR 2 DELETING ROW FROM TABLE 'AS.VOLUM $3 $3 SYSROUTES: IY09067(AIX),PQ31537(MVS),IC26457(NT),IC26458(HP),IC26459(SUN), $3 PQ36549(VM),IC26460(AIX37),PQ36550(MVS37),IC26461(NT37), $3 IC26462(HP37),IC26463(SUN37) $3 $3 If expiration is running and reclamation begins shortly $3 after, there is a small window of opportunity for $3 reclamation to delete the volume being reclaimed before $3 expiration can perform deallocation. Expiration fails $3 to find the row for the volume in the volume status $3 table and fails. The transaction rolls back leaving $3 entries in the inventory with no volume. $3 $3 -------- $3 PQ33042 ABEND0C4 IN ANRSERV $3 $3 SYSROUTES: PQ33042(MVS),PQ36455(MVS37) $3 $3 The server encountered a storage shortage and attempted to $3 release reserved storage to relieve the shortage. In doing $3 so, an 0C4 abend resulted. As a circumvention, the customer $3 was advised to increase the region size of the address space $3 where the server was running. $3 $3 -------- $3 PQ33234 WEB BROWSER CONNECTS TO THE VM SERVER BUT THE SERVER IS SLOW TO $3 $3 SYSROUTES: IY07891(AIX),PQ35221(MVS),IC26069(NT),IC26070(HP),IC26071(SUN), $3 PQ33234(VM),IC26072(AIX37),PQ35222(MVS37),IC26073(NT37), $3 IC26074(HP37),IC26075(SUN37) $3 $3 HTTP session open but never close and are not canceled based $3 on commtimeout parameter in the server options. This happen $3 when an admin client connect to the http port instead of the $3 tcp port the session hangs. Another example of the problem $3 is a bunch of web sessions hang around and never seem to close. $3 $3 -------- $3 PQ35041 ADSM VM SERVER 565511901 V2R1L0.19 INVALID CREATION DATE WRITTE $3 $3 SYSROUTES: PQ35041(VM21),PQ35610(VM) $3 $3 Tapes used by ADSM/Tivoli Storage Manager have an invalid $3 creation date on tapes first used on 1/1/2000 or after. $3 The date will be 0xxxyy where xxx is 100 for the year 2000, up $3 to 199 for the year 2999, and yy is the day of the year $3 divided by 10 - 1-9 = 00, 10-19 = 01,... 360-366= 36. $3 This does not affect ADSM/Tivoli Storage Manager functions in $3 any way, the creation date on the tape label is not used for any $3 calculations, dates or age functions inside of ADSM/Tivoli Stora $3 Manager. $3 $3 -------- $3 IC25321 NT SERVER DURING STARTUP IGNORES THE DSMSERV -O FLAG $3 $3 SYSROUTES: IC26393(NT),IC25321(NT37) $3 $3 The NT Server does not honor the '-o' flag as documented. $3 $3 -------- $3 IC25471 ANR0000E UNABLE TO OPEN LANGUAGE AMENG FOR MESSAGE FORMATTING I $3 $3 SYSROUTES: IY09204(AIX),PQ36714(MVS),IC26524(NT),IC26525(HP),IC26526(SUN), $3 PQ36715(VM),IC25471(AIX37),PQ36716(MVS37),IC26527(NT37), $3 IC26528(HP37),IC26529(SUN37) $3 $3 AIX Server initialization fails with unable to open language $3 AMENG when no 'en_US' installed. $3 $3 -------- $3 IC25984 TRYING TO LOG EVENTS FROM A 3.7 TSM SERVER ON SUN SOLARIS TO TE $3 $3 SYSROUTES: IC26383(AIX37),PQ36456(MVS37),IC26384(NT37),IC26385(HP37),IC25984(SUN37) $3 $3 TEC startup can cause segmentation fault, abending server. $3 $3 -------- $3 IC26176 TRAP DURING DATABASE AUDIT WITH FIX=YES $3 $3 SYSROUTES: IY09272(AIX),PQ36806(MVS),IC26604(NT),IC26605(HP),IC26606(SUN), $3 PQ36807(VM),IC26607(AIX37),PQ36809(MVS37),IC26176(NT37), $3 IC26608(HP37),IC26609(SUN37) $3 $3 In very rare situations, the server can trap during a database $3 audit with fix=yes. This problem can occur if the server $3 attempts to delete an object that is stored in a sequential- $3 access storage pool. $3 $3 -------- $3 IY08334 LABEL FAILING ON SD3 (REDWOOD) DRIVES. LABEL LIBVOLUME FAILS ON $3 $3 SYSROUTES: IY08334(AIX),IC26357(NT),IC26396(HP),IC26397(SUN),IC26358(AIX37), $3 IC26359(NT37),IC26360(HP37),IC26361(SUN37) $3 $3 The server does not configure the STK SD3 drives correctly to $3 write the internal tape label. $3 $3 -------- $3 PQ33480 MVS SERVER DOES NOT ACCEPT LF (0X0A) IN SQL STATEMENT FROM ODBC $3 $3 SYSROUTES: PQ33480(MVS),PQ35849(VM),PQ35850(MVS37) $3 $3 The EBCDIC Line Feed character 0x25 is not recognized as a $3 space, so SQL commands including that character will not $3 parse correctly. $3 $3 -------- $3 PQ35037 DM0001S SERVER INITIALIZATION LOG WRITE ERROR $3 $3 SYSROUTES: IC26386(AIX37),PQ35037(MVS37),IC26387(NT37),IC26388(HP37), $3 IC26389(SUN37) $3 $3 The recovery log consistency checks that the TSM server does $3 when reading the recovery log were not at a low enough $3 granularity to detect the specific hardware failure experienced $3 during the recovery log write. $3 $3 -------- $3 IY07226 ADSMSERV.MIB RETURNS INCORRECT ENTERPRISE ID $3 $3 SYSROUTES: IY07226(AIX),IC26589(NT),IC26590(HP),IC26591(SUN),IC26592(AIX37), $3 IC26593(NT37),IC26594(HP37),IC26595(SUN37) #$3 $3 -------- $3 IY07930 CRASH AND CORE DUMP WHEN USING SERVER TO SERVER VIRTUAL VOLUMES $3 $3 SYSROUTES: IY07930(AIX),PQ35990(MVS),IC26270(NT),IC26271(HP),IC26272(SUN), $3 IC26273(AIX37),PQ35994(MVS37),IC26274(NT37),IC26275(HP37), $3 IC26276(SUN37) $3 $3 While using server-to-server virtual volumes, the source server $3 may crash. The crash only occurs if the passwords are not $3 synchronized between the source and target servers. $3 $3 -------- $3 IY08736 WHEN DELETE DRIVE IS GENERATED WHILE A DRIVE IS IN POLLING, $3 $3 SYSROUTES: IY08736(AIX),IC26375(NT),IC26376(HP),IC26377(SUN),IC26378(AIX37), $3 IC26379(NT37),IC26380(HP37),IC26381(SUN37) $3 $3 The server may crash if a customer issues a DELETE DRIVE $3 command during the last iteration of the drive polling $3 algorithm. $3 $3 -------- $3 PQ32418 WITH IUCV COMMMETHOD DFSMS MIGRATION OF DATA TO ADSM CAN WRONGL $3 $3 SYSROUTES: $3 $3 At the close of an IUCV communications session, ADSM may issue $3 message: $3 $3 ANR0480W Session session-number for node (node name) $3 (platform) terminated - connection with client severed. $3 $3 The message is misleading because when a session has ended $3 normally (without errors or problems). $3 $3 -------- $3 PQ32918 ABEND0C4 WHEN SERVER ALREADY COMING DOWN WITH ABENDEC6 $3 $3 SYSROUTES: PQ32918(MVS),PQ36803(MVS37) $3 $3 During the recovery of an EC6 abend, the server abended with $3 an 0C4 (protection exception) system completion code. $3 $3 -------- $3 PQ33542 ABENDU0301 ON DEFINE LOGVOLUME WHEN TOTAL RECOVERY LOG CAPACITY $3 $3 SYSROUTES: IY09200(AIX),PQ33542(MVS),IC26511(NT),IC26512(HP),IC26513(SUN), $3 PQ36712(VM),IC26514(AIX37),PQ36713(MVS37),IC26515(NT37), $3 IC26516(HP37),IC26517(SUN37) $3 $3 LVMCKPT227 assert occurs when defining a log volume that will $3 make the log size 5420M in size. $3 $3 -------- $3 PQ35119 ANR9999D DBALLOC SMP PAGE ZERO BIT COUNT MISMATCH $3 $3 SYSROUTES: IY09199(AIX),PQ35119(MVS),IC26504(NT),IC26505(HP),IC26506(SUN), $3 PQ36710(VM),IC26507(AIX37),PQ36711(MVS37),IC26508(NT37), $3 IC26509(HP37),IC26510(SUN37) $3 $3 When making a backup of the server's database, the server did $3 not perform sufficient consistency checks on the database in $3 order to help ensure that the backup would be usable. $3 $3 -------- $3 PQ35199 ADSM243S ABENDING: SIGNAL_ERROR CODE 0000012D WHEN TRYING TO IN $3 $3 SYSROUTES: PQ35199(VM) $3 $3 Signal_Error code 12D (assert) causes VM server to terminate $3 abnormally. The IUCV session was terminated by the CMS admin $3 client while the server was in the Accept routine. The server $3 routine sensed the termination and attempted to display a $3 message. Since a control block needed by the message routine $3 was not initialized properly, the server abended with code 12D. $3 $3 -------- $3