Sponsored Content
Top Forums Shell Programming and Scripting Connect Direct for copying files from Mainframes to UNIX Post 302695929 by karthikm on Tuesday 4th of September 2012 05:34:19 AM
Old 09-04-2012
Connect Direct for copying files from Mainframes to UNIX

Hai Friends,

Please help me in providing unix shell script for pulling data from mainframe dataset to unix using connect direct (NDM).

Thanks in advance
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

How to direct-connect two UNIX boxes

Hello, I have a V880 and a 420 running Solaris 9. Each box has more than one NIC card. I'd like to know how to configure the network on the two boxes so that I can directly connect the NIC cards. Meaning, I don't want a switch or router between the two. I just want to run a CAT5 cable to each... (3 Replies)
Discussion started by: agcodba
3 Replies

2. Shell Programming and Scripting

Problem using connect direct

Hi, I have a script in which i'm using ndm connect direct to fetch data from the client server..syntax i'm using is ./con_using_connectdirect /load/nctrl nctrl $xhost where con_using_connectdirect is the script which establishes connection load/nctrl is the path from where data... (4 Replies)
Discussion started by: Sheema
4 Replies

3. Solaris

Connect direct configuration on Solaris

Hi, I am configuring Connect direct on Solaries 6.0, but whenever i am giving the below command cdpmgr -i /export/app/cdunix/ndm/cfg/khello/initparm.cfg i am getting the message Component <cdpmgr ndmcmgr ndmsmgr ndmumgr cdstatm> permissions are not set. Please follow instructions in the... (3 Replies)
Discussion started by: sidd
3 Replies

4. Shell Programming and Scripting

Shell Script to connect to another server and copying files

Hi Unix Gurus, I have a doubt reg file transfer. I have used the below script to connect to another server and find files having modified for the last 24 hours and have to move the file to another server. While i tried i am getting authentication failed, destination path not found issue. ... (2 Replies)
Discussion started by: incepted
2 Replies

5. Red Hat

IBM Connect:Direct Error

Hi to all, I've installed IBM Connect:Direct 4.1.00 on Red Hat Enterprise Linux Server release 5.5, but when I try to execute the "direct cli", I obtain the following error: $ ./direct *********************************************************** * ... (2 Replies)
Discussion started by: f.vietti
2 Replies

6. Shell Programming and Scripting

Connect:Direct

Hello all, I have a requirement to transfer files to mainframe usinf NDM connect:direct. So can anybody provide me a sample shell script on how to call a connect;direct script by providing filename as a parameter please? Thanks, Ajay (0 Replies)
Discussion started by: ajaykumar4534
0 Replies

7. Shell Programming and Scripting

Connect direct script for unix

I want to connect direct a xml file and a excel file each separately from unix system to another unix system.The size of the xml file and excel file may vary each time. Below is the possible connect direct script to transfer the files.Please check if it is correct? Also does DCB parameter... (4 Replies)
Discussion started by: bk_12345
4 Replies

8. Red Hat

Linux to Connect direct transfer

I am transfering a file using connect direct from Linux to Mainframe. Its a point to point transfer but its failing with below error: **** Error from CONNECT:Direct API - ndmapi_recvresp_c error Can we do PTP transfers? code tags for code, please. (1 Reply)
Discussion started by: gerryperillo
1 Replies

9. UNIX for Dummies Questions & Answers

Issue with Connect direct ndmcli

Hi.. We are using connect direct to transfer the files between servers. The CD scripts run on HP UX. Below is the code using ndmcli. ndmcli -x << EOJ submit maxdelay=0 proc1 process snode=$3 step1 ... (1 Reply)
Discussion started by: anijan
1 Replies

10. UNIX for Advanced & Expert Users

Connect direct - SFTP - List of servers that I can connect

Greetings Experts, I am working for a bank client and have a question on connect-direct and SFTP. We are using Linux RedHat servers. We use connect-direct to transfer (NDM) files from one server to another server. At times, we manually transfer the files using SFTP from one server to another... (2 Replies)
Discussion started by: chill3chee
2 Replies
GETPEEREID(3)						   BSD Library Functions Manual 					     GETPEEREID(3)

NAME
getpeereid -- get the effective credentials of a UNIX-domain peer LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
#include <sys/types.h> #include <unistd.h> int getpeereid(int s, uid_t *euid, gid_t *egid); DESCRIPTION
The getpeereid() function returns the effective user and group IDs of the peer connected to a UNIX-domain socket. The argument s must be a UNIX-domain socket (unix(4)) of type SOCK_STREAM on which either connect(2) or listen(2) have been called. The effective used ID is placed in euid, and the effective group ID in egid. The credentials returned to the listen(2) caller are those of its peer at the time it called connect(2); the credentials returned to the connect(2) caller are those of its peer at the time it called listen(2). This mechanism is reliable; there is no way for either side to influence the credentials returned to its peer except by calling the appropriate system call (i.e., either connect(2) or listen(2)) under different effective credentials. One common use of this routine is for a UNIX-domain server to verify the credentials of its client. Likewise, the client can verify the cre- dentials of the server. IMPLEMENTATION NOTES
On FreeBSD, getpeereid() is implemented in terms of the LOCAL_PEERCRED unix(4) socket option. RETURN VALUES
The getpeereid() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to indi- cate the error. ERRORS
The getpeereid() function fails if: [EBADF] The argument s is not a valid descriptor. [ENOTSOCK] The argument s is a file, not a socket. [ENOTCONN] The argument s does not refer to a socket on which connect(2) or listen(2) have been called. [EINVAL] The argument s does not refer to a socket of type SOCK_STREAM, or the kernel returned invalid data. SEE ALSO
connect(2), getpeername(2), getsockname(2), getsockopt(2), listen(2), unix(4) HISTORY
The getpeereid() function appeared in FreeBSD 4.6. BSD
July 15, 2001 BSD
All times are GMT -4. The time now is 05:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy