hi.... i went through my logfiles.. and saw the below commands. need
your confirmation. pardone my for my ignorance...

1) Are sysdumpdev and sysdumpdev –l same commands?
a) sysdumpdev –l gives

primary /dev/pridumpdev
secondary /dev/secdumpdev
copy directory /var/adm/ras
forced copy flag TRUE
always allow dump TRUE
dump compression OFF

b) sysdumpev, I don't dare to issue..

Before doing a shutdown –ry 0, necessary to do a sync? We need to do
sync, when we re-configures our volumegroup such as deactivateas, and
remore vgs thru varyoffvg and exportvg?

1) Lsattr –El hdisk gives different results
a) scsi_id b N/A True
lun_id a N/A True
location N/A True
ww_name c N/A False
pvid none Physical volume identifier False
q_type simple Queuing TYPE True
queue_depth 20 Queue DEPTH True
start_timeout 180 START unit time out value True
rw_timeout 60 READ/WRITE time out value True

b) pvid a Physical volume
identifier False
queue_depth 3 Queue DEPTH
False
size_in_mb 36400 Size in Megabytes
False

from the output, it is because of the type of hdisk, either SSA or SAN


3) varyoffvg vgname and exportvg vgname , say the vgname is the
same and I issue these commands, I do not have to issue reducevg to
get my physical volumes so that I can assigned to other servers/volume
groups


4) bosboot -ad hdisk0 and bosboot -ad hdisk1 will make both hdisk0
and hidsk1 bootable?

5) by entering bosboot, will i see the order of booting. example
5.1) bootlist -m normal -o ->will gives the normal booting order where
bootlist -m normal hdisk0 hdisk1 will change the booting to hdisk0 and
hdisk1?

6)chdev -a cpuguard=enable -l sys0 , this is to change the device...
but i dont really understand what does this do..

7) odmget -a name=vg02 CuDv, retrieves objects from the specified
object classes into an odmadd input file. that is from man... and i
dont understand too

yls177 <yls177@hotmail.com> wrote:
y> hi.... i went through my logfiles.. and saw the below commands. need
y> your confirmation. pardone my for my ignorance...

y> 1) Are sysdumpdev and sysdumpdev ?l same commands?
y> a) sysdumpdev ?l gives

y> primary /dev/pridumpdev
y> secondary /dev/secdumpdev
y> copy directory /var/adm/ras
y> forced copy flag TRUE
y> always allow dump TRUE
y> dump compression OFF

y> b) sysdumpev, I don't dare to issue..

There is little reason to worry about running sysdumpdev wrongly.
I would expect sysdumpdev to return a usage message or some error
if you ran it without any argument. Anyway, the command that
initiates a system dump is sysdumpstart.

I will be of no help for your other questions. It might be useful
to break a message with so many questions into different posts.

Regards,

Nicholas

--
"Why shouldn't I top-post?" http://www.aglami.com/tpfaq.html
"Meanings are another story." http://www.ifas.org/wa/glossolalia.html

yls177@hotmail.com (yls177) wrote in message news:<c06e4d68.0312040027.43283210@posting.google. com>...
> hi.... i went through my logfiles.. and saw the below commands. need
> your confirmation. pardone my for my ignorance...
>
> 1) Are sysdumpdev and sysdumpdev ?l same commands?
> a) sysdumpdev ?l gives
>
> primary /dev/pridumpdev
> secondary /dev/secdumpdev
> copy directory /var/adm/ras
> forced copy flag TRUE
> always allow dump TRUE
> dump compression OFF
>
> b) sysdumpev, I don't dare to issue..
>

Yes, they are the same command

> Before doing a shutdown ?ry 0, necessary to do a sync? We need to do
> sync, when we re-configures our volumegroup such as deactivateas, and
> remore vgs thru varyoffvg and exportvg?

No, you don't need to do a sync when shutting the system down. I have
never issued a sync when running varyoffvg and exportvg, as to do
these you have to have unmounted the filesystems

