This is why you have specialty routines that you load and if I remember correctly, IDENTIFY.
What is being described is part of the joys of being an ISV. Imagine, back in the day, of providing code that was sensitive to JES2 releases and Maint changes. My headache w/ ACS/WYLBUR while also handling JES3, RACF, ACF2, etc. You do what your customers need. Sent from iPhone - small keyboard fat fingers - expect spellinf errots. > On Nov 29, 2015, at 7:22 PM, Ed Gould <[email protected]> wrote: > > Charles, > > I have been watching this thread and if I am not mistaken you want to know > which instructions are available (or not) at execution time. > I am not knowledgeable of c/c++ but unless you compile the program at run > time (with the correct arch type) you will always get an 0C1 if you execute > the instruction on a machine that is incapable of executing that instruction. > I would suggest that you compile at the lowest level and therefore should run > on all types of the machine. If you are concerned about "efficiency" there is > no real answer and you are exercising a way to get a medical > condition(ulcer). Tell your boss to either ship the source and compile it > whenever the machine type changes (make the customer do it). > OR just ship at the lowest architected of the Z models or let the customer do > it. > We are probably talking about a few CPU seconds or there unless this is a > MAJOR usage animal. Then I would suggest let the responsibility lie with the > customer. > > Ed >> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
