Dave:
Thank you for the tip. This helps a great deal.
Dan
>>> [EMAIL PROTECTED] 6/1/2004 2:13:47 PM >>> To shorthand your path definitions, try using reference declarations. For example: DECLARE XTAG_1 REFERENCE TO InputBody.OCF_SAP.IC.PMX.BOMMAT03; SET "OutputRoot"."XML"."IDOC"."E2STZUM"."E2STZUTH"."SEGNAM"= TRIM ("XTAG_1"."OFF_SAP.IFC.BOMMAT03.E2STZUM"."OFF_SAP.IFC.BOMMAT03.E2SZUTH"."OFF_SAP.IFF.BOMMAT03.E2SZUTH"."E1SZUTH_E1SZUTH"); As far as internal subroutines, look at the documentation for procedures and functions. Although the capabilities under v2.1 are limited, for example, you can not reference OutputRoot, InputBody, etc... directly within a procedure or function. WBIMB v5.0 provides a lot more capability. Daniel Graper <[EMAIL PROTECTED]> &! nbsp; To: Sent by: MQSeries List [EMAIL PROTECTED] <[EMAIL PROTECTED]> cc: &n! bsp; Subject: Variable assig nment and subrountine branching in MQSI v2.1 ESQL Tuesday June 1, 2004 01:24 PM Please respond to MQSeries List I have some huge set statements that I would like to shorten using ESQL defined variables. I have tried several things but have had no success yet. An example of my set statement is as follows: SET "OutputRoot"."XML"."IDOC"."E2STZUM"."E2STZUTH"."SEGNAM"= TRIM ("InputBody"."OCF_SAP.IC.PMX.BOMMAT03"."OFF_SAP.IFC! .BOMMAT03.E2STZUM"."OFF_SAP.IFC.BOMMAT03.E2SZUTH"."OFF_SAP.IFF.BOMMAT03.E2SZUTH"."E1SZUTH_E1SZUTH"); I was trying to define OCF_SAP.IC.PMX.BOMMAT03 as XTAG_1 using the set statment SET XTAG_1 = 'OCF_SAP.IC.PMX.BOMMAT03'; but the variable does not work when I try to place it in the set statement SET "OutputRoot"."XML"."IDOC"."E2STZUM"."E2STZUTH"."SEGNAM"= TRIM ("InputBody".XTAG_1."OFF_SAP.IFC.BOMMAT03.E2STZUM"."OFF_SAP.IFC.BOMMAT03.E2SZUTH"."OFF_SAP.IFF.BOMMAT03.E2SZUTH"."E1SZUTH_E1SZUTH"); Does anyone know how I can do this? Also, is there a way in ESQL to branch to an internal subroutine? Any feedback is greatly appreciated, Dan (See attached file: C.htm) |