On Mon, 5 Oct 2009 02:14:51 +0000, Ted MacNEIL wrote: >>I'm naive; enlighten me. In what cases does userid differ from OWNER? > >OWNER is, I believe, the userid that submits the job. >Having never used OWNER for anything, I can't truly say. > >>How can the programmer control these independently? > >USER= & PASSWORD= are valid JOB CARD parms. > OK. I tried the experiment. I submitted a job with USER= different from the user submitting the job, and PASSWORD= as parms on the JOB CARD. SDSF shows the name from USER= on the JOB CARD as OWNER. "EXEC PGM=IEFBR14,PARM='&SYSUID'" substitutes the USER= value from the JOB CARD for &SYSUID.
Until someone shows me documentation or an example to the contrary, I'll believe that OWNER is a synonym for userid. Different components should always use different names for the same entities -- it keeps programmers alert. Or perhaps it's just Conway's law again. The MIS department (which I didn't work for) of a company that employed me until four years ago had rules: o Each employee's VM user ID was "V" followed by his six-digit employee number. o Each employee's TSO user ID was "T" followed by his six-digit employee number. PHB. I suppose the PHB believed a programmer couldn't tell whether he was logging on to CMS or to TSO except by whether he typed an ID beginning with "V" or with "T". (Well, if logs were merged, it distinguished CMS sessions from TSO sessions.) OTOH, it was an extremely poor choice because jobs submitted via NJE from CMS to MVS wouldn't automatically pick up the programmer's MVS ID. PHB. Given those conventions, I might say that a reasonable set of job name rules would be: o "P" is reserved as a prefix for production jobs. No other job names may begin with "P". o Job names beginning with "T" or "V" followed by six numeric digits are reserved for employees with those six-digit employee numbers. o Otherwise, programmers are not restricted in their choice of job names. Job names need not begin with the programmer's user ID. Programmers who are possessive about jobnames would have their enclave; other programmers have freedom of choice as long as they stay out of the reserved enclave. -- gil ---------------------------------------------------------------------- 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