>
> 1) Lsattr ?El hdisk gives different results
> a) scsi_id b N/A True
> lun_id a N/A True
> location N/A True
> ww_name c N/A False
> pvid none Physical volume identifier False
> q_type simple Queuing TYPE True
> queue_depth 20 Queue DEPTH True
> start_timeout 180 START unit time out value True
> rw_timeout 60 READ/WRITE time out value True
>
> b) pvid a Physical volume
> identifier False
> queue_depth 3 Queue DEPTH
> False
> size_in_mb 36400 Size in Megabytes
> False
>
> from the output, it is because of the type of hdisk, either SSA or SAN

Yes, differewnt disk types. "lsdev -Cc disk" will show you what the
disk types are.

>
>
> 3) varyoffvg vgname and exportvg vgname , say the vgname is the
> same and I issue these commands, I do not have to issue reducevg to
> get my physical volumes so that I can assigned to other servers/volume
> groups
>

Is that a question or a statement ? To remove a disk from a volume
group, assuming there are no logical volumes on the disk, you need to
use the reducevg command.

>
> 4) bosboot -ad hdisk0 and bosboot -ad hdisk1 will make both hdisk0
> and hidsk1 bootable?

Yes

>
> 5) by entering bosboot, will i see the order of booting. example
> 5.1) bootlist -m normal -o ->will gives the normal booting order where
> bootlist -m normal hdisk0 hdisk1 will change the booting to hdisk0 and
> hdisk1?
>

You are confusing the commands here bosboot creates a boot image,
bootlist command writes the bootlist to the NVRAM on the RS/6000, so
it knows which device to boot from. bootlist -m normal hdisk0 hdisk1
will set the boot order for normal mode to hdisk0 and hdisk1

> 6)chdev -a cpuguard=enable -l sys0 , this is to change the device...
> but i dont really understand what does this do..
>

cpuguard enable allows AIX to dynamically dealloacte a CPU if the
system detects the CPU is failing, the system needs a minimum of two
CPU's for this feature.

> 7) odmget -a name=vg02 CuDv, retrieves objects from the specified
> object classes into an odmadd input file. that is from man... and i
> dont understand too

The command does not create an input file, the output of the command
goes to standard out, you have to use redirection to create a file.
The odm is a database and the odm commands allow you to extract the
data in human readable format.

From all these questions you have asked here and on many other posts,
it appears that you need to attend a course on AIX or get one of the
many books available, The AIX Survival Guide is a good one to start
with.

Steve

