Richard, If you plan is to do this long term or in production, you should write a SMPE user mod to move them into SCSQLINK or whatever MQ dataset you have in LPA. What you did just broke SMPE.
_______________________________ Dave Jousma Vice President | Director, Platform Engineering Fifth Third Bank | 38 Fountain Square Plaza | Cincinnati, OH. 45202 From: IBM Mainframe Discussion List <[email protected]> on behalf of rpinion865 <[email protected]> Date: Monday, August 3, 2026 at 10:27 AM To: [email protected] <[email protected]> Subject: Re: MQ 9.3 module CSQBDSC CAUTION EXTERNAL EMAIL This message came from outside your organization. DO NOT open attachments or click on links from unknown senders or unexpected emails. Report Suspicious<https://us-phishalarm-ewt.proofpoint.com/EWT/v1/MwwqYLOC6b6whF7V!pHOGFn8lp2COPWT3ozcC2mzSbgvgbhvVFopiXW5pActhrOuEpSTny5Tajx8NtwOF9nlu52O-Vq-VHvFL5HMxn3bV2Oj5DDJ6HNJk-_0bCJh-eE6mV6bNhgAEtvvx7PAcU1kFLuleunmKxFSXvGXLFhkDCdy4Im_YMnzKWg2QoyE2TEdhnF7egsNdagnAMCwJmF9YR84Wng$> I loaded the modules into LPA of our TECH LPAR, renamed them in the SCSQAUTH library (was in the STEPLIB of the MQ MSTR and CHIN), and IPLed. The modules are not showing up in SDSF MFM and no nastygrams coming out of MQMSTR or MQCHIN. "Confidentially doc, I am the wabbit." Bugs Bunny Sent with Proton Mail secure email. On Monday, August 3rd, 2026 at 3:57 PM, Peter Vander Woude <[email protected]> wrote: > Doh! > > On Fri, 31 Jul 2026 13:26:55 +0000, rpinion865 <[email protected]> > wrote: > > >9.3 as the title indicates. > > > > > > > >"Confidentially doc, I am the wabbit." > > > >Bugs Bunny > > > >Sent with Proton Mail secure email. > > > >On Friday, July 31st, 2026 at 3:23 PM, Peter Vander Woude > ><[email protected]> wrote: > > > >> What version of MQ are you running? > >> > >> The latest is V10, though it just came out. 9.1 is out of support. 9.2 I > >> think is still supported. 9.3 and 9.4 are definitely still supported. > >> > >> Peter > >> > >> On Thu, 30 Jul 2026 12:33:49 +0000, rpinion865 <[email protected]> > >> wrote: > >> > >> >EXACTLY! Which is why I am asking on the list. Our MQ/CICS > >> >SYSPROG has sent a question to IBM. But IBM says we are not > >> >licensed for MQ. Strange, since we are paying for it. Although, > >> >the MQ/CICS SYSPROG does not seem to be in a hurry to get the > >> >question of support resolved. > >> > > >> >Richard Pinion > >> > > >> > > >> > > >> >"Confidentially doc, I am the wabbit." > >> > > >> >Bugs Bunny > >> > > >> >Sent with Proton Mail secure email. > >> > > >> >On Thursday, July 30th, 2026 at 2:28 PM, Peter Relson > >> ><[email protected]> wrote: > >> > > >> >> <snip> > >> >> I feel confident that loading the module into LPA will not > >> >> cause any problems, since the module is RENT/REUS. I just > >> >> want to make sure. > >> >> </snip> > >> >> > >> >> You might be right that it is OK to place the module into LPA, but > >> >> being "confident" is way further than you should be. Not every > >> >> RENT/REUS module can be in LPA. And sometimes an application will have > >> >> dependencies on the location of its modules. A good rule is that you > >> >> should not place anyone else's modules into LPA without explicit > >> >> indication that it is OK to do so. > >> >> > >> >> Peter Relson > >> >> z/OS Core Technology Design (retired) > >> >> > >> >> ---------------------------------------------------------------------- > >> >> 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 > > ---------------------------------------------------------------------- > 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 This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
