We do not have a Throughput Manager, we just have JES2. If DISP=NEW, the UNIT value will not be tested for "correctness" until step execution time and then only if the data set has no STORCLAS assigned (non-SMS-managed). If DISP=SHR (and VOL=SER does not reference a non-SMS-managed volume) and the data set is found in the catalog by the converter/interpreter and it is an SMS-managed data set, then the UNIT will be ignored.
In the JES2 JCL Reference manual, under "subparameter definition" for UNIT, I find: "SMS ignores a device number, if specified for SMS-managed DASD." "If you specify the device-type subparameter, SMS ignores it." "If you specify the group-name subparameter, SMS ignores it." JES3 may function differently. Do you have some JCL-checker software in place that scans jobs as they are being submitted? Greg Shirey Ben E. Keith Company -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Behalf Of Pat Schlehuber Sent: Wednesday, March 01, 2006 6:58 AM To: [email protected] Subject: Re: Esoterics set in SMS we are very quick to make HCD changes. I guess I am a bit confused, does your Thoughput Manager override somehow? When I use a non-existent UNIT SMS is not nvolved yet and I receive this error: IEF210I ............. - UNIT FIELD SPECIFIES INCORRECT DEVICE NAME ---------------------------------------------------------------------- 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
