=======================================================================
Tivoli Storage Manager Server APAR History File -- Version 3.7.1.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
======================================================================
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=<DRIVE, 3590E-B or 3590E-C>
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 <VOLNAME> FROM SLOT 30 OF LIBRARY <LIBNAME>
||
|| 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.
||