Operating System - HP-UX
1755672 Members
3827 Online
108837 Solutions
New Discussion юеВ

Re: Connect direct (for encrypting) version 3.6.00

 
SOLVED
Go to solution
Manuales
Super Advisor

Connect direct (for encrypting) version 3.6.00

Hi ...
anybody of your knows about connect direct for unix??
I need learn about this ...

Thamks, Manuales.
7 REPLIES 7
David DiBiase
Frequent Advisor
Solution

Re: Connect direct (for encrypting) version 3.6.00

Connect:Direct is a product from sterling commerce. 1 of our clients has us use it for secure 'ftp-like' communication with an IBM Mainframe system. Thats about all I know. Here the vendors web site:
http://www.sterlingcommerce.com/
HTH
Dave
Manuales
Super Advisor

Re: Connect direct (for encrypting) version 3.6.00

Thank you !!!
do you know use this software?

Manuales.
David DiBiase
Frequent Advisor

Re: Connect direct (for encrypting) version 3.6.00

The following is the only example I could find for copying a file to or from another machine. Everything within the EOJ's is using the direct command syntax.

cdfrom=$1
cdto=$2
snode=$3
CDDIR=/FS1/sys/connectdirect
NDMAPICFG=$CDDIR/ndm/cfg/cliapi/ndmapi.cfg

export cdfrom cdto snode CDDIR NDMAPICFG

$CDDIR/ndm/bin/direct -x << EOJ
submit maxdelay=unlimited
label process snode=$snode
step01
copy from (file=$cdfrom pnode)
to (dsn=$cdto disp=rpl snode)
pend;
EOJ

SAVE=$?
echo $SAVE

if [[ $SAVE > 0 ]]
then
echo "Error: $SAVE"
exit 1
fi

echo "No error"
exit 0
Dave La Mar
Honored Contributor

Re: Connect direct (for encrypting) version 3.6.00

Manuales -
Though we have not yet to use it, it is functional on our 11.0.
The installation was straightforward. Note that we installed the client.
This was installed so that we may perform file transfers to the server owned by a banking institution. (Their insistance on our using it, thus they supplied the client.)

Attached is the manual used in the installation.

Best of luck.

Regards,

dl
"I'm not dumb. I just have a command of thoroughly useless information."
Dave La Mar
Honored Contributor

Re: Connect direct (for encrypting) version 3.6.00

Sorry, forgot the attachment.
"I'm not dumb. I just have a command of thoroughly useless information."
Steve Lewis
Honored Contributor

Re: Connect direct (for encrypting) version 3.6.00

We were forced to use it too. It was originally a mainframe file transfer product. All the syntax is very mainframe-ish, with jobs that need to be defined and submitted. Internally it appears to work just like rcp.
It requires a job control daemon to be running all the time. There is an installation subtree (we put it in /opt) and this contains quite a few configuration files. The syntax takes a lot of learning and the log files terribly cryptic although they are quite comprehensive. In all its a lot easier for a UNIX person to use sftp instead and probably more secure, but you know what banks are like when it comes to their standards...
I just wish they would install PGP and sftp on their mainframes instead.

Kok HPG
New Member

Re: Connect direct (for encrypting) version 3.6.00

I use a script in the same way too.

Only thing is...
When running script in unix and echoing $?, it says 0.
The file has been succesfully send, but looking in the ndm logging it says:
STAR=20070604 14:46:08|RECI=CXIT|RECC=CAEV|MSGT=Pnode SMGR exited. Pid=438278. Exitcode=1.

Anyone an idea why in ndm logging result is Exitcode=1 ? Is this standard or is there a small problem (although a succesfull copy) ??

Thx, Hans