RE: qntc userid in a production batch job

If *public is write only, any one can put something into the share.  You can
define one share as "c:\whatever" shared as "newonly$$" which will hide it
from users and public access is write only, no read/update/delete.  The
AS400 program then writes to that share.  Now you define a second share over
the same directory giving public exclude authority and what ever group of
users the access they need.  No profile sync necessary.

Christopher K. Bipes      mailto:ChrisB@Cross-Check.com
Operations & Network Mgr  mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.                  http://www.cross-check.com
6119 State Farm Drive     Phone: 707 586-0551 x 1102
Rohnert Park CA  94928    Fax: 707 586-1884

-----Original Message-----
From: Joel Fritz [mailto:JFritz@sharperimage.com]
Sent: Friday, October 05, 2001 11:44 AM
To: 'midrange-l@midrange.com'
Subject: RE: qntc userid in a production batch job


I think it could work this way, but one of the obstacles is that when we
went to NT from Novell a few years back, the network userids were no longer
the same as the 400 userids. I could give public access to the share on the
NT box, but...  One way I know that works is to hard code a userid that
exists in both worlds and has synchronized passwords in the USER parm of the
SBMJOB command.  Seems that there could be a security problem, although I'm
pretty ignorant in that area.