Versions - How does it work ? Corrupted ?

Hi List,

Specific Versions (Corruption)

We have been experiencing this very often. When jobs are submitted to the
server, they just end up in 'E' - version specific. What we would normally
do is copy the version to a new name and delete the old one and it works
fine from then on until it gets 'corrupted' again. It keeps on happening and
we are spending much time in doing this and caused delays in our operation
cycle.

How do versions get corrupted when it was running fine a couple of minutes
ago ? We did not terminate any jobs. We notice that each time after the UBE
completes, the last modified date of the version is updated. Is this how it
behaves ? Does anyone has documentation on what actually happens when the
users clicks 'OK' to submit, server or local - what specs are updated, how
does the deployment server come into the picture,if at all (since last
modified date is updated) ??? And we do not need to deploy versions to the
server unless it's being called by another UBE, isn't it ?


Versions Hung at server

We have jobs submitted to the server is 'S' status for a long time, there is
actually a process stuck at the server. We normally wait for 10-15 mins or
so and finally kill at OS level. Why does this happen so often - couple of
times a day for different UBEs ? We just refreshed our server specs 2 days
ago. We would normally refresh the server specs on a monthly basis.

Noticed that there are some files with userid in the
/home/oneworld/b732/PRODB732/spec directory. Do we need to occassionally
delete these off ? Are these the temp files when versions spec are updated
to the server ? Does refreshing the server specs help in version corruptions
?? We do not re-install clients but rather we do it via workstation
packages.


Changing data selection of existing versions

What is happening to us right now is also this - when I check-out a version
and change the data selection on my workstation and subsequently check-in,
all other users do not see the change - it just didn't JITI again. This
happens for existing versions. Right now we are taking all the trouble to
ensure each time we run a job that the data selection is in sync across all
clients for critical jobs - sales update, etc...


FRW versions

We customise our own financial reports using the FRW. We have the template
done by an outsourced programmer and our users are just changing the
versions but the format / layout can be very different from the template.
It's not just font or text change - columns / rows as well.

Does this pose any problem ? I'd think versions are for different set of
data selection / processing option. How are they actually link and when does
it happen - at runtime, load template first, then ....etc??

We are having most problems here as UBEs done using FRW can be in 'P' until
'security error' and no one can sign on and everyone is frozen until the
process is killed. Some days they work fine but not always. They run fine
locally but a Balance sheet may take up to 3 hours.

Any special consideration / issues relating to FRW ?


Thanks for reading !

Regards

Sook Fun
HP 9000 / Oracle / OW B 732.2 SP 12.2 - Fat clients

Sook Fun,
Check out your JDE.ini file and change the "Specs to Server=Y" to
"Specs to Server=N" for your user population. The only people that
should have this setting set to Y is the admin machine or developers.
This will help eliminate data corruption.
Also, you can refresh the specs again by first object transferring
your UBE from your CRP environment to your PROD environment and then
creating an update package with the template of the UBE. This should
refresh the server specs for all users without causing you to have to
"recreate" or make a new version copy. Hope this helps.
Lisa Stinebuck

Lisa,

Do you mean the 'InstallSpecs=y' in the Network Queue Settings? What are the
components that are in this specs ? ie . data selection & proc opt or
layout. Believe this to be version specs and not template.

Our users change at runtime the data selection ie. batch no. ....Does this
mean this solution is not workable in our environment?

I'm not too sure if I understand fully about the way the server specs is
refreshed as suggested but so far the Tamftp after building a full package
worked well for us. It's normally version / template problems on the server
and running the same UBE on individual workstation is fine.

Maybe you can explain more on object transfer from CRP to PROD and is the
update package a full package ? Sounds a little like the full package &
TAMFTP. If this is so, a temporary solution is to create a new version and
life goes on even though it may be a nuisance because TAMFTP takes time and
we may not always have the latest full package to refresh the server there
and then.

Any suggestion to avoid spec corruption in any form is greatly appreciated !

Thnks & rgds

Sook Fun

SF,

What version of OneWorld are you on?


>From: sf_woo <[email protected]>
>Reply-To: [email protected]
>To: [email protected]
>Subject: RE: Versions - How does it work ? Corrupted ? ~~1203:1308
>Date: Fri, 17 Nov 2000 01:21:21 -0800 (PST)
>
>Lisa,
>
>Do you mean the 'InstallSpecs=y' in the Network Queue Settings? What are
>the
>components that are in this specs ? ie . data selection & proc opt or
>layout. Believe this to be version specs and not template.
>
>Our users change at runtime the data selection ie. batch no. ....Does this
>mean this solution is not workable in our environment?
>
>I'm not too sure if I understand fully about the way the server specs is
>refreshed as suggested but so far the Tamftp after building a full package
>worked well for us. It's normally version / template problems on the server
>and running the same UBE on individual workstation is fine.
>
>Maybe you can explain more on object transfer from CRP to PROD and is the
>update package a full package ? Sounds a little like the full package &
>TAMFTP. If this is so, a temporary solution is to create a new version and
>life goes on even though it may be a nuisance because TAMFTP takes time and
>we may not always have the latest full package to refresh the server there
>and then.
>
>Any suggestion to avoid spec corruption in any form is greatly appreciated
>!
>
>Thnks & rgds
>
>Sook Fun
>
>
>
>
>
>--------------------------
>To view this thread, visit the JDEList forum at:
>http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=1308
>*************************************************************
>This is the JDEList One World / XE Mailing List.
>Archives and information on how to SUBSCRIBE, and
>UNSUBSCRIBE can be found at http://www.JDELIST.com
>*************************************************************
>

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Share information about yourself, create your own public profile at
http://profiles.msn.com.

B732.2 sp 12.2

Sook Fun,
The package is a Server Package that has the template and versions
in it.
Lisa Stinebuck