Closed GoogleCodeExporter closed 9 years ago
Object (CLAS & INTF) Connector will auto fix type-pools implicit declaration
within
sections (public, protected or private).
This will generare on-line adaptation of component. This on-line adaption might
generate short dump : LOAD_PROGRAM_CLASS_MISMATCH
because the adapted component is currently in use. Restarting program should
correct
the problem (no new short dump).
Original comment by taryck%b...@gtempaccount.com
on 6 May 2010 at 10:15
For exception clas editorder is not repected
in source system :
CONSTANTS BAL_LOG TYPE SOTR_CONC VALUE . "#EC NOTEXT
CONSTANTS ZAPLINK_CX TYPE SOTR_CONC VALUE . "#EC NOTEXT
CONSTANTS SYSTEM_ERROR TYPE SOTR_CONC VALUE . "#EC NOTEXT
in target system :
CONSTANTS BAL_LOG TYPE SOTR_CONC VALUE . "#EC NOTEXT
CONSTANTS SYSTEM_ERROR TYPE SOTR_CONC VALUE . "#EC NOTEXT
CONSTANTS ZAPLINK_CX TYPE SOTR_CONC VALUE . "#EC NOTEXT
Original comment by taryck%b...@gtempaccount.com
on 6 May 2010 at 12:53
For type and attributes definition beware of the position of the dot :
TYPES tt_tables TYPE SORTED TABLE OF dd26e WITH UNIQUE KEY tabpos.
will become
TYPES tt_tables TYPE SORTED TABLE OF dd26e WITH UNIQUE KEY tabpos .
after importing (adding a space at the end)
Fixed changing every '.' at the end with ' .' because with condense after ' .'
will
become ' .'
Original comment by taryck%b...@gtempaccount.com
on 6 May 2010 at 2:58
In source
TYPE TT_KEYS...
In target
TYPE:
TT_KEYS ...
Original comment by taryck%b...@gtempaccount.com
on 6 May 2010 at 3:51
Section slight differences Fixed using FUNCTION 'SEO_CLASS_GENERATE_SECTIONS'
Both :
- 'WITH UNIQUE KEY tabpos.' => 'WITH UNIQUE KEY tabpos .'
- 'TYPE TT_KEYS' => 'TYPE: <crlf> TT_KEYS'
Original comment by taryck%b...@gtempaccount.com
on 6 May 2010 at 4:21
Added also SEO_INTERFACE_GENERATE_SECTION for interface
Original comment by taryck%b...@gtempaccount.com
on 7 May 2010 at 2:31
Partial RollBack with this changeset :
https://code.google.com/p/zaplink/source/detail?r=8825b2b553e1ef71bdd70a972d0217
bc604fc493
Problem in comment 3 was corrected by substitution of '.' with ' .' but it's
meaning
less with use of FUNCTION 'SEO_CLASS_GENERATE_SECTIONS' describe in comment 5.
Substitution has been removed but intrudice new code_signature that are in
changeset
:
https://code.google.com/p/zaplink/source/detail?r=d0ebfc430bfc064209ebea7d279403
b19362147c
Original comment by taryck%b...@gtempaccount.com
on 20 May 2010 at 2:58
Original issue reported on code.google.com by
taryck%b...@gtempaccount.com
on 6 May 2010 at 8:19