Sponsored Content
Operating Systems AIX AIX Forum: FTP from AIX to Mainframe Post 303010089 by TechGyaann on Tuesday 26th of December 2017 12:09:03 PM
Old 12-26-2017
Error

Quote:
Originally Posted by bakunin
By NDM, i take it, you mean Connect:Direct? Connect:Direct is a file transfer solution for the host, because ftp (the protocol as well as the program) is part of (the) TCP/IP (stack). The hosts native network stack is SNA (or, more precisely "a SNA-based protocol stack"), though. Ones uses LU2-connections to transfer data in this environment.

So, you first need to determine if your hosts still talks over SNA to others. You need some complex machinery including a 3745 frontend-processor and a 3174-compatible cluster controller or a virtualised replacement for the latter (SNA gateway software usually acts as a 3174 with its own NCP to the host) to do so. Many companies have therefore cut their SNA networks and work exclusively over TCP/IP.

If your host uses TCP/IP you should stay away from FTP at all costs: use scp or (preferably) rsync which is both available for z/OS. These tools will save you perhaps days and weeks of shell-programming efforts because whatever you can come up with they do: out of the box and perhaps better.

I hope this helps.

bakunin
Thanks bakunin.., for taking your time and sharing your point.

But I am still not sure what is SNA, how to get if we have SNA.
Cant I just write a script to NDM the files from AIX to Mainframe server?

Sorry these questions might be silly., i totally don't know what NDM is.

Last edited by rbatte1; 12-27-2017 at 04:24 AM.. Reason: Removed smileys in quoted section by adding NOPARSE tags as appropriate
 

9 More Discussions You Might Find Interesting

1. AIX

Problems with SSH/SFTP between AIX and Mainframe

Hi, I'm not sure if this has been solved in this forum already but please do help me out if possible. Basically, I've already setup a passwordless SSH connection between 2 AIX IDs (say ID-1 and ID-2) with a Mainframe server ID (say MVSID). I'm able to successfully do an SSH from the AIX server to... (1 Reply)
Discussion started by: sambeet
1 Replies

2. AIX

Problem in ftpying the datasets containing comp values to AIX from mainframe

Hi, When i am trying to ftp COBOL generated data sets which contain comp values to AIX in ASCII mode. the comp values are getting corrupted. If i ftp the data set in binary mode it is working properly, but for this i have to change some compiler options in the COBOL. Also if i want to use the... (5 Replies)
Discussion started by: sekhar gajjala
5 Replies

3. UNIX for Advanced & Expert Users

AIX - FTP

Hello, I have a FTP script below that automatically send files to host. Currently, i am having problems if our network connection is down. Our host cannot receive a file once the network connect is down. Could there be a additional command that i need to add below so that it would not send... (4 Replies)
Discussion started by: vibora
4 Replies

4. AIX

ODBC Connectivity between Oracle10g on AIX and Mainframe

Hi, I have a task of setting up connectivity between Oracle 10g (AIX) and Mainframe (1 library). Went through couple of documents, forums, blogs etc. MY understanding is ODBC Generic Connectivity is free from Oracle side. Question: (may be dumb to you) 1. Has anybody done this and would... (3 Replies)
Discussion started by: jvmani_1
3 Replies

5. AIX

FTP on AIX

Hi All We have planned to communicate with our trading prtner via FTP. We both have servers running on AIX. We want to exchange files with each other via FTP. I am new to AIX. Any help appreciated:) Thanks:) (7 Replies)
Discussion started by: user1183
7 Replies

6. Shell Programming and Scripting

shell script returning error code 2 from AIX to Mainframe

Hi, I have a shell script which is residing on AIX which is triggered by Mainframe through Connect Direct. The shell script creates several files and sends those files to mainframe using Connect Direct. The shell script is working fine, still it is returning exit code 2 to mainframe. What... (0 Replies)
Discussion started by: Yogesh Aggarwal
0 Replies

