| Author |
Message
|
| madi |
 Posted: Wed Mar 29, 2006 12:24 pm Post subject: BIP2523E |
 |
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
I am getting this msg when Im deploying the bar file.
It deploys fine to another broker but gives error when I try to deploy it in the local machine. (I just created a broker and am trying to deploy to it)
| Code: |
BIP2523E: (.DatabaseExtract_RA.Main, 43.5) : Cannot assign to a symbolic constant or input message.
Values cannot be assigned to symbolic constants or input message fields.
Correct the syntax of the expression and redeploy the message flow. |
Let me know if i have to put in thte eSQL
--madi |
|
| Back to top |
|
 |
| JT |
| Posted: Wed Mar 29, 2006 12:29 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Post the ESQL code for DatabaseExtract_RA.Main |
|
| Back to top |
|
|
| madi |
| Posted: Wed Mar 29, 2006 12:41 pm Post subject: |
|
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
Local fix
Problem summary
****************************************************************
* USERS AFFECTED: All users of WBIMB 5.0 *
****************************************************************
* PROBLEM DESCRIPTION: BIP2523E occurs when deploying a flow *
* having a compute node in which a FOR *
* statement uses a reference as the *
* correlation name. *
****************************************************************
****************************************************************
A BIP2523E occurs when deploying a flow having a compute node
in which a FOR statement uses a reference as the correlation
name.
This is because the FOR statement correlation name validation
disallows references because they may resolve to correlation
names that are not modifyable.
Problem conclusion
The FOR statement correlation name validation has been changed
to allow or disallow correlation names based on their effective
modifyability.
This means that references can be used if they are known to
resolve to a modifyable correlation name.
It is possible to use a valid reference that changes to an
invalid one at runtime, and in that case a runtime error will
result.
Last edited by madi on Wed Mar 29, 2006 1:44 pm; edited 1 time in total |
|
| Back to top |
|
|
| JT |
| Posted: Wed Mar 29, 2006 12:54 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
| BIP2523E: (.DatabaseExtract_RA.Main, 43.5) : Cannot assign to a symbolic constant or input message. |
The hilighted text pinpoints the line and column of the offending reference in your ESQL code. |
|
| Back to top |
|
|
| JT |
| Posted: Wed Mar 29, 2006 12:56 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| I don't see the declaration for 'batchCount' |
|
| Back to top |
|
|
| madi |
| Posted: Wed Mar 29, 2006 1:03 pm Post subject: |
|
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
that would be in
| Code: |
FOR cursor AS Environment.Variables.TempOrderIds.Id[] DO
SET Environment.Variables.TempOrderIds.Id[i].SeqNum[] = (SELECT T.AIPCNB AS TSeq FROM Database.RTCQACDTA.RTINPD AS T WHERE T.AIIGNB = FIELDVALUE(cursor.OrderID));
FOR cursor1 AS Environment.Variables.TempOrderIds.Id[i].SeqNum[] DO
SET cursor1.Seq.No = FIELDVALUE(cursor1.TSeq);
SET cursor1.Seq.PODet[] = (SELECT T.AIBECD AS ProductID,
T.AIPCQJ AS Quantity,
T.AICXDT AS ExpectedReceiptDate
FROM Database.RTCQACDTA.RTINPD AS T
WHERE T.AIPCNB = FIELDVALUE(cursor1.TSeq) AND T.AIIGNB = FIELDVALUE(cursor.OrderID));
DELETE FIELD cursor1.TSeq;
END FOR;
SET i = i + 1;
END FOR; |
I cant find what it is!!
but how can it work without error in another broker?? |
|
| Back to top |
|
|
| madi |
| Posted: Wed Mar 29, 2006 1:14 pm Post subject: |
|
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
i did a search on this on ibms site. looks like its a bug and they fixed it the fix packs. i will install the fixpacks and i should be fine i think
thanks for the help |
|
| Back to top |
|
|
| JT |
| Posted: Wed Mar 29, 2006 1:22 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| For posterity, what was the bug fixed ? |
|
| Back to top |
|
|
| madi |
| Posted: Wed Mar 29, 2006 1:32 pm Post subject: |
|
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
| Quote: |
Local fix
Problem summary
****************************************************************
* USERS AFFECTED: All users of WBIMB 5.0 *
****************************************************************
* PROBLEM DESCRIPTION: BIP2523E occurs when deploying a flow *
* having a compute node in which a FOR *
* statement uses a reference as the *
* correlation name. *
****************************************************************
****************************************************************
A BIP2523E occurs when deploying a flow having a compute node
in which a FOR statement uses a reference as the correlation
name.
This is because the FOR statement correlation name validation
disallows references because they may resolve to correlation
names that are not modifyable.
Problem conclusion
The FOR statement correlation name validation has been changed
to allow or disallow correlation names based on their effective
modifyability.
This means that references can be used if they are known to
resolve to a modifyable correlation name.
It is possible to use a valid reference that changes to an
invalid one at runtime, and in that case a runtime error will
result.
|
--madi |
|
| Back to top |
|
|
|
|
