Yes there is a parameter and is used for the data coming from the csv file to pass along but exchange you should be able to declare external variables that is known in all conditions without using the parameters...My understanding is the parameters are constant and do not change where as my external variables can change.
These exchange scheme had been written back in 2000 and have NOT had any issues with use of the external variables being declared in the first condition. This is first time having issues due to a change in the server environment and having to make a change to the exchange scheme. I have other schemes that are working as is but if I were to "regenerate" it will have issues.
I have tried what Mark suggested and through debug I see it is retaining the value in each condition with it being declared as external in each condition that it is used.
I have a new issue now with my lack of understanding on how exchange processes. For example I have two lines in my csv file:
861,5507,ZZ,18,,,76250THR A120M6 NH830M,,3000521AA,39.9506,,,,4091008,WFG,R785168,30,,,E785169,5,E5304,30
Watching in debug it's like it processes one column at a time for each line....meaning in this situation I have an existing contract 861 and I need to add a new position and packaging...I see it create the new positions two of them and then it goes to do the packaging...not sure if it's due how the exchange has been created but I would have thought it process one row at a time completely before moving onto the next row...due to this issue I have lost pointer on the new contract position to determine which position is to get specific packaging.