DaveBarber
Active Member
I have an issue with a business function header file being overwritten during the package build process. I wonder if anyone can help?
I have a function called N5555256 (NER). It has a data structure called D5555256I. When it was created this structure originally looked like this:
/*********************************************************************
* TYPEDEF for Data Structure
* Template Name: LMS - Get Callout Config and Submit
* Template ID: D5555256I
* Generated: Thu Sep 18 10:25:29 2008
*
* DO NOT EDIT THE FOLLOWING TYPEDEF
*
*********************************************************************/
#ifndef DATASTRUCTURE_D5555256I
#define DATASTRUCTURE_D5555256I
typedef struct tagDSD5555256I
{
char szXMLWorkItemType[3];
char szXMLWorkItemSubType[11];
char szXMLOutboundMessage[2049];
MATH_NUMERIC mnUniqueKeyIDInternal;
char cCallingMode;
} DSD5555256I , *PDSD5555256I , *LPDSD5555256I;
#define IDERRszXMLWorkItemType_1 1L
#define IDERRszXMLWorkItemSubType_2 2L
#define IDERRszXMLOutboundMessage_4 4L
#define IDERRmnUniqueKeyIDInternal_5 5L
#define IDERRcCallingMode_6 6L
#endif
Notice that szXMLOutboundMessage = [2049]. This was the length of the data item when the data structure was created.
Since then I have changed the length of this data item to 16384. Here is the updated definition:
/*********************************************************************
* TYPEDEF for Data Structure
* Template Name: LMS - Get Callout Config and Submit
* Template ID: D5555256I
* Generated: Fri Sep 19 09:27:25 2008
*
* DO NOT EDIT THE FOLLOWING TYPEDEF
*
*********************************************************************/
#ifndef DATASTRUCTURE_D5555256I
#define DATASTRUCTURE_D5555256I
typedef struct tagDSD5555256I
{
char szXMLWorkItemType[3];
char szXMLWorkItemSubType[11];
char szXMLOutboundMessage[16385];
MATH_NUMERIC mnUniqueKeyIDInternal;
char cCallingMode;
} DSD5555256I , *PDSD5555256I , *LPDSD5555256I;
#define IDERRszXMLWorkItemType_1 1L
#define IDERRszXMLWorkItemSubType_2 2L
#define IDERRszXMLOutboundMessage_4 4L
#define IDERRmnUniqueKeyIDInternal_5 5L
#define IDERRcCallingMode_6 6L
#endif
This definition was changed locally on my fat client and checked in successfully. The check in location on the dep server is updated with the correct definition in the include directory.
I promoted the project to 26 and the include directory on the dep server in PY is also correct and reflects the include in DV and on my fat client.
When I created both an update and full package I am finding that the .h file in the include directory in the package folder is created with the old definition as below:
/*********************************************************************
* TYPEDEF for Data Structure
* Template Name: LMS - Get Callout Config and Submit
* Template ID: D5555256I
* Generated: Thu Sep 18 10:25:29 2008
*
* DO NOT EDIT THE FOLLOWING TYPEDEF
*
*********************************************************************/
#ifndef DATASTRUCTURE_D5555256I
#define DATASTRUCTURE_D5555256I
typedef struct tagDSD5555256I
{
char szXMLWorkItemType[3];
char szXMLWorkItemSubType[11];
char szXMLOutboundMessage[2049];
MATH_NUMERIC mnUniqueKeyIDInternal;
char cCallingMode;
} DSD5555256I , *PDSD5555256I , *LPDSD5555256I;
#define IDERRszXMLWorkItemType_1 1L
#define IDERRszXMLWorkItemSubType_2 2L
#define IDERRszXMLOutboundMessage_4 4L
#define IDERRmnUniqueKeyIDInternal_5 5L
#define IDERRcCallingMode_6 6L
#endif
My understanding has always been that the package build process creates the package dirs for the path code under the \PY7333\PACKAGE\PYFnnnnnn (where nn is package name). In this folder the include dir is created and then the .h file is copied in from the py7333/include and then the functions and built in the busbuild of the package build process.
I cannot find any reference to this legacy definition of the .h file on the dep server, so where is it coming from and how is it being created and overwriting my valid checked in definition?
Any help would be greatly appreciated.
thanks
Dave
JDE OW XE SP22 on Oracle
I have a function called N5555256 (NER). It has a data structure called D5555256I. When it was created this structure originally looked like this:
/*********************************************************************
* TYPEDEF for Data Structure
* Template Name: LMS - Get Callout Config and Submit
* Template ID: D5555256I
* Generated: Thu Sep 18 10:25:29 2008
*
* DO NOT EDIT THE FOLLOWING TYPEDEF
*
*********************************************************************/
#ifndef DATASTRUCTURE_D5555256I
#define DATASTRUCTURE_D5555256I
typedef struct tagDSD5555256I
{
char szXMLWorkItemType[3];
char szXMLWorkItemSubType[11];
char szXMLOutboundMessage[2049];
MATH_NUMERIC mnUniqueKeyIDInternal;
char cCallingMode;
} DSD5555256I , *PDSD5555256I , *LPDSD5555256I;
#define IDERRszXMLWorkItemType_1 1L
#define IDERRszXMLWorkItemSubType_2 2L
#define IDERRszXMLOutboundMessage_4 4L
#define IDERRmnUniqueKeyIDInternal_5 5L
#define IDERRcCallingMode_6 6L
#endif
Notice that szXMLOutboundMessage = [2049]. This was the length of the data item when the data structure was created.
Since then I have changed the length of this data item to 16384. Here is the updated definition:
/*********************************************************************
* TYPEDEF for Data Structure
* Template Name: LMS - Get Callout Config and Submit
* Template ID: D5555256I
* Generated: Fri Sep 19 09:27:25 2008
*
* DO NOT EDIT THE FOLLOWING TYPEDEF
*
*********************************************************************/
#ifndef DATASTRUCTURE_D5555256I
#define DATASTRUCTURE_D5555256I
typedef struct tagDSD5555256I
{
char szXMLWorkItemType[3];
char szXMLWorkItemSubType[11];
char szXMLOutboundMessage[16385];
MATH_NUMERIC mnUniqueKeyIDInternal;
char cCallingMode;
} DSD5555256I , *PDSD5555256I , *LPDSD5555256I;
#define IDERRszXMLWorkItemType_1 1L
#define IDERRszXMLWorkItemSubType_2 2L
#define IDERRszXMLOutboundMessage_4 4L
#define IDERRmnUniqueKeyIDInternal_5 5L
#define IDERRcCallingMode_6 6L
#endif
This definition was changed locally on my fat client and checked in successfully. The check in location on the dep server is updated with the correct definition in the include directory.
I promoted the project to 26 and the include directory on the dep server in PY is also correct and reflects the include in DV and on my fat client.
When I created both an update and full package I am finding that the .h file in the include directory in the package folder is created with the old definition as below:
/*********************************************************************
* TYPEDEF for Data Structure
* Template Name: LMS - Get Callout Config and Submit
* Template ID: D5555256I
* Generated: Thu Sep 18 10:25:29 2008
*
* DO NOT EDIT THE FOLLOWING TYPEDEF
*
*********************************************************************/
#ifndef DATASTRUCTURE_D5555256I
#define DATASTRUCTURE_D5555256I
typedef struct tagDSD5555256I
{
char szXMLWorkItemType[3];
char szXMLWorkItemSubType[11];
char szXMLOutboundMessage[2049];
MATH_NUMERIC mnUniqueKeyIDInternal;
char cCallingMode;
} DSD5555256I , *PDSD5555256I , *LPDSD5555256I;
#define IDERRszXMLWorkItemType_1 1L
#define IDERRszXMLWorkItemSubType_2 2L
#define IDERRszXMLOutboundMessage_4 4L
#define IDERRmnUniqueKeyIDInternal_5 5L
#define IDERRcCallingMode_6 6L
#endif
My understanding has always been that the package build process creates the package dirs for the path code under the \PY7333\PACKAGE\PYFnnnnnn (where nn is package name). In this folder the include dir is created and then the .h file is copied in from the py7333/include and then the functions and built in the busbuild of the package build process.
I cannot find any reference to this legacy definition of the .h file on the dep server, so where is it coming from and how is it being created and overwriting my valid checked in definition?
Any help would be greatly appreciated.
thanks
Dave
JDE OW XE SP22 on Oracle