I know of at least one installation where something similar is done, although the group userid on zOS has no relationship to the zVM userids which utilize it. It's used mostly by automated processes, but interactive users also have access to the procedure. The zOS userid is just a RACF batch profile. Its password is maintained automatically. zVM users don't have the password, but submit jobs via a process which reads their jcl and sends it on to zOS, supplying the password en passant when it recognizes a group userid on the JOB statement.
Mike Harding EDS VM National Capability 134 El Portal Place Clayton, Ca. USA 94517-1742 * phone: +01-925-672-4403 * Fax: +01-925-672-4403 * mailto:[EMAIL PROTECTED] * <mailto:[EMAIL PROTECTED]> (personal) Note: For 2005, I am off on Fridays with even Julian dates and Mondays with odd ones. -----Original Message----- From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On Behalf Of Judson West Sent: Monday, October 17, 2005 11:15 AM To: [email protected] Subject: z/OS Batch Job Submission From z/VM This is really RACF related, but I thought I'd come here first since there is probably at least one shop on this list that has both z/VM and z/OS. We have several userids submitting batch jobs to our z/OS system. We don't have any of these userids defined to RACF on z/OS. What we would like to do is have some sort of "group" userid on z/OS that the submitting users on VM can reference on their JOB cards and be validated that way. For example, submitting VM userids BOB1-BOBn can submit using a USER=BOB on their job card. RACF would then validate that BOB1-BOBn could submit jobs based on the rules covering BOB on z/OS. What needs to be done in z/OS RACF to allow this, if possible? ----------------- Judson West Teradata, a division of NCR Corporation
