Mike, >Hello, all. A bit more investigation is showing that I can use any entry >in the unit field and the system accepts it. I can use unit=sort, >unit=mike, unit=ward, etc... Does this mean that I have an ACL that is >allowing this. Or should I be looking for a user exit the replaces the >unit parameter? Anyone have a guess? I didn't think sms got involved >until the interpreter did its job. And then it should have crapped out >during the interpreter read phase.
If the dataset is SMS managed, the value specified in the UNIT= is ignored. SMS will provide a default unit value if you omit it but it applies to all datasets, not just SMS managed. In my shop, I was going to use UNIT= values that were not defined as esoterics but found that Throughput manager detects the bogus value and jcl errors out the job. Now if the dataset is not SMS managed, you will get through the intepreter and into the input queue. Your job will fail when the system tries to initiate it and can not find the esoteric. Regards, John ---------------------------------------------------------------------- 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
