IBM Support

II05440: INFORMATION APAR ON LOTUS 1-2-3/M MAINTENANCE PROCEDURES.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as documentation error.

Error description

  • SERVICE PROCESS FOR LOTUS 123M
    ------------------------------
    Beginning with release 1.2.0 of Lotus 1-2-3/M for VM, the
    "VMFMERGE" process is to be used for applying service (PTFs).
    This Information APAR explains how to do this, in a detailed
    step by step manner.
    
    If your installation of Lotus 1-2-3/M has not had any service
    applied to it yet, the first PTF you will need to order is PTF
    UN57300 (for Lotus 1-2-3/M release 1.2.0), or PTF UN57301 (for
    Lotus 1-2-3/M release 1.2.1), for APAR PN52824.  The reason is
    explained later on in this document.
    .
    In order to apply service, you must have write access to the
    Lotus 1-2-3/M installation disk.  In general, after applying
    service using "VMFMERGE" and copying the serviced files to the
    installation disk, the Lotus 1-2-3/M installation process will
    have to be re-executed.  The original product tape is not
    needed when re-installing Lotus 1-2-3/M to activate the
    serviced code.  Since this is a re-installation, all of the
    questions that the installation process asked during the
    initial installation will have to be re-answered.
    .
    You may be familiar with VMFMERGE already if you have applied
    service to VM products such as VTAM, NETVIEW or AS. Some other
    VM products are using another newer service process called
    VM/SES. VMFMERGE is not like VM/SES.
    .
    Lotus 1-2-3/M Service Process overview
    -----------------------------
    Service for Lotus 1-2-3/M will arrive on a tape.  The tape will
    contain consist of one or more files plus a Service Control
    File ("SCF") for each PTF.  Each SCF will contain details such
    as the PTF number, APAR(s) fixed, and file(s) to be replaced.
    .
    The contents of the tape are loaded, using VMFPLC2, to a disk
    called the "Delta" disk.
    .
    The "apply list" is updated to list the PTF(s) to be applied.
    .
    VMFMERGE is run to check that any prerequisite or co-requisite
    PTF(s) are available, to place files onto the "Merge" disk, and
    then update the control files.
    .
    After VMFMERGE completes successfully, you must copy the files
    from the Merge disk to the product installation disk, and then
    run the Lotus 1-2-3/M installation procedure (I5713AGL) to
    regenerate all Lotus 1-2-3/M executable code.
    .
    Lotus 1-2-3/M Service Process details
    --------------------------------------
    The VMFMERGE service process requires several disks, files,
    and programs.  These are listed below, with explanations in the
    following paragraphs.
    .
    Disk                        Description
    ----  ---------------------------------------------------------
    "A"   the Installation disk (used to build executable code).
          The UserId applying service must access this disk in
          write mode as its "A" disk. It does not have to be at its
          "191" disk address.
          The recommended minimum size is 50 3390 cylinders
          formatted at 4096 blocksize.
    .
    1A1   the Delta disk (receives service from tape).
          This must be the 1A1 disk address.
          The recommended access mode is "G".
          The recommended minimum size is 10 3390 cylinders
          formatted at 4096 blocksize.
    .
    1A2   the Merge disk (contains merged service from VMFMERGE).
          This must be the 1A2 disk address.
          The recommended access mode is "E".
          The recommended minimum size is 10 3390 cylinders
          formatted at 4096 blocksize.
    .
    1A3   This disk is not used by the Lotus 1-2-3/M service
          process, however VMFMERGE requires it.
          This must be the 1A3 disk address.
          No access mode is needed.
          The recommended minimum size is 1 3390 cylinders
          formatted at 4096 blocksize.
    .
    348   the VMFMERGE control file disk.
          This must be the 348 disk address.
          The recommended access mode is "F".
          The recommended minimum size is 1 3390 cylinders
          formatted at 4096 blocksize.
    .
    types of files     disk                  description
    -----------------  ----- -------------------------------------
    5713AGLF MESSAGES   348  contains Lotus 1-2-3/M message texts
    .
    5713AGLF VMFPARM    348  Product Parameter file
    .
    5713AGLF VMFMGLOG   1A2  VMFMERGE history file
    .
    5713AGLF APPLIST    1A1  list of PTF(s) to apply
    .
    5713AGLF EXCLIST    1A1  list of PTF(s) to not apply
    .
    *        SCF        1A1  Service Control Files (with each PTF)
    .
    *        ttt#####   1A1  code service files for each PTF,
                             in VMFMERGE name format where "ttt"
                             represents the destination filetype,
                             and "#####" is the number of the  PTF.
    
    programs used               description
    -------------  ---------------------------------------
    VMFPLC2        loads service files from tape to disk
    .
    VMFMERGE       copies service to the merge disk, reconciling
                   prerequisites and corequisites, and moving files
                   to the Merge disk.
    .
    I5713AGL       Lotus 1-2-3/M (re-)installation program
    .
    The first two files are available from IBM by ordering PTF
    UN57300 (for Lotus 1-2-3/M release 1.2.0), or PTF UN57301 (for
    Lotus 1-2-3/M release 1.2.1), for APAR PN52824.  When you
    receive them, they will be named "5713AGLF MSG#####" and
    "5713AGLF VMP#####". Rename them to "5713AGLF MESSAGES" and
    "5713AGLF VMFPARM" respectively, and place them on the VMFMERGE
    control file disk.  The VMFPARM file specifies what disks
    contain what files, and uses the default minidisk numbers (191,
    1A1, 1A2, 1A3) as used in this document.  You may use any disk
    addresses you want to by updating the VMFPARM file.
    .
    When service arrives on a tape, it will include the updated
    files plus a Service Control File ("SCF") for each PTF.  All
    the code service files on the tape will have filetypes with the
    standard format of the first three characters representing the
    destination filetype, and the next five characters are the PTF
    number. For example:
           ACCESS   TXT12384  --  for text files
           STARTAS  EXC12390  --  for exec files
           L123JPN  RII12372  --  for ri (resource) files
    .
    The contents of the tape are loaded onto the Delta (1A1) disk
    using VMFPLC2 load.  The Delta disk is used to store all Lotus
    1-2-3/M service, even that which has been superseded.
    .
    If VMFMERGE hasn't been used for Lotus 1-2-3/M yet, then you
    must create three files before running VMFMERGE:  the apply
    list, the exclude list, and the merge log.  Comments can be
    included in any of these files by placing an asterisk (*) in
    the first column of a line.
    
    .
    The apply list ("5713AGLF APPLIST") lists all PTFs to be
    applied.  This file must be stored on the Delta (1A1) disk.
    .
    The Exclude list ("5713AGLF EXCLIST") contains a list of PTFs
    not to apply.  If IBM does not inform you of any PTFs to put in
    this file, you must still create the file, with the first
    column of the first line being just an asterisk. The exclude
    list must also reside on the Delta (1A1) disk.
    .
    The last file you must create is the Merge log ("5713AGLF
    VMFMGLOG").  Create the file with the first column of the first
    line being just an asterisk.  VMFMERGE maintains this log of
    changes which have been merged, superseded, or both.  This file
    must be reside the Merge disk (1A2).
    .
    Once you have created these three files, you are ready to apply
    service to Lotus 1-2-3/M.
    .
    Lotus 1-2-3/M service process, step by step
    --------------------------------------------
    1.  Ensure the environment is initialized (see above).
    2.  Load the service files you have received onto the delta
        disk.
    3.  Modify the apply ("5713AGLF APPLIST") and exclude ("5713AGLF
        "EXCLIST") lists so that they include the PTFs you wish to
        apply (or not apply).
    4.  Run VMFMERGE as follows:
             VMFMERGE 5713AGLF PTFLIST 5713AGLF HIST
        If any prerequisite or corequisite PTFs are missing, the
        program will inform you.  Obtain the necessary PTFs and
        rerun VMFMERGE.
    5.  Access the Merge disk.  Copy all files there to the Lotus
        1-2-3/M installation disk, using the command:
              COPYFILE * * E = = A (OLDDATE REPLACE
        assuming "E" is the merge disk as specified above, and "A"
        is the installation disk.
    6.  Release all disks except the installation disk and
        your CMS system disks.
    7.  Run the Lotus 1-2-3/M installation procedure, using the
        command:
             I5713AGL RESTART
        "RESTART" tells the program to skip the step that loads
        Lotus 1-2-3/M files from tape to disk, and proceed
        directly to building the Lotus 1-2-3/M programs. See the
        Lotus 1-2-3/M program directory for a full explanation of
        this procedure.
    .
    ADDITIONAL SEARCH KEYWORDS:
    LOTUS 123M L123 L123M R120 R121 5713AGL00
    

Local fix

Problem summary

  •  same as above.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II05440

  • Reported component name

    PA LIB INFO ITE

  • Reported component ID

    INFOPALIB

  • Reported release

    001

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1991-10-02

  • Closed date

    1995-05-24

  • Last modified date

    1995-05-24

  • 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":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"001"}]

Document Information

Modified date:
13 December 2020