D
dbeavon
Guest
I have a LONGCHAR that disappears (becomes null) when passed into a procedure. See below. Anyone have any idea why the LONGCHAR is fine on one side of the procedure call and becomes blank on the other? /* FILE Send.p */ DEFINE TEMP-TABLE TT_Markup XML-NODE-NAME "Markup" FIELD ManualDisplayOrder AS INTEGER INIT 1 XML-NODE-TYPE "ATTRIBUTE". DEFINE DATASET DS_Root XML-NODE-NAME "Root" FOR TT_Markup. DATASET DS_Root:EMPTY-DATASET(). /* Write empty dataset clob */ DEFINE VARIABLE v_Clob AS LONGCHAR NO-UNDO INIT ?. DATASET DS_Root:WRITE-XML ("LONGCHAR", v_Clob, TRUE). COPY-LOB v_Clob TO FILE "_before.xml". /* GO FOR IT */ LOG-MANAGER:WRITE-MESSAGE("{&FILE-NAME} {&LINE-NUMBER} RUN " ). DEFINE VARIABLE v_Error AS CHARACTER NO-UNDO. RUN aaa/ClobTest/Receive.p ( v_Clob, OUTPUT v_Error). LOG-MANAGER:WRITE-MESSAGE("{&FILE-NAME} {&LINE-NUMBER} DONE " ). /* DONE */ MESSAGE "Error was: " v_Error. /* FILE Receive.p */ DEFINE INPUT PARAMETER p_ClobSerializerData AS LONGCHAR NO-UNDO. DEFINE OUTPUT PARAMETER p_Error AS CHARACTER NO-UNDO. p_Error = "{&FILE-NAME}: Unexpected Error. ". /* COPY-LOB p_ClobSerializerData TO FILE "_after.xml". */ IF p_ClobSerializerData = ? THEN DO: LOG-MANAGER:WRITE-MESSAGE("{&FILE-NAME} {&LINE-NUMBER} Bad " ). p_Error = "Invalid clob data.". RETURN. END. LOG-MANAGER:WRITE-MESSAGE("{&FILE-NAME} {&LINE-NUMBER} GOOD " ). p_Error = "". Basically we get an error message that we shouldn't be getting. Here is the process that sends the data: Here is the one that should be receiving it:
Continue reading...
Continue reading...