DDDEF? In a sysmod?
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Paul Gilmartin <[email protected]> Sent: Wednesday, November 19, 2025 1:32 AM To: [email protected] <[email protected]> Subject: Re: Variables in SMP/E JCLIN records? External Message: Use Caution On Tue, 18 Nov 2025 23:54:54 -0600, Jon Perryman wrote: > >2. Customers should never have the ability to modify functions nor PTFs.. >"&USSPATH.lib/libsapi.a" is unacceptable. Functions, PTFs and more belong to >you. They should never be under the customer's control. > Except for DDDEFs. >3. Never use hardcoded paths (e.g. /usr/lib/libsapi.a) in your functions or >PTFs. Instead, use relative paths (e.g. ../../lib/libsapi.a or >./lib/libsapi.a) where possible. I'm guessing that libsapi.a is not part of >your product which should be referenced through a DDN instead of a path. As a >last resort, you supply the customer with UCLIN that modifies the appropriate >SMP/e object because customers must never modify your PTFs nor functions. > Relative to what? -- gil ---------------------------------------------------------------------- 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
