Archives of the TeradataForum

Message Posted: Tue, 25 Feb 2003 @ 15:29:47 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

<-- Anonymously Posted: Tuesday, February 25, 2003 10:23 -->

This doesn't seem to be a scheduler package problem, but an M&P issue.

Can't you create unique logon members in a protected library and then have the SYSIN DD in your JCL point to the logon member? Then each job or function would use a specific logon id. In my shop only the DBA can update the library, and only the DBA and Batch jobs can read the library.

//SYSIN DD DSN=SYS4.LGNSQL(logonid),DISP=SHR

	<Prev	Next>		<<First	<Prev	Next>	Last>>