============================================================================== ============================================================================== Licensed materials - Property of IBM 5724-D96 (C) Copyright IBM Corp. 2002, 2012 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 UK75850 for APAR PM51780 = Date 2012-05-31 = ============================================================================== ============================================================================== ============================================================================== Table of contents ----------------- A About this document B Summary of changes C Planning D Preparation E Activating F APAR details G Other changes A. About this document ---------------------- If you install this PTF as part of the migration from WebSphere BI for FN Version 3.1.0 to Version 3.1.1 then do not follow the steps in this readme, but those described in the Migration Information 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. The installation of this PTF is done in two phases: 1. Preparation - During this phase your system can continue to process messages as usual. 2. Activation - During this phase 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/dniv311/cus is used in examples. The deployment directory. The directory /var/dniv311/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: PM51780 MSIF WRONG STATE OF A SNF-QUEUE AFTER A BROKEN CONNECTION TO SAG PM52187 MSIF CLEANUP MUST BE ABLE TO CLEAN UP MORE THAN 100.000 TRANSFERS IN ONCE PM54682 MSIF DNFL1034E NOT WRITTEN WHEN RESPONSE RETURNED TO APPLICATION PM52837 MSIF MSIF V3.1.1 SNF SNDMSG - MWH RECORD UPDATE OF THE TIMESTAMP FIELD AFTER THE TRANSFER STATUS IS SET TO FINISHED PM57161 MSIF MWH_PD_INDICATOR FLAG IS NOT SET TO 'YES' DURING THE AUTOMATIC PM58475 MSIF MESSAGE CHUNKING IS NOT WORKING ON SYSPLEX AND SHARE QUEUE PM57987 MSIF AN AUTORECOVERY SHOULD NOT BE FAILED WITH 'THE FILE ALREADY EXISTS' PM59573 MSIF GENERATES MORE (COA-COD) REPORT MESSAGES THAN NEEDED. PM59206 MSIF COULD ONLY ACCEPT ALPHABETICAL CHARACTERS AS THE CHANNEL NAME PM57980 MSIF PDM HANDLING OF FILERECEIVEFSM HAVE A PROBLEM WHEN MULT-OUTPUTCHANNELS CONNECTING TO ONE SNF QUEUE WITH MULT-SAGS PM61908 MSIF INTRODUCE NEW AUTORECOVERY OPTIONS FOR THE MSIF TRANSFER SERVICE PM64011 MSIF APPNOTIFQUEUE IS MANDATORY TO CONFIGURE MSIF FOR USE WITH INTERACT SNF SERVICES PM63728 MSIF LFT RESPONSE COULD NOT BE CORRELATED WITH DNFO1019I ERROR Additional functional changes: - References of previous transfers will only be found when they were processed in the same OU. If no previous reference is found, the FSM will go into INVALID state. - Behavior of IA/FA on TPlist if MIMode is SWIFTNet6 is synchronized. - List command has new list option to show SnFInputTime. - Create channel command has new parameter -force. - Section added to the System Administration guide that describes what has to be planned, prepared, and performed after a SWIFTNet InterAct and FileAct SnF cold start. Documentation updates: - Planning, Installation, and Customization - Concepts and Components - Messages and Codes - System Administration - Application Programming The following modules have been changed: /dnfv311/run/data/dnfczoch.lst /dnfv311/run/data/dnfczoct.cli /dnfv311/run/data/dnfczocy.cli /dnfv311/run/jplugin/dnfco.jar /dnfv311/run/msg/dnfcomsg.cat /dnfv311/run/res/dnfcomsg.xml /dnfv311/admin/data/DNFEFAS.xml /dnfv311/admin/data/dnfcocmo.cli /dnfv311/admin/data/dnfczoct.cli /dnfv311/admin/data/dnfczodt.cli /dnfv311/admin/data/dnfczocy.cli /dnfv311/admin/data/dnfcocpy.cli /dnfv311/admin/data/dnfcocsy.cli /dnfv311/admin/data/dnfczocs.mq /dnfv311/admin/data/dnfczors.mq /dnfv311/admin/data/dnfxzocs.def /dnfv311/admin/data/dnfxzors.def /dnfv311/admin/data/dnfczoch.lst /dnfv311/run/flows/DNF_O_CMD.bar /dnfv311/run/flows/DNF_O_FT.bar The following modules are new: /dnfv311/admin/data/dnfxzo1s.def /dnfv311/admin/data/dnfczo1s.mq /dnfv311/admin/data/dnfcocry.cli C. Planning ----------- Before installing a new PTF, ensure that: - All previously prepared deployment instructions have been carried out. - All previous CDD changes have been implemented using the CDP. - 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'. - 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'. Customization changes other than those described in a PTF readme document are not allowed during PTF installation. Prerequisite and supersede information: This PTF requires the following PTFs: - UK77970 for APAR PM55951 (DNICZBAP THROWS NULLPOINTEREXCEPTION DURING RECUSTOMIZATION, Base 3.1.1.5) - UK72302 for APAR PM52045 (MSIF PROCESSING WITH AUTORECOVERY FOR OUTOFSEQUEUCE MESSAGES CAN RESULT IN DUPLICATE FILES BEING TRANSFERRED, MSIF 3.1.1.3) This PTF supersedes the following PTFs: - none Roles involved: The activities in this PTF involve the following roles: - Installer (root) - Customizer (ucust1) - WebSphere MQ administrator (uwmqadm1) - WebSphere MB administrator (uwmba1) - First WebSphere BI for FN system configuration administrator (sa1) D. Preparation -------------- D1. Installation ---------------- 1. 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. 2. Stop all WebSphere BI for FN message brokers. 3. 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. 4. Share the files in the /dnfv311/admin directory with your customization system. 5. 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 shell: chgrp -R dniadmin /dnfv311/admin 6. Share the files in the /dnfv311/run directory with your runtime systems. These files are already needed during the preparation phase and do not influence normal operation. 7. Set the group ownership of these directories and files to group dnilpp. To do this, enter the following command in AIX shell: chgrp -R dnilpp /dnfv311/run D2. 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/_UK75850.cdd > import cdd/_UK75850.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: - MQ * queue DNF_O_CMDCTRL added * alias queue DNF_O_CMDCTRL added - MQAUT * permission on queue DNF_O_CMDCTRL added * permission on alias queue DNF_O_CMDCTRL added Deployment instructions are generated in the file '///instructions.txt'. You will need this later in the 'E. Activating' section. 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 D3. 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. Check if you have enabled wildcard escaping for the 'list -ro' command and disable it temporarily. To check if you have configured an escape character enter the following commands: dnicli -s DNI_SYSADM -ou SYSOU > list -ou SYSOU -co DniSecAdm.list -attr DniEscapeCharacter -lo osv If the response is 'No OUs match search criteria.' no escape character is defined. Otherwise note the value displayed and enter the following command in the CLI session to temporarily disable the escape character: > rem -ou SYSOU -ct DniSecAdm.list -co DniSecAdm.list -attr DniEscapeCharacter Commit, approve and deploy the OU SYSOU. Close the CLI session: > .quit 3. Create a temporary directory where dnfczmlc stores the CLI command files which will contain the configuration migration statements. 4. 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 5. Enable the escape character for the 'list -ro' command if you have temporarily disabled it in step 2: dnicli -s DNI_SYSADM -ou SYSOU > add -ou SYSOU -co DniSecAdm.list -ct DniSecAdm.list -attr DniEscapeCharacter -val where is the value that was displayed in response to the list command in step 2. This PTF changes the following configuration entities: - creates CT DnfEfaRecoveryOptionSet - adds the attribute 'RTRecoveryOptionSet' to CT 'DnfEfaSagCommOptionSet' - adds the attribute 'SnFRecoveryOptionSet' to CT 'DnfEfaSagCommOptionSet' D4. Manually customize updated BAR files when not using the BAP to deploy them ------------------------------------------------------------------------------ If you use the BAP (dniczbap) to deploy the updated broker archive (BAR) files, the BAR files will be automatically customized during deployment, so you can skip this step. If you do not use the BAP to deploy the updated BAR files, which of the following procedures you must follow depends on whether there is a connection to the configuration manager: - If so, follow the procedure described in D4.1 - If not, follow the procedure described in D4.2 Note: Ensure that configuration manager is running and no flows or execution groups are stopped during the deployment of updated BAR files. Otherwise it may happen that old flow levels are not deleted during the BAP update operation (-cmd prepare -update new). To verify that the update was successful you can use the BAP list command. There should be no flows running with the same name but a different version. D4.1. Customize BAR files without connection to the configuration manager - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Carry out the following steps when there is no connection to the configuration manager, for example, because the configuration manager runs on Windows. The BAP customizes all BAR files that it processed earlier, for example, during installation of WebSphere BI for FN. You then select which files are to be updated for the current PTF. 1. On the runtime system, log on to AIX as the system configuration administrator, for example, sa1, or 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 temporary directory where dniczbap stores the customized BAR files. You will need up to 35 MB free space in this directory. 3. Issue the following command: dniczbap -cmd prepare -all -dir where represents the directory created in the previous step. Each of the customized BAR files has a name of the form: ...bar where The name of the broker to which the BAR file is to be deployed. The name of the execution group to which the BAR file is to be deployed. The name of the BAR file as provided by WebSphere BI for FN. 4. Identify the BAR files that are listed in section 'B. Summary of changes' and delete all other BAR files in the temporary output directory. 5. Transfer, in binary mode, the customized BAR files to the Toolkit or to the system on which you will issue the mqsideploy command. 6. If you want to deploy using the Toolkit, import the customized BAR files. D4.2. Customize BAR files with connection to the configuration manager - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Carry out the following steps when there is a connection to the configuration manager. The connection enables the configuration manager to automatically detect updated BAR files. 1. Ensure that the configuration manager is started. 2. On the runtime system on which the configuration manager runs, 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. Create a temporary directory where dniczbap stores the customized BAR files. You will need up to 35 MB free space in this directory. 4. Issue the following command: dniczbap -cmd prepare -update new -dir where represents the directory created in the previous step. Each of the customized BAR files has a name of the form: ...bar where The name of the broker to which the BAR file is to be deployed. The name of the execution group to which the BAR file is to be deployed. The name of the BAR file as provided by WebSphere BI for FN. *-----------------------------------------------------------------------------* * End of Preparation * *-----------------------------------------------------------------------------* E. Activating ------------- E1. 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", SH12-6943. E2. Stopping all application servers ------------------------------------ NOT APPLICABLE. E3. Stopping all WebSphere BI for FN message brokers ---------------------------------------------------- Stop all WebSphere BI for FN message brokers. E4. Sharing the runtime directory structure ------------------------------------------- 1. Share the files in the /dnfv311/run directory with the runtime systems. 2. Set the group ownership of these directories and files to group dnilpp. To do this, enter the following command in AIX shell: chgrp -R dnilpp /dnfv311/run E5. Backing up configuration and security data in image copies -------------------------------------------------------------- NOT APPLICABLE. E6. Following the deployment instructions created in step D2.4 -------------------------------------------------------------- Follow the deployment instructions that were created in step D2.4. This will update the run-time system resources. E7. Additional activities ------------------------- E7.1. DB2 related activities - - - - - - - - - - - - - - NOT APPLICABLE. E7.2. WebSphere MB related activities - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. E8. Restarting all WebSphere BI for FN message brokers ------------------------------------------------------ Restart all WebSphere BI for FN message brokers. E9. Redeploy updated BAR files ------------------------------ To customize and deploy the updated WebSphere BI for FN BAR files, you must have the access rights of the WebSphere MB administrator (uwmba1). To redeploy updated BAR files: 1. Ensure that the configuration manager is running. 2. If you already have prepared the customized BAR files as described in step D5 proceed with step E9.1; otherwise, proceed with step E9.2. Note: Ensure that configuration manager is running and no flows or execution groups are stopped during the deployment of updated BAR files. Otherwise it may happen that old flow levels are not deleted during the BAP update operation (-cmd prepare -update new). To verify that the update was successful you can use the BAP list command. There should be no flows running with the same name but a different version. E9.1. Deploying the BAR files customized in step D4 - - - - - - - - - - - - - - - - - - - - - - - - - - Use the Toolkit or the mqsideploy command to deploy the BAR files. Remove the old versions of the flows which have been updated by this PTF as otherwise two different versions of the flows are running. You can list the flows running in the broker to identify the names including their version suffix. You can also refer to the Planning, Installation, and Customization manual for a list of flows contained in each BAR file. E9.2. Updating BAR files when step D4 has not been performed - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Use these steps when your configuration manager runs on AIX and you want to deploy directly using the BAP (dniczbap). To customize and deploy the BAR files: 1. On the runtime system on which the configuration manager runs, 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. Ensure that you have sufficient free space in the current directory. To deploy all message flows requires about 35 MB of free space. 3. Issue the following command: dniczbap -cmd prepare -update new -deploy E9.3. Activating WebSphere BI for FN accounting - - - - - - - - - - - - - - - - - - - - - - - - NOT APPLICABLE. E10. Migrating configuration data --------------------------------- Execute the CLI command files generated in step D3 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) 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 D3.2 and execute the generated CLI command files by entering the following command: dnicli -s -ou SYSOU -cft | tee -a UK75850_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. E11. Updating the WebSphere BI for FN enterprise application ------------------------------------------------------------ NOT APPLICABLE. E12. Restarting all sessions and services ----------------------------------------- 1. 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", SH12-6943. 2. A subscription to receive FileAct events is needed for each SAG that the MSIF Transfer Service uses to conduct file transfers. Because one of the previous steps erased all subscriptions from the WebSphere BI for FN database, for each SAG that the MSIF Transfer Service is to use to conduct file transfers, resubscribe manually by issuing the "subscribe" command. E13. Updating the Toolkit development environment ------------------------------------------------- NOT APPLICABLE. *------------------------------------------------------------------------------* * End of Activating * *------------------------------------------------------------------------------* F. APAR details --------------- Fixes for the following APARs are contained in this PTF: PM51780 MSIF WRONG STATE OF A SNF-QUEUE AFTER A BROKEN CONNECTION TO SAG Periodically, the MSIF transfer service contacts each SAG to ensure that active SnF queue sessions and output channels sessions have not terminated unexpectedly. If a connection to an SAG is broken, then the MSIF transfer service is unable to determine the current status of active sessions on that SAG. Formerly, when the MSIF transfer service was unable to determine the current session status, it regarded the session as still active, that means that in the status command (for SnF queue sessions) and query command (for output channels) a session status was displayed as Active. Now in such an error scenario the session status is displayed as Unknown. After a session status is set to Unknown, the MSIF transfer service continues to automatically contact each SAG to check whether the session is still active or has terminated unexpectedly. If the MSIF transfer service determines that the session is still active, then it changes the status from Unknown to Active. PM52187 MSIF CLEANUP MUST BE ABLE TO CLEAN UP MORE THAN 100.000 TRANSFERS IN ONCE Formerly, when cleanup was issued and a huge amount of transfers were identified to be cleaned up, the generated request messages piled up in queue DNF_O_FTTML. Other requests processed via this queue were not handled timely any more (e.g. CLI commands like 'acquire' etc.). Now, new queue DNF_O_CMDCTRL has been introduced to handle the generated cleanup request messages separately. A user will be able to issue CLI commands, and they will be processed, while a large batch of cleanup messages is processed. PM54682 MSIF DNFO1034E NOT WRITTEN WHEN RESPONSE RETURNED TO APPLICATION MSIF sends for a send message scenario an SwInt:ExchangeRequest SNL primitive to an SAG, and the SAG returns an SwInt:ExchangeResponse SNL primitive containing a SwGbl:Status. This SwGbl:Status contains one or more SwGbl:StatusAttrubutes, and they contain one or more SwGbl:Details. Formerly, MSIF sent back in the API response of the send message scenario only the information of the SwGbl:StatusAttributes, but not the information of the SwGbl:Details. Now, MSIF sends back in the API response all details of the SAG status information. Please refer also to WebSphere BI for FN RMA APAR PM56106. PM52837 MSIF MSIF V3.1.1 SNF SNDMSG - MWH RECORD UPDATE OF THE TIMESTAMP FIELD AFTER THE TRANSFER STATUS IS SET TO FINISHED Formerly, an MWH record was created unnecessary because cleanup was done already. The MWH record update was performed only for the timestamp field. Now, an MWH record update happens only, if at least one field has changed that is different from the timestamp field. PM57161 MSIF MWH_PD_INDICATOR FLAG IS NOT SET TO 'YES' DURING THE AUTOMATIC RETRY OF MSIF PDE SEND FILE TRANSFER ERROR SITUATION Formerly, MWH_PD_INDICATOR flag was not set to 'Yes' during the automatic retry of MSIF PDE send file transfer error situation, but it was set to 'N'. Now, it is set to 'Y'. PM58475 MSIF MSIF MESSAGE CHUNKING IS NOT WORKING ON SYSPLEX AND SHARE QUEUE Formerly, MSIF LFT chunking did not work correctly with a GetFile queue defined as a shared queued in a z/OS sysplex environment. Now, this problem is solved by a new chunk assembly algorithm implemented directly in MSIF. PM57987 MSIF AN AUTORECOVERY SHOULD NOT BE FAILED WITH 'THE FILE ALREADY EXISTS' Formerly, if an SND+FILE scenario tried to send a file and the file did already exist on the SAG, the sending of the file failed and ended with an LFT error 0110 'File already exists'. Note that this is only possible in rare circumstances when a previous transfer of the file failed after the file was transferred to the SAG. Now, if the LFT error 0110 'File already exists' is encountered, an LFT retry is initiated after WBIFN tried to delete the file on the SAG. Note that LfTMaxRetryCount has to be larger than 1 in order for this to work. A new state was introduced in the SagSend FSM called 'DeletingRetry' - this state is reached when the SagSend FSM issues an LFT Delete command and waits for its completion. PM59573 MSIF MSIF GENERATES MORE (COA-COD) REPORT MESSAGES THAN NEEDED. Formerly, if the application issued a SND+FILE, SND+MSG, DL or PRVDL request and was using a MQMD report option like COA or COD it received too many report messages. The surplus messages were created because the report option was also present in the API response MQMD. Now, if an application issues such requests with MQMD report options, it only gets the requested report messages once. PM59206 MSIF MSIF COULD ONLY ACCEPT ALPHABETICAL CHARACTERS AS THE CHANNEL NAME Before MSIF executes one of the channel commands (create, delete, open, close, or query), it verifies the syntax of the specified channel name. The name of a channel must be in lower case and start with the BIC8 followed by an underscore and followed by a reference string. Formerly MSIF rejected a channel name with a BIC8 that contains digits. Now, MSIF allows channel names with all BIC8 strings. PM57980 MSIF PDM HANDLING OF FILERECEIVEFSM HAVE A PROBLEM WHEN MULT-OUTPUTCHANNELS CONNECTING TO ONE SNF QUEUE WITH MULT-SAGS Formerly, when receiving a file in SnF mode via output channel or SnF queue session, MSIF retrieved the SagMPOptionSet defined in the TransferOptionSet matching the scenario criterias (LocalDN, RemoteDN, Service, RequestType). Furthermore it retrieved the SagCommOptionSet related to that SagMPOptionSet. MSIF used both option sets to determine the parameters for fetching the file from SWIFT. Errors could happen when the SagMPOptionSet and SagCommOptionSet used to establish the SnF queue session or the output channel defined parameters different from the parameters defined in the SagMPOptionSet and SagCommOptionSet that were retrieved from the matching TransferOptionSet. Especially, an error could happen when the SnF queue session or the output channel and the SAG was switched during the handling of the file retrieval request and MSIF started the PDM handling. MSIF still tried to use the SagMPOptionSet and SagCommOptionSet from the matching TransferOptionSet. But the parameters of these option sets did not match the parameters of the SagMPOptionSet and SagCommOptionSet used to establish the new SnF queue session or output channel. Now, when receiving a file in SnF mode via output channel or SnF queue session, MSIF uses the SagMPOptionSet and the SagCommOptionSet that were used to establish the SnF queue session or the output channel to determine the parameters for fetching the file. When the SnF queue session or the output channel and the SAG switches during the handling of the file retrieval request and MSIF starts PDM handling, then MSIF uses the SagMPOptionSet and the SagCommOptionSet of the newly established SnF queue session or output channel to determine the parameters for fetching the file from SWIFT. PM63728 MSIF LFT RESPONSE COULD NOT BE CORRELATED WITH DNFO1019I ERROR Formerly, it was possible that in a multi-server environment and for an MSIF SendFile scenario the LFT response was received before the processing of the corresponding LFT request was fully completed. This caused the event DNFO1019I that indicated that the received LFT response could not be correlated to the LFT request. Now, the transaction handling of the LFT processing has been changed so that the correlation of a response to its request is always guaranteed. PM61908 MSIF INTRODUCE NEW AUTORECOVERY OPTIONS FOR THE MSIF TRANSFER SERVICE Previously, the MSIF transfer service used exactly one pair of settings for auto recovery. The attributes 'MaxAutoRecoverCount' and 'AutoRecoverInterval' in the DnfEfaSagCommOptionSet. These settings applied to all scenarios, all types of scenarios (store and forward or realtime) and to all phases of the scenarios (transfer and notification phase). The problem was that some scenarios or some phases of scenarios needed different values to let MSIF work smoothly. Now you can define different values for different scenarios and phases using a RecoveryOptionSet. The usage of this new option set is optional - if you don't change anything in your configuration, MSIF will continue to use the 'MaxAutoRecoverCount' and 'AutoRecoverInterval' in the DnfEfaSagCommOptionSet as before. PM64011 MSIF APPNOTIFQUEUE IS MANDATORY TO CONFIGURE MSIF FOR USE WITH INTERACT SNF SERVICES Formerly, the sample script provided with MSIF, dnfcocmo.cli, did not specify attribute values for QueueManager and AppNotifQueue in COs of type DnfEfaMsgReceiveOptionSet. When configuring MSIF for use with WebSphere BI for FN RM application (RMA) or any other InterAct SnF service, the attribute AppNotifQueue for the DnfEfaMsgReceiveOptionSet is mandatory. If the AppNotifQueue is not specified, RMA will not be able to receive RM authorisations properly. Now this has been corrected in script dnfcocmo.cli and System Administration guide. G. Other changes ---------------- - Now, it is assured that references of previous transfers will only be found if they were processed in the same OU. If no previous reference is found, the FSM will go into INVALID state. - Now, the behavior of IA/FA on TPlist if MIMode is SWIFTNet6 is synchronized. - Now, the list command has been enhanced by the new list option 'i' to display the SnFInputTime. For further information, see "MSIF transfer service operation and administration commands" in "WebSphere BI for FN for Multiplatforms: System Administration". - Now, create channel command has been extended by parameter -force. - Now, a section has been added to the "WebSphere BI for FN for Multiplatforms: System Administration". that describes what has to be planned, prepared, and performed after a SWIFTNet InterAct and FileAct SnF cold start. - Formerly, in the system OU DNFSYSOU the value 'Yes' was configured for attribute DoCmdAudit in CO DnfEfaBouParameters. Now it is set to 'No'. - Formerly, the file dnfcocsy.cli contained a comment that attribute TimeToRecover of CT DnfEfaSagCommOptionSet applies only to InterAct scenarios. Now this comment has been removed. - Message updates: * Changed event messages: DNFO9010E, DNFO9030E, DNFO9031E DNFO1711I, DNFO1714E, DNFO1715E, DNFO1716E, DNFO1717E, DNFO1777E DNFO1048E becomes DNFO1048I * New event messages: DNFO1724I, DNFO3922E * Changed response messages: DNFO0408E, DNFO0543E * New response messages: DNFO0226I ++++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End +++ End ++++