steve@wakefieldrfc.freeserve.co.uk (Steve Nottingham) wrote in message news:<42862645.0312050817.6e54e211@posting.google. com>...
> yls177@hotmail.com (yls177) wrote in message news:<c06e4d68.0312040027.43283210@posting.google. com>...
> > hi.... i went through my logfiles.. and saw the below commands. need
> > your confirmation. pardone my for my ignorance...
> >
> > 1) Are sysdumpdev and sysdumpdev ?l same commands?
> > a) sysdumpdev ?l gives
> >
> > primary /dev/pridumpdev
> > secondary /dev/secdumpdev
> > copy directory /var/adm/ras
> > forced copy flag TRUE
> > always allow dump TRUE
> > dump compression OFF
> >
> > b) sysdumpev, I don't dare to issue..
> >
>
> Yes, they are the same command
>
> > Before doing a shutdown ?ry 0, necessary to do a sync? We need to do
> > sync, when we re-configures our volumegroup such as deactivateas, and
> > remore vgs thru varyoffvg and exportvg?
>
> No, you don't need to do a sync when shutting the system down. I have
> never issued a sync when running varyoffvg and exportvg, as to do
> these you have to have unmounted the filesystems
>
> >
> > 1) Lsattr ?El hdisk gives different results
> > a) scsi_id b N/A True
> > lun_id a N/A True
> > location N/A True
> > ww_name c N/A False
> > pvid none Physical volume identifier False
> > q_type simple Queuing TYPE True
> > queue_depth 20 Queue DEPTH True
> > start_timeout 180 START unit time out value True
> > rw_timeout 60 READ/WRITE time out value True
> >
> > b) pvid a Physical volume
> > identifier False
> > queue_depth 3 Queue DEPTH
> > False
> > size_in_mb 36400 Size in Megabytes
> > False
> >
> > from the output, it is because of the type of hdisk, either SSA or SAN
>
> Yes, differewnt disk types. "lsdev -Cc disk" will show you what the
> disk types are.
>
> >
> >
> > 3) varyoffvg vgname and exportvg vgname , say the vgname is the
> > same and I issue these commands, I do not have to issue reducevg to
> > get my physical volumes so that I can assigned to other servers/volume
> > groups
> >
>
> Is that a question or a statement ? To remove a disk from a volume
> group, assuming there are no logical volumes on the disk, you need to
> use the reducevg command.
>
> >
> > 4) bosboot -ad hdisk0 and bosboot -ad hdisk1 will make both hdisk0
> > and hidsk1 bootable?
>
> Yes
>
> >
> > 5) by entering bosboot, will i see the order of booting. example
> > 5.1) bootlist -m normal -o ->will gives the normal booting order where
> > bootlist -m normal hdisk0 hdisk1 will change the booting to hdisk0 and
> > hdisk1?
> >
>
> You are confusing the commands here bosboot creates a boot image,
> bootlist command writes the bootlist to the NVRAM on the RS/6000, so
> it knows which device to boot from. bootlist -m normal hdisk0 hdisk1
> will set the boot order for normal mode to hdisk0 and hdisk1
>
> > 6)chdev -a cpuguard=enable -l sys0 , this is to change the device...
> > but i dont really understand what does this do..
> >
>
> cpuguard enable allows AIX to dynamically dealloacte a CPU if the
> system detects the CPU is failing, the system needs a minimum of two
> CPU's for this feature.
>
> > 7) odmget -a name=vg02 CuDv, retrieves objects from the specified
> > object classes into an odmadd input file. that is from man... and i
> > dont understand too
>
> The command does not create an input file, the output of the command
> goes to standard out, you have to use redirection to create a file.
> The odm is a database and the odm commands allow you to extract the
> data in human readable format.
>
> From all these questions you have asked here and on many other posts,
> it appears that you need to attend a course on AIX or get one of the
> many books available, The AIX Survival Guide is a good one to start
> with.
>
> Steve


that book is for sale on http://www.computerhelpbooks.com/a/AIX/

i thought could get it from redbooks.

anyway, i have downloaded this "aix reference for sun solaris
administrators" from redbooks..

okay, basically... i am not a unix admin. but just that my
applications are ran on unix. and so.. thought of learning more in
this area.

yls177@hotmail.com (yls177) wrote in message news:<c06e4d68.0312040027.43283210@posting.google. com>...
> hi.... i went through my logfiles.. and saw the below commands. need
> your confirmation. pardone my for my ignorance...
>
> 1) Are sysdumpdev and sysdumpdev ?l same commands?
> a) sysdumpdev ?l gives
>
> primary /dev/pridumpdev
> secondary /dev/secdumpdev
> copy directory /var/adm/ras
> forced copy flag TRUE
> always allow dump TRUE
> dump compression OFF
>
> b) sysdumpev, I don't dare to issue..
>
> Before doing a shutdown ?ry 0, necessary to do a sync? We need to do
> sync, when we re-configures our volumegroup such as deactivateas, and
> remore vgs thru varyoffvg and exportvg?
>
> 1) Lsattr ?El hdisk gives different results
> a) scsi_id b N/A True
> lun_id a N/A True
> location N/A True
> ww_name c N/A False
> pvid none Physical volume identifier False
> q_type simple Queuing TYPE True
> queue_depth 20 Queue DEPTH True
> start_timeout 180 START unit time out value True
> rw_timeout 60 READ/WRITE time out value True
>
> b) pvid a Physical volume
> identifier False
> queue_depth 3 Queue DEPTH
> False
> size_in_mb 36400 Size in Megabytes
> False
>
> from the output, it is because of the type of hdisk, either SSA or SAN
>
>
> 3) varyoffvg vgname and exportvg vgname , say the vgname is the
> same and I issue these commands, I do not have to issue reducevg to
> get my physical volumes so that I can assigned to other servers/volume
> groups
>
>
> 4) bosboot -ad hdisk0 and bosboot -ad hdisk1 will make both hdisk0
> and hidsk1 bootable?
>
> 5) by entering bosboot, will i see the order of booting. example
> 5.1) bootlist -m normal -o ->will gives the normal booting order where
> bootlist -m normal hdisk0 hdisk1 will change the booting to hdisk0 and
> hdisk1?
>
> 6)chdev -a cpuguard=enable -l sys0 , this is to change the device...
> but i dont really understand what does this do..
>
> 7) odmget -a name=vg02 CuDv, retrieves objects from the specified
> object classes into an odmadd input file. that is from man... and i
> dont understand too

This looks to me like someone is skimming for test answers. I won't
accuse of that - but it just seems like it.

bverzal@komatsuna.com (Bill) wrote in message news:<51157c68.0312080646.7cf50706@posting.google. com>...
> yls177@hotmail.com (yls177) wrote in message news:<c06e4d68.0312040027.43283210@posting.google. com>...
> > hi.... i went through my logfiles.. and saw the below commands. need
> > your confirmation. pardone my for my ignorance...
> >
> > 1) Are sysdumpdev and sysdumpdev ?l same commands?
> > a) sysdumpdev ?l gives
> >
> > primary /dev/pridumpdev
> > secondary /dev/secdumpdev
> > copy directory /var/adm/ras
> > forced copy flag TRUE
> > always allow dump TRUE
> > dump compression OFF
> >
> > b) sysdumpev, I don't dare to issue..
> >
> > Before doing a shutdown ?ry 0, necessary to do a sync? We need to do
> > sync, when we re-configures our volumegroup such as deactivateas, and
> > remore vgs thru varyoffvg and exportvg?
> >
> > 1) Lsattr ?El hdisk gives different results
> > a) scsi_id b N/A True
> > lun_id a N/A True
> > location N/A True
> > ww_name c N/A False
> > pvid none Physical volume identifier False
> > q_type simple Queuing TYPE True
> > queue_depth 20 Queue DEPTH True
> > start_timeout 180 START unit time out value True
> > rw_timeout 60 READ/WRITE time out value True
> >
> > b) pvid a Physical volume
> > identifier False
> > queue_depth 3 Queue DEPTH
> > False
> > size_in_mb 36400 Size in Megabytes
> > False
> >
> > from the output, it is because of the type of hdisk, either SSA or SAN
> >
> >
> > 3) varyoffvg vgname and exportvg vgname , say the vgname is the
> > same and I issue these commands, I do not have to issue reducevg to
> > get my physical volumes so that I can assigned to other servers/volume
> > groups
> >
> >
> > 4) bosboot -ad hdisk0 and bosboot -ad hdisk1 will make both hdisk0
> > and hidsk1 bootable?
> >
> > 5) by entering bosboot, will i see the order of booting. example
> > 5.1) bootlist -m normal -o ->will gives the normal booting order where
> > bootlist -m normal hdisk0 hdisk1 will change the booting to hdisk0 and
> > hdisk1?
> >
> > 6)chdev -a cpuguard=enable -l sys0 , this is to change the device...
> > but i dont really understand what does this do..
> >
> > 7) odmget -a name=vg02 CuDv, retrieves objects from the specified
> > object classes into an odmadd input file. that is from man... and i
> > dont understand too
>
> This looks to me like someone is skimming for test answers. I won't
> accuse of that - but it just seems like it.

i wont accuse u of accusing me. but in my previous posts, i did
indicate why my knowledge of aix is so shallow. no pun intended.

