You have to realize there are two SUBMIT (SUB) commands: the standard TSO line mode SUBMIT command and the SUB command in ISPF. I'm not 100% certain how the ISPF SUB command works, but it tricks the TSO SUBMIT command into using the ZTEMPF facility.
Now you are not clear what you mean by "other IDs." There are three security related issues here.
- The standard security environment, in which the job being submitted inherits the userid of the user submitting the job.
- The USER=xxx (and the PASSWORD=xxx) parameters on the JOB JCL statement. The USER=xxx and PASSWORD=xxx business is in place to permit security to be in place when a job is submitted on a real card reader or an RJE card reader. There is an ability to alter the user without also specifying the user's password. This is called "surrogate" submission and was devised to permit job scheduler packages - whether a user devised package or a vendor supplied package or just a casual user, say you - to submit jobs with just the USER specified. This requires a special security setup controlled by security administration.
- The sort of standard jobname from the JOB JCL statement, which generally requires the jobname to include the userid of the user assigned to the job. This requires security administration setup which is usually done when the userid is created.
Now we have to know what you are doing, which is what Mr. Jensen is asking, before anyone can help you.
Properly speaking this matter should be discussed with
your security administration, not in a public forum like this one.
Your security administration knows how security is implemented in your environment. We do not.