IBM Support

II09291: WAF R310 INFO APAR FOR PSP TYPE INFO: INSTALLATION TIPS, ETC. 573322800 R100 IMAGEPLUS FESN0902816 0902816 INFORMATION

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • INTRAN

Error description

  • This APAR is intended to be used as an informational APAR for
    migration and installation tips related to ImagePlus WAF R310.
    It contains general hints and tips re: the product known as
    V3R1 WAF, or to RETAIN as: 573322800 r100. WAF R310 is supported
    on OS/400 R230, R305, R310, R320, R360, R370 and R410
    ..... updated: 10/02/97 .....
    NOTE: V2R4 WAF went out of support on November 14, 1996
    .
    WAF V3R1 is compatible with OS/400 V2R3, V3R0M5, V3R1,
    V3R2, V3R6, V3R7 and V4R1.  WAF PTF SH12078 is required for
    compatibility with OS/400 V3R2, V3R6, V3R7 and V4R1.
    .
    **NOTE: this contains separate sections for
       WAF V3R1 Installation and Migration - Please
       be careful to reference the proper sections
    .
    BEFORE YOU INSTALL:
    Hints and Tips for new WAF installations:
    1) The installation process requires all of the product
       tapes and the PTF tape received in your shipment.
    2) The latest PTF for WAF V3R1 is SH12078 and is shipped
       automatically with the product for all orders placed
       after May 17, 1996.  Orders for WAF V3R1 placed prior
       to this date were shipped with PTF WAF310-1.  SH12078 is
       cumulative, so it should be applied instead of WAF310-1.
    3) Step-by-step instructions for installing this product
       can be found in the IBM ImagePlus Workfolder Application
       Facility Version 3 Release 1 for OS/400: Planning and
       Installation Guide, which is automatically shipped with
       this product.
    4) If message CPF0817 ("Decimal variable too small to
       hold results") is issued from program EKDINSTP, the
       installation will need to be restarted using the following
       circumvention to bypass this error:
    .
       Before restarting installation, issue the following two
       commands:
    .
          STRDBG EKDIAM2924/EKDINSTP UPDPROD(*YES)
          ADDBKP 71800 ('&disk')
    .
       Now restart the installation.  When the breakpoint is
       encountered, press F10 to access a command line, and
       issue the command below, exactly as written:
    .
          CHGPGMVAR PGMVAR('&disk' ()) VALUE('00099999')
    .
       and press Enter.
       Press F12 to return to the debug panel; press Enter to
       continue processing.
    .
    Installation Notes Specific to OS/400 V3R6 or higher:
    1) The WAF team recommends that you ensure all products (fax
       solutions, custom solutions, etc.) related to your
       ImagePlus solution are supported on the AS/400 V3R6 or
       higher system before installing.
    2) The WAF V3R1 product and its PTFs are not built on an
       AS/400 RISC system.  This means an object code conversion
       must occur for the objects on these tapes to be utilized
       on OS/400 V3R6 or higher.  Reference your AS/400
       publications in regards to object code conversion for
       AS/400 applications, as there are various methods
       for performing this task.
    3) To assist in your planning effort, we are providing some
       performance information gathered during our own test efforts.
       The WAF team chose to convert objects upon restore to the
       system.  Your actual install time may vary due to differences
       in system configuration and utilization.
       -- Installation of WAF V3R1
          - 9406 Model 510 Feature Code 2144
          - 16514 MB DASD / 320 MB Memory
          - 3.5 hours
       -- Installation of WAF V3R1 PTF SH12078
          - 9406 Model 510 Feature Code 2144
          - 16514 MB DASD / 320 MB Memory
          - 1 hour
       -- Installation of WAF V3R1 and PTF SH12078
          - Model 400 Feature Code 2132
          - 12.38 G DASD / 163 MB Memory
          - 6.5 hours
    .
    BEFORE YOU MIGRATE:
    Hints and Tips for existing WAF customers that are migrating:
    1) Estimated time for migration from WAF V2R4 to WAF V3R1 is
       30 minutes.
    2) Step-by-step instructions for migrating this product can
       be found in the IBM ImagePlus Workfolder Application
       Facility Version 3 Release 1 for OS/400: Planning and
       Installation Guide, which is automatically shipped with
       the product.
    3) You are required to migrate from Workfolder Application
       Facility/400 Version 2 Release 4 at PTF level SH12025 or
       SH12076.  To determine the level of WAF on your AS/400
       perform:
    .
          DSPDTAARA ekdlib/EKDVERSION
    .
       where ekdlib is the name of your WAF program library.
    4) The migration process requires only a portion of the
       product tapes (for example, two of the three 6250 BPI
       tapes) received in your shipment.
    5) The migration process may or may not require the PTF
       tape received in your shipment.  If you are migrating
       from WAF V2R4 PTF SH12025, you are required to install
       WAF V3R1 PTF SH12078.  If you are migrating from WAF
       V2R4 PTF SH12076, you are not required to install WAF
       V3R1 PTF SH12078, but you are required to run two extra
       commands in place of installing this PTF (described later).
    6) Before beginning migration check for the existance of
       these objects and source code:
    .
       Using the WRKOBJ command check for these objects:
       -- Object EKDDNPT, in library ekdlibtxt, of type *FILE
       -- Object EKDDNPT, in library ekdlibtxt, of type *PNLGRP
    .
       Using the WRKMBRPDM command check for this source member:
       -- Member EKDDNPT in file QPNLSRC, in library ekdlibtxt
    .
       where ekdlibtxt is the name of your WAF text library.
    .
       These objects would have been added to your system if you
       followed the "Additional Installation Requirements for the
       3489 Enhancement" and "Installing Source" sections
       during your previous PTF installation.  These objects
       are required for migration.  If they do not exist,
       you need to create them before beginning migration.
       Use the appropriate command listed below to create the
       object or objects you are missing:
    .
          CRTDSPF FILE(ekdlibtxt/EKDDNPT)
          CRTDUPOBJ OBJ(EKD200H) FROMLIB(ekdlibtxt)
             OBJTYPE(*PNLGRP) TOLIB(ekdlibtxt) NEWOBJ(EKDDNPT)
          CPYSRCF FROMFILE(ekdlibtxt/QPNLSRC)
             TOFILE(ekdlibtxt/QPNLSRC) FROMMBR(EKDLOCKH)
             TOMBR(EKDDNPT)
    .
       where ekdlibtxt is the name of your WAF text library.
       During migration, WAF will replace the objects with the
       correct version of the objects.
    7) Ensure there are no WAF libraries appearing in any portion
       of any active job's library list.  For example, no WAF
       background processes can be active.  Use the DSPLIBL
       command to display your library list.  If it is necessary
       to access the system portion of the library list, you can
       use the WRKSYSVAL command and reference 2 system values:
             QSYSLIBL
        and  QUSRLIBL
    8) If after beginning migration, the process fails with error
       EKD-8391, cancel out of the migration program.  Check the
       report which is generated and placed on your spool file.
       The report should list only non-WAF objects found during
       migration.  If any WAF objects (usually prefixed by EKD)
       are found, they can be ignored as migration will ensure
       you get the correct copy.  Any non-WAF or custom objects
       found should be saved or moved to a non-WAF library.
       Restart the migration from the EKDIAM menu, choosing to
       continue migration at the point where you canceled, when
       prompted for that input.  After successful migration,
       restore the non-WAF objects to the appropriate library
       if they have been deleted by the migration process.
       It is recommended that custom objects be placed in non-WAF
       libraries, otherwise you may be replacing a WAF product
       object.  File cabinet display files should remain in your
       WAF Text library.
    9) If message CPF0817 ("Decimal variable too small to hold
       results") is issued from program EKDINSTP, the migration
       will need to be restarted using the following circumvention
       to bypass this error:
    .
       Before restarting migration, issue the following commands:
    .
          STRDBG EKDIAM2924/EKDINSTP UPDPROD(*YES)
          ADDBKP 71800 ('&disk')
    .
       Now restart the migration.  When the breakpoint is
       encountered, press F10 to access a command line
       and issue the following command, exactly as written:
    .
          CHGPGMVAR PGMVAR('&disk' ()) VALUE('00099999')
    .
       and press Enter.
       Press F12 to return to the debug panel; press Enter to
       continue processing.
    10)If you are migrating from WAF V2R4 PTF SH12076, you are
       required to run two sets of extra commands as part of your
       migration, one prior to migration and one after migration.
    .
       Issue the following three commands just prior to
       beginning migration:
    .
          ADDLIBLE ekdlib
          EKDUPDTDA1 ekdlibfil
          RMVLIBLE ekdlib
    .
         where ekdlib is the name of your WAF Program library and
         ekdlibfil is the name of your WAF File library.  When
         the command completes successfully, you are ready to begin
         migration.
    .
         Do the following 3 steps at a command line JUST AFTER
         COMPLETING THE MIGRATION:
    .
           ADDLIBLE ekdlib
           EKDUPDTA2 ekdlibfil
           RMVLIBLE ekdlib
    .
         where ekdlib is the name of your WAF Program library and
         ekdlibfil is the name of your WAF file library.  When
         the command completes successfully your migration is
         complete.
    .
    Migration Notes Specific to customers with Multiple Environments
    ----------------------------------------------------------------
      If you have multiple environments which do NOT share any of
      the WAF libraries, you can simply migrate all environments
      as defined above.
    .
      However, if libraries ARE shared between the environments you
      will need to plan as follows:
      1) When performing the 2nd and all subsequent migrations
         select to migrate only the ekdlibfil and ekdlibtxt
         libraries (which are required) and any other unique
         (non-shared) library on panel EKDIAM01.  So, do not list
         any other libraries which have already been migrated.
      2) Ensure the EKDVERSION data area in each of these libraries
         reflects PTF level SH12025.  To view the data area enter:
    .
           DSPDTAARA xxxxxxxxx/EDKVERSION
    .
         If the data area does NOT reflect SH12025 it should be
         changed using the following command:
    .
           CHGDTAARA DTAARA(xxxxxxxxx/EKDVERSION (104 10))
             VALUE(SH12025)
    
    .
         where 'xxxxxxxxx' represents one of the libraries you
         will be migrating.
    .
      3) If you had to change a data area because it reflected
         PTF SH12076 prior to the migration, you will need to
         change it after the migration as follows:
    .
           CHGDTAARA DTAARA(xxxxxxxxx/EKDVERSION (104 10))
             VALUE (SH12078)
    .
         where 'xxxxxxxxx' represents the library name
    .
    Migration Notes Specific to OS/400 V3R6 or higher:
    1) The WAF team recommends that you ensure all products (fax
       solutions, custom solutions, etc.) related to your ImagePlus
       solution are supported on the AS/400 V3R6 or higher system
       before installing.
    2) AS/400 provides a tool at various operating system levels
       called Upgrade Assistant.  This tool allows customers to
       analyze applications prior to migrating to an OS/400 V3R6 or
       higher system.  If you use this tool to produce a report
       about the WAF application, you will receive warning messages
       for many of the WAF programs written in C.  The
       programs are listed because they were created using a
       compiler which is no longer supported.  This will NOT
       cause any problems for you in migrating or running the WAF
       code on an OS/400 V3R6 or higher system.
    3) The WAF V3R1 product and its PTFs are not built on an AS/400
       RISC system.  This means an object code conversion must occur
       for the objects on these tapes to be utilized on OS/400 V3R6
       or higher.  For this reason, we recommend you migrate from
       WAF V2R4 to WAF V3R1 and apply any PTFs prior to migrating
       the product to OS/400 V3R6 or higher.  This will decrease
       your object code conversion time later.  Reference your
       AS/400 publications in regards to object code conversion for
       AS/400 applications, as there are various methods
       for performing this task.
    .
    SERVICE TIPS FOR ALL CUSTOMERS:
       Electronic ordering of PTFs is in place to allow customers
       to request shipment of a WAF V3R1 PTF.  ECS ordering is set
       up to only place the PTF order for the customer; due to the
       large size of our PTFs, they will not be distributed online.
    .
       To order a specific WAF PTF using ECS, in a manner similar
       to that used for ordering OS/400 PTFs, issue the following
       command:
    .
          SNDPTFORD PTFID(SHxxxxx) DELIVERY(*ANY)
    .
       If you do not know the latest WAF PTF and simply want to
       ensure you get the latest WAF V3R1 cumulative PTF, use:
    .
          SNDPTFORD PTFID(SH99310) DELIVERY(*ANY)
    .
    IBM SERVICE REPS:
    Refer to Informational APAR II09507 for service
    information and tips regarding WAF.
    

Local fix

  • informational apar info infoapar v3r1m0 v3r1 msgcpf0817
    

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II09291

  • Reported component name

    PA LIB INFO ITE

  • Reported component ID

    INFOPALIB

  • Reported release

    001

  • Status

    INTRAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    1996-02-23

  • Closed date

  • Last modified date

    1997-10-03

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG32M","label":"APARs - VSE\/ESA environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]

Document Information

Modified date:
03 October 1997