Further to my previous posting on this topic:

I haven’t seen the source code of the T24 Updater so I do not know
EXACTLY how it operates step by step, but to the best of my
understanding I think my comments below explain why the problem you
describe occurs and the steps to be taken to avoid the problem. I
would welcome any further comments correcting me if my technical
understanding is wrong or offering further technical insight into the
process.

The unwisely named program EX (for ‘execute’, not ‘exit’) runs
everything else in Globus. It calls the subroutine OVERLAY.EX which is
very much at the centre of the Globus core system. It initialises
common areas when starting Globus.

Occasionally, the T24 Updater needs to update these core routines or
even itself.

In such situations the updater must be run from a temporary run area,
to make changes to the permanent t24lib and t24bin directories (the
core object code libraries) within the bnk.run directory.

The steps to do this based on the Temenos T24 Updater troubleshooting
document are given below. I have used an example based on a Windows
platform as the Temenos document assumes Unix but the steps are the
same.

Situation A – Only applicable if the update contains modified
R10_EB_Upgrade_X or R10_EB_Updates_X component

1)      Create run1 directory with bnk.run. This will be your temporary run
environment from which to perform the update with the permanent
bnk.run as target.
2)      Copy t24lib and t24bin from bnk.run to %HOME%\run1 directory.
3)      Copy R10_EB_Upgrade_X_WIN64 or R10_EB_Updates_X_WIN64 to a
temporary directory.
4)      Extract these tar files in the temporary directory.
5)      Delete the eb_upgrade and eb_updates directories from %HOME%
\run1\t24lib and %HOME%/run1/t24bin directories.
6)      Copy t24bin from R10_EB_Updates_X_WIN64 to %HOME%\run1\t24bin
\eb_updates.
7)      Copy t24lib from R10_EB_Updates_X_WIN64 to %HOME%\run1\t24lib
\eb_updates.
8)      Copy t24bin from R10_EB_Upgrade_X_WIN64, to %HOME%\run1\t24bin
\eb_upgrade.
9)      Copy t24lib from R10_EB_Upgrade_X_WIN64, to %HOME%\run1\t24bin
\eb_upgrade.

The temporary run area now contains the latest object code for the
updater itself.

10)     Modify the JBASE_PATH and JBCOBJECTLIST variables in remote.cmd to
point to $HOME\run1\t24bin and $HOME\run1\t24lib respectively.
11)     Set TEMP.RELEASE in SYSTEM file to point to %HOME%.
12)     Place downloaded zip file of updates inside the %HOME%\updater
\updates directory
13)     Uncomment the lines in %HOME%\updater\config\updater.xml:
<service name="T24" pathType="EXEC" updateType="AUTO">
   <path>[T24_HOME]/t24bin/eb_updatesrun/T24Version</path>
   <installpath>[T24_HOME]</installpath>
   <installprogram>[T24_HOME]/t24bin/eb_updatesrun/
T24.UPDATE.INSTALLER</installprogram>
</service>

14)     Run updater.bat
15)     Set SYSTEM > TEMP.RELEASE back to point back to its original
location
16)     Delete %HOME%\run1 directory

Situation B – The updater does not contain a modification to the
updater components themselves.

As above but without steps 3-9.

1)      Create run1 directory with bnk.run. This will be your temporary run
environment from which to perform the update with the permanent
bnk.run as target.
2)      Copy t24lib and t24bin from bnk.run to %HOME%\run1 directory.
3)      Modify the JBASE_PATH and JBCOBJECTLIST variables in remote.cmd to
point to $HOME\run1\t24bin and $HOME\run1\t24lib respectively.
4)      Set TEMP.RELEASE in SYSTEM file to point to %HOME%.
5)      Place downloaded zip file of updates inside the %HOME%\updater
\updates directory
6)      Uncomment the lines in %HOME%\updater\config\updater.xml:
<service name="T24" pathType="EXEC" updateType="AUTO">
   <path>[T24_HOME]/t24bin/eb_updatesrun/T24Version</path>
   <installpath>[T24_HOME]</installpath>
   <installprogram>[T24_HOME]/t24bin/eb_updatesrun/
T24.UPDATE.INSTALLER</installprogram>
</service>

7)      Run updater.bat
8)      Set SYSTEM > TEMP.RELEASE back to point back to its original
location
9)      Delete %HOME%\run1 directory

All cases:

1- Log off and on again to pick up on your re-catalogued object code.
2- Restart the TSM, then run the T24.UPDATES service to update the
SPF>SYSTEM record T24.UPDATES field.
3- Check the COMO file for the update for any errors:

Example (no problems in this one):
    UPD.R10_MD_ModelBank_3
