Tivoli Storage Manager for OS390/MVS Server Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2000. All rights reserved. ------------------------------ ATTENTION -------------------------------- This is a service PATCH based on certified service level 4.2.1.0. ------------------------------------------------------------------------ Service Level We strongly advise that you do not replace your installed code with this patch, but instead place it in a temporary linklib and access that linklib until an installable PTF is available. ------------------------------------------------------------------------ ********************************************************************** $$42111 Interim fixes delivered by patch 4.2.1.11 $$ Patches are cumulative, just like PTFs. So Interim fixes $$ delivered as "4.2.1.11" include those delivered in previous patches $$ $$ ------------------------- ATTENTION ------------------------------ $$ $$ For this patch, install of device support will not preserve $$ device definitions. Record device definitions and re-define $$ via SMIT when the install is complete. $$ ********************************************************************** efix2257 adsmscsi.sys still claims IBM LTO drive after 4.2.1.2 <@> efix2618 DD: support for more modules in Compaq MSL5026 <@> IC29916 FIBER CHANNEL ATTACHED STK9840 I/O PROBLEM <@> IC32153 ANR8836E - IBM ULTRIUM LTO CANNOT BE USED THROUGH RSM (WIN 2000) After upgrade to 4.2.1, the server cannot use the LTO library through RSM. Message ANR8836E is issued in actlog. The following is shown in a PVR MMS trace: mmsrsm.c(2804): RsmLibInitialze library start for CHANGER1 mmsrsm.c(2819): RsmLibInitialze library finish for CHANGER1 mmsrsm.c(1195): Verify Device Type is 21 pspvr.c(2257): PvrTapeIoctl: function = 0x8400C000 pspvr.c(2257): PvrTapeIoctl: function = 0x8400C008 pvr.c(3601): IOCTL (IOCINFO) failed on drive . Tape3. pvr.c(3726): Unable to determine the device type for device . The following combinations work OK: - TSM using LTO without RSM - TSM using DLT with RSM - NTBACKUP using LTO with RSM <@> IC32159 ANR7837S INTERNAL ERROR IMIMPORT01 DETECTED. During import node TSM server crashes with the following dsmserv.err / activity log entries. dsmserv.err: ANR7837S Internal error IMIMPORT01 detected. File imbkins.c, Line 822. <@> IC32239 MT -F /DEV/RMT/19MT STAT COMMAND ISSUED AGAINST A 9840 DISK RESULTS IN A SYSTEM PANIC ON SOLARIS Environment: Sun Fire 680 Server, running Solaris 2.8 and TSM server 4.2.1 StorageTek L700 containing 9840 Disks Command issued in TSM: mt -f /dev/rmt/19mt stat Problem: Solaris system panic panic cpu14 /thread=30015cdb800: BAD TRAP: type=31 rp=2a10217cee0 addr=0 mmu_fsr =0 occurred in module "SUNW,UltraSPARC-III" due to a NULL pointer dereference mt: trap type = 0x31 <@> IC32311 HP LTO ULTRIUM DRIVES SHOW AS UNKNOWN IN TSM DEVICE TYPE When setting up a library with HP Ultrium drives, the drives show up in the TSM Device Type field as UNKNOWN. This is seen in the Device Information of the TSM Management Console. <@> IC32360 CANNOT DELETE ACSLS LIBRARY WITHOUT COMMUNICATION TO ACSLS When deleting an ACSLS library definition from TSM, we attempt to speak to the ACSLS server to unlock all the volumes associated with the library. If we are not connected to the ACSLS server, these unlocks will fail and the delete library will fail as well. So if the ACSLS server is down, one cannot delete the ACSLS library definition from TSM because TSM cannot communicate with the ACSLS server. <@> IC32592 ANR9999D ASVOLMNT.C(519): BACKUP STORAGE POOL During a tape to tape operation or a migration from one sequential pool to another the following error may be encountered in the actlog. ANR9999D asvolmnt.c(519): ThreadId<56> Mount point deadlock possible. After the error is recieved the process that was trying to access the drives will fail. There are no corresponding errors in a trace file. The error may also be visible when performing the following functions: Backup storage pool, import, export, reclamation <@> IC32678 PVR:MULTIPLE MOUNTS OF A VOLUME WHEN USING LIBTYPE OF EXTERNAL The TSM server may hang when an UPDATE DRIVE command is issued and there are other library processes running. <@> IC32694 HARDWARE COMPRESSION DISABLED SUPERDLT DS_MT_SET_MODE <@> IC32704 TSM HPUX SERVER OPERATING SYSTEM PREREQS NEED TO BE REMOVED FROM INSTALL PACKAGE Beginning with TSM HPUX server level 4.1.2 an install prereq was put in place for the HPUX OS patch level XSWGR1100. This is a roll up of numerous (500+) HPUX patches. Apply this full patch level has been a problem for some customers. In addition this patch has now be superceeded/replaced with the QPK1100 bundle. <@> IC32707 ADIC 1200D LIBRARY IS UNABLE TO CHECKIN VOLUMES ON WINDOWS 4.2 ADIC 1200Don a Windows 4.2.x.x server fails upon checking in a volume. In running a label libv process, the volume gets labeled, but the process fails on the checkin. <@> IC32731 GENERATE BACKUPSET CRASHES TSM SERVER On TSM Server 4.2.1.8 and 4.2.1.9, run a Generate Backupset. . Backupset ends, TSM Server crashes . No Dr. Watson, dsmsvc.err, or dsmserv.err produced . Application.evt shows the following . ANR7837S Internal error PK_EXCEPTION (Refer to the N . application event log for details) detected. . ANR7838S Server operation terminated. . ANR9999D: PK_EXCEPTION -- Thread 35 (NT TID 3148): . pkReleaseMutex error, object -1: Unknown err 0 <@> IC32739 TSM SERVER HANGS AFTER UPDATE DRIVE COMMAND IS ISSUED WHILE If the TSM server option IDLETIMEOUT is set to something high like 999999999 it can prevent sessions from being established. This was seen specifically on Solaris. As a result of setting the value to 999999999 on a Solaris box with TSM 4.2 server running, the following output occurs when attempting to open a TSM Admin command line to the server: . Enter your user id: admin ANS1017E Session rejected: TCP/IP connection failure ANS8023E Unable to establish session with server. ANS8002I Highest return code was -50. . After lowering the value of IDLETIMEOUT, admin sessions can be established without any problems. <@> IC32766 IN LIBRARY SHARING ENVIRONMENT, 'UNABLE TO OPEN DEVICE' ERRORS In a library sharing environment, customers may see the following sequence of errors: ANR8779E Unable to open drive , error number=16. ANR9999D pvr.c(4681): Unable to opend device . Forcing dismount. ANR8311E An I/O error occurred while accessing drive (/dev/rmt/xxst) for SETPARM-3 operation, errno = 9. ANR8355E I/O error reading label for volume in drive (/dev/rmt/xxst). ANR8779E Unable to open drive /dev/rmt/xxst, error number=16. ANR8469E Dismount of LTO volume from drive (/dev/rmt/xxst) in library failed. ANR8779E Unable to open drive /dev/rmt/xxst, error number=16. ANR9730I Manual intervention required for library device (/dev/rmt/xxst)'. ANR8923I Dismount failed because drive in library is not currently owned by . <@> IC32791 DD: DEFINING ATL P3000 LIBRARIES CAN FAIL Define library can fail with ANR8300E I/O error on library (op=8401c050, cc=205,key=ff,asc=ff,ascq=ff,description=SCSI adapter failure) This problem is with TSM 4.2 on WINNT 4.0 and WIN2K servers, when defining libraries that are ATL P300/w one slot module! <@> PQ56314 ANR9999D SMADMIN EXPORT NODE - FILESPACE NOT EXPORTED TSM server hangs intermittently when a script runs Enable and Disable Event commands. <@>