What I said below about "good installation documentation" applies. Usermod or not in the previous install, that's so important. Too bad more and more I see people with the "just install and get it working" mentality and they don't document anything and put things in their own personal libraries etc. :-( That's probably where your missing source code is - in someone's personal library that may be long gone.
Do you have the macro libraries for both versions to compare and find how many changes there actually were? You may be lucky and the exits could work under 5.4, but what about the next upgrade? Eventually you'll have to bite the bullet and re-write the exits (do you even understand what they are doing exactly with no source code) or try to disassemble them using the HLASM toolkit disassembler if you are licensed for it or try the free one on the CBT. Best Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 Foundation Certified mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://search390.techtarget.com/ateExperts/ On Thu, 9 May 2019 22:24:20 +0400, Peter <dbajava...@gmail.com> wrote: >We have some user exits used for TPX 5.2 and unfortunately we don't know >where the source codes are located. > >Is it ok to just copy over to 5.4 ? > >On Fri, 3 May, 2019, 3:09 AM Mark Zelden, <m...@mzelden.com> wrote: > >> On Thu, 2 May 2019 15:44:14 -0500, Michael Cleary < >> michaeljosephcle...@yahoo.com> wrote: >> >> >If the product is installed with SMPE best practice would be to install >> the exit via an SMPE USERMOD. >> > >> >> Not a bad idea, but I don't consider that necessary if the product doesn't >> come with an LMOD >> for that exit in the product loadlib that is being replaced by the one you >> want to create. There >> is no chance that product maintenance will regress the exit which is the >> main reason you would >> want a usermod. Good product installation documentation that says there >> is an exit in use >> and putting it in a concatenated loadlib or even directly into the product >> loadlib is fine as far >> as I'm concerned. Just so the next pour sole that has to upgrade the >> product next knows >> there is an exit and where the source code and asm/lnk JCL is. >> >> But that's just my opinion. Creating the usermod is more trouble than I >> want to go through >> if I don't have to do it to protect the integrity of the product >> installation. >> >> Best Regards, >> >> Mark >> -- >> Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS >> ITIL v3 Foundation Certified >> mailto:m...@mzelden.com >> Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html >> Systems Programming expert at http://search390.techtarget.com/ateExperts/ >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