001 COMO UPD.R10_MD_ModelBank_3 established 11:15:12  19 JUL 2011
002 [11:15:13]_k tar -xf \bnk\bnk.run\updater\updates\tmp
\R10_MD_ModelBank_3_WIN64.tar
003
004
005                               T24.UPDATE.RELEASE
006                               ==================
007
008
009           Current Release        R10.000
010           Installing Update      R10_MD_ModelBank_3
011
012
013           Component bins and libs will be replaced
014
015
016 Removing old t24bin\md_modelbank directory at 11:15:13
017 [11:15:13]_k del /s /q t24bin\md_modelbank
018 Finished removing old t24bin\md_modelbank directory at 11:15:13
019 Removing old t24lib\md_modelbank directory at 11:15:13
020 [11:15:13]_k del /s /q t24lib\md_modelbank
021 Finished removing old t24lib\md_modelbank directory at 11:15:13
022 Copying new t24bin  md_modelbank
023 [11:15:13]XCOPY R10_MD_ModelBank_3_WIN64\t24bin\md_modelbank .
\t24bin\md_modelbank /Y /Q /S /I
024 Copied new t24bin.
025 Copying new t24lib md_modelbank
026 [11:15:15]XCOPY R10_MD_ModelBank_3_WIN64\t24lib\md_modelbank .
\t24lib\md_modelbank /Y /Q /S /I
027 Copied new t24lib.
028
029  No Records selected
030
031
032
033 Already released data items are
034 F.VERSION>MD.DEAL,GTINVPRO
035 Success:Update R10_MD_ModelBank_3, Successfully copied the
libraries and binaries.
036 COMO completed 11:15:15  19 JUL 2011

4 - Authorise any records brought in by the update.
5 - If you are using the tcserver, restart that as well.




On Jul 27, 11:16 am, Phil Knight <[email protected]> wrote:
> You need to create a temporay bnk.run environment and modify the
> SYSTEM>TEMP.RELEASE pointer and JBCOBJECTLIST and JBC_PATH environment
> variables during the update.
>
> Get the document 'Troubleshooting in T24Updater tool' from Temenos
> Helpdesk and refer to the section 'Precautionary Steps to avoid above
> mentioned errors:' for details.
>
> Phil
>
> On Jul 27, 3:35 am, andibaso <[email protected]> wrote:
>
>
>
> > Hi Pat,
>
> > I already set JBCOBJECTLIST.
> > jsh t24r10 ~ -->echo %JBCOBJECTLIST%
> > C:\Temenos\R10\bnk\bnk.run\lib;C:\Temenos\R10\bnk\bnk.run\t24lib.
>
> > VK, I agree with you, this is happen only for
> > R10_EB_API_9_WIN32_VC80.tar. After running updater, there are no
> > library definition in t24lib/eb_api.
> > After manual copy libdef.def from R10_EB_API_2_WIN32_VC80.tar, 'jshow -
> > a' can list all subroutine, but i can not call any subroutine inside
> > eb_api\lib0.dll through basic program. I think jshow only read this
> > library definition, it is not read shared library like 'dependency
> > walker'. With dependency walker, i can see JBC_OVERLAY_2EEX in eb_api
> > \lib0.dll.
>
> > I have R10_EB_API_2_WIN32_VC80.tar in an older update package and
> > update process is successfully with this package.
> > I should waiting for technical from chennai, he will arrive this
> > weekend.
>
> > Thanks all for your reply.
>
> > On Jul 26, 1:52 pm, VK <[email protected]> wrote:
>
> > > Hi,
> > > if you don't have the object of OVERLAY.EX any longer and EX still
> > > calls it, the update is broken. I think you need to write to helpdesk.
>
> > > VK
>
> > > On Jul 25, 1:32 pm, andibaso <[email protected]> wrote:
>
> > > > Hi VK,
> > > > Thanks for your respond.
> > > > jshow -c OVERLAY.EX didn't display anything.
>
> > > > I can not find OVERLAY_2EEX.obj.  When I compare it with Model Bank
> > > > before updating(or another dev environment), there are
> > > > OVERLAY_2EEX.obj under bnk.run\t24lib\eb_api\objdir directory. This
> > > > file deleted when i applied update R10_EB_API_9_WIN32_VC80.tar.
> > > > R10_EB_API_9_WIN32_VC80.tar doesn't contain *.obj file.
>
> > > > This is como output :
>
> > > > Removing old t24bin\eb_api directory at 20:04:43
> > > > [20:04:43]ÿk del /s /q t24bin\eb_api
> > > > Finished removing old t24bin\eb_api directory at 20:04:43
> > > > Removing old t24lib\eb_api directory at 20:04:43
> > > > [20:04:43]ÿk del /s /q t24lib\eb_api
> > > > Finished removing old t24lib\eb_api directory at 20:04:44
> > > > Copying new t24bin  eb_api
> > > > [20:04:44]XCOPY R10_EB_API_9_WIN32_VC80\t24bin\eb_api .\t24bin\eb_api /
> > > > Y /Q /S /I
> > > > Copied new t24bin.
> > > > Copying new t24lib eb_api
> > > > [20:04:46]XCOPY R10_EB_API_9_WIN32_VC80\t24lib\eb_api .\t24lib\eb_api /
> > > > Y /Q /S /I
> > > > Copied new t24lib.
>
> > > > I don't think i have mixed x86 object with x64 object, because i
> > > > download all update  using my own system definition from tcsp
> > > > websites. I disabled UAC in my computer and t24r10 is administrator
> > > > member. I wonder maybe there are a way to create file *.obj in objdir
> > > > directory.
>
> > > > Thanks- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -

-- 
Please read the posting guidelines at: 
http://groups.google.com/group/jBASE/web/Posting%20Guidelines

IMPORTANT: Type T24: at the start of the subject line for questions specific to 
Globus/T24

To post, send email to [email protected]
To unsubscribe, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/jBASE?hl=en

Reply via email to