Update scenario on OS/2 client platform

This section describes the necessary steps to update the code of the TME 10 Netfinity Server V4.0 from any prior modification level to the latest one. Only update from level 2 to 3 has been tested, and while updates from other level have not been verified, it is applicable.

Limitation

  • On preparation site the latest modification level has to be installed

    • How to perform the update on OS/2 client

    On preparation site, where you have already installed the latest service level, create a profiles. To write this profile, from SYSVIEW2 directory run the command

    dir /s /f

    redirecting the output in a file with the extension dir. Delete from this list the configuration file as written in the READ.ME file released with the refresh 3(under CLIENT_2 directory) This is the list of the file:

    PFALIST.DAT
    NVDM.CFG
    FNDLOG
    DSKCAM.INI
    KARAT.INI
    FNDSHARE.INI
    FNDSWOBJ.INI
    FNDSWINV
    FNDTKINV
    SWPRO\NVDMUPD.*
    WORK\*.*
    SERVICE\*.*
    REPOS\*.*
    BACKUP\*.*
    BIN\xxxxxxx.ini (xx are random numbers)
    BIN\NETDRVR.INI
    BIN\DCAF.INI
    BIN\SVSHAPP.INI
    BIN\SVCMGR.INI
    BIN\ALERTS.LOG
    BIN\SECIN.INI
    BIN\SECOUT.INI
    BIN\MACTIONS.INI
    BIN\PROFILES.INI
    BIN\ALACTION.INI
    BIN\IBMAVSP.LOG
    BIN\CUMULLOG.LOG
    BIN\PROFILE.PRF
    BIN\CSSETUP.CMD
    BIN\CIDPREP.LOG
    BIN\MONCRITF.INI
    BIN\SERMODEM.DAT
    BIN\SERCALL.DAT
    BIN\SINVGUI.INI
    BIN\DEFAULT.SID
    BIN\ADAPTER.BAG
    BIN\SYSINFO.HST
    BIN\SYSINFO.RPT
    BIN\MONSCH.INI
    BIN\MONTHR.INI
    BIN\MONGUI.INI
    BIN\PROFILE.DAT
    BIN\MONDATA.INI
    CFGS\CFGS.INI
    CFGS\SVSERV00.INI
    CFGS\DEFAULT.CSP
    CFGS\CSPRFS
    UICFG\FNDPULL.CLI
    \ETC\GLB_OBJ.TXT
    \ETC\GLB_SITE.TXT
    \LS\CONF\I4LS.INI
    \LS\CONF\NODELOCK
    \LS\CONF\I4CONMGR.LOG

    Then write the rest of the file following the example below.

    GLOBAL NAME: NFS.REF.4.0.3
    DESCRIPTION: NetFinity Server CLient OS/2
    CHANGE FILE TYPE: GEN
    COMPRESSION TYPE: LZW
    DEFAULT TOKEN: TargetDir=D:çSYSVIEW2
    OBJECT: SOURCE
    NAME: D:çSYSVIEW2çCOMMCLI.PKG
    TARGET NAME: $(TargetDir)çCOMMCLI.PKG
    TYPE: FILE
    ACTION: COPY
    INCLUDE SUBDIRS: NO
    OBJECT: SOURCE
    NAME: D:çSYSVIEW2çCONFIG.PKG
    TARGET NAME: $(TargetDir)çCONFIG.PKG
    TYPE: FILE
    ACTION: COPY
    INCLUDE SUBDIRS: NO
    OBJECT: SOURCE
    NAME: D:çSYSVIEW2çDOC.PKG
    TARGET NAME: $(TargetDir)çDOC.PKG
    TYPE: FILE
    ACTION: COPY
    INCLUDE SUBDIRS: NO
    OBJECT: SOURCE
    NAME: D:çSYSVIEW2çEPFIHLB.PKG
    TARGET NAME: $(TargetDir)çEPIFIHLB.PKG
    TYPE: FILE
    ACTION: COPY
    INCLUDE SUBDIRS: NO

    The file CREPRO.EXE included in the UPDV403.ZIP file and released with this document will allow you to write this profile. Run it in this way:

    crepro outfile "product directory"

    where outfile is the file previously generated by dir /s /f

    After you have prepared this profile, check if the connection with the server is up. From any command prompt on preparation site, run the command:

    nvdm start

    to start the Software Distribution Agent on preparation site. To catalogue the profile, run the command:

    nvdm bld profile

    To see if the profile have been catalogued correctly, from any command prompt on the server type:

    nvdm ls "global name"

    Where global name is in GLOBAL NAME section of the profile. After that, you can perform from the server the upgrade of the code at the service level 3 in activate area.

    nvdm inst "global_name" -w "workstation name" -n -vs -f

    Where workstation name

    is the name of the client you want to upgrade (i.e., nvdm lstg from the server). Then run the activate to install the product from the service area to the activate area.

    nvdm act -w "workstation name"-f