Current Posting: 11/07/2005 **** ALWAYS REVIEW INSTALLATION INSTRUCTIONS FOR POSSIBLE UPDATES *** The @SCNNNNN APAR fixes and WAF530x patch libraries are provided by IBM as a means of delivering the latest fixes to V5R3 Content Manager for iSeries WAF feature customers. This document includes the installation instructions for the files from our FTP site. The latest copy of this document is available as 'readme.txt' at FTP site: 'ftp.software.ibm.com/as400/products/contentmanager/v530/waf'. This document is also available as member NEWFUNCTN in file README, once the fix packages are restored to your system. You can use the DSPPFM or WRKMBRPDM commands to view or print that member. Information on the APAR fixes included in these fix packages can also be viewed once you have restored them to your system. See the installation instructions below for more information. If you have difficulties using FTP to receive these fixes or require further assistance, please contact Content Manager for iSeries Support through your normal support channels. ********************************************************************* Contents: * Installation Instructions * TCP/IP Interface for IWPM/NT * Viewing WAF Documents with Form Overlays in CM Client * Want to Stay Informed? ********************************************************************* * Installation Instructions: ********************************************************************* NOTE: These packages also contains APAR fixes. For information on the APAR fixes included in the WAF530x fix packages, once you have restored them to your AS/400, refer to the FIXESx (ex: FIXESA) member in the README file. To view or print that file, use the DSPPFM FILE(WAF530A/README) MBR(FIXESA) command, for example. WAF530A.BIN -- This contains the current version of WAF530A patch library which should be restored to your AS/400. WAF530B.BIN -- This contains the current version of WAF530B patch library which should be restored to your AS/400 on TOP of the WAF530A fixes. INSTALLING WAF530A: Before FTP'ing this file to your AS/400, use the CRTSAVF command to create a save file named WAF530A. Then, you can either use AS/400 FTP to GET the file directly from the FTP, or retrieve it to a workstation file then from DOS use PUT to transfer it onto the AS/400 save file. REMEMBER TO USE BINARY TRANSFER MODE! Once the WAF530A savf exists on your AS/400, use the RSTLIB command to restore the WAF530A library from the WAF530A save file onto your AS400: RSTLIB SAVLIB(WAF530A) DEV(*SAVF) SAVF(xxx/WAF530A) + MBROPT(*ALL) ALWOBJDIF(*ALL) INSTALLING WAF530B: Before FTP'ing this file to your AS/400, use the CRTSAVF command to create a save file named WAF530B. Then, you can either use AS/400 FTP to GET the file directly from the FTP, or retrieve it to a workstation file then from DOS use PUT to transfer it onto the AS/400 save file. REMEMBER TO USE BINARY TRANSFER MODE! Once the WAF530B savf exists on your AS/400, use the RSTLIB command to restore the WAF530B library from the WAF530B save file onto your AS400: RSTLIB SAVLIB(WAF530B) DEV(*SAVF) SAVF(xxx/WAF530B) + MBROPT(*ALL) ALWOBJDIF(*ALL) CREATING A PATCH LIBRARY: In order to save a library list entry or two, it is suggested that you create a library such as WAF530LIB, and then copy the contents of WAF530A to this library, followed by the fixes from WAF530B. Any future fix libraries, such as WAF530C, will be copied on top of A and B, so that objects with the same name are replaced with more recent versions. Then, add the WAF530LIB to the top of the image users' library list. POST INSTALLATION INSTRUCTIONS: Each time you install this library you will need to: 1) Use the GRTOBJAUT command to grant authority to your CM/400 users to library WAF530LIB and objects contained within 2) Remove any patch libraries (@SCxxxxx) for APAR's which have fixes provided in this fix package. See the appropriate FIXESx members referenced above. Reference these steps each time for special instructions which may be required. ********************************************************************* * TCP/IP Interface for IWPM/NT, IWPM/2000 and IWPM/XP: ********************************************************************* For customers that require the user of keystroke buffering or desire a native TCP/IP interface, you can choose "TCP/IP" inside IWPM's EHLLAPI Session settings. All users need to make sure that the version of the EKDTIR01 program that is highest in their library list is the version that matches the emulator setting inside IWPM's EHLLAPI "Session settings". The module EKDTIR01XX, currently included in the xxxLIB library of your WAF environment, is the program to be used for the TCP/IP command interface. It is used when the EHLLAPI emulator is set to TCPIP. The 'XX' at the end of the name should be removed if you need this version of the program. We suggest that you rename the program to EKDTIR01 and keep it in your WAF530LIB library, so that it will be in the highest image library in the users' library list. There are 2 versions of the EKDTIR01 program: EKDTIR01 *PGM EKDLIB CBL IWP/DOS command interface EKDTIR01XX *PGM EKDLIB CBLLE TCP/IP interface If you have chosen "IBM Personal Communications" for your Emulator in IWPM/NT or IWPM/2000's EHLLAPI "Session settings", then you would not need to do any program renaming, because the IWP/DOS version of EKDTIR01 is shipped as the default. If, on the other hand, you have chosen "TCP/IP" for your Emulator in IWPM/NT or IWPM/2000's EHLLAPI "Session settings", then you would copy the EKDTIR01XX program in the xxxLIB library to the WAF530LIB library and rename it to EKDTIR01. This way it is in the library highest in the users' library list. Please note that TCP/IP has the following limitations: ------------------------------------------------------ 1. Session A must be the session used to send images to IWPM. 2. Multiple 5250 sessions are not supported. 3. Attempting to "enable" the AS/400 portion of the code without installing the workstation code will result in a hang condition on the workstation. 4. Scan functions require the user to press the Enter key in order to cause the IWPM/NT scan dialog to appear. Once started, the scan interface should be the same as with EHLLAPI. 5. Capture functions require the user to press the Enter key twice in the 5250 session in order to cause the document in the IWPM/NT window to be stored. 6. Annotation and modify work about the same as with EHLLAPI. If problems persist, the user may enable a debug feature that will cause the AS/400 server code to log information. If the CM/400 SupportLine personnel instruct you to do this, you would: 1. From the user's interactive 5250 session, create a data area as follows: CRTDTAARA DTAARA(QTEMP/EKDTCPDBG) TYPE(*CHAR) LEN(10) 2. Recreate the failing scenario. 3. Print the data in QTEMP/QVISNDRCV using CPYF to *PRINT Please note that IWPM/NT and IWPM/2000 fixpacks are available at the following web site: ftp://ftp.software.ibm.com/ps/products/imageplus/fixes You should check this site regularly to make sure you're operating with the most recent fixes and enhancements. ********************************************************************** * Viewing WAF Documents with Form Overlays in the CM Client ********************************************************************** Steps need to be taken in order for the CM Client to be able to view WAF documents which contain overlays (PTOCA architecture documents), as well as IWPM-created annotations, masks and highlights. The CM Client will be unable to hide these annotations made on a WAF document because they are part of the architected data stream and not a "layer" to be peeled off as they are in the native CM Client documents. You will need to implement the code as follows: On the PC side: --------------- 1. From an MS-DOS prompt on your Windows desktop, type FRNWVIEW from your C:\FRNROOT directory. This will start the viewer component of the CM Client. 2. Select "Options", then "File Handlers". 3. Now use the Remove button for the two existing file handlers (this will cause them to move their entries to the window on the left). 4. Then, use the "Browse" option to locate FRNROOT\IBMBR.ENG, and select "Open". This file handler will be added to the window on the left. 5. Now add each file handler, with the "IBM Engine" first, then the Pixel engine, then the Mastersoft engine. As you add each file handler, it will appear in the window on the right. On the AS/400 side: ------------------- 1. Sign on as the CM Administrator. 2. Through the key field profile maintenance screen, define an 8-byte key field named VIFORM with a description of VIFORM. 3. Define an index class named VIFORM. The first key field should be VIFORM. Any of the other key fields can be used to help identify or manage the form overlays. Note that the form names (VIFORM) are expected to be unique, but this is not enforced. 4. After a form has been created in WAF, the actual form document (in folder EKDFORMS) should be imported into CM through the CM Client. When you do this, be sure to specify a Data Format of MODCA_FO (FO stands for Form Overlay). 5. Then, index the imported document into the VIFORM index class, identifying the overlay with the 8 character form name. This name must be in all upper case (even if the form itself in EKDFORMS is lower case). Note: The CM version of the form (in index class VIFORM) will not display independently but is used during display of other documents which include the form. When a document is displayed that contains a form overlay, the viewer engine (IBMBR.ENG) will send a message back to the CM Client. The CM Client will call SimLibOpenObjectByUniqueName, which is an existing CM API that has been added to CM/400. This API will search for the form name, open it, and return the content to the CM Client, which will pass it on to the viewer engine. ********************************************************************** * Want to Stay Informed?!?!?!?! ********************************************************************** In an effort to be proactive for our customers, we are maintaining an e-mail distribution list of our customers that we can use to notify you of service-related information, e.g., when new fixes are available. If you are interested in having someone in your organization on this list, send an e-mail with the address AND THE RELEASE LEVEL OF CM/400 you are using to cm400spt@us.ibm.com. END Last updated: 11/07/05 ****************** End of data ****************************************