yls177@hotmail.com (yls177) wrote in message news:<c06e4d68.0312090143.66d66989@posting.google. com>...
> bverzal@komatsuna.com (Bill) wrote in message news:<51157c68.0312080646.7cf50706@posting.google. com>...
> > yls177@hotmail.com (yls177) wrote in message news:<c06e4d68.0312040027.43283210@posting.google. com>...
> > > hi.... i went through my logfiles.. and saw the below commands. need
> > > your confirmation. pardone my for my ignorance...
> > >
> > > 1) Are sysdumpdev and sysdumpdev ?l same commands?
> > > a) sysdumpdev ?l gives
> > >
> > > primary /dev/pridumpdev
> > > secondary /dev/secdumpdev
> > > copy directory /var/adm/ras
> > > forced copy flag TRUE
> > > always allow dump TRUE
> > > dump compression OFF
> > >
> > > b) sysdumpev, I don't dare to issue..
> > >
> > > Before doing a shutdown ?ry 0, necessary to do a sync? We need to do
> > > sync, when we re-configures our volumegroup such as deactivateas, and
> > > remore vgs thru varyoffvg and exportvg?
> > >
> > > 1) Lsattr ?El hdisk gives different results
> > > a) scsi_id b N/A True
> > > lun_id a N/A True
> > > location N/A True
> > > ww_name c N/A False
> > > pvid none Physical volume identifier False
> > > q_type simple Queuing TYPE True
> > > queue_depth 20 Queue DEPTH True
> > > start_timeout 180 START unit time out value True
> > > rw_timeout 60 READ/WRITE time out value True
> > >
> > > b) pvid a Physical volume
> > > identifier False
> > > queue_depth 3 Queue DEPTH
> > > False
> > > size_in_mb 36400 Size in Megabytes
> > > False
> > >
> > > from the output, it is because of the type of hdisk, either SSA or SAN
> > >
> > >
> > > 3) varyoffvg vgname and exportvg vgname , say the vgname is the
> > > same and I issue these commands, I do not have to issue reducevg to
> > > get my physical volumes so that I can assigned to other servers/volume
> > > groups
> > >
> > >
> > > 4) bosboot -ad hdisk0 and bosboot -ad hdisk1 will make both hdisk0
> > > and hidsk1 bootable?
> > >
> > > 5) by entering bosboot, will i see the order of booting. example
> > > 5.1) bootlist -m normal -o ->will gives the normal booting order where
> > > bootlist -m normal hdisk0 hdisk1 will change the booting to hdisk0 and
> > > hdisk1?
> > >
> > > 6)chdev -a cpuguard=enable -l sys0 , this is to change the device...
> > > but i dont really understand what does this do..
> > >
> > > 7) odmget -a name=vg02 CuDv, retrieves objects from the specified
> > > object classes into an odmadd input file. that is from man... and i
> > > dont understand too
> >
> > This looks to me like someone is skimming for test answers. I won't
> > accuse of that - but it just seems like it.
>
> i wont accuse u of accusing me. but in my previous posts, i did
> indicate why my knowledge of aix is so shallow. no pun intended.

Thanks for not being offended. It was not my intent to do so. It is
just that I've seen it before and the way the questions were posted,
including content sounded familiar to me.

sysdumpdev and sysdumpdev -l are the same command. The -l says to
list dump devices. sysdumpdev without the -l will run a sysdumpdev
-l.

No need to sync before shutdown.

lsattr means "list attributes". So, the command output will be
different for different models of disk drives.

bosboot will create boot images on the specified boot devices.

bootlist changes or views the boot devices.

cpuguard is used for dynamic processor deallocation - used when CPU's
fail. Not supported on boxes with less than 2 CPUs.

The format of the files created by the odmget command is like the
/etc/filesystems file.

stanza:
option
option
option

And so on. The ODM is discussed in the advanced sysadmin classes.
There are several files in the ODM, located in a few different
directories. CuDv, CuAt, CuDvDr, etc. Look at them sort of like the
Windows registry. Only - more robust.

BV