By specifying L(255) your second group of 255 bytes starts on an odd address. Everything in that second group is misaligned.
It doesn't affect the data but it makes it difficult to eyeball. > On Mar 21, 2018, at 22:55, Joseph Reichman <[email protected]> wrote: > > The paste didn’t work should be l(255) m(2) > Anyway I’ll check out the ASCB again though I’m sure it was right > > Thanks > > > >> On Mar 21, 2018, at 10:22 PM, J R <[email protected]> wrote: >> >> Also, the second half of your data is misaligned. L 1R? L(256) M(2) XC >> would fix that. >> >>> On Mar 21, 2018, at 21:54, Joe Reichman <[email protected]> wrote: >>> >>> .hi >>> I am getting an abend on xmem post I’ll post the macro >>> >>> POST (R4), X >>> (R7), >>> X >>> ASCB=(R2), X >>> ECBKEY=0, X >>> ERRET=ISSMES, X >>> LINKAGE=SYSTEM, X >>> MF=(E,S_DUMP.PSTDSECT) >>> >>> I am stepping thru this under testauth and up unitl PC instruction >>> Of the post everything is okay >>> I have checked the paramters 4 points to a ECB in CSA >>> R2 points to the right ASCB >>> I display both from storage in TASID >>> The ECB has the 80 bit on followed by the RB >>> The ASCB at offset x’24’ has the right asid >>> I then make a breakpoint at the instruction after the post pc >>> And my estae recovery routine >>> Execution goes to the recovery routine >>> List below is the SDWA >>> The abend code is 460 which isn’t documented >>> The SDWANAME is zeros because I am running in supervisor state >>> However the SDWAMODN is Nucleus >>> And SDWACSCT points to csect IEAVESLK >>> >>> Any suggestion how to further debug this would be appreciated >>> thanks >>> L 1R? L(255) M(2) XC >>> >>> 008B08D0. 00000000 84602000 0004000D 00000000 *....d-..........* 0000 >>> FF040061 00000000 84000000 84073000 *.../....d...d...* >>> >>> 008B08F0. 9EC6963C 9EC6952C 00000038 00000BE0 *.Fo..Fn.........* >>> 1E85B734 029AE580 017559B0 8002B3E0 *.e....V.........* >>> >>> 008B0910. 00000000 00FB7880 00000000 00000000 *................* >>> 8175387C 0000000C 008B4198 00000000 *[email protected]....* >>> >>> 008B0930. 00000000 00000000 040C1000 8128B24E *............a..+* >>> 0002000D 7F485400 070C1000 9EC6952C *...."........Fn.* >>> >>> 008B0950. 00020061 7F485400 8002B3E0 9EC7BAB4 *.../"........G..* >>> 00FB7880 1EC693D0 1E85B734 1EC6F5EC *.....Fl..e...F5.* >>> >>> 008B0970. 1EC6F5EC 0002B3E0 1EC6F614 00000098 *.F5......F6....q* >>> 1EC7B072 00F99280 1EC7B000 1EC7BA6A *.G...9k..G...G..* >>> >>> 008B0990. 0000030E 1EC6963C E6000730 00000000 *.....Fo.W.......* >>> 00000000 00000000 00000000 00000000 *................* >>> >>> 008B09B0. 00000000 00000000 04020001 00001000 *................* >>> 00000000 008B0A60 00000000 000000 *.......-....... * >>> >>> 008B09CF. 00000000 00000000 00000000 00000000 *................* >>> 00000000 00000000 00000000 00000000 *................* >>> >>> 008B09EF. 00003800 0040D5E4 C3D3C5E4 E2C9C5C1 *..... NUCLEUSIEA* >>> E5C5E2D3 D2000000 00000000 00008B0A *VESLK...........* >>> >>> >>> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to [email protected] with the message: INFO IBM-MAIN >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