7. AIX

Nim on AIX 7.1 used to migrate AIX 5.3 to AIX 6.1...is possible?

Using nimadm: nimadm -j nimadmvg -c sap024 -s spot_6100 -l lpp_6100 -d "hdisk1" -Y Initializing the NIM master. Initializing NIM client sap024. 0505-205 nimadm: The level of bos.alt_disk_install.rte installed in SPOT spot_6100 (6.1.3.4) does not match the NIM master's level (7.1.1.2).... (2 Replies)
Discussion started by: sciacca75
2 Replies

8. Shell Programming and Scripting

AIX FTP client

I am trying to transfer logs from Aix 6.1 to a linux appliance but it is not happening from last one month if i execute the batch command by command i can execute well but if i do it in shell script it is stuck without any error. Any one know how to generate a FTP client trace to know the issue... (10 Replies)
Discussion started by: ra8ul
10 Replies

9. Shell Programming and Scripting

FTP from AIX to Mainframe

Hi All, This is the scenario:- I am writing a script to automate FTP files from AIX to Mainframe. ( Binary mode, passive connection) FTP the currently available files(poll a directory to find the list) and put it to mainframe in one connection instance Verify if all the files are copied... (24 Replies)
Discussion started by: TechGyaann
24 Replies
netconfig(4)															      netconfig(4)

