Search Results

there are a few things you can do
Kill -6 will crate a coredump

kill -l will provide you with a full list of kill codes
in AIX you can now control where you want any core dumps to go ...

jfs2 is all you need to know there is no real bennifit in using jfs any more

may be usefull to look at the output from
lsvg |lsvg -il
lsvg |lsvg -ip
Studdy this output and see what is going on
Now you will be able to see if one or more mirrors are stale and if there...

There are many ways in which you can keep the systems in sync
1 Using Rsync Copy from one system to the other directly
This also alows cloning of directories , exports...

This will allow you to check all network settings on your system


#!/bin/ksh
#for i in `lsdev -Cc if |grep en |awk '{print $1}'`
for i in 0 1 2 3 4 5 6 7 8 9 ; do
ifdev=`lsdev -C |grep...

It refers to your operating system settings

smitty system changes sys0 as well


have a look at smitty chgsys and compare to output from lsattr -EL sys0

lquerypv -h ./core

Also to findout what cause the system core use this
lquerypv -h ./core 6b0 64

try using diag

chvg -G

Extended Error Handling (EEH) device drivers that allow recovery from intermittent PCI bus errors. This approach works by recovering and resetting the adapter, thereby initiating system recovery for...

go to www-912.ibm.com/pod/pod

make sure you have a code that show you vet on the system you are looking at
then speak to support to help you find out what is going on

YOU WILL HAVE TO SEE WHAT IS IN
/etc/security/user

AS THIS RESTRICTS THE SYSTEM EVEN MORE
also have a look at
the /etc/security/login.cfg
make sure that Ldap is not configerd on this...

mkdvd -d /dev/cd0 -m /fullpath_to_mksysb_image


From one system to other
===================
smitty mkdvd
use an existing mksysb image? --> no
Select format
-->leave DVD-R or DVD-RAM Device...

I use this to find my big file bud do not use it in / as it will find all the big files on a system.

This version will only give you name and size and sort it by the bigest at the top.


...

SCRIPT bla
bla
mail_to="yourmail@mail1 othermail@mail"
/bin/mailx -s "`uname -n|tr '[a-z]' '[A-Z]'` Backup Report `" $mail_to < /tmp/bkp_monitor.log.$$

bla
#end script

Sorry I should have explaned some more the information is in the output as well
you get the model number ( 2107900) storage

Pop this in to GOOGle and you will findout what you have IBM Model...

Normaly you have to have a look at the disks

lscfg -vlp hdiskxx
this should be done on any disk that you need to find out

-----Post Update-----

sorry


-----Post Update-----

sorry...

This is related to boot device could not be opened or read you may have to do mksysb recovery of your system.

There is a few thing that could cause this problem

One that I have come across is settings in the system that will cause the system not to boot

One like lgpg_regions or lgpg_size If this is...

There are no obvious and known limitations by default.


/etc/services is read via getservent > line by line > first match wins
There may a line lenth limit but I have used port 80000 be for for...

make sure you have installed the corect device driver for this tape ( lib )
cfgmgr
then you can use tapeutil
tctl or mt -f /dev/rmtX - rewind


Also have a lookat
Rosetta Stone for...

You will have to ask IBM to help you fix this

There are a few things that I know you need to have a look
If you are using the new 450 disks and you are using space efficient flash copy you...

Now then you use

chvg -G vgname


This will pick up the changes

Yes you will have to unmap the disk and remap it back to the Lpar

if the Lpar is up you may have to export the vg (not rootvg )
Unmap the disk in the vioserver ( rmdev -dev device_name )
remap...

to findout what it is have a look at this

oslevel -r
oslevel -rq
5300-09
5300-08
5300-07

then use the top one fro the following command

eg
oslevel -rl 5300-09

this will tel you...