Why not turn the table: make the Windows server define a shared
directory which points to the IFS of the AS/400? That's easier done than
trying to find out which API's to use to use the shared folders of any
particular server. This design scales up better as well, if another
server were ever to be serviced, hardly anything would have to change
for your program (and nothing for the server either....). Low impact,
low cost...
As for the question "how to prevent premature reading of the
beforementioned file?" I would suggest that a semaphore file to be used,
which is set by the process accessing the file:
- semaphore.LIS (locked by Iseries)
- semaphore.WSR (locked by Windows Server)
- semaphore.FRE (no lock)
And if you want to be absolutely very sure you could semaphore the
semaphore indicating which server last accessed the file... Or you could
vary the name of the file being written, or... Well there are various
alternatives.
Cor
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Dave Murvin
Sent: woensdag 22 augustus 2007 22:40
To: rpg400-l@xxxxxxxxxxxx
Subject: Write directly to 2003 Windows Server
Hello,
I am working on an application that needs to read program described
files on the iSeries and write them as a stream file on a 2003 Windows
Server. I am in the process of testing an RPGLE program (using
C-Functions) that will write a stream file to the IFS, but am not sure
what I need to do to be able to write directly to the Windows Server.
Do I just change the directory?
Thanks
Dave
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
midrange.com