NAME
netconfig - network configuration database SYNOPSIS
/etc/netconfig The network configuration database, /etc/netconfig, is a system file used to store information about networks that are connected to the system. The netconfig database and the routines that access it (see getnetconfig(3NSL)) are part of the Network Selection component. The Network Selection component also includes getnetpath(3NSL) routines to provide application-specific network search paths. These routines access the netconfig database based on the environment variable NETPATH. See environ(5). netconfig contains an entry for each network available on the system. Entries are separated by newlines. Fields are separated by whitespace and occur in the order in which they are described below. Whitespace can be embedded as ``lank'' or `` ab''. Backslashes may be embedded as ``\''. Lines in /etc/netconfig that begin with a # (hash) in column 1 are treated as comments. Each of the valid lines in the netconfig database correspond to an available transport. Each entry is of the form: network ID semantics flag protocol-family protocol-name network-device translation-libraries network ID A string used to uniquely identify a network. network ID consists of non-null characters, and has a length of at least 1. No maximum length is specified. This namespace is locally significant and the local system administrator is the naming authority. All network IDs on a system must be unique. semantics The semantics field is a string identifying the ``semantics'' of the network, that is, the set of services it sup- ports, by identifying the service interface it provides. The semantics field is mandatory. The following semantics are recognized. tpi_clts Transport Provider Interface, connectionless tpi_cots Transport Provider Interface, connection oriented tpi_cots_ord Transport Provider Interface, connection oriented, supports orderly release. flag The flag field records certain two-valued (``true'' and ``false'') attributes of networks. flag is a string com- posed of a combination of characters, each of which indicates the value of the corresponding attribute. If the character is present, the attribute is ``true.'' If the character is absent, the attribute is ``false.'' ``-'' indicates that none of the attributes are present. Only one character is currently recognized: v Visible (``default'') network. Used when the environment variable NETPATH is unset. protocol family The protocol family and protocol name fields are provided for protocol-specific applications. The protocol family field contains a string that identifies a protocol family. The protocol family identifier follows the same rules as those for network IDs; the string consists of non-null characters, it has a length of at least 1, and there is no maximum length specified. A ``-'' in the protocol family field indicates that no protocol family identifier applies (the network is experimental). The following are examples: loopback Loopback (local to host). inet Internetwork: UDP, TCP, and the like. inet6 Internetwork over IPv6: UDP, TCP, and the like. implink ARPANET imp addresses pup PUP protocols: for example, BSP chaos MIT CHAOS protocols ns XEROX NS protocols nbs NBS protocols ecma European Computer Manufacturers Association datakit DATAKIT protocols ccitt CCITT protocols, X.25, and the like. sna IBM SNA decnet DECNET dli Direct data link interface lat LAT hylink NSC Hyperchannel appletalk Apple Talk nit Network Interface Tap ieee802 IEEE 802.2; also ISO 8802 osi Umbrella for all families used by OSI (for example, protosw lookup) x25 CCITT X.25 in particular osinet AFI = 47, IDI = 4 gosip U.S. Government OSI protocol name The protocol name field contains a string that identifies a protocol. The protocol name identifier follows the same rules as those for network IDs; that is, the string consists of non-NULL characters, it has a length of at least 1, and there is no maximum length specified. A ``-'' indicates that none of the names listed apply. The following pro- tocol names are recognized. tcp Transmission Control Protocol udp User Datagram Protocol icmp Internet Control Message Protocol network device The network device is the full pathname of the device used to connect to the transport provider. Typically, this device will be in the /dev directory. The network device must be specified. translation libraries The name-to-address translation libraries support a ``directory service'' (a name-to-address mapping service) for the network. A ``-'' in this field indicates the absence of any translation libraries. This has a special meaning for networks of the protocol family inet : its name-to-address mapping is provided by the name service switch based on the entries for hosts and services in nsswitch.conf(4). For networks of other families, a ``-'' indicates non- functional name-to-address mapping. Otherwise, this field consists of a comma-separated list of pathnames to dynam- ically linked libraries. The pathname of the library can be either absolute or relative. See dlopen(3C). Each field corresponds to an element in the struct netconfig structure. struct netconfig and the identifiers described on this manual page are defined in <netconfig.h>. This structure includes the following members: char *nc_netid Network ID, including NULL terminator. unsigned long nc_semantics Semantics. unsigned long nc_flag Flags. char *nc_protofmly Protocol family. char *nc_proto Protocol name. char *nc_device Full pathname of the network device. unsigned long nc_nlookups Number of directory lookup libraries. char **nc_lookups Names of the name-to-address translation libraries. unsigned long nc_unused[9] Reserved for future expansion. The nc_semantics field takes the following values, corresponding to the semantics identified above: NC_TPI_CLTS NC_TPI_COTS NC_TPI_COTS_ORD The nc_flag field is a bitfield. The following bit, corresponding to the attribute identified above, is currently recognized. NC_NOFLAG indicates the absence of any attributes. NC_VISIBLE Example 1: A Sample netconfig File Below is a sample netconfig file: # # The "Network Configuration" File. # # Each entry is of the form: # # <networkid> <semantics> <flags> <protofamily> <protoname> <device> # <nametoaddrlibs> # # The "-" in <nametoaddrlibs> for inet family transports indicates # redirection to the name service switch policies for "hosts" and # "services". The "-" may be replaced by nametoaddr libraries that # comply with the SVr4 specs, in which case the name service switch # will not be used for netdir_getbyname, netdir_getbyaddr, # gethostbyname, gethostbyaddr, getservbyname, and getservbyport. # There are no nametoaddr_libs for the inet family in Solaris anymore. # udp6 tpi_clts v inet6 udp /dev/udp6 - tcp6 tpi_cots_ord v inet6 tcp /dev/tcp6 - udp tpi_clts v inet udp /dev/udp - tcp tpi_cots_ord v inet tcp /dev/tcp - rawip tpi_raw - inet - /dev/rawip - ticlts tpi_clts v loopback - /dev/ticlts straddr.so ticotsord tpi_cots_ord v loopback - /dev/ticotsord straddr.so ticots tpi_cots v loopback - /dev/ticots straddr.so <netconfig.h> dlopen(3C), getnetconfig(3NSL), getnetpath(3NSL), nsswitch.conf(4) 18 Nov 2003 netconfig(4)
All times are GMT -4. The time now is 07:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy