Caveat: the daily list digestion leads to delayed list responses... (besides, I'm only catching up on my reading now.)
gil (& other interested folx): SuperC can compare program objects but not as 'objects'. [1] Rather, it treats them as binary comparisons (Byte or Word) such as you would a data file containing packed or binary data. For example, if you compare a before/after from a re-link of the same input, SuperC will report the difference created by the 'Linked Date' & 'Linking job' information fields. Of course, those should be the only difference and are (mostly) easily distinguishable. (by a sentient, anyway *grin*) [1] I did not research to be certain. I know I've used it to validate two load libraries as essentially equivalent. Someone with more in-depth knowledge will surely set me straight, right? --------> signature = 8 lines follows <-------- Neil Duffee, Joe Sysprog, uOttawa, Ottawa, Ont, Canada telephone:1 613 562 5800 x4585 fax:1 613 562 5161 mailto:NDuffee of uOttawa.ca http:/ /aix1.uOttawa.ca/ ~nduffee “How *do* you plan for something like that?” Guardian Bob, Reboot “For every action, there is an equal and opposite criticism.” “Systems Programming: Guilty, until proven innocent” John Norgauer 2004 "Schrodinger's backup: The condition of any backup is unknown until a restore is attempted." John McKown 2015 -----Original Message----- From: Paul Gilmartin [mailto:[email protected]] Sent: January 13, 2017 12:38 Subject: SuperC and Program Objects I was pleasantly surprised to learn that SuperC can compare program objects. How does it do that? Does it use the Program Management API? [xnip] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
