What is the format of your JCLIN? Binder or IEBCOPY? The answer to that will determine the need for a relfile to contain the module you have to provide to get the new JCLIN to take effect.
FILES(n) on the ++PTF statement means how many external files that SMP/E will need. For PTFs, this should be zero. JCLIN can be inline in the sysmod. It does not have to be in a relfile. If the JCLIN is inline, then you code "++JCLIN" instead of "++JCLIN RELFILE(n)". If you have no relfiles, then there is no FILES(n) on the ++PTF. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Monday, July 25, 2016 3:43 PM To: [email protected] Subject: Re: SMP/E packaging question On Mon, 25 Jul 2016 18:38:37 +0000, Way, Richard wrote: >Or am I misunderstanding it even more basically, and my example will work, but >with FILES(1)? In other words, does the file count specifically exclude the >JCLIN? Or does it only exclude the JCLIN when the JCLIN is inline as opposed >to coming from a RELFILE? > Files() counts all the RELFILEs including JCLIN. If you code FILES(0) it causes a syntax error -- you must entirely omit FILES(). (Grrr... Why? It's a PITA when generating MCS with a program.) If your PTF contains only JCLIN, APPLY will receive RC4, and as mentioned earlier, no modules will be relinked. (Grrr.... PITA; worth RFE someday.) Why deliver a PTF in RELFILE format rather than inline? It proliferates TLIBs and inflates the catalog. -- 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
