10 More Discussions You Might Find Interesting
1. AIX
This is getting very confusing for me, and appreciate if someone can help.
Platform: Power VM ( Virtual I/O Server)
ioslevel 2.1.3.10-FP23
# oslevel -s
6100-05-00-0000
Storage: IBM DS4300
Two HBAs - Dual Port Fibre Adapter Channels
Each card has two ports , so a total of 4 ports going... (3 Replies)
Discussion started by: filosophizer
3 Replies
2. Hardware
In general terms what are the differences platform driver,codec driver and Machine driver? (1 Reply)
Discussion started by: rupeshkp728
1 Replies
3. AIX
hi all
we recently upgraded our san switches. after that, i found i got many hdisks showing in lsdev with status "Defined" and "Available". the number of "Defined" is equal to "Available". the time stamp shows all "Available" disks created at our downtime night.
"datapath query device"... (0 Replies)
Discussion started by: rs6000er
0 Replies
4. UNIX for Dummies Questions & Answers
Help, suspect hacked via serial or electric! any ideas on error "Pid:1, comm:swapper Tainted:G W 2.6.35-22 generic #33 -unbutu device = "(null)" or unknown-blocklist(8.1) please append a correct "root"boot option Available partitions 0b00 1048575 sr0 driver:sr 0800 488386584 sda driver:sd. Thanks... (3 Replies)
Discussion started by: kryclear
3 Replies
5. AIX
I have sdd driver installed correctly but
when I run the command:
datapath query adapter
No device file found
what does it mean.. it is not using vpath or whats wrong? (2 Replies)
Discussion started by: Vit0_Corleone
2 Replies
6. AIX
Hi folks.
We want to move a "physical" AIX box to a VIOed LPAR. The physical box is running SDD with disks from a DS8300. I want to be able to reattach those LUNs from the DS8300 to my VIO server which is running SDDPCM and then assigned them back to my AIX LPAR. Any thoughts about this?
I... (1 Reply)
Discussion started by: Stephan
1 Replies
7. Filesystems, Disks and Memory
Hello Unix Admins:
Has any one in this distribution list implemented SVC (SAN Volume Contoller - A solution from IBM) in your environment? If you have, do you have any do's / don'ts? Anything which you like sharing would be really appreciated.
For example, my inputs:
I tried implementing... (1 Reply)
Discussion started by: kdossjojo
1 Replies
8. UNIX for Dummies Questions & Answers
Hi...
I m working on UNIX z/OS. Actually i have to pass the parameters from the JCL to java-db2 program thru PARM. I am able to pass the arguments but the problem occured is, it is throwing an exception while loading the db2 driver as 'Javaclassnotfound:com.ibm.db2.jcc.DB2Driver'... (0 Replies)
Discussion started by: Sujatha Gowda
0 Replies
9. Solaris
I've been researching minimizeing Solaris 8 and found that on the web page http://www.sun.com/bigadmin/content/packagelist/s8u7PkgList/p2.html the package SUNWglmr
is listed as "rasctrl environment monitoring driver for i2c, (Root) (32-bit)" while in the document "Solaris 8 minimize-updt1.pdf"... (1 Reply)
Discussion started by: roygoodwin
1 Replies
10. Solaris
I just installed IBMsddsun64_........... on my sun server. I untarred it (tar xvf) & I tried to install the paxkage. When I did pkgadd -d ./IBMsdd..... I get a message Error, no packages were found.
Any idea
Thanks, (1 Reply)
Discussion started by: Remi
1 Replies
cfgmgr_set_status(9r) cfgmgr_set_status(9r)
NAME
cfgmgr_set_status - General: Reports failure to the cfgmgr framework
SYNOPSIS
int cfgmgr_set_status(
char *driver_name );
ARGUMENTS
Specifies the name of the device driver for which you want to report an associated failure. This name is a string that matches the string
you specified for the entry_name item in the /etc/sysconfigtab database. Typically, third-party driver writers specify the driver name
(followed by a colon) in the sysconfigtab file fragment, which gets appended to the /etc/sysconfigtab database during the driver product
installation.
DESCRIPTION
The cfgmgr_set_status routine reports to the cfgmgr framework that a failure has occurred during static configuration. If the specified
device driver is in the static configuration state, it does not know that the configuration operation is complete until all register call-
back requests (routines) have successfully completed. Therefore, a device driver calls cfgmgr_set_status to report a possible failure dur-
ing static configuration to the cfgmgr framework.
Specifically, cfgmgr_set_status performs the following failure operations: Adjusts the state of the specified device driver Unconfigures
the specified device driver from the cfgmgr framework
The cfgmgr_set_status routine calls the device driver's configure routine at its CFG_OP_UNCONFIGURE entry point as part of these failure
operations. The code associated with the CFG_OP_UNCONFIGURE entry point is responsible for determining how to deallocate any allocated
resources during these failure operations.
The cfgmgr_set_status routine does not notify the operator of a configuration failure. Part of the code associated with the CFG_OP_UNCON-
FIGURE entry point could include an error logging operation to record the fact that a failure has occurred. The reason for doing this is
that the cfgmgr framework's task is to accomplish the unconfigure operation of a statically configured device driver.
You call the cfgmgr_set_status routine in the device driver's callback routine when the static configuration operation fails. You register
a callback routine by calling the register_callback routine.
RETURN VALUES
Upon successful completion, cfgmgr_set_status returns the value ESUCCESS. This success value indicates that cfgmgr_set_status adjusted the
state of the device driver and caused the cfgmgr framework to unconfigure the driver. Otherwise, cfgmgr_set_status returns one of the fol-
lowing error constants defined in /usr/sys/include/sys/sysconfig.h and /usr/sys/include/sys/errno.h: The device driver that you specified
in the driver_name argument does not exist. In this case, cfgmgr_set_status cannot adjust the state and unconfigure the device driver. The
device driver that you specified in the driver_name argument was not statically configured. The device driver that you specified in the
driver_name argument is not in the static configuration state.
EXAMPLES
See Writing Device Drivers: Tutorial for a code example of the cfgmgr_set_status interface.
SEE ALSO
Routines: cfgmgr_get_state(9r), register_callback(9r)
cfgmgr_set_status(9r)
