SPFCopy's "magic" SVC went thru several iterations to make it secure too. It was one of those SVC's that was written to be "serially secure".... but in a multi-tasking environment when two or more tasks could be set up to run concurrently, then a "serially secure" task, doing what it did in a secure manner (if it was the only thing running) allowed everyone running in the address space to participate in the authorization. STATUS STOP became very much a requirement for those serially secure tasks to remain such.
---------------------------------------------------------------------- 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
