Frank: I have not been following this so closely, so I need to ask some questions. Is this program being CALLED under CICS from a COBOL program? Is the program FCOBOL or COBOL/VSE? How is the COBOL program defined to CICS and linked? And what are the RDO settings for the transaction? It would seem to me that key CICS must be used. In some of the programs I wrote that needed to run under

No, I didn't think to look, but yes it looks like it did in fact retrieve the data. I can see the value of the parm and its length in the Cobol working storage area. Interesting... I noticed that in my original code I saved off the value of R13 before the call and restored it afterward. So I decided to do something similar here. Here's my new code: GETSYMBX TITLE 'GET THE VALUE OF

Hi Frank, Without looking at the dump etc its a bit hard to tell from just the CICS messages what went wrong. But looking at your assembler program the first thing that stands out is that is non-reentrant. Depending upon how the programs/transaction is defined this may not go down too well. To me the simplest thing would be to convert it to LE-conforming. LE will then handle the re-entrancy

______________________________________________________________________ 6. XXDP LISTS NOTE This article forms part of an attempt to document XXDP. The information is based on an examination of XXDP disks and the scant documentation available on the web. Thus omissions and errors are guaranteed. Ian Hammond/2008 alt.sys.pdp11 __________

ON THE FLOP Hand[Board]Opps IDNo Prs+Str+Fl=Outs IDNo OutsSum\Odds Qs9c[As9s4d]5 EB03 ___+___+___=___ EB03 5+ +1=06\7 7s6s[4s3d2c]2 BK38 ___+___+___=___ BK38 6+4+2=12\3 QsJs[KsTd3c]1 BL01 ___+___+___=___ BL01 +8+2=10\3+ Ts9s[JdTh9h]4 BD30 ___+___+___=___ BD30 4+ + =04\10 9c6s[8s7s3s]5 DR28 ___+___+___=___ DR28 3+6+1=10\3+ 8s8h[Ks7s4d]5 ER07 ___+___+___=___ ER07 2+1+1=04\10 Ts9s