RE: qntc userid in a production batch job

[Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>]

Is it possible to set the share up as public write only?  This way the AS400
can write to the share but not alter/delete/read it.  I have run into this
user id problem with trying to use my magstar tape drive for backing up the
NT shares.

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 8:04 AM
To: MIDRANGE-L@midrange. com (E-mail)
Subject: qntc userid in a production batch job


Discussion of QNTC here yesterday made me look at it again.  It worked for
us under v4r3 and didn't under v4r4.  We went to v4r5 a couple of weeks ago
and now it works.  We have a data mart product running on NT that gets text
files from the 400 daily.  I'd like to replace the FTP session initiated on
the NT box with something that is controlled by the job on the 400 that
creates the text files.  I could enable the FTP server on the NT box and run
the FTP session from the 400, but I think it would be more elegant (and
conserve disk space) to do a cpytoimpf directly to the directory on the NT
machine.

Any thoughts on how to handle the userid problem?  The job that interacts
with the NT box needs to have a userid and password that exist on the NT
box, unless there's a way around it.  The job that extracts the data is a
production batch job run nightly.
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.