ESU objects and backup

[CHo]

Hi. We have applied ESUs with backups. When I go into the planner directory on the deployment server, the number of objects are different than the ones in the backup directory. For example \Planner\Package\Jd11180\include on the deployment server, has 95 objects as opposed to Planner\Package\Jd11180\Pd7333bak\include folder which has 46 objects.

Why is there a difference? Is it because the ESU will not merge all of the objects according to Breaking News doc, Package Builds after applying ESU's OTM-01-0033?

Thanks for your help.

C Ho
Intermediate Programmer/Analyst
Xe SP 15.1 AS/400 V4R3 coexistant
CO on SQL 7.0 SP2 + hotfix

 

[hotm6654]

Conceivably some of them include NER. Maybe the backup is omitting the .C
and .H files for the NER in the ESU because it is already backing it up into
the Access database and the backup spec files.

It is my understanding that the .C and .H code created from NER are always
included in the ESU directories, but it is not necessarily THE source code.
The SOURCE code for NER is actually in the Central Objects database of code
(F98741). In fact, I was told by JDE SL that sometimes they don't even ship
the right .C and .H files for NER in the ESU.






JD Nowell
OW: B7332
ES: AS400 V4R4 CO: DB2/400 SP: 11.2
Users: 250 TSE Users: 100

 

[Carl_Fisher]

Two reasons:

1) The remaining Objects are new for your installation - so do not currently
exist, therefore no backup.

2) Have you applied an ESU before across some of these Objects? ESU's are
cumulative, so only update Objects not previously updated, I assume that the
back up will only take the objects to be updated, and not all the objects
included in the ESU.




OW733.3 Xe SP 14.2
Enterprise Server - Intel NT + Oracle 8.0.6
Client - Citrix TSE + 4 NT PC's for development

 

[jenga61688]

It will only back-up the objects that it intends to change. So if you have
objects on your system that aren't any different in the ESU than they won't
touch them or save them.