Just wanted to add to my earlier post. The disassembler provided with the Assembler Toolkit is now part of HLASM and shipped as load module ASMADOP in SYS1.MIGLIB. Looks like this was done with APAR PQ27453 back in 1999!
Regards, Peter Van Dyke HCL Software On Wed, 9 Dec 2020 at 10:54, Mike Hochee <[email protected]> wrote: > Thanks all, yet again, for all the excellent ideas! These IBM- listservs > are a truly fine resource. ('the power of many brains working!') I will > probably end up doing some flavor of opcode evaluation, and assumed, maybe > erroneously, that opcode evaluation would be simpler/cleaner to implement > than parsing or scanning source (which is available). I generally feel more > comfortable working with machine/product outputs rather than the curveballs > humans sometimes throw. > > Best, > Mike > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Mike Hochee > Sent: Tuesday, December 8, 2020 5:50 PM > To: [email protected] > Subject: Re: Determining required z/series hardware level - REVISED > > Warning! This is a fake (spoofed) message. DO NOT TRUST! > > Oops, got the hardware lvl for AHI wrong, so changed 'G9' to 'G10' > > Hi, > > I'm looking for a utility/program which is capable of reading a z/OS > executable, whether an lmod or program object, or unbound object code, and > examining it for hardware/architecture level compatibility. I'm not > specifically referring to the ARCLVL of on the SYSSTATE macro, although I > know there is some correspondence, but rather to the set of unprivileged > instructions introduced at a particular hardware architecture levels. > Apologies in advance for any imprecise/inaccurate terminology. > > For example, let's say I happen to know that the most recently introduced > z/Series instruction used by a particular executable is the AHI > instruction, then I would expect this utility/program to output 'G10', > suggesting the minimum hardware architecture required to support execution. > > I understand things are not always black/white in this area and could be > clouded by instruction facility requirements, etc.. > > Thanks in advance for any suggestions, guidance. > > Mike > > > ---------------------------------------------------------------------- > 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
