ACS, SMS definitions are site defined with no IBM defaults. You might try a sample of STORGROP(SMPEGROP), STORCLAS(SMPECLAS), or DSN=SMPE*.** going to SMPE* volumes.
On Wed, Nov 12, 2025 at 2:32 PM Phil Smith III <[email protected]> wrote: > Um. I'm sure that's all 100% accurate, but all I get out of it is "It's > not that easy". Correct? > > -----Original Message----- > From: IBM Mainframe Discussion List <[email protected]> On Behalf > Of Mike Schwab > Sent: Wednesday, November 12, 2025 2:45 PM > To: [email protected] > Subject: Re: SMS and SMP/E: Naive questions > > https://www.ibm.com/docs/en/zos/3.1.0?topic=commands-define-cluster > > DEFINE CLUSTER includes DATACLASS(), MANAGEMENTCLASS(), and STORAGECLASS() > but not STORAGEGROUP(), requiring ACS updates. > > https://www.ibm.com/docs/en/zos/2.5.0?topic=guide-smpe-primer > https://www.ibm.com/docs/en/zos/3.1.0?topic=guide-preparing-use-smpe > > DDDEF configures the output of the load module editor. > > On Wed, Nov 12, 2025 at 1:10 PM Phil Smith III <[email protected]> wrote: > > > We install our product via SMP/E, and of course provide sample JCL to > > do so. Those jobs currently specify VOLSERs everywhere via a VOLSER > > variable, with the expectation that customers will further configure > > the jobs for their installation, especially if using SMS. > > > > I'd like to make it simpler. Looking at the jobs, there are three > > places that the VOLSER gets used. > > > > The ALLOC job contains: > > // VOL=SER=&VOLSER., > > (on a bunch of DDs) and > > VOLUMES(&VOLSER) + > > (on a bunch of DEFINE CLUSTER statements) and > > VOLUME(&VOLSER). > > (on a bunch of ADD DDDEF statements) > > > > and the RECEIVE jobs each have a single instance of: > > //SMPTLIB DD UNIT=&UNIT,VOL=SER=&VOLSER,SPACE=(CYL,(10,10,100)) > > > > I'm wondering if it seems plausible to do something like add a > > variable named (say) VSORSC (that's "VolSer OR StorClas"). The value > > of this would be (doh) a VOLSER or storage class name, plus another > > variable indicating whether it's a VOLSER or storage class. Then our > > code would set and use more variables in the appropriate places,e.g.: > > > > If using VOLSERs: > > SD1 gets set to VOL=SER=&VSORSC > > SD2 gets set to VOLUMES(&VSORSC) > > SD3 gets set to VOLUME(&VSORSC) > > > > If using STORCLAS: > > SD1 gets set to STORCLAS(&VSORSC) > > SD2 gets set to ?? > > SD3 gets set to ?? > > > > The question is what SD2 and SD3 should be set to when using STORCLAS; > > I don't know (maybe just STORCLAS(&VSORSC) again??). And those with > > more knowledge of SMS and SMP/E than me (I can spell both about two > > out of three > > times) may say "Nah, this is pointless because there are too many > > other possibilities for this to even come close to making sense". > > > > Obviously I'm ignoring the case of them wanting to use VOLSERs but > > with stuff spread across multiple volumes, or using SMS but wanting > > stuff in different storage classes; those are possible but seem like > > the advanced class--those folks won't have a problem just updating the > jobs directly. > > > > Plausible? Or fool's errand? > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to [email protected] with the message: INFO IBM-MAIN > > > > > -- > Mike A Schwab, Springfield IL USA > Where do Forest Rangers go to get away from it all? > > ---------------------------------------------------------------------- > 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 > -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
