============================================================================== ============================================================================== Licensed materials - Property of IBM 5724-D96 (C) Copyright IBM Corp. 2002, 2013 All Rights Reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. ============================================================================== ============================================================================== README for IBM(R) WebSphere(R) Business Integration for Financial Networks for Multiplatforms V3.1.1 Messaging Services for SWIFTNet InterAct and FileAct PTF UK97480 for APAR PM92781 Driver level: 3440 Date 2013-11-01 ============================================================================== ============================================================================== Table of contents ----------------- A About this document B Summary of changes C Planning D Installation E APAR details F Other changes G Known issues A. About this document ---------------------- Only the online version of this readme document is current. Before you install the corresponding PTF, download the latest version from: http://www.ibm.com/software/integration/wbifn/support Download the latest version of the WebSphere BI for FN product documentation from: http://www.ibm.com/software/integration/wbifn/library The structure of WebSphere BI for FN readme documents is identical for all PTFs. Sections that are not applicable are left blank. If you install more than one PTF at a time, combine the readme documents by merging the contents of each section. During the installation phase of this PTF your system cannot process messages. This readme document uses the following variables: The installation directory of WebSphere BI for FN. The directory /opt/IBM is used in examples. The customization directory. The directory /var/dni_03_01/cus is used in examples. The deployment directory. The directory /var/dni_03_01/cus/depdata is used in examples. The name of the WebSphere BI for FN instance. The name INST1 is used in examples. The name of the organizational unit. Depending on the context, this might be SYSOU, DNFSYSOU, or the name of a business OU. The names of users, groups, files, and directories are the same as those used in WebSphere BI for FN for Multiplatforms Planning, Installation, and Customization, SH12-6942. If you use different names, use those names instead of the names shown here. B. Summary of changes --------------------- APARs addressed by this PTF: PM92781 MSIF PROCESSING OF BIG FILES IN MSIF LEADS TO TIMEOUTS FOR OTHER TRANSFERS PM91756 MSIF DISABLE SAG SWITCHING WITHOUT DEACTIVATING WORKLOADBALANCING PM84492 MSIF TEMPORARY COMMAND RESPONSE QUEUE NO LONGER AVAILABLE FOR MSIF PM85697 MSIF MSIF SEND MESSAGE REQUEST REJECTED DUE TO DB2 DEADLOCK/TIMEOUT PM96617 MSIF IMPROVEMENTS TO THE DNF_O_CMD ERROR HANDLING TO AVOID OUT-OF-MEMORY PROBLEMS Additional functional changes: - This PTF introduces the possibility to deploy up to four DNF_O_FT services to allow splitting the MSIF traffic according to specific business needs. After migrating to this PTF level, your environment is still running with one single DNF_O_FT service. If you want to use the new functionality of multiple DNF_O_FT services, you need to do a re-customisation of your installation once the migration of this PTF is complete. For further information, see "Sending and receiving business messages and transferring files" in "WebSphere BI for FN for Multiplatforms: Concepts and Components" , "Planning for customization" in "WebSphere BI for FN for Multiplatforms: Planning, Installing, and Customizing", and "Sending and receiving business messages and transferring files" and "Configuring the MSIF services" in "WebSphere BI for FN for Multiplatforms: System Administration". Documentation updates: The following manuals have been changed: - Planning, Installation, and Customization - Concepts and Components - Messages and Codes - System Administration - Application Programming Note: Documentation will be published on IBM library site two weeks after PTF availability. In case you need a draft before contact IBM support. The following modules have been changed: /dnfv311/admin/data/dnfcocdo.cli /dnfv311/admin/data/dnfcocro.cli /dnfv311/admin/data/dnfczocb.cli /dnfv311/admin/data/dnfczoch.lst /dnfv311/admin/data/dnfczocs.mq /dnfv311/admin/data/dnfczoct.cli /dnfv311/admin/data/dnfczoct.ddl /dnfv311/admin/data/dnfczors.mq /dnfv311/admin/data/DNFEFAS.xml /dnfv311/admin/data/dnfxzocs.def /dnfv311/admin/data/dnfxzors.def /dnfv311/admin/data/dnfo.properties /dnfv311/admin/data/dnfo.xml /dnfv311/run/data/dnfczocb.cli /dnfv311/run/data/dnfczoch.lst /dnfv311/run/data/dnfczoct.cli /dnfv311/run/flows/DNF_O_CMD.bar /dnfv311/run/flows/DNF_O_FT.bar /dnfv311/run/jplugin/dnfco.jar /dnfv311/run/msg/dnfcomsg.cat /dnfv311/run/msg/DNFO_Msg.properties /dnfv311/run/res/dnfcomsg.xml The following modules are new: /dnfv311/admin/data/dnfcoco1.mq /dnfv311/admin/data/dnfcoco2.mq /dnfv311/admin/data/dnfcoco3.mq /dnfv311/admin/data/dnfcocs1.mq /dnfv311/admin/data/dnfcocs2.mq /dnfv311/admin/data/dnfcocs3.mq /dnfv311/admin/data/dnfcocy1.cli /dnfv311/admin/data/dnfcocy2.cli /dnfv311/admin/data/dnfcocy3.cli /dnfv311/admin/data/dnfcoro1.mq /dnfv311/admin/data/dnfcoro2.mq /dnfv311/admin/data/dnfcoro3.mq /dnfv311/admin/data/dnfcors1.mq /dnfv311/admin/data/dnfcors2.mq /dnfv311/admin/data/dnfcors3.mq /dnfv311/admin/data/dnfczo04.ddl /dnfv311/admin/data/dnfczo2s.mq /dnfv311/admin/data/DNFEFAS1.properties /dnfv311/admin/data/DNFEFAS1.xml /dnfv311/admin/data/DNFEFAS2.properties /dnfv311/admin/data/DNFEFAS2.xml /dnfv311/admin/data/DNFEFAS3.properties /dnfv311/admin/data/DNFEFAS3.xml /dnfv311/admin/data/dnfxoco1.def /dnfv311/admin/data/dnfxoco2.def /dnfv311/admin/data/dnfxoco3.def /dnfv311/admin/data/dnfxocs1.def /dnfv311/admin/data/dnfxocs2.def /dnfv311/admin/data/dnfxocs3.def /dnfv311/admin/data/dnfxoro1.def /dnfv311/admin/data/dnfxoro2.def /dnfv311/admin/data/dnfxoro3.def /dnfv311/admin/data/dnfxors1.def /dnfv311/admin/data/dnfxors2.def /dnfv311/admin/data/dnfxors3.def /dnfv311/admin/data/dnfxzo2s.def /dnfv311/run/data/dnfcocy1.cli /dnfv311/run/data/dnfcocy2.cli /dnfv311/run/data/dnfcocy3.cli /dnfv311/run/flows/DNF_O_FT1.bar /dnfv311/run/flows/DNF_O_FT2.bar /dnfv311/run/flows/DNF_O_FT3.bar C. Planning ----------- C1. Checks to be done >>BEFORE<< installing a new PTF ----------------------------------------------------- 1. Ensure that all previously prepared deployment instructions were carried out. 2. Ensure that all previous CDD changes were implemented using the CDP. To check this, log on to AIX on the customization system as a customizer (ucust1) and enter the following command on your customization system: /dniv311/admin/bin/dnicdpst -i -cdefs where The name of the WebSphere BI for FN instance The name of the customization definitions directory as specified in the CDP ini file, for example: /var/dni_03_01/cus/defs If the response to this command indicates that a customization operation is still pending and it was carried out in: - Customization mode (dnicdp), implement the pending operation before continuing. - Migration mode (dnicdpm): - Ensure that you have not yet shared the files contained in this or any other PTF as described in section D5 step 2. - Implement the pending operation before continuing. 3. Until the migration for this PTF has been completely finished, ensure that no changes are made to the currently implemented CDD. 4. Ensure that all configuration administration changes have been deployed. To check this, enter the following commands: dnicli -s DNI_SYSADM -ou SYSOU > list -ou % -qo amorz > list -cos % -qo amorz > list -ct % -qo amorz Each list command should result in 'No [OU/COS/CT] match search criteria'. 5. Ensure that all security administration changes have been approved. To check this, enter the following commands for each OU: dnicli -s DNI_SECADM -ou > list -ro % -qo mor [only for SYSOU] > list -user % -qo mor Each list command should result in 'No roles found that match specified criteria'. C2. Prerequisite and supersede information ------------------------------------------ This PTF requires the following PTFs: - UK94072 for APAR PM82710 (MSIF 3.1.1.8, IN CASE DIRECTORY CONDITION WAS WRONG, THE TRANSFER STATUS IS STILL IN RUNNING AFTER RESTART COMMAND). - UK97565 for APAR PM93601 (Base 3.1.1.15, CIN UPDATE FOR MSIF APAR PM92781). C3. Roles involved ------------------ The activities in this PTF involve the following roles: - Installer (root) - Customizer (ucust1) - DB2 administrator (udb2adm1) - WebSphere MQ administrator (uwmqadm1) - WebSphere MB administrator (uwmba1) - First WebSphere BI for FN system configuration administrator (sa1) - Second WebSphere BI for FN system configuration administrator (sa2) D. Installation --------------- D1. Stopping all sessions and services you use ---------------------------------------------- Stop all sessions and services, for example: - Stop all applications that send requests to WebSphere BI for FN. - Log out SIPN FIN LTs. - Close MSIF SnF input and output channels. - Release SWIFTNet SnF queues. - Stop the MSIF Message Transfer service. - Stop the Enhanced InterAct service. - Close all dnicli sessions. For further information, see "Administering and operating components, sessions, and services" in "WebSphere BI for FN for Multiplatforms: System Administration". D2. Stopping all application servers ------------------------------------ NOT APPLICABLE. D3. Stopping all WebSphere BI for FN message brokers ---------------------------------------------------- Stop all WebSphere BI for FN message brokers. D4. Backing up your system -------------------------- We recommend to backup your AIX LPAR so that in case of migration issues you can revert to your previous system setup and continue to process workload. D5. Installing PTF by InstallAnywhere ------------------------------------- 1. Install this PTF using IAW based on the chapter "Installing WebSphere BI for FN" in WebSphere BI for FN for Multiplatforms Planning, Installation, and Customization, SH12-6942. Please be aware of the directory containing the installation data for this PTF has changed compared to the directory documented in this chapter, use the path Disk1/InstData/NoVM instead of Disk1/InstData/VM. 2. Ensure that the group ownership of the /dnfv311/admin directory and all of its subdirectories and files, is set to group dniadmin. To do this, enter the following command in AIX: chgrp -R dniadmin /dnfv311/admin 3. Set the group ownership of the runtime directories and its files to group dnilpp. To do this, enter the following command in AIX: chgrp -R dnilpp /dnfv311/run D6. Steps on a customization system ----------------------------------- To update your current definition directory and the customized administrative scripts, and to create deployment instructions and vehicles: 1. Log on to AIX on the customization system as a customizer (ucust1). 2. Change to the customization directory: cd 3. Run your customization profile: . ./dnicus_ 4. Start the CDP in migration mode and use the following commands to migrate customization data: dnicdpm -i > export cdd/_UK97480_temp.cdd > supplement cdd/_UK97480_temp.cdd cdd/_UK97480.cdd Edit the supplemented CDD to specify values for the new placeholders DNFvQTHFT, DNFvQTHIO, DNFvQTHTMH, DNFvQTHTML, DNFvQTHUMH. Search for each occurrence of the string value=" and specify the appropriate placeholder values. > import cdd/_UK97480.cdd > prepare This step updates the customized administrative scripts in the directory '//admin' and generates deployment data for migration of the run-time system for the following resource classes: -DB - adds column FT_SERVICE to table DNFO_FSM_STATE - adds column FT_SERVICE to table DNFO_FSM_SUBSCRIBE -MBRK - new placeholder added to DNF_O_FT.bar -MQ - add new queue 'DNIvQPFX.DNF_O_FTIO' - add new queue 'DNIvINST.DNFSYSOU.DNF_O_FTIO' -MQAUT - add authorities on DNIvMQMN.DNIvQPFX.DNF_O_FTIO for DNIvSGRP - add authorities on DNIvMQMN.DNIvINST.DNFSYSOU.DNF_O_FTIO for DNIvSGRP Deployment instructions are generated in the file '///instructions.txt'. You will need this later in the step D7. 5. Implement the customization definition data and quit the CDP session: > implement When the message "DNIZ9013I: Current Definition file already exists." is displayed enter 'y' to continue. > quit D7. Following the deployment instructions created in step D6 ------------------------------------------------------------ Follow the deployment instructions that were created in step D6. D8. Additional activities ------------------------- D8.1. DB2 related activities - - - - - - - - - - - - - - - NOT APPLICABLE. D8.2. WebSphere MB related activities - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. D8.3. WebSphere MQ related activities - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. D9. Restarting all WebSphere BI for FN message brokers ------------------------------------------------------ Restart all WebSphere BI for FN message brokers. D10. Prepare BAR file deployment ------------------------------- In this MSIF PTF the resource class MBRK has been changed as described in section 'D6. Steps on a customization system'. The CDP generates deployment data not only for BAR files affected by this MSIF PTF but for all BAR files used in the instance. If you use the BAP (dniczbap) to automatically deploy BAR files directly as described in section D11.2.2. not only the affected but all BAR files will be deployed. To avoid unnecessary deployment operations that prolong the PTF installation we recommend to follow the description in section D10.2., steps 1 - 10 and D11.2.1. D10.1. Backup the BTD repository - - - - - - - - - - - - - - - - 1. On the runtime system on which you use the BAP, log on to AIX as the WebSphere MB administrator (for example, uwmba1) and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 2. Create a backup of your BTD repository. The location of this directory depends on the version of WebSphere Message Broker you are using: - for version 6.1: $DNI_BAP_PATH/bap/$DNI_QMGR_CFG - for version 7: $DNI_BAP_PATH/bap/$DNI_I where the values of the environment variables DNI_BAP_PATH, DNI_QMGR_CFG and DNI_I correspond to the settings made in your dniprofile. For example, to create a backup of a Broker 7 BTD repository by copying the directory, enter the following commands: mkdir -p $DNI_BAP_PATH/bap/UK97480/$DNI_I cp -R $DNI_BAP_PATH/bap/$DNI_I/ $DNI_BAP_PATH/bap/UK97480/$DNI_I D10.2. Customize BAR files when using mqsideploy or the Toolkit to deploy them - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This step is different for this MSIF PTF compared to other PTFs. If you install this MSIF PTF with other PTFs and you combine this MSIF PTF readme with other PTF readmes follow the description in this MSIF PTF readme. Regardless of whether you usually deploy BAR files manually using mqsideploy or the Toolkit, or if you usually use the BAP, perform the following steps: 1. Create a copy of the deployment vehicle created in step D6.4. by the CDP for resource class MBRK: cp MBRK0000.sh MBRK0001.sh 2. Open the copy MBRK0001.sh of the deployment vehicle in an editor. 3. Replace the parameter '-deploy' with '-dir ' where represents the directory in which the BAP is to store the customized BAR files. 4. Save the changes and close the editor. 5. Ensure that you have sufficient free space in the output directory specified in step 3. To deploy all message flows requires about 30 MB of free space. 6. Run the user profile for the run-time system, for example dniprofile. 7. Run the copy MBRK0001.sh of the deployment vehicle. It generates the customized BAR files and stores them in the directory specified in step 3. If you use mqsideploy or the Toolkit to deploy broker archive (BAR) files manually, perform the following additional steps: 8. Identify the BAR files that are listed in section "B. Summary of changes" and delete all other BAR files from the output directory specified in step 3. When you merge this PTF with other PTFs check also if BAR files are listed in section "B. Summary of changes" in the readmes of these PTFs and handle those BAR files accordingly. 9. Transfer, in binary mode, the customized BAR files in the output directory to the Toolkit or to the system on which you will later issue the mqsideploy command. 10.If you will use the Toolkit to deploy the message flows, import the customized BAR files. If you use the BAP to automatically deploy BAR files you can ignore the contents of the directory specified in step 3. D11. Redeploy updated BAR files ------------------------------- Deploying the WebSphere BI for FN BAR files that are delivered in this PTF updates the message flows that run in the broker. For a list of flows contained in each BAR file, refer to "Planning execution groups" section of "Planning, Installation, and Customization". Each WebSphere BI for FN message flow has a suffix that represents its version. For example, the flow DNI_SYSADM_1141 has the version 1141. The version of a flow corresponds to the number of the PTF that most recently updated it. Refer to the header of this readme to determine the PTF number of this PTF. To deploy BAR files, you must have the access rights of the WebSphere MB administrator (uwmba1). D11.1. Deploy new message flows - - - - - - - - - - - - - - - NOT APPLICABLE D11.2. Update existing message flows - - - - - - - - - - - - - - - - - - If you use the Toolkit or the mqsideploy command already prepared the customized BAR files as described in step D10, proceed with step D11.2.1 to deploy the customized BAR files already prepared in step D10; otherwise, proceed with step D11.2.2 D11.2.1 Deploying the BAR files customized in step D10 - - - - - - - - - - - - - - - - - - - - - - - - - - - Use the Toolkit or the mqsideploy command to manually deploy the BAR files. Remove the old versions of the message flows that have been updated by the BAR files you deployed. If you neglect to do this, two different versions of the flows will run simultaneously with unpredictable results. D11.2.2 Deploying BAR files when step D10 was not performed - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Use the BAP (dniczbap) to customize and automatically deploy the BAR files: 1. Ensure that: - The configuration manager is running (applies only for Broker V6.1) - The brokers are running - No flows or execution groups are stopped. Otherwise, old flow levels might not be deleted during the BAP update operation. 2. On the runtime system where you use the BAP, log on to AIX as the WebSphere MB administrator (for example, uwmba1) and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 3. Ensure that you have at least 35 MB of free space in the current directory. 4. Issue the following command: dniczbap -cmd prepare -update new -deploy 5. Issue the following command to verify that all previous versions of the updated message flows were removed successfully: dniczbap -cmd check The result should be: DNIZ1314I: No problems detected. If you receive the message DNIZ1313E follow the instructions provided in the user response to correct the problem. D11.3. Activating WebSphere BI for FN accounting - - - - - - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. D12. Migrating configuration data --------------------------------- D12.1 Generating configuration data migration scripts - - - - - - - - - - - - - - - - - - - - - - - - - - - To prepare the migration of configuration entities: 1. On the runtime system on which the message broker runs, log on to AIX as the system configuration administrator, for example, sa1, and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 2. Create a temporary directory where dnfczmlc stores the CLI command files which will contain the configuration migration statements. 3. Switch to this directory and enter the following command: dnfczmlc.sh -i [-dual YES|NO] [-to timeout] where: -i The name of the instance. -dual YES|NO Specifies whether files are to be created for a system that uses dual authorization for SYSOU. The default is -dual YES. Specify -dual NO only if dual authorization is to be turned off for both DNI_SYSADM and DNI_SECADM in SYSOU at the time when the created files are executed. Whether dual authorization is switched on or off for other OUs is irrelevant. -to timeout The number of milliseconds that the CLI waits for a response to this command before it issues an error message. The default is 100000 (100 seconds). It must be a whole number between 20000 and 9999999. Note: This command starts a long-running task that might take several minutes to complete. Check the file dnfczmlc.log to ensure that it completed successfully. The program dnfczmlc creates the following CLI command files: If dual authorization is not used (-dual NO): 1. dnfczmlc_2_sa_ent_all.cli If dual authorization is used (-dual YES): 1. dnfczmlc_5_sa_cre_ct_com.cli 2. dnfczmlc_5_sa_cre_ct_dep.cli 3. dnfczmlc_6_sa_cre_co_com.cli 4. dnfczmlc_6_sa_cre_co_dep.cli This PTF changes the following configuration entities: - Adds the attribute 'SagSwitchMode' to CT 'DnfEfaBouParameters': add -ct DnfEfaBouParameters -attr SagSwitchMode - Adds attribute 'SagSwitchMode' to CO 'DnfEfaBouParameters' of type 'DnfEfaBouParameters' : add -ct DnfEfaBouParameters -ou DNIvOU -co DnfEfaBouParameters -attr SagSwitchMode -val Auto - Adds the attribute 'DeliveryMode' to CT 'DnfEfaFileReceiveOptionSet' and to CT 'DnfEfaDownloadOptionSet': add -ct DnfEfaFileReceiveOptionSet -attr DeliveryMode add -ct DnfEfaDownloadOptionSet -attr DeliveryMode - For each DownLoadOptionSet adds: add -ct DnfEfaDownloadOptionSet -ou DNIvOU -co -attr DeliveryMode -val Copy - For each FileReceiveOptionSet adds: add -ct DnfEfaFileReceiveOptionSet -ou DNIvOU -co -attr DeliveryMode -val Copy D12.2 Executing the migration scripts ------------------------------------- Execute the CLI command files generated in step D12.1 in the following sequence and using the following user authorization: If dual authorization was not used (-dual NO): - dnfczmlc_2_sa_ent_all.cli by any SA If dual authorization was on (-dual YES): - dnfczmlc_5_sa_cre_ct_com.cli by the first SA (sa1) - dnfczmlc_5_sa_cre_ct_dep.cli by the second SA (sa2) - dnfczmlc_6_sa_cre_co_com.cli by the first SA (sa1) - dnfczmlc_6_sa_cre_co_dep.cli by the second SA (sa2) 1. On the runtime system, log on to AIX as the indicated user and run the profile for your runtime environment by entering: . /var/dni_03_01/run/dniprofile 2. Switch to the temporary directory you created in step D12.1 and execute the generated CLI command files by entering the following command: dnicli -s -ou SYSOU -cft | tee -a UK97480_cli.log where: DNI_SYSADM for files executed by the system configuration administrators, abbreviated as SA The CLI command file name, for example dnfczmlc_5_sa_cre_ct_com.cli. D13. Updating the WebSphere BI for FN enterprise application ------------------------------------------------------------ NOT APPLICABLE. D14. Restarting all sessions and services ----------------------------------------- Restart all of the sessions and services that you use. How to do this depends on which WebSphere BI for FN features you use. For example: - Log in SIPN FIN LTs. - Subscribe MSIF to SAGs to enable file transfer and session monitoring. - Start the MSIF Message Transfer service. - Start the Enhanced InterAct service. - Acquire SWIFTNet SnF queues. - Open MSIF SnF input and output channels. - Start the applications that send requests to WebSphere BI for FN. For further information, see "Administering and operating components, sessions, and services" in "WebSphere BI for FN for Multiplatforms: System Administration". D15. Updating the Toolkit development environment ------------------------------------------------- NOT APPLICABLE. D16. Verifying your Installation -------------------------------- NOT APPLICABLE. *------------------------------------------------------------------------------* * End of Installation * *------------------------------------------------------------------------------* E. APAR details --------------- Fixes for the following APARs are contained in this PTF: PM92781 MSIF PROCESSING OF BIG FILES IN MSIF LEADS TO TIMEOUTS FOR OTHER TRANSFERS The MSIF service processes each FileAct transfer in multiple execution steps, where each step is executed in a separate transaction. Some of these transactions execute file operations that can last several minutes, especially when very large files are copied or compressed. Formerly, such long file operations can have impact on other transfers that are processed at the same time. If, for example, large files are copied or compressed, and all available MSIF treads are busy with such file operations, then messages remain or can expire in MQ queues and timeouts can occur. Now, all these file operations are separated from the other MSIF execution steps, where at most one thread executes such file operations, and at least one thread is always available for other MSIF execution steps. This design change reduces the probability of timeouts significantly. The solution for this APAR introduces two functional enhancements: - Multiple DNF_O_FT services: Formerly, MSIF has had only one transfer service DNF_O_FT that processes all FileAct and InterAct transfers. This can lead to situations when processing one transfer type impacts processing another transfer type. Now, a customer can deploy up to three additional services named DNF_O_FT1, DNF_O_FT2 and/or DNF_O_FT3. These services use separate processing resources in the broker and have separate input queues. Transfers processed by one service cannot impact a transfer processed by another service any more. - Customizable CIN input queue threshold parameters Formerly, some customization parameters to the Controlled Input Node (CIN) for service DNF_O_FT were hard coded. Now, these customization parameters can be customized by means of the customization definition document (CDD.xml). The formerly hard coded values are the default values and must not be altered unless told by IBM support. PM91756 MSIF DISABLE SAG SWITCHING WITHOUT DEACTIVATING WORKLOADBALANCING Formerly, MSIF automatically switched the SAG when the SagCommOptionSet specifies attribute group and when the number of failing auto-recovery attempts exceeds the configured maximum. Now, this can be controlled by setting a new attribute SagSwitchMode in EfaBouParameter to either 'Auto' (default) or 'Disabled'. PM84492 MSIF TEMPORARY COMMAND RESPONSE QUEUE NO LONGER AVAILABLE FOR MSIF Formerly, when the reply-to queue was no longer available at the time when the MSIF command service (DNF_O_CMD) attempted to send the response for a command, error event DNFO3801E was issued. Now, this has been changed. If the reply-to queue is no longer available at the time when the MSIF command service attempts to send to response, the response is discarded and no error event is issued. PM85697 MSIF MSIF SEND MESSAGE REQUEST REJECTED DUE TO DB2 DEADLOCK/TIMEOUT Formerly, when an error occurred during the attempt to check whether an MSIF request is authorized, the request was rejected. Now, when an error occurs during the attempt to check whether an MSIF request is authorized, the request is no longer rejected. Instead, depending on the error situation, the MSIF transfer service suspends the request or re-attempts to check whether the request is authorized. PM96617 MSIF IMPROVEMENTS TO THE DNF_O_CMD ERROR HANDLING TO AVOID OUT-OF-MEMORY PROBLEMS The MSIF DNF_O_CMD service periodically looks for transfers that are timed out. For each of these transfers the DNF_O_CMD service sends an internal MQ message to the DNF_O_FT service to further process the timed-out transfer. Formerly in case the DNF_O_CMD service finds a large number of timed-out transfers in one transaction, and with limited memory resources, this could lead to an out-of-memory problem and an abend of the DNF_O_CMD service. Now, the number of transfers that the DNF_O_CMD service processes in one single transaction is limited to the value that is configured in the configuration object DnfEfaParameters and attributes BatchSize. If this attribute is not configured, then the default value of 500 is used. F. Other changes ---------------- - Message updates: * Response messages new: DNFO0412E, DNFO3924E, DNFO3926E, DNFO3928E, DNFO3930E * Response messages updated: DNFO0400I, DNFO0401E, DNFO0402I, DNFO0405I, DNFO0406E, DNFO0407I, DNFO0408E, DNFO0420I, DNFO0421I, DNFO0423I, DNFO0424I * Event messages new: DNFO3923E, DNFO3925E, DNFO3927E, DNFO3929E * Event messages updated: DNFO2028I, DNFO2321E G. Known issues --------------- - When during a file transfer using LFT an error occurs and the file transfer is cancelled, it is possible that in some cases a temporary file in the MSIF work or transfer directories is not deleted. ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++