when you have 2 or more contiguous fields and you have single field moves,
and there is no conversion involved,
the optimizer will generate a move for the first instruction with a length equal to the length of all the contiguous fields,
and not generate a move for the remaining instructions.

look at the assembler generated and you will see the length of the first move is equal to all the fields.
there will be no generated assembler instructions for the remaining fields,
thus it will 'appear' that xpeditor 'skips' the remaining fields.

when abt to execute MOVE 1 TO NBA-TYPE it skipped next two lines. and when i checked the values using KEEP command , those variables(NBA-NT-ID,NBA-RP) were filled with garbage, not with WS-NT-ID and WS-RP-ID .

you are right, that program in xpediter is optimized ,when i view the help option ,it is telling that follow the recommendations

Compuware Recommendations :

We recommend that you compile with the NOOPT (equivalent of OPT(0)) and NOINLINE (if supported by your compiler) options when preparing your program for debugging with Xpediter/CICS. These compile options ensure that the code generated by the compiler corresponds exactly to your source
code. This will allow you to accurately test and debug your program.

im using changeman Version = 6.1.1B.

if anyone know how to compile a cics module with the NOOPT (equivalent of OPT(0)) and NOINLINE .

when abt to execute MOVE 1 TO NBA-TYPE it skipped next two lines. and when i checked the values using KEEP command , those variables(NBA-NT-ID,NBA-RP) were filled with garbage, not with WS-NT-ID and WS-RP-ID .

Make sure that these statements are not commented in your source program(I am sure that they will not be, but just to be on the safer side).

i changed the sequence of MOVE statements(those stmts are not commented) and tried also using nopt(compilar options) before compilation of the module.but finally its of no use ,,,,its totally bugging me..

i changed the sequence of MOVE statements(those stmts are not commented) and tried also using nopt(compilar options) before compilation of the module.but finally its of no use ,,,,its totally bugging me..

can anyone come up with the solutions.....

can you copy-paste the whole SECTION(where you are doing these MOVEs) here? I mean the whole section from the compiler listing as you see in Xpeditor session.

I have thought about this for a while,
and xpeditor is in about 100-thousand installations.

The TS is full of BULL.
he has not bothered to provide all the information.

a word to others.

yes, xpeditor will optimize things.
as i indicated, if you have contiguous moves of contiguous items (none requiring conversion),
xpeditor will make one (1) move (for the length of all items)
and not generate code for each individual move.

again, double check your code, and insure that you have nothing
improperly coded.