MQSeries.net :: View topic - Usage of Default Values within CWF Message Set

harish_td · Posted: Tue Feb 19, 2008 2:13 am Post subject:

All,

I have a XML to CWF flow. The copybook(CWF Output) is a fairly big one considering that it has a lot of fields.
During the course of transformation we would initialize zeros/spaces to all the fields that were mandatory in the copybook but no values would be assigned to them for useful business mapping.

Ex:
SET OR.field1 = '';
SET OR.field2 = IR.MRM.XMLField1;
SET OR.field3 = 0;
SET OR.field4 = CAST(IR.MRM.XMLField2 AS INTEGER);
.
.
.
SET OR.field999 = '';
and so on

This works fine except that we have to re-do the initializations over and over again for every project in which this message set is used.

In order to overcome this i assigned default values to each field in the message set. Space for Strings and 0 for integers.

So in my flow i earlier had MQInput --> Compute --> MQOutput

I would like to add that the compute node now has code that maps the fields that are necessary for our business.

Now i have MQInput --> Compute --> ResetContentDescriptor --> MQOutput.

The fields not necessary to the specific requirement are not created at all. Since the message set has defaults set within them, every absent field would be populated by its default value at the o/p of the RCD Node.
Voila!! it works fine.

As per the MB Bible(Info-centre), it is perfectly legal to do so as the RCD merely reparses the message with the parser specified
(In my case CWF to CWF re-parsing)

Is my understanding right or am i unknowingly creating a bug? Do let me know if there is another way of overcoming lengthy initialization statements within ESQL.

Thanks in Advance,
Harish