C:D job running on the NT server... copies file on NT server to AS400 server, then force-initiates a job on the AS400.
From what you've posted, my code might look something like this:
STEP1 COPY
FROM (
PNODE
FILE=NT filename
TO (
SNODE
FILE=libraryname/filename
STEP2 CALL
libraryname/programname
(is this a valid C:D request? currently we use "RUN JOB SNODE (job)" to execute)
Is this correct?
My other concern is about any sysopt or file parameters needed to put the file on the AS400. When we do this same copy from NT to MVS, we use parameters like "DISP", "DCB", "SPACE", and "UNIT" to define the file. When we copy to NT, we often use a "SYSOPTS" statement to define the file as either ascii or binary. I'm just concerned / curious as to whether I need similar parameters for the AS400, or if the "FILE=" is enough.
Darrell
Main Topics
Browse All Topics





by: Mind_nlPosted on 2005-02-11 at 03:33:25ID: 13284518
to start the AS/400 filename would be formated like this: libraryname/filename
to start a program on the AS/400 you use: call libraryname/programname
I'm running connect:direct to transfer data between several AS/400 systems but have never used it on NT. Are you sending the file from NT to the AS/400 or are your recieving and NT file on the AS/400? (where is the sending connect:direct job running, on NT or 400?)