11-24-2008
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 needs to be fetched from
the client server.
nctrl is where it gets stored on our local machine.
xhost is the host name.
when i try executing the above command ,its throwing an error saying "failed to submit connect direct request"
what could be the problem?
Appreciate ur help,
Sheema
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
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. 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
3. Red Hat
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
4. Shell Programming and Scripting
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
5. Shell Programming and Scripting
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 (1 Reply)
Discussion started by: karthikm
1 Replies
6. Shell Programming and Scripting
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
7. Red Hat
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
8. UNIX for Dummies Questions & Answers
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
9. AIX
i have directly connect AIX pwer 7 to lenovo v3700 v2 without San through fiber card. but i cannot see the WWPN to add AIX as host in management console. (10 Replies)
Discussion started by: khalid khanAIB
10 Replies
10. UNIX for Advanced & Expert Users
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
XHOST(1) General Commands Manual XHOST(1)
NAME
xhost - server access control program for X
SYNOPSIS
xhost [[+-]name ...]
DESCRIPTION
The xhost program is used to add and delete host names or user names to the list allowed to make connections to the X server. In the case
of hosts, this provides a rudimentary form of privacy control and security. It is only sufficient for a workstation (single user) environ-
ment, although it does limit the worst abuses. Environments which require more sophisticated measures should implement the user-based
mechanism or use the hooks in the protocol for passing other authentication data to the server.
OPTIONS
Xhost accepts the following command line options described below. For security, the options that effect access control may only be run
from the "controlling host". For workstations, this is the same machine as the server. For X terminals, it is the login host.
-help Prints a usage message.
[+]name The given name (the plus sign is optional) is added to the list allowed to connect to the X server. The name can be a host name or
a user name.
-name The given name is removed from the list of allowed to connect to the server. The name can be a host name or a user name. Existing
connections are not broken, but new connection attempts will be denied. Note that the current machine is allowed to be removed;
however, further connections (including attempts to add it back) will not be permitted. Resetting the server (thereby breaking all
connections) is the only way to allow local connections again.
+ Access is granted to everyone, even if they aren't on the list (i.e., access control is turned off).
- Access is restricted to only those on the list (i.e., access control is turned on).
nothing If no command line arguments are given, a message indicating whether or not access control is currently enabled is printed, fol-
lowed by the list of those allowed to connect. This is the only option that may be used from machines other than the controlling
host.
NAMES
A complete name has the syntax ``family:name'' where the families are as follows:
inet Internet host
dnet DECnet host
nis Secure RPC network name
krb Kerberos V5 principal
local contains only one name, the empty string
The family is case insensitive. The format of the name varies with the family.
When Secure RPC is being used, the network independent netname (e.g., "nis:unix.uid@domainname") can be specified, or a local user can be
specified with just the username and a trailing at-sign (e.g., "nis:pat@").
For backward compatibility with pre-R6 xhost, names that contain an at-sign (@) are assumed to be in the nis family. Otherwise the inet
family is assumed.
DIAGNOSTICS
For each name added to the access control list, a line of the form "name being added to access control list" is printed. For each name
removed from the access control list, a line of the form "name being removed from access control list" is printed.
FILES
/etc/X*.hosts
SEE ALSO
X(7x), Xsecurity(7x), Xserver(1), xdm(1)
ENVIRONMENT
DISPLAY to get the default host and display to use.
BUGS
You can't specify a display on the command line because -display is a valid command line argument (indicating that you want to remove the
machine named ``display'' from the access list).
The X server stores network addresses, not host names. This is not really a bug. If somehow you change a host's network address while the
server is still running, xhost must be used to add the new address and/or remove the old address.
AUTHORS
Bob Scheifler, MIT Laboratory for Computer Science,
Jim Gettys, MIT Project Athena (DEC).
X Version 11 Release 6.6 XHOST(1)