This thread has begotten and promulgated some misnomers, 'TLIB' being prominent. That word is *not* shorthand for 'TARGET LIB'. Unfortunately TARGET has no nickname. DLIB is short for 'DISTRIBUTION LIBRARY', but 'TLIB' is not short for TARGET. To quote from the doc:
"SMPTLIB data sets (TLIBs) are used as temporary storage for relative files that are loaded from SMPPTFIN during RECEIVE processing." . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Ed Jaffe Sent: Friday, July 19, 2019 9:07 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: EQA10OSM On 7/18/2019 8:25 PM, Lizette Koehler wrote: > Just by looking at the dataset names. > > Typically the AEQAMOD should be a DLIB dataset The SEQAMOD would be > your TLIB. > > TLIBs would go into your live environment > > DLIB would only be used when an SMP/e ACCEPT is done. > When did target libraries start being called TLIBs? ISTR TLIBs used to be the "temporary" libraries that were built on the SMPTLIB volume when unloading the RELFILEs during RECEIVE processing. APPLY would copy/assemble/link the TLIB content to the target libraries. ACCEPT would then a) copy/assemble/link the TLIB content to the distribution libraries (aka DLIBs) and b) delete the TLIBs and update the global zone. -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
