Shmuel, how about https://bixoft.nl/english/oplist.htm I think what you are asking for is: https://bixoft.nl/english/opl_cnxm.htm
You can toy with the selectors at the top of the page to get what you need. I hope you'll enjoy as much as I did when creating the generator. (I'm way too lazy to do maintain all those lists by hand) Kind regards, Abe === Op 11/06/2024 om 16:29 schreef Seymour J Metz: >> are the old names > What I really want is a single alphabetical table that contains all of the > mnemonics for instructions valid on Z. That's in addition to the current > table, not in place of it. > >> CONCS and DISCS > Now that's a blast from the past! > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > עַם יִשְׂרָאֵל חַי > נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר > > ________________________________________ > From: IBM Mainframe Assembler List <[email protected]> on > behalf of Jonathan Scott <[email protected]> > Sent: Tuesday, June 11, 2024 7:26 AM > To: [email protected] > Subject: Re: Current list of extended mnemonics? > > Shmuel (Seymour J.) Metz writes: >> A lot but not all :-( > As far as I can see (using a program to compare appendix J with > the table that I recently added to the HLASM Programmer's Guide) > the only extended mnemonics omitted from Appendix J are the old > names for instructions that have been renamed or extended: > > ADTR AXTR CDFBR CDGBR CDGTR CEFBR CEGBR > CFDBR CFEBR CFXBR CGDBR CGDTR CGEBR CGXBR > CGXTR CUTFU CUUTF CXFBR CXGBR CXGTR DDTR > DXTR FIDBR FIEBR FIXBR LDXBR LEDBR LEXBR > LRDR LRER MDTR ME MER MXTR PPNO > SDTR SXTR TMH TML > > I also note that my table has two spurious "extended mnemonic" > indications, in that the program to generate it found that > mnemonics CONCS and DISCS within OPTABLE(UNI) are marked not to > be used during disassembly but they have the same hex opcodes as > LBEAR and STBEAR, so it assumes they were extended mnemonics for > them. When new instructions were created for the same opcodes, > it seemed unnecessary to remove CONCS and DISCS from the UNI > table as that could in theory still be useful for reassembling > ancient 370 code, but it has caused that weird side-effect. > I don't want to update the table manually to fix that, but I > may modify the program in future to spot that the opcode is > no longer current so it cannot be an extended mnemonic for a > current instruction. > > Jonathan Scott, HLASM > IBM Hursley, UK
