Have you have worked with Connect:Direct HP NonStop? I wish to make the transmission of a file located in 'OSS' HP NonStop to UNIX.
Connect:Direct run it through NDMCOM in GUARDIAN90 but can not interpret my route home from OSS, they will have some idea of missing my script to reconnoitre the route of OSS?
Below I add my script and messages received from the execution of the process.
my process:
SEND PROCESS SNODE=TEST.HPTEST SNODEID=(user,passwd)
STEP01 COPY FROM (FILE=/home/sat/origen.txt - SYSOPTS=":datatype=binary:" – PNODE) - TO (FILE='/home/user/destino.txt' - SYSOPTS=":datatype=binary:" - DISP = RPL SNODE)messages:
2 Related questions 1 Hpux telnet using socket 1 Idle tcp file descriptor after failed connect on HPUX 0 hp -ux remote cpio copy Related questions 1 Hpux telnet using socket 1 Idle tcp file descriptor after failed connect on HPUX 0 hp -ux remote cpio copy 3 How to send simple text file as attachment using HP-UX shell script? 2 How do you transfer a binary file via Connect:Direct NDM? 0 Sending files through connect direct from UNIX to MAINFRAME 1 Transferring files from Windows to HP NonStop using FTE 10 transfer files from unix to windows using java 0 Connect Direct : File sending from Mainframe to Unix 1 How to transfer a file from unix server to windows pc Load 7 more related questions Show fewer related questions Reset to default**XSMG622I: (RC=8, FDBK="0")
An exception response was received during process exec.
An exception response was received from the remote node
during process execution.SYSTEM ACTION: The copy step was aborted.
RESPONSE: Check the condition of the copy step and resubmit the copy step.**SFLH055I: (RC=8, FDBK="13")
source DSN can only be a disk/ spooler file : \DESA.$OSS./home/sat/origen.txt