One more thing that I find interesting.
A quick trip through the archives indicates that using TRSMAIN on tape datasets
yields the same illuminating error.
I'd like to someday know what that program is doing.
Bob
David Shein wrote:
Oh, and one more thing!
The only reason we solved this problem was that we HAPPENED to notice,
in passing, that the original data set was a PDSE. If we hadn't, we
would probably still be searching for the answer.
Yes, the restriction is documented, but for that to be of any help, it
has to occur to you to check the original data set type. The error
symptoms that you get in this case don't even faintly hint, imply, or
suggest what the cause might be. What you get is a B37 on a work file.
Obviously that points to the data set type of the input file as the
culprit, right? Not!
----------------------------------------------------------------------
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
