Sponsored Content
Operating Systems AIX Lenovo v3700 v2 direct connect to AIX Post 303022179 by khalid khanAIB on Sunday 26th of August 2018 11:27:14 PM
Old 08-27-2018
Ok Next time i will take care of that . can i move now this question to AIX HOw please?

Code:
lscfg -vl fcs0
 fcs0             U78AA.001.WZSJK39-P1-C6-T1  8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)

        Part Number.................10N9824
        Serial Number...............1B1090430B
        Manufacturer................001B
        EC Level....................D77040
        Customer Card ID Number.....577D
        FRU Number..................10N9824
        Device Specific.(ZM)........3
        Network Address.............10000000C9B46932
        ROS Level and ID............02781174
        Device Specific.(Z0)........31004549
        Device Specific.(Z1)........00000000
        Device Specific.(Z2)........00000000
        Device Specific.(Z3)........09030909
        Device Specific.(Z4)........FF781116
        Device Specific.(Z5)........02781174
        Device Specific.(Z6)........07731174
        Device Specific.(Z7)........0B7C1174
        Device Specific.(Z8)........20000000C9B46932
        Device Specific.(Z9)........US1.11X4
        Device Specific.(ZA)........U2D1.11X4
        Device Specific.(ZB)........U3K1.11X4
        Device Specific.(ZC)........00000000
        Hardware Location Code......U78AA.001.WZSJK39-P1-C6-T1

As we are not using any switch in between so i think sddpcm or sdd will not be required ?




Moderator's Comments:
Mod Comment Please use CODE tags as required by forum rules!

Last edited by RudiC; 08-27-2018 at 04:52 AM.. Reason: Added CODE tags.
 

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. 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

5. 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

6. 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

7. 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

8. 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

9. AIX

StorWize v3700 and Power8 (S822) AIX, configuration best practice for LUNs?

Hello, We have an Power8 System (S822) and a IBM StorWize v3700 SAN. The OS is AIX 7.1. With this hardware from what I read I need to download/install special SDDPCM drivers, so I did (SDDPCM VERSION 2.6.6.0 (devices.sddpcm.71.rte). I carved my volumes in the StorWize and presented to... (3 Replies)
Discussion started by: c3rb3rus
3 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
CUDA Runtime API Specific Functions(3)			     Hardware Locality (hwloc)			    CUDA Runtime API Specific Functions(3)

NAME
CUDA Runtime API Specific Functions - Functions static inline int hwloc_cudart_get_device_pci_ids (hwloc_topology_t topology , int idx, int *domain, int *bus, int *dev) static inline int hwloc_cudart_get_device_cpuset (hwloc_topology_t topology , int idx, hwloc_cpuset_t set) static inline hwloc_obj_t hwloc_cudart_get_device_pcidev (hwloc_topology_t topology, int idx) static inline hwloc_obj_t hwloc_cudart_get_device_osdev_by_index (hwloc_topology_t topology, unsigned idx) Detailed Description Function Documentation static inline int hwloc_cudart_get_device_cpuset (hwloc_topology_t topology, intidx, hwloc_cpuset_tset) [static] Get the CPU set of logical processors that are physically close to device idx. Return the CPU set describing the locality of the CUDA device whose index is idx. Topology topology and device idx must match the local machine. I/O devices detection and the CUDA component are not needed in the topology. The function only returns the locality of the device. If more information about the device is needed, OS objects should be used instead, see hwloc_cudart_get_device_osdev_by_index(). This function is currently only implemented in a meaningful way for Linux; other systems will simply get a full cpuset. static inline hwloc_obj_t hwloc_cudart_get_device_osdev_by_index (hwloc_topology_ttopology, unsignedidx) [static] Get the hwloc OS device object corresponding to the CUDA device whose index is idx. Return the OS device object describing the CUDA device whose index is idx. Return NULL if there is none. The topology topology does not necessarily have to match the current machine. For instance the topology may be an XML import of a remote host. I/O devices detection and the CUDA component must be enabled in the topology. If not, the locality of the object may still be found using hwloc_cudart_get_device_cpuset(). Note: The corresponding PCI device object can be obtained by looking at the OS device parent object. This function is identical to hwloc_cuda_get_device_osdev_by_index(). static inline int hwloc_cudart_get_device_pci_ids (hwloc_topology_t topology, intidx, int *domain, int *bus, int *dev) [static] Return the domain, bus and device IDs of the CUDA device whose index is idx. Device index idx must match the local machine. static inline hwloc_obj_t hwloc_cudart_get_device_pcidev (hwloc_topology_ttopology, intidx) [static] Get the hwloc PCI device object corresponding to the CUDA device whose index is idx. Return the PCI device object describing the CUDA device whose index is idx. Return NULL if there is none. Topology topology and device idx must match the local machine. I/O devices detection must be enabled in topology topology. The CUDA component is not needed in the topology. Author Generated automatically by Doxygen for Hardware Locality (hwloc) from the source code. Version 1.7 Sun Apr 7 2013 CUDA Runtime API Specific Functions(3)
All times are GMT -4. The time now is 12:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy