> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of R.S. > Sent: Tuesday, December 27, 2016 1:47 PM > To: [email protected] > Subject: Looking for USERMOD samples > > I'm trying to learn a little bit about SMP/E usermods. > Unfortunately neither SMP/E manuals nor google did not provide good > (*well explained*) samples. > > > Example (from File Manager): > //SMPCNTL DD * > SET BDY(GLOBAL). > RECEIVE SELECT(FMN2001) SYSMODS. > SET BDY (TARGET). > APPLY SELECT(FMN2001) RETRY(YES) REDO. > /* > //SMPPTFIN DD DATA,DLM=$$ > ++USERMOD (FMN2001) REWORK(201601) . > ++VER (Z038) FMID(JADLD12) PRE(UI25246) . > ++JCLIN. > /* > ++SRC(FMN2POPT) TXLIB(FMN2SRC) DISTLIB(AFMNSAM1). > $$ > FMN2SRC is a DD name pointing to a member with source code.
That is wrong. It should identify the library. The first operand following the ++SRC identifies the member. > Q1: How can I know what's target library for the load module? If the source of FMN2OPT (SRC element) and the CSECT (MOD element) that results from assembling it already exist in the CSI, then issuing a LIST command against either will show you the corresponding target library. It appears as the SYSLIB. If either does not exist, you get to define it as part of your input using the SYSLIB operand and +JCLIN. > Q2: there is no assemble or linkedit jobstep. I assume it comes from SMP/E. Yes. The only reason to APPLY an SRC is to assemble and link it. > Q3: FMN2SRC DD - should it describe library or member? In other words: > DSN=MY.LIB or DSN=MY.LIB(MEM) ? There is a reason it is called TXLIB and not TXDATA. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
