That's right SYSALLDA is a system defined ESOTERIC my bad.
From: Mark Zelden <[EMAIL PROTECTED]> To: IBM-MAIN@BAMA.UA.EDU Date: 02/22/2008 11:21 AM Subject: Re: ZOS Upgrade Issue On Fri, 22 Feb 2008 10:39:01 -0600, Michael Saraco <[EMAIL PROTECTED]> wrote: >I have worked on numerous systems that never had SYSALLDA setup in HCD or >ALLOCxx and never had a problem running TSO BATCH. The default for generic >for DASD is 3390 that has no ESOTERIC assigned to it. >I tired a Randy's job on Zos14 and a Zos17 and it ran fine without any >SYSALLDA in esotrics or a ALLOCxx and without adding the unit to the JCL. > > SYSALLDA is a system defined ESOTERIC for DASD and is always present. You don't need to define in in HCD. That is why almost all my JCL uses it and didn't need to change when moving from shop to shop or from 3380 to 3390. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
