Hitachi Device Manager Agent for HPUX Post: 302736555

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unix Device Manager?

I am a complete noob trying to learn my way around Solaris. I need to learn it for work so I though the best way to do that would be to go ahead and load it up and play with it. I downloaded the latest version from the Sun website and put it on a box with an AMD processor and Via Chipset KM400. ...

2. Filesystems, Disks and Memory

hpux vg accessible but device files missing!

Hi all, I am looking at a MC cluster comprised of 2 nodes. There is a package named backup which does nothing more than mount a VG. At one point we noticed errors in syslog that look like this: cmclconfd: Could not access device file /dev/dsk/c20t0d0: No such file or directory There are...

3. Solaris

Solaris & Hitachi identify

Hello, Is there anyway to tell which set of Hitachi array the disks belong to? I'm remotely located so I cannot do the physical check. The possible Hitachi arrays are: AMS1000 and 9570 This is what I see on the format: 2. c2t50060E800475EA02d1 <HITACHI-OPEN-V*9-SUN-5007 cyl 65533 alt 2...

4. UNIX for Dummies Questions & Answers

snmp manager and agent

Hi, I'm reading net-snmp, using Unix (Solaries) and C language ... - I can manipulate variable (managed object) declared in agent, but the manager can't see that ... it only see the initialization and the value which it ulters using snmpset ... Ex: Agent: static int ...

5. Shell Programming and Scripting

Need Script to Use CPUs on a HPUX server to simulate Workload Manager on HPUX.

I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas?

6. HP-UX

Hitachi arrays to HP-UX 11.11

We have 2 servers (L1000 and rp7410) running 11.11. We would like to hook them up to either a Hitatchi AMS 2500 or Hitachi USPV via fiber channel. I need to what drivers I need for this and if it will work. Oh, they are using HP Tachyon XL2 Fiber Channel Mass Storage Adapters. Thanks, Bill

7. Solaris

Hitachi Airis Mate 2007, Unix 5.0

Hello everyone! Today we have a problem and decided to ask people on this forum maybe someone can help. At our medical center we have an Hitachi Airis Mate MRI system, yom 2007 with Unix OS (don't know exactly the version). As usually, in the morning we started up the system normally and it...

8. AIX

Aix and Storage Hitachi

Hello everyone I would like to hear your opinions about Aix 6.1 and Aix 5.3 with Storage Hitachi the model is USP VM. We buy it and I want to know day to day task with this storage and Aix. Thanks for your comments. Best wishes for this 2010

9. Hardware

Hitachi HD issues

I have an adapter that can read ide and sata HD's. When the drive is good it lights up green and when its bad it lights up red. I have used the adapter already to read about 10 other HD's with no problem. When I got to the hitachi HD it lights up green but I can't see what is on it or even format....

LEARN ABOUT OPENSOLARIS

dat_cno_create

dat_cno_create(3DAT)				     Direct Access Transport Library Functions				      dat_cno_create(3DAT)

NAME

       dat_cno_create - create a CNO instance

SYNOPSIS

       cc [ flag... ] file... -ldat [ library... ]
       #include <dat/udat.h>

       DAT_RETURN
	   dat_cno_create (
	   IN	 DAT_IA_HANDLE		  ia_handle,
	   IN	 DAT_OS_WAIT_PROXY_AGENT  agent,
	   OUT	 DAT_CNO_HANDLE 	  *cno_handle
	   )

PARAMETERS

       ia_handle     Handle for an instance of DAT IA.

       agent	     An  optional  OS  Wait Proxy Agent that is to be invoked whenever CNO is invoked. DAT_OS_WAIT_PROXY_AGENT_NULL indicates that
		     there is no proxy agent

       cno_handle    Handle for the created instance of CNO.

DESCRIPTION

       The dat_cno_create() function creates a CNO instance. Upon creation, there are no Event Dispatchers feeding it.

       The agent parameter specifies the proxy agent, which is OS-dependent and which is invoked when the CNO is triggered. After it  is  invoked,
       it is no longer associated with the CNO. The value of DAT_OS_WAIT_PROXY_AGENT_NULL specifies that no OS Wait Proxy Agent is associated with
       the created CNO.

       Upon creation, the CNO is not associated with any EVDs, has no waiters and has, at most, one OS Wait Proxy Agent.

RETURN VALUES

       DAT_SUCCESS		     The operation was successful.

       DAT_INSUFFICIENT_RESOURCES    The operation failed due to resource limitations.

       DAT_INVALID_HANDLE	     The ia_handle parameter is invalid.

       DAT_INVALID_PARAMETER	     One of the parameters was invalid, out of range, or a combination of parameters was  invalid,  or	the  agent
				     parameter is invalid.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |Standard: uDAPL, 1.1, 1.2    |
       +-----------------------------+-----------------------------+
       |MT-Level		     |Safe			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       libdat(3LIB), attributes(5)

SunOS 5.11							    16 Jul 2004 					      dat_cno_create(3DAT)