******************************************************************************* Content Manager V6.1.2 fixpack4 for AIX October 26th, 2001 This is an interim fixpack between Formal Corrective Service Deliverables (CSDs). Table of Contents 1. Installation Requirements 2. Installation Instructions 3. APAR Descriptions 4. Documentation APAR Fixes with Descriptions ******************************************************************************* ********************************************* 1. Installation Requirements ********************************************* In order to install this fixpack, you must have Content Manager v61 installed with CSD2 applied (syslevel 6.1.2.0) To determine your AIX syslevel, enter: lslpp -L frn.* ********************************************* 2. Installation Instructions ********************************************* 1. Download the cm6124.tar.gz file in binary mode to a temporary subdirectory on your workstation. You will need at least 20mb of free space. 2. To unpack the GZIP compression, enter: gzip -d cm6124.tar.gz If you don't have GZIP, you can obtain this freeware tool from: http://aixpdslib.seas.ucla.edu/aixpdslib.html 3. Unpack the cm6123.tar file using the AIX tar utility. For example: tar -xvf cm6124.tar 4. Log in as root. 5. Change to the 6120 subdirectory and start the Installation wizard by entering ./frnxupdate.sh 6. Change to the 6124 subdirectory and start the Installation wizard by entering ./frnxupdate.sh 7. After the installation has completed, you must rebind the databases of your library server and object server. You can rebind the server databases as follows: Library Server: logon as your library server admin id (lsadmin by default) Issue the command: frnbind.lib Object Server: logon as your object server admin id (osadmin by default) Issue the command: frnbind.obj ***************************************************** 3. APAR Fixes with Descriptions ***************************************************** ************************************ Fixpack 612.4 ************************************ APAR NUMBER: IR46071 / AIX COMPONENT: LS PMR NUMBER: 03486 APAR DESCRIPTION: In the 'Selected' pull down in the sysadmin are three utilities (Optimize, History, Expired time). Using the Optimize utility for testing, once it is set, it can not be unlocked. It appears to take the update but a subsequent logon displays the same scheduled status. FIX DESCRIPTION: Provided a new pgm to delete the utility schedules. SPECIAL INSTALLATION INSTRUCTIONS: NT/DB2: Copy the uptsched.bnd file to %FRNROOT%\bind directory. Copy frnnschd.DB2.exe to FRNROOT. NT/ORACLE: copy frnnschd.ORACLE.exe to %frnroot%. AIX/DB2: copy utpsched.bnd to $FRNINSTALL/BIND directory. Copy frnxsched.DB2 to $FRNINSTALL AIX/ORACLE: copy frnxschd.ORACLE to $FRNINSTALL. For DB2: Issue the following commands to bind the package: db2 connect to db2 bind utpschd.bnd REFERENCE DOCUMENTATION: ***** APAR NUMBER: IR46771 / AIX COMPONENT: LS PMR NUMBER: 36410,075,724 APAR DESCRIPTION: The following message is posted at the object server: <2001-06-27 10:43:43.10 Type: ERRLOG File: lbsdb.c Line: 8984 Func: LbsUpdateTargetObjectRowReplace RC: -911 MsgCode: 9861> FRN9861A:Database operation type UPDATE for the LAN-based object server finished. Return code = -911. <2001-06-27 10:43:43.30 Type: ERRLOG File: lbsdb.c Line: 8798 Func: LbsFetchSourceObjectRowReplace RC: 100 MsgCode: 9861> FRN9861A: Database operation type FETCH SOURCE for the LAN-based object server finished. Return code = 100. FIX DESCRIPTION: Removed the deadlock retry logic from the library server. It was causing problems with the transaction commit scope on the object server. SPECIAL INSTALLATION INSTRUCTIONS: none REFERENCE DOCUMENTATION: none ***** APAR NUMBER: IR45703 / AIX COMPONENT: TK / 5648D0452 APAR DESCRIPTION: AIX frnxdamn process will end with an exception when running with Multithreaded applications like Dynamic Page Builder and EIP. The problem is no limited to these applications and could occur with any AIX application. FIX DESCRIPTION: A zero file handle(0) is considered valid during object store and retrieve within the object server on AIX. SPECIAL INSTALLATION INSTRUCTIONS: none REFERENCE DOCUMENTATION: none ***** APAR NUMBER: IR46471 / Windows & AIX COMPONENT: 5648D0452 / 5648D0452 PMR NUMBER: PMR 46692,019 APAR DESCRIPTION: The nhttp.exe application on the Notes server was crashing causing the Domino server to fail. The DLL involved is the FRNNDAPI.dll. This is to handle CM crash problem. This problem can occur on CM 6.1 and CM 7.1.This problem can occur on CM 6.1 and CM 7.1. FIX DESCRIPTION: In DmnGetResponse function, added semophore protection before the SymDeleteSymbol() function call, and release the semophore after the call. This way there will be no interruption between different threads on the symbol table. SPECIAL INSTALLATION INSTRUCTIONS: 1. Rename FRNROOT\DLL\frnndapi.dll to something else. 2. Apply the new frnndapi.dll to the same directory as above. 3. Bring up your application and try again. REFERENCE DOCUMENTATION: none ***** APAR NUMBER: IR43090 / Windows & AIX COMPONENT: OS PMR NUMBER: 64570,519,000 APAR DESCRIPTION: After the migrator migrates an objects into a storage class, it will set the OBJ_ACCTIONDATE (the next migration date) to a new date which matches the retention period, for example, if the retention period of the destination storage class is set to 60 day, then after migrating into this storage class, the OBJ_ACTIONDATE of an object will be set to 60 days from the current date. This means, during the next 59 days, the migrator will bypass this object when selecting candidates for migration. If the retention period has been set as "FOREVER", than after the migration, the OBJ_ACTIONDATE will be set to 12/31/9999, which means that the migrator will never consider it again as a potential candidate for migration. During every migration cycle, the migrator will "look" at any object with OBJ_ACTIONDATE set to the current day or early, and decide is the object due to migrate. Currently, unless the user set the retention period of a storage class to "FOREVER" or to a date before the year 2038 (some 13000+ days from now), the OBJ_ACTIONDATE of the migrated object will be set incorrectly to the next day. As more and more objects been migrated to the storage class with the wrong action date set, the migrator will waste most of the migration cycle time looking for objects that need not be migrated at all. Eventually, in some extreme case, all the migration cycle time are wasted, and there is no time left for any real object migration in the migration cycle. The migrator is using the ANSI C's time() function to compare two dates, but the time() function always return a negative value for any date after Jan 18, 2038, and this negative time will confuse the migrator and make it to set the next migration date incorrectly. FIX DESCRIPTION: The fix put in a check for the negative time returned from the time() function, and will set the next action date to 12/31/9999 in this case. So, if the user set the retention date of a storage class in the migration policy after Jan, 2038 (for example, from 13000+ to 32000 days) it will be treated as FOREVER. SPECIAL INSTALLATION INSTRUCTIONS: 1. Shut down the object server 2. Back up the old frnnlbcm.dll (Windows) or frnxlbcm.o (AIX) 3. On Windows platform, copy the frnnlbcm.dll to $FRNROOT\DLL, On AIX platform, copy the frnxlbcm.o to /usr/lpp/frn/lib REFERENCE DOCUMENTATION: none **************************************** Fixpack 612.3 **************************************** APAR NUMBER: IR46546 / AIX COMPONENT: Library Server APAR DESCRIPTION: Source Object Server Remote Migration causes Target Object Server to have no DB entries. ************************* APAR NUMBER: IR44258 / AIX COMPONENT: Library Server APAR DESCRIPTION: Jobber dies from DLL build processing making the library server unavailable. This is due to the size of the .sqc file exceeding a limitation in memory usage. FIX DESCRIPTION: Processing a very complex search on a database canoverflow our 10k buffer search clause. I have modified thecode to check the complexity of the search being processed.If the complexity is above a certain level, we will not try to process that search. ************************* APAR NUMBER: IR44629 / AIX COMPONENT: Library Server APAR DESCRIPTION: OLD PROBLEM DESCRIPTION (NOT ACCURATE): Migrator fails to delete a 'D' status object. The following messages are posted: FRN9763A, FRN9763A,FRN9767A, FRN9763A FRN9763A and FRN9860A rc9763. The row in BASE_OBJECTS shows the volume where the file is located does not belong to the collec- tion. This condition was caused by two quick requests for collection changes without running destager in between the requests. In the case of this customer, collections are assigned by index class. A user reindexed the same itemid twice quick enough that destager did not have a chance to run. The second collection change used the undestaged row from the first collection change and then flagged it with 'D' status which then shielded it from the destager. The problem is that the collection change process copies the source row without altering the file name and path. It is expected that destager will do this. Destager never gets a chance so the row is left with an invalid volume path and 'D' status from the second collection change. Migrator can not mount this (ADSM) volume and fails. The impact is that there are 6 messages per error which creates a large frndiag.log and the through put of migrator can be adversly affected. --------------------------------------------------------------------------- NEW PROBLEM DESCRIPTION: Migrator fails to delete a 'D' status object. The primary message is FRN9860A rc9763 but FRN9763A and FRN9767A usually preceed it. The row in BASE_OBJECTS is identified by the 'object' in the FRN9860A message which is a timestamp that replaced the original OBJ_OBJECTNAME at the time the delete status was changed. The OBJ_VOLUMEID will relate to an ADSM/TSM SMS definition that will not belong to the storage class. This condition is the result of rapid collection changes (at least two) where the original source volume was ADSM/TSM and destager is either disabled or the collection change occurs so rapidly that destager is inbetween cycles. The first collection change created a 'U' status object that would normally be handled by destager. It is the second collection change that processes the 'U' status such that the odd 'D' status BASE_OBJECTS row is created. This APAR number will be used to identify this issue in CM 6.1 and 7.1 fixpacks/CSDs (AndyM). FIX DESCRIPTION: During reindex, if the object's status is 'U', there is no need to delete the file in the original storage system. SPECIAL INSTALLATION INSTRUCTIONS: backup original frnnlblb.dll frnnlbdb.bnd frnnlbmd. for NT, frnxlblb.o frnxlblb.bnd, frnxlbmd AIX. Install the new one. ************************* APAR NUMBER: IR45810 / AIX COMPONENT: CS CAPI Toolkit AIX / 5648D0451 APAR DESCRIPTION: Turning off CM client default signal handler FIX DESCRIPTION: Java applications using the CM client code can now turn off the CM signal handler in order to determine their own application problems. Before running the Java application, a user should export FRNSIG=0 to turn off signal handler in CM client code. If this environment variable is not set or is set to a different value, the CM signal handler is on. Note that the detection of this environment variable occurs at application initialization time. Therefore, once the application is started, changing the value of the environment variable does not turn on or off the CM signal handler. ************************* APAR NUMBER: IR44582 / AIX COMPONENT: Library Server / 5648D0421 APAR DESCRIPTION: FRNXMIIL utility does not allow user to enter the password FIX DESCRIPTION: Code has been added to read the password **************************************** Fixpack 612.2 **************************************** APAR NUMBER: IR42669 COMPONENT: Common Services / 5648D0431 APAR DESCRIPTION: Under System Administration Library Server, when selecting the Users only 38 of 60 userids are being shown. When groups are selected, the missing userids that where assigned to a group do show up. All the users can login with their ID even if it does not show up in the System Admin. FIX DESCRIPTION: SBTPATRONS table, column DFTLITEMOWNER refers to column USERID in the same table. By default, when a customer creates a new user using SysAdmin, the value in these two columns are the same. However, if using folder manager API to create a new user, the value in DFLTITEMOWNER can be different from the USERID value for that row, and refer to a different USERID. Changes have been made to fix this problem by changing DFLTITEMOWNER to 0 if the above situation happened. When deleting a user, DFLTITEMOWNER field will be reset if necessary. ************************* APAR NUMBER: IR43002 COMPONENT: Library Server / 5648D0421 APAR DESCRIPTION: Receive FRN7188A the library server could not generate a unique userid, when defining a large number of users to the system. FIX DESCRIPTION: Previous logic to generate a random userid was not adequate. Changed to use the system random number generation lrand48_r(). ************************* APAR NUMBER: IR43170 COMPONENT: Common Services / 5648D0431 APAR DESCRIPTION: Client using unsupported codepage hangs the library server during logon. FIX DESCRIPTION: Library Server will test the codepage combination and reject invalid combinations. ************************* APAR NUMBER: IR43332 COMPONENT: Object Server / 5648D0411 APAR DESCRIPTION: Remote object server migration fails with message FRN9792A RC0 when the file to be moved resides in ADSM. If a copy of the file exists in Staging (ubosstg), the remote migration works fine. FIX DESCRIPTION: Remote object server migration from ADSM now works. ************************* APAR NUMBER: IR43479 COMPONENT: Library Server / 5648D0421 APAR DESCRIPTION: The LLsInitializeJobber function does a CreatThread call for the LLsTableRefresh function and passes it the address of pAnchor in a local, automatic storage variable. The next thing LLsInitializeJobber does after the CreateThread is return (thereby popping the automatic variable stack). The first thing LLsTableRefresh does on entry is retrieve the pAnchor address and put it into a local variable. But the race is on between LLsTableRefresh picking up the passed in argument and the caller's stack area getting freed and reused. FIX DESCRIPTION: Change LLsInitializeJobber function to malloc a four byte area to pass the argument through not using the caller's stack area. Change LLsTableRefresh to free this area once it has picked up the argument. ************************* APAR NUMBER: IR43486 COMPONENT: Library Server / 5648D0421 APAR DESCRIPTION: Warning errors from DB2 during a PREPARE for a dynamic query when retrieving an object resulted in a failure of the retrieve. FIX DESCRIPTION: In the case of receiving a warning code during a PREPARE, log the SQLCODE but attempt to continue the processing. ************************* APAR NUMBER: IR44109 COMPONENT: Library Server / 5648D0421 APAR DESCRIPTION: No trace output from FRNCMD if the utility encounters an error. To trace the execution of the frncmd utility, the batch file that starts the utility ( frnnstcu.bat ) needs to be updated. Once the updates are made and the batch file is executed, the trace starts as expected. But if the utility ends with an errorlevel of '1', the statements in the batch file to format and turn off the trace are bypassed, and the trace is lost. FIX DESCRIPTION: Moved the code to format and stop the trace to cmnexit function. ************************* APAR NUMBER: IR44446 COMPONENT: Library Server / 5648D0421 APAR DESCRIPTION: Running Content Manager servers on a Windows NT system with more than 512 MB of RAM may result in the servers failing to start with the following message displayed: FRN9255A: Cp=14; Fc=FrnSysInitSharedMem; Tr=5; MC=9256; Fi=slpglint.cpp; Ln=1103; LA=(null); RC=-2538; FIX DESCRIPTION: Shared memory conflict between CM and Java runtime has been corrected. ************************* APAR NUMBER: IR44458 COMPONENT: Toolkit / 5648D0451 APAR DESCRIPTION: When calling simlibsearch with the null (0 Length) search string client receives FRN6772A error message. FIX DESCRIPTION: In LibPackageHostVarValue function (in frnpllrs.c) set string length to 1 when host var's attrType is varchar and host var string is null and the usOperator is relational. ************************* APAR NUMBER: IR44486 COMPONENT: Library Server / 5648D0421 APAR DESCRIPTION: Apparent Library Server hang; frndiag.log has the following message: FRN7474A: An internal system problem occurred. The FRN7474A is issued by frnpllch at this point because there is an error in receiving an order from the isolator api that we call. This APAR is created because the error code that is returned is not captured in the FRN7474 message. FIX DESCRIPTION: Fixed the log statement to log the IsoReceive error message. ************************* APAR NUMBER: IR44489 COMPONENT: Library Server / 5648D0421 APAR DESCRIPTION: Expired time is locked by the last person/userid who logged onto sys admin. The customer has to log onto sys admin, then log off and log on again to have the rights to update/change expired time. Expired time is supposed to be locked by the last person who updated, not the last userid/person who logged onto sys admin. Side note: expired time, once enabled can't be disabled. FIX DESCRIPTION: Fixed the error in assignement of the scheduler id. ************************* APAR NUMBER: IR44921 COMPONENT: Toolkit / 5648D0451 APAR DESCRIPTION: FRN8635A - Timeout occured waiting for the Library Server to respond to a request. The program times out at the retreive step (ExtRC=8635). DB2 traces show that the update and retrieve are sent to DB2 as two different units of work, so the retrieve ends up waiting for the update to finish, which won't happen until the retrieve finishes. A classic deadlock / timeout situation. FIX DESCRIPTION: Depending whether we are in a transaction or not, derive the proper Library Client session handle to be used within SimLibqueryPartExtSrch. This APAR also fixes a login problem where ProcessACLRows causes an access violation during logon. ************************* APAR NUMBER: IR45048 COMPONENT: Library Server / 5648D0421 APAR DESCRIPTION: The Library Server does not issue an error message if the wrong userid is used to start it. If the wrong userid is used to start the Library Server, it initializes and presents the user with the "Accepting Requests" message. However, users get error message " FRN6740A: The logon was not successful because of error 6056 " when they try to log on. The system admin client gets a " FRN8571A: =6056 " message. The frndiag.log shows -204 SQL return codes (undefined name). FIX DESCRIPTION: Added a dymamic sql query that will fail under the wrong id. ************************* APAR NUMBER: IR45224 COMPONENT: Toolkit / 5648D0451 APAR DESCRIPTION: Customer deleted frnadmin userid and they loged on to sys admin with another userid w/ maxprivs and created a new userid called "frnadmin". The customer then logs on with the userid "frnadmin" and receives a msg saying "the password doesn't match the userid for the patron..." frndiag.log on lib srvr: Type: ERRLOG file: frnpllcn.c Line 5528 RC: 7051 Msg Code: 7051 FRN7051A: The password specified for patron FRNADMIN is not valid. FIX DESCRIPTION: LibDefinePatron() in lcporder.c module the encrypted password was set to "FED0F6C9018BCF4A". It should be "B59CC182B7BDCD01". ************************* APAR NUMBER: IR45268 COMPONENT: Object Server / 5648D0411 APAR DESCRIPTION: Remote data migration from OS/2, WinN, or AIX v241 to CM 61 or later leaves files on the Target Object Server's "staging" volume without DB entries due to a design change in transaction logic in CM61. These HOMELESS files reside on the "staging" volume and are not destaged/archived to other volumes. The customer subsequently has their "staging" volume fill up. FIX DESCRIPTION: Remote migration cleanup on CM61/71 destages/archives the HOMELESS files to other volumes and the "staging" volume then reclaims space. On the Object Server, the environment variable FRN_DESTAGEALL=1 must be set for the destager to handle these unique files. ************************* APAR NUMBER: IR45362 COMPONENT: Object Server / 5648D0411 APAR DESCRIPTION: Object server reports FRN9919A, FRN9883A on retrieval of an object, followed by an abnormal termination of the FRNXLBPR process, FRNsysSignalHandler, this process received a signal 4. FIX DESCRIPTION: Handling of the SIG4 corrected. ************************* APAR NUMBER: IR45512 COMPONENT: Toolkit / 5648D0451 APAR DESCRIPTION: Utilization of the supported ip2toccount api (as used by the Content Management client application) to determine the count of items in a workbasket results in a lenghthy response time when the number of items and workbaskets is large. While the same values to determine the same results is contained in the FRNWIPITEMS table, the values are not kept in sync with the FRNITEMS table. Subsequently, any attempts to bypass the performance issues of the api by issuing a direct sql against the FRNWIPTEMS table results in possibly incorrect information. FIX DESCRIPTION: Check if all search filters are set to ALL in MakeQueryTOCEntries function (in fipquery.c). If so, issue dynamic SQL search selection only from SBTWIPITEMS. ************************* APAR NUMBER: IR45627 COMPONENT: Toolkit / 5648D0451 APAR DESCRIPTION: After loading one or more objects into CM, either SimLibUpdatePartExtSrch or SimLibUpdateObject is called to update the content of the objects. If the size of any object is greater than 67000 bytes, SimLibUpdatePartExtSrch or SimLibUpdateObject will fail on AIX with return code = 6256, or SIM_RC_RESIZE_FAILED, and returned hErrLog = 6395, or SIM_RC_WRITEOBJECT_FAILED. If Folder Manager trace is turned on, it will report a return code of 6256 by SimLibWriteObject. As a result, the update activity fails. FIX DESCRIPTION: Function CmnRetrieveFileData called fread() incorrectly. The third parameter of fread() function call should be 1, not the size of the file. Only the second parameter should be the size of the file, but not both the second and third parameters. ************************* APAR NUMBER: IR45951 COMPONENT: Toolkit / 5648D0451 APAR DESCRIPTION: The 16-byte itemID's currently are generated by clients randomly. This may cause performance problems for customers if the number of itemId's is huge. To solve that performance problem, a Library Client user exit is created to allow users to use their own algorithms to generate new itemID's in a more sequential manner. FIX DESCRIPTION: The default userexit is a no-op function and simply returns 0 to the caller. A sample userexit (commented out) is provided in this userexit. To use the sample method, users can simply un-comment it and modify it anyway desirable by the users, and build the userexit again. So the default behavior of this userexit is business as usual, that means no impact to existing customers, unless the userexit is modified and rebuilt by the customers. User exit: LibCreateItemID (generate item ID user exit) Format: LibCreateItemId (pszItemID,pszWorkStationID,sIndexClassID,pszUserID,sSemType) PURPOSE: When an application creates an item, Content Manager assigns the item several system-defined attributes. One of those system-defined attributes is an item identifier (item ID), which is randomly created by the Library Server Client. This user exit allows you to change the way the Library Server client generates item IDs. You can use the sample in this user exit to have the library client create sequential item IDs. To use the sample, remove the comments tags in the code and recompile. You can also modify the sample code and add your own algorithms. The library client encrypts the password that is associated with the user before it is transmitted to the library server. Use LibEncryptPassword if you want to provide your own encryption algorithm or eliminate the password encryption. Note: If you don't "uncomment" the sample code, the CM library server client will create item IDs as it is originally designed to do; random ID generation. PARAMETERS: pszItemID: CHAR - input and output A parameter passed in by the internal code. pszWorkStationID: CHAR - input The character string of the host name. The maximum length for this string is 18 bytes, which includes the null terminator. sIndexClassID: SHORT - input The index class identifier. pszUserID: CHAR - input The NULL-terminated character string that specifies the password for the user ID. This parameter is not case sensitive. sSemType: SHORT - input The semantic type of the item to store. The semantic type of an item indicates its general classification. Use a 2-byte integer. The predefined semantic types are: SEMTYPE_ACL Indicates that the item is an access list. SEMTYPE_ANNOTATION Indicates that the item is an annotation. SEMTYPE_DOCUMENT Indicates that the item is a document. SEMTYPE_FOLDER Indicates that the item is a folder. SEMTYPE_HISTORY Indicates that the item contains history events. SEMTYPE_MGDS Indicates that the item contains MGDS data. SEMTYPE_NOTE Indicates that the item is a note. SEMTYPE_USER Indicates that the item is a user item. SEMTYPE_WORKBASKET Indicates that the item is a workbasket. SEMTYPE_WORKFLOW Indicates that the item is a workflow. SEMTYPE_NONE Indicates that the item has no semantic type. All other values are for use by applications. The library server does not interpret them, so they can be used by the application in any way you want to. RETURN VALUES: The function returns a value of SHORT with zero for SUCCESS and -1 for FAILURE. COMMENTS: The function is located in the FRNPLCPW.C module. The LibCreateItemID function is a single function in FRNWLCPW.DLL. You can replace FRNWLCPW.DLL with your own FRNWLCPW.DLL. ************************* APAR NUMBER: IR46025 COMPONENT: Toolkit / 5648D0451 APAR DESCRIPTION: Custom written user application terminates indicating a failure in module frnndamn.exe, and text of: 'Exception: Access violation (0xc0000005)'. The application is used to load data into CM. Increasing FRNHEAPSIZE delays the access violation, setting it very small causes it to happen almost immediately. Tracing the application revealed that the access violation is actually in frnnslap.dll (which is a part of frnndamn.exe). This appears to be a memory leak in folder manager. FIX DESCRIPTION: 1. Daemon has been changed to handle the error correctly when no more memory is available, instead of continuing and thus causing a crash. 2. Folder Manager API, SimLibAddFolderItem, and several other API's, have been changed to always free the response block regardless of whether the return code is good or bad. This will avoid a memory leak when an error occurs. ************************* APAR NUMBER: IR46219 COMPONENT: Object Server / 5648D0411 APAR DESCRIPTION: Object Server Recovery deletes files not found in the database. Normally this is recommended, but in the case of APARS IR45028 and IR45268, these files will unintentionally be left in an abnormal state and are not in the database. So deleting these files before IR45268 is applied and run will permanently remove these files. FIX DESCRIPTION: The default behavior of Object Server recovery NO LONGER deletes files not found in the database. If you wish this behavior to happen, then you must set the Environment variable FRNRECDELETE=1 and run recovery to delete the files. **************************************** Fixpack 612.1 **************************************** APAR NUMBER: IR42529.b / AIX COMPONENT: OS / 5648D0411 PMR NUMBER: 99999,999,000 APAR DESCRIPTION: AIX Object Server can not be monitored by Tivoli GEM console. FIX DESCRIPTION: Added certified Tivoli Ready support to AIX Object Server SPECIAL INSTALLATION INSTRUCTIONS: There is a README.html file which has been reviewed by the Tivoli Competency Center in Raleigh and is part of the deliverables. It will be in the "tivready" subdirectory after you untar the fixpack. Please install it both on the system where the Object Server to be monitored live, as well as into your Tivoli GEM console. ********************* APAR NUMBER: IR43368 / AIX COMPONENT: TK / 5648D0451 PMR NUMBER: 84091,500,000 APAR DESCRIPTION: Customers can not easily create a "readonly" privilege set using the SysAdmin tool because the default "all user's" privilege bits (which gets added) includes the "DiscardBlobs" privilege Group. FIX DESCRIPTION: Removed "DiscardBlobs" privilege group from the default "all user's" privilege set. Added additional DiscardBlob privilege bits to three other sets used by the SysAdmin to grant authorizations to users. Those three assumed the required bits would already be set by the "all user's" defaults. ********************* APAR NUMBER: IR43747 / AIX COMPONENT: LSs / 5648D0431 PMR NUMBER: 19079,500,000 APAR DESCRIPTION: Occasionally, when starting a client application during initialization of the OSS component for the client, an error message is produced. FRN9255A: Cp=14; Fc=FrnSysInitSharedMem; Tr=5; MC=9256; Fi=../sl/slpglint.cpp; Ln=1112; LA=; RC=-2538; FIX DESCRIPTION: While the first process creating the shared memory has not yet finished, the second process tries to attach to the shared memory and fails. Logic has been added to handle this race condition. ********************* APAR NUMBER: IR43979 / AIX COMPONENT: TK / 5648D0451 PMR NUMBER: 99999 APAR DESCRIPTION: If MVS is the Library Server platform and the Ip2ListUser API is called from AIX or Windows platform, the password field's return is different from information saved in the SBTPATRONS table. This will make QBIC users not be able to logon. FIX DESCRIPTION: In the SimLibListUser API, once the user information is returned from the Library Server and put into the USERINFOSTRUCT data structure, we add a new step to the password field of this data structure. If the Library Server is not MVS, then no more processing is done. Otherwise, the internal function IsoPutFixChar is called for the password field to convert it back to the way it was stored in the SBTPATRONS table in Library Server. ********************************************* ********************************************** 4. Documentation APAR Fixes with Descriptions ********************************************** APAR NUMBER: IR45737 COMPONENT: Admin APAR DESCRIPTION: Customer reports that the System Admin Client does not show correct data on the Staging area as system is running. They have to shut down and reboot to show correct data. The SysAdmin Client is working as designed in this case, and the customer needs to use the command interface (frncmd) to obtain this information. FIX DESCRIPTION: In the Content Manager for Multiplatforms System Administration Guide Version 6 Release 1, the following information is added: Chapter 6, Server Control, "Monitoring and controlling the servers" For AIX, or Windows NT: To monitor the current status of the staging area, use the command utility with the status command (see Command utility on page 44). For example, to monitor current status on the object server named LDVOSAIX, enter: frncmd ldvosaix status ************************* APAR NUMBER: IR42268 COMPONENT: Admin APAR DESCRIPTION: System Administration client would no longer come up after changing SysAdmin machine name to bib-nt. Changed the machine name of a Sys Admin machine ( it was dladmin; we changed it to bib-nt). After doing this, the System Administration Client would no longer come up. Found a reference to the old name in a frnntmcl.jar.lnk file which was in the \winnt\profiles\dluser\recent directory (dluser is the user id under which system admin was installed and run ). To fix the problem with System Administration, Dev had to completely uninstall it ( including the Text Miner client ) and reinstall. FIX DESCRIPTION: In the Content Manager for Multiplatforms System Administration Guide Version 6 Release 1, the following information is added: Chapter 7, System setup and system maintenance "Adjusting system administration to network or host name changes" Text: Changing the host name If you change the host name of the system on which the system administration gateway is installed, you might receive the message: could not communicate with gateway when trying to access the system administration program, using the system administration client. You must modify the host name set in the system administration client. To change the host name for the system administration client: 1. Click the right mouse button on the Start push button on the Windows taskbar to display the pop-up menu. 2. Select Explore All Users to open the Exploring Programs window with the contents of the All Users folder expanded. 3. In the contents pane, click the Programs folder to display the contents of the folder. 4. Click the Content Manager folder to display the contents of the folder. 5. Click the right mouse button on the System Admin Client icon to open the pop-up menu. 6. Select Properties in the pop-up menu to open the properties notebook. 7. Click the Shortcut tab to open the Shortcut page. 8. Enter the new host name in the Targetfield after sa.client.SajcAdmin. 9. Click OK. ************************ APAR NUMBER: IR42892 COMPONENT: Object Server APAR DESCRIPTION: The message FRN9020A is used to reflect an error received from the protocol that is in use. This can TCP/IP as well as APPC. The message text needs to be changed to reflect this usage. FIX DESCRIPTION: In the Content Manager for Multiplatforms Version 6 Release 1 Messages and Codes manual, the following message is updated with TCP/IP information: FRN9020A Communications Manager/2 or SNA Server/6000 returned an advanced program-to-program communications (APPC) error or transmission control protocol/internet protocal (TPC/IP) error. Explanation: Communications Manager/2 or SNA Server/6000 issued an APPC or TPC/IP error, which caused the client or server program to stop processing. Component: Communications Isolator #Define: ISOERR_APPC_ERROR Action: Check the error logging facility to see which APPC or TCP/IP error code was issued. See the error codes in the Communications Manager/2 APPC publication or TCP/IP publication and correct the problem. ************************* APAR NUMBER: IR44499 COMPONENT: Object Server APAR DESCRIPTION: OBJECT SERVER WITH A LARGE STAGING DIRECTORY BUT NOT ON A DEDICATED SPACE WILL ENCOUNTER EXTENDED STARTUP AND RECOVERY If a large staging area is to be used, it is recommended to utilize a dedicated staging area. If the area is not a dedicated partition, the object server recovery and startup, which performs an automatic recovery, will be extended due to the large number of files that will be reviewed. Installations migrating from previous versions of Visualinfo should strongly consider implementing this option. In addition to setting STA_DEDICATED='Y' in the BASE_STAGING table, modify the value of STA_PATH to the newly defined dedicated partition. FIX DESCRIPTION: In the Content Manager for Multiplatforms Planning and Installation Guide Version 6 Release 1, the following information is added: Page 48, Step 4 Installing the Object Server on Windows, Fast object server recovery is now Fast object server startup Page 52, Step 4 Installing the Object Server on AIX, add the following information: Fast object server startup The object server should be started and shutdown once after installation. If the staging area is a dedicated space, you see that a column added to the object server table BASE_STAGING called STA_DEDICATED. This column is "dedicated" because it is only used by the object server, and only staged blobs are stored in it. To update the server: 1. Log on to object server admin user ID Example: su - osadmin 2. Connect to the object server database Example: db2 connect to objsrvrx 3. Update the BASE_STAGING database table, column STA_DEDICATED, using the following query: Example: db2 UPDATE BASE_STAGING SET STA_DEDICATED = 'Y' This command queries the file system to find out how much space is being used on the file system. This avoid a time consuming filter of the files in staging. The result is a close to constant startup time independent of the number of files in the staging area. If STA_DEDICATED is set to ’N’ then the startup time depends on how many files are in the staging area. Never set STA_DEDICATE to yes if the file system or partition holds files other than object server blobs. In the system administration program, do not allocate the staging space to be the size of the entire partition. Allow for some level of error as file systems report of space is not always completely usable due to overhead in the file systems. For most file systems the error is less than 10%. A good starting point for a 10,000 MB partition would be to set staging space to 9,000 MB with a purge start of 90% and a stop of 80%. These are only guidelines -- you should monitor the staging area as it approaches its full state and during periods of intense activity be able to ensure the staging file system does not get completely full at any time. If the file system is never close to being full, then the values can be increased. Destaging and purging problems might result if the values are set incorrectly. ************************* APAR NUMBER: IR46023 COMPONENT: Object Server APAR DESCRIPTION: Customer reports that Object Server start up time is 5.5 hours. The Object Server appears to be looking at every file in the staging area (ubosstg) which has approximately 190,000 files. FIX DESCRIPTION: In the Content Manager for Multiplatforms Planning and Installation Guide Version 6 Release 1 Page 52, Step 4 Installing the Object Server on AIX, add the following information: Fast object server startup The object server should be started and shutdown once after installation. If the staging area is a dedicated space, you see that a column added to the object server table BASE_STAGING called STA_DEDICATED. This column is "dedicated" because it is only used by the object server, and only staged blobs are stored in it. To update the server: 1. Log on to object server admin user ID Example: su - osadmin 2. Connect to the object server database Example: db2 connect to objsrvrx 3. Update the BASE_STAGING database table, column STA_DEDICATED, using the following query: Example: db2 UPDATE BASE_STAGING SET STA_DEDICATED = 'Y' This command queries the file system to find out how much space is being used on the file system. This avoid a time consuming filter of the files in staging. The result is a close to constant startup time independent of the number of files in the staging area. If STA_DEDICATED is set to ’N’ then the startup time depends on how many files are in the staging area. Never set STA_DEDICATE to yes if the file system or partition holds files other than object server blobs. In the system administration program, do not allocate the staging space to be the size of the entire partition. Allow for some level of error as file systems report of space is not always completely usable due to overhead in the file systems. For most file systems the error is less than 10%. A good starting point for a 10,000 MB partition would be to set staging space to 9,000 MB with a purge start of 90% and a stop of 80%. These are only guidelines -- you should monitor the staging area as it approaches its full state and during periods of intense activity be able to ensure the staging file system does not get completely full at any time. If the file system is never close to being full, then the values can be increased. Destaging and purging problems might result if the values are set incorrectly. ************************* APAR NUMBER: IR44174 COMPONENT: Object Server APAR DESCRIPTION: The Planning and Installation Guide, GC26-9831-00, Chapter 4, Installing Content Manager components on AIX, Step 4.Installing the object server on AIX, states the frnbind.obj should be run in #7. under the Oracle set of instructions. Development states this is not true FIX DESCRIPTION: In the Content Manager for Multiplatforms Planning and Installation Guide Version 6 Release 1 Pages 50 - 52, Step 4. Installing the object server on AIX Page 52, under Table 40, delete the following item (because you do not need to bind the database for Oracle): 7. If you did not create a database while using the wizard, bind your existing database. Enter: frnbind.obj ************************ APAR NUMBER: IR38764 COMPONENT: Library Server APAR DESCRIPTION: VisualInfo - Digital Library - trace - FRNTRC - FRNTRACE The discussion contained in Messages and Codes Chapter 3 Tracing Facility does not clearly identify the relationship of the controls (and variables) to the effect on the trace. For example, the variable FRNTRACELEV and those that follow almost seem to be unrelated to the FRNTRACE function by the way it is worded. The file 'frntrace.ctl' does not exist on NT. How does FRNLOGMAXMB relate to the -l parm for FRNTRC, and if there is no connection, what does FRNLOGMAXMB really do? OS2 is referred to repeatedly in the discussion for FRNTRACE but it is not functional on the OS2 platform for VI. FIX DESCRIPTION: In the Content Manager for Multiplatforms Messages and Codes Version 6 Release 1 manual, the following information is deleted: Page 6, Chapter 2. Tracing facility Deleted text: Tracing on AIX and Windows NT: Digital Library also provides additional features through its Independent Trace Facility (ITF) for collecting trace information. Pages 6 through 19: all information describing the following options is not valid and is deleted: * [-m mask] mask= products. event-types. components. functions * [-e maxSysErrors] Stop tracing after maxSysErrors have been recorded * [-r maxRecordSize] Truncate trace records at maxRecordSizebytes * [-rc return-code] Suspend tracing when return-code is encountered * [-p processId[. threadId]] Process ID and thread ID to trace. Thread ID does not apply to AIX. * [-c companion-id] The companion ID to trace in a server environment * [-s | -n | -mmio | -f fileName] Send trace records to shared memory, native trace facility, performance monitoring hardware, or a file * [-crash crash-mask] crash-mask = product-id. event-types. components. functions. trace-point Cause the program to exit when a specific trace point is reached ************************* APAR NUMBER: IR44974 COMPONENT: Library Server APAR DESCRIPTION: There is a need to document the limits of what the Optimization utility can be expected to do for the customer. For medium to large installations to get the best performance from the VI databases the customers' DBA will need to manage the database through the database utility functions that come with the database product FIX DESCRIPTION: In the Content Manager for Multiplatforms System Administration Guide Version 6 Release 1, the following information is added: Page 72, Chapter 9, Database installation and maintenance The optimization utility The optimization utility that is provided with VisualInfo is intended to be used for a small to a moderately sized database. This utility performs the basic optimization functions necessary to keep your server database performing optimally. As your system grows and becomes more complex, it is recommended that optimization of the server database be performed by a qualified database administrator using the tools provided by your database product. As a rule of thumb you may use the following guidelines to determine when your system has gotten to complex for the optimization tool of VisualInfo: System with more than 100K items System with more than 20 index classes System containing multiple database indexes on an index class ************************* APAR NUMBER: IR42533 COMPONENT: Library Server APAR DESCRIPTION: For the RELCRITERIASTRUCT used by Ip2SuspendItem, the doc says that itemDeadlineWB is ignored if the tsExpDateTime is NULL. TL says this isn't true and that an itemid needs to be filled in anyway (a copy of what's in itemidReadyWB should do). The doc should be modified to reflect this. FIX DESCRIPTION: In the Content Manager for Multiplatforms C Application Programming Reference for Workstation Vol 2 Version 6 Release 1 Page 894, RELCRITERIASTRUCT (Release Criteria Data Structure) RELCRITERIASTRUCT description of itemidDeadlineWB has changed to: ITEMID - input The item ID of the workbasket to send the suspended item to if the expiration time criteria are satisfied. Add the following text: This field cannot be NULL. If you want to release the suspended item due to other criteria (e.g., not deadline), then you need to copy the item ID from the itemidReadyWB or pitemidReadyWBArray to itemidDeadlineWB parameter. Delete the following text: This field is required if the usReleaseType field contains the value OIM_SUSP_ANY_CLASS or OIM_SUSP_ALL_CLASS, and if pitemidReadyWBArray has not been specified. Otherwise, this field is ignored. ************************* APAR NUMBER: IR44446 COMPONENT: Library Server APAR DESCRIPTION: Running Content Manager servers on a Windows NT system with more than 512 MB of RAM may result in the servers failing to start with the following message displayed: FRN9255A: Cp=14; Fc=FrnSysInitSharedMem; Tr=5; MC=9256; Fi=slpglint.cpp; Ln=1103; LA=(null); RC=-2538; Or the servers may start and run, but the frncmd utility (frnnutsc.exe ) may not run. The command utility window opens and displays the copyright information, but the command prompt never appears. After a few minutes the following message is issued: FRN9254A : CMDUTIL component program frnnutsc.exe terminated with a problem return code FIX DESCRIPTION: In the Content Manager for Multiplatforms Application Programming Reference for Workstation Version 6 Release 1 When you try to bring up Library Server or Object Server, if the Server GUI hangs and the correspond DOS window displays the message: FRN9255A: Cp=14; Fc=FrnSysInitSharedMem; Tr=5; MC=9256; Fi=slpglint.cpp; Ln=1103; LA=(null); RC=-2538; Try the following: For Library Server: Open the file frnnstls.bat located in the %FRNROOT% directory, and add the following line after the line SET TRACELEV=0: SET FRNADDRON=YES For Object Server: Open the file frnnstos.bat located in the %FRNROOT% directory, and add this following line after the line SET TRACELEV=0: SET FRNADDRON=YES Note: do not set FRNADDRON as a global environment variable. Otherwise, other programs (command utility, network verification) might fail to start. ************************* APAR NUMBER: IR42479 COMPONENT: Library Server APAR DESCRIPTION: For both the C version (COMPID 569725044) and the Java Sysadmin, if the library server configuration is set for a single logon per user, the utilities that can be scheduled such (as expired time) will post FRN7213A. The utility requires the ability to make a second connection when the utility starts. The chapter in System Administration Guide ' System setup and system maintenance' fails to mention that library server configuration must be set for multiple sessions if you want to use the system admin. GUI server utilities. FIX DESCRIPTION: Ensure the library server configuration is not set for 'single session' in the 'Active sessions(Per UserID)' section on the 'Access' page of the library server configuration. ************************* TRADEMARKS __________________________________________________________________________ IBM Enterprise Information Portal for Multiplatforms V6.1 (program number 5648-D03) (c ) Copyright IBM Corp. 1998, 1999. IBM Content Manager for Multiplatforms V6.1 (program number 5648-D04) (c ) Copyright IBM Corp. 1994, 1999. Licensed Materials - Property of IBM All Rights Reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation