aix command for certification

7/29/2019 AIX Command for certification

1/33

qcan Command

Purpose

Cancels a print job.

Syntax

qcan [ -X ] [ -xJobNumber] [ -PPrinter]

Flags

-P PrinterSpecifies thePrinterwhere either all jobs or the selected job number

will be canceled.

-x JobNumberSpecifies that only the job number specified by theJobNumbervariable

be canceled.

-X

Cancels all jobs or all jobs for the specified printer. If you have root

user authority, all jobs on that queue are deleted. If you do not have

root user authority, only jobs you submitted will be canceled. This flagis only valid for local print jobs.

Examples

1. To cancel all jobs queued on printerlp0, enter:

qcan -X -P lp0

2. To cancel job number123 on whatever printer the job is on, enter:

qcan -x 123

qchk Command

Purpose

Displays the status of a print queue.

Syntax

qchk[ -A ] [ -L |-W ] [ -PPrinter] [ -#JobNumber] [ -q ] [ -uUserName ] [ -wDelay ]

Description
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qcan.htm#a1519d21http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qcan.htm#a1519d20http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qcan.htm#a1519d1fhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qcan.htm#a1519d21http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qcan.htm#a1519d1fhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qcan.htm#a1519d20http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#ig7350rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a2269989http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a1qxzo8dvickhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a1qxzo8dvickhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#dh7210rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a2269988http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#fh760rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a6i7280rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#oi7360rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qcan.htm#a1519d20http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qcan.htm#a1519d1fhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qcan.htm#a1519d21http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qcan.htm#a1519d1fhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qcan.htm#a1519d20http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#ig7350rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a2269989http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a1qxzo8dvickhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#dh7210rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a2269988http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#fh760rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a6i7280rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#oi7360rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qcan.htm#a1519d21


2/33

The qchkcommand displays the current status information regarding specified print jobs,

print queues, or users. Use the appropriate flag followed by the requested name or

number to indicate specific status information. If you run the qchkcommand with noflags, the status of the default queue is returned.

-# JobNumber

Requests the status of the job number specified by theJobNumbervariable. The qchkcommand looks forJobNumberon the defaultqueue when the -#JobNumberflag is used alone. To search for

JobNumberon all queues -# flag must be used with the -A flag. The -#flag may also be used in conjunction with the -P Queue flag.

Notes:

1. Specify the -P Queue to override the default destination printer.

2. If jobs 1, 2, and 3 are in the printer queue, and you specify that

you want the status of job 3 while job 1 is running, the statusinformation will show job 1 and job 3, not only job 3.

3. If you specify a job number that does not exist, the system

displays the current job number on the queue instead of an error

message.

-A Requests the status of all queues.

-L

Specifies information be displayed in long-form mode. This flag cannot

be used with the-W flag. If the -L flag and the -W flag are used

simultaneously, the first one specified takes precedence.

-P Printer Requests the status of the printer specified by thePrintervariable.

-q Requests the status of the default print queue.

-u UserName

Requests the status of all print jobs sent by the user specified by the

UserName variable.

-W

Specifies information be displayed in wide-form mode with longer

queue names, device names, and job numbers. Larger job number

information is available on AIX 4.3.2 and later. This flag cannot beused with the -L flag. If the -L flag and the -W flag are used

simultaneously, the first one specified takes precedence.

-w DelayUpdates requested status information at intervals, in seconds, as

specified by theDelay variable until all print jobs are finished.

Examples

1. To display the default print queue, enter:

qchk -q

2. To display the long status of all queues until empty, while updating the screen

every 5 seconds, enter:
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a1qxzo8dvickhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a1qxzo8dvickhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#fh760rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a1qxzo8dvickhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#fh760roll


3/33

qchk -A -L -w 5

3. To display the status for printerlp0, enter:

qchk -P lp0

4. To display the status for job number123, enter:

qchk -# 123

5. To display the status of all print jobs while restricting the queue status to only

printer lp0, enter:

qchk -A -P lp0

6. To display the wide status of the default print queue for AIX 4.2.1 or later, enter:

qchk -W -q

qmov Command

Purpose

Moves spooled print jobs to another queue.

Syntax

qmov-mNewQueue { -#JobNumber[ -PQueue ] | -PQueue | -uUser[ -PQueue ] }

Description

The qmov command moves spooled print jobs to another print queue. The print job to be

moved is identified by job number, queue, or user name. The format of the command

requires the queue where the job is to be moved to as the first argument and the name ofthe job to move as the second argument.

Flags

-#JobNumber Specifies the job number of the print job to be moved.

-mNewQueue Specifies the name of the destination print queue.

-PQueue Specifies the present print queue of the job to be moved.

-uUser Specifies the name of the user whose print jobs are to be moved.

Examples
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#ig7350rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a2269989http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#oi7360rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#dh7210rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a2269988http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#ig7350rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#dh7210rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a1qxzo8dvickhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#fh760rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qmov.htm#eir3j1cekbarhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qmov.htm#qir3j244kbarhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qmov.htm#djr3j3bakbarhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qmov.htm#djr3j3bakbarhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qmov.htm#ikr3j3b9kbarhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qmov.htm#djr3j3bakbarhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#ig7350rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a2269989http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#oi7360rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#dh7210rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a2269988http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#ig7350rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#dh7210rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a1qxzo8dvickhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#fh760rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qmov.htm#eir3j1cekbarhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qmov.htm#qir3j244kbarhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qmov.htm#djr3j3bakbarhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qmov.htm#djr3j3bakbarhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qmov.htm#ikr3j3b9kbarhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qmov.htm#djr3j3bakbar


4/33

1. To move job number280 to queue lp0, enter:

qmov -mlp0 -#280

2. To move all print jobs on queue lp1 to queue lp0, enter:

qmov -mlp0 -Plp1

3. To move all of Mary's print jobs to queue lp0, enter:

qmov -mlp0 -u mary

passwd Command

Purpose

Changes a user's password.

Syntax

passwd [ -Rload_module ] [ -f | -s ] [ User]

Description

The passwd command sets and changes passwords for users. Use this command tochange your own password or another user's password. You can also use the passwdcommand to change the full name (gecos) associated with your login name and the shell

you use as an interface to the operating system

Flags

-fChanges the user information accessed by the finger command. You

can use this flag to provide your full name in the /etc/passwd file.

-s Changes the login shell.

-Rload_moduleSpecifies the loadable I&A module used to change a user's

password.

alog Command

Purpose

Creates and maintains fixed-size log files created from standard input.

Syntax
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/passwd.htm#a050141jshttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/passwd.htm#psq130crawhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/passwd.htm#buqd0crawhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/passwd.htm#a050141jshttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/passwd.htm#psq130crawhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/passwd.htm#buqd0craw


5/33

To Show the Contents of a Log File

alog-fLogFile [ -o ]

Description

The alog command reads standard input, writes to standard output, and copies the output

into a fixed-size file. This file is treated as a circular log. If the file is full, new entries arewritten over the oldest existing entries.

Examples

1. To record the current date and time in a log file named sample.log, enter:

date | alog -f /tmp/sample.log

2. To list the contents of/tmp/sample.log log file, enter:

alog -f /tmp/sample.log -o

3. To change the size of the log file named /tmp/sample.log to 8192 bytes, enter:

echo "resizing log file" | alog -f /tmp/sample.log -s 8192

To change the name of the log file for the log type sample to /var/sample.log in

the alog configuration database, enter:alog -C -t sample -f /var/sample.log

To change the size of the boot log to 8192 bytes and reflect the new size in ODM,

enter:alog -C -t boot -s 8192echo "Changed log size" | alog -t boot -s 8192

at Command

Purpose

Runs commands at a later time.

Syntax

To Schedule Jobs to Run at a Later Time

at [ -c | -k| -s |-qQueue ] [ -m ] [ -fFile ] { -tDate |Time [Day ] [Increment] }
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/alog.htm#e108638086joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/alog.htm#e108638086joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/alog.htm#e108638216joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a167z93e35http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a167z93e36http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a167z93e38http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a167z93e38http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a5oo2d0bobhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a167z93e37http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#zs2si289candhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#lrn110bobhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a26fc022502janbhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a26fc022529janbhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/alog.htm#e108638086joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/alog.htm#e108638216joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a167z93e35http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a167z93e36http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a167z93e38http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a5oo2d0bobhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a167z93e37http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#zs2si289candhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#lrn110bobhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a26fc022502janbhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a26fc022529janb


6/33

To Report Scheduled Jobs

at-l [ -v ] [ -o ] [Job ... | -qQueue ]

at-n [ User]

To Remove Scheduled Jobs

at-r [ -F ] [ -i ]Job ...

at-r [ -F ] [ -i ] -uUser

Description

The at command reads from standard input the names of commands to be run at a later

time and allows you to specify when the commands should be run.

The at command mails you all output from standard output and standard error for the

scheduled commands, unless you redirect that output. It also writes the job number andthe scheduled time to standard error.

In addition, you may specify one of the following suffixes:

am

pm

zulu

If you do not specify am orpm, the at command uses a 24-hour clock. These suffixescan follow the time as a separate argument or separated with spaces. The am and pmsuffixes are defined values from the AM_STRand PM_STRitems in the LC_TIMElocale category. The suffix zulu indicates that the time is GMT (Greenwich Mean Time).

The at command also recognizes the following keywords as special values for the Time

parameter:

noon

midnight

now

A for AM P for PM

N for noon

M for midnight

lsps Command
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a133z91848http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#at_command_flags_vhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#dnosi243candhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a5oo2d0bobhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#pu2si48candhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a133z91849http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a4w2si28acandhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#mw2si327candhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a133z91849http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a4w2si28acandhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#mw2si327candhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#fw2si76candhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a133z91848http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#at_command_flags_vhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#dnosi243candhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a5oo2d0bobhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#pu2si48candhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a133z91849http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a4w2si28acandhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#mw2si327candhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a133z91849http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#a4w2si28acandhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#mw2si327candhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/at.htm#fw2si76cand


7/33

Purpose

Displays the characteristics of a paging space.

Syntax

lsps { -s | [ -c |-l ] { -a |-t { lv | nfs |ps_helper} |PagingSpace } }

Flags

-aSpecifies that the characteristics of all paging spaces are to be given. The size isgiven in megabytes.

-cSpecifies that the output should be in colon format. The colon format gives the

paging space size in logical partitions.

-l Specifies that the output should be in list format.

-s

Specifies that the summary characteristics of all paging spaces are to be given. This

information consists of the total paging space in megabytes and the percentage of

paging space currently assigned (used). If the -s flag is specified, all other flags areignored.

Note:

To list the characteristics of all paging spaces, enter:lsps -a

This displays the characteristics for all paging spaces and provides a listing similar to thefollowing listing:

Page Space PhysicalVolume Volume Group Size %Used Active AutoType Chksumhd6 hdisk0 rootvg 512MB 1 yes yeslv 8

lsuser Command

Purpose

Displays user account attributes.

Syntax

lsuser [ -Rload_module ] [ -c | -f] [ -aList] { ALL |Name [ ,Name ] ... }

entstat Command

Purpose
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsps.htm#c2afaa0363sylvhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsps.htm#a339f9b2fhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsps.htm#a339f9b2fhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsps.htm#a339f9b30http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsps.htm#a339f9b31http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsps.htm#a137c1862http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsps.htm#a137c1862http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsps.htm#a339f9b31http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsuser.htm#a050126jshttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsrole.htm#ahn12419http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsrole.htm#ahn12421http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsrole.htm#cjf997http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsps.htm#c2afaa0363sylvhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsps.htm#a339f9b2fhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsps.htm#a339f9b30http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsps.htm#a339f9b31http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsps.htm#a137c1862http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsps.htm#a339f9b31http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsuser.htm#a050126jshttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsrole.htm#ahn12419http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsrole.htm#ahn12421http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsrole.htm#cjf997


8/33

Shows ethernet device driver and device statistics.

Syntax

entstat [ -d-r-t ]Device_Name

Description

The entstat command displays the statistics gathered by the specified Ethernet device

driver. The user can optionally specify that the device-specific statistics be displayed in

addition to the device generic statistics. If no flags are specified, only the device generic

statistics are displayed.

This command is also invoked when the netstat command is run with the -v flag. The

netstat command does not issue any entstat command flags.

If an invalidDevice_Name is specified, the entstat command produces an error messagestating that it could not connect to the device.

Flags

-d Displays all the statistics, including the device-specific statistics.

-rResets all the statistics back to their initial values. This flag can only be issued byprivileged users.

-t Toggles debug trace in some device drivers.

lspv Command

Purpose

Displays information about a physical volume within a volume group.

Syntax

lspv

OR

lspv [ -L ] [ -l |-p |-M ] [ -n DescriptorPhysicalVolume] [-vVolumeGroupID]

PhysicalVolume

Description
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds2/entstat.htm#db307bf265janihttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds2/entstat.htm#db307bf303janihttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds2/entstat.htm#db307bf303janihttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds2/entstat.htm#i0820971355mkmhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#lspvflaguplhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#a12898abhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#p21100carohttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#p21100carohttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#p21100carohttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#a12898aahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#a12898aahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#a12898achttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#a15099f3http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#a15099f3http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds2/entstat.htm#db307bf265janihttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds2/entstat.htm#db307bf303janihttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds2/entstat.htm#i0820971355mkmhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#lspvflaguplhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#a12898abhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#p21100carohttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#a12898aahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#a12898achttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#a15099f3


9/33

The lspv command displays information about the physical volume if the specific

physical volume name is specified. If you do not add flags to the lspv command, the

default is to print every known physical volume in the system

lsvg Command

Purpose

Displays information about volume groups.

Syntax

lsvg [ -L ] [ -o ] | [ -n DescriptorPhysicalVolume ] | [-i ] [ -l |-M | -p ] VolumeGroup ...

Description

The lsvg command displays information about volume groups. If you use theVolumeGroup parameter, only the information for that volume group is displayed. If you

do not use the VolumeGroup parameter, a list of the names of all defined volume groups

is displayed.

mksysb Command

Purpose

Creates an installable image of the root volume group either in a file or onto a bootable

tape.

Syntax

mksysb [ -a ] [ -A ] [ -b Number] [ -e ] [ -F filename ] [ -i ] [ -m ] [ -p ] [ -t argument] [

-v ] [ -V ] [ -X]Device |File

Description

The mksysb command creates a backup of the operating system (that is, the root volume

group). You can use this backup to reinstall a system to its original state if it is corrupted.

If you create the backup on tape or UDFS capable media, the backup is bootable andincludes the installation programs needed to install from the backup.

Flags
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsvg.htm#lsvgflaguplhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsvg.htm#kj2320carohttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsvg.htm#a12898b0http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsvg.htm#a12898aehttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsvg.htm#a12898aehttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsvg.htm#gl22a0carohttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsvg.htm#ori150joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsvg.htm#ori150joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsvg.htm#a12898b1http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#mksysb_flags_smallahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#mksysb_flags_bigahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#a2wqaj21aharrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#iwqaj3e5harrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#mksysb_flags_bigfhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#ywqaj2eaharrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#qwqajf8harrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#qnseo2c5melahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#mksysb_flags_thttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#a9oseo273melahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#mksysb_flags_bigvhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#soseo323melahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#soseo323melahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsvg.htm#lsvgflaguplhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsvg.htm#kj2320carohttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsvg.htm#a12898b0http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsvg.htm#a12898aehttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsvg.htm#gl22a0carohttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsvg.htm#ori150joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsvg.htm#a12898b1http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#mksysb_flags_smallahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#mksysb_flags_bigahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#a2wqaj21aharrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#iwqaj3e5harrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#mksysb_flags_bigfhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#ywqaj2eaharrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#qwqajf8harrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#qnseo2c5melahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#mksysb_flags_thttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#a9oseo273melahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#mksysb_flags_bigvhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm#soseo323mela


10/33

-a Does not back up extended attributes or NFS4 ACLs.

-A Backs up DMAPI file system files.

-b Number

Specifies the number of 512 - byte blocks to write in a single outputoperation. When the backup command writes to tape devices, the default is

100 for backups by name.

The write size is the number of blocks multiplied by the block size. The

default write size for the backup command writing to tape devices is 51200(100 * 512) for backups by name. The write size must be an even multiple

of the tape's physical block size.

-e

Ecludes files listed in the /etc/exclude.rootvg file from being backed up.The rules for exclusion follow the pattern matching rules of the grepcommand.

-v Verbose mode. Lists files as they are backed up.

-V

Verifies a tape backup. This flag causes the mksysb command to verify thefile header of each file on the backup tape and report any read errors as they

occur.

-X

Specifies to automatically expand the /tmp file system if necessary. The

/tmp file system may need to be extended to make room for the boot image

when creating a bootable backup to tape.

Examples

1. To generate a system backup and create an /image.data file (generated by the

mkszfile command) to a tape device named /dev/rmt0, type:

mksysb -i /dev/rmt0

2. To generate a system backup and create an /image.data file with map files

(generated by the mkszfile command) to a tape device named /dev/rmt1, type:

mksysb -m /dev/rmt1

3. To generate a system backup with a new /image.data file, but exclude the files in

directory /home/user1/tmp, create the file /etc/exclude.rootvg containing the line

/home/user1/tmp/, and type:

mksysb -i -e /dev/rmt1

This command backs up the /home/user1/tmp directory but not the files itcontains.

4. To generate a system backup file named /mksysb_images/node1 and a new

/image.data file for that image, type:

mksysb -i /mksysb_images/node1


11/33

Note:

This file will not be bootable and can only be installed using Network Installation

Management (NIM).

5. To generate a system backup on the tape in /dev/rmt0, and then verify thereadability of file headers, enter:

mksysb /dev/rmt0 -V

6. To generate a system backup and create an /image.data file (generated by the

mkszfile command) to a UDFS capable device named /dev/usbms0, enter the

following command:

mksysb -i /dev/usbms0

chfs CommandPurpose

Changes attributes of a file system.

Syntax

chfs [ -nNodeName ] [ -mNewMountPoint] [ -uMountGroup ] [ -A { yes | no } ] [ -p {

ro | rw } ] [-t { yes | no } ] [ -aAttribute=Value ] [-dAttribute ]FileSystem

Description

The chfs command changes the attributes of a file system. The new mount point,

automatic mounts, permissions, and file system size can be set or changed. TheFileSystem parameter specifies the name of the file system, expressed as a mount point.

Examples

1. To change the file system size of the /test Journaled File System, enter:

chfs -a size=24576 /test

This command changes the size of the /test Journaled File System to 24576

512-byte blocks, or 12MB (provided it was previously no larger than this).

2. To increase the size of the /test Journaled File System, enter:

chfs -a size=+8192 /test
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_nhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_mhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_uhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_bigahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_phttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_thttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_thttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_ahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_dhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_dhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_dhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_ahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_ahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_nhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_mhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_uhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_bigahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_phttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_thttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_ahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_dhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_ahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_a


12/33

This command increases the size of the /test Journaled File System by 8192

512-byte blocks, or 4 MB.

3. To convert a JFS2 file system to a version which can support NFS4 ACLs, type:

chfs -a ea=v2 /test

4. To change the mount point of a file system, enter:

chfs -m /test2 /test

This command changes the mount point of a file system from /test to /test2.

5. To delete the accounting attribute from a file system, enter:

chfs -d account /home

This command removes the accounting attribute from the /home file system. Theaccounting attribute is deleted from the /home: stanza of the /etc/filesystems file.

6. To split off a copy of a mirrored file system and mount it read-only for use as an

online backup, enter:

chfs -a splitcopy=/backup -a copy=2 /testfs

This mount a read-only copy of /testfs at /backup.

7. To change the file system size of the /test Journaled File System, enter:

chfs -a size=64M /test

This command changes the size of the /test Journaled File System to 64MB

(provided it was previously no larger than this).

8. To reduce the size of the /test JFS2 file system, enter:

chfs -a size=-16M /test

This command reduces the size of the /test JFS2 file system by 16MB.

9. To freeze a file system, enter:

chfs -a freeze=60 /adl

This command freezes the /adl file system for a maximum of 60 seconds.

10. To thaw a file system, enter:
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_mhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/chfs.htm#chfs_flags_m


13/33

chfs -a freeze=off /zml

This command thaws the /zml file system.

who Command

Purpose

Identifies the users currently logged in.

Syntax

who [ -a | -b-d-i-l-m-p-q-r-s-t-u -w-A-H-T-X ] [File ]

who am { i | I }

Description

The who command displays information about all users currently on the local system.

The following information is displayed: login name, tty, date and time of login. Typing

who am i orwho am I displays your login name, tty, date and time you logged in. If the

user is logged in from a remote machine, then the host name of that machine is displayed

as well.

Flags

-a Processes the /etc/utmp file or the named file with all information.Equivalent to specifying the -bdlprtTu flags.

-b Indicates the most recent system startup time and date.

-d

Displays all processes that have expired without being regenerated by init.The exit field appears for dead processes and contains the termination and

exit values (as returned by wait) of the dead process. (This flag is useful for

determining why a process ended by looking at the error number returned bythe application.)

-l Lists any login process.

-mDisplays information about the current terminal only. The who -m command

is equivalent to the who am i and who am I commands.

-p Lists any active process that is currently active and has been previouslygenerated by init.

-q Prints a quick listing of users and the number of users on the local system.

-r Indicates the current run-level of the process.

-sLists only the name, line, and time fields. This flag is the default; thus, the

who and who -s commands are equivalent.

-t Indicates the last change to the system clock by the root user using the date
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eee584endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eee654endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eee725endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eee725endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eee725endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef286endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eee791endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eee791endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eee862endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eee932endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef000endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef000endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef000endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef077endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef146endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef146endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef146endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef218endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef218endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef286endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef492endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef356endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef356endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef423endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef492endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#who_flags_upperxhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.files/doc/aixfiles/utmp.htm#a3039269fhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eee584endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eee654endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eee725endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef286endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eee791endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eee862endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eee932endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef000endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef077endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef146endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef218endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef286endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef492endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef356endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef423endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef492endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#who_flags_upperxhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.files/doc/aixfiles/utmp.htm#a3039269f


14/33

command. If the date command has not been run since system installation,

the who -t command produces no output.

-u or-iDisplays the user name, tty, login time, line activity, and process ID of eachcurrent user.

-ADisplays all accounting entries in the /etc/utmp file. These entries are

generated through the acctwtmpcommand.-H Displays a header (title).

-T or-w

Displays the state of the tty and indicates who can write to that tty as follows:

+

Writable by anyone.

-

Writable only by the root user or its owner.

?

Bad line encountered.

-X

Prints all available characters of each user name instead of truncating to the

first 8 characters. The user name is also moved to the last column of the

output.

Examples

1. 1. To display information about who is using the local system node, type:

who

Information similar to the following is displayed:

pts/1 Nov 9 00:20long_username_greater_than_eight_characters (localhost)

2. To display your user name, type:

who am i


george lft/0 Jun 8 08:34

3. To display a history of logins, logouts, system startups, and system shutdowns,

type:

who /var/adm/wtmp


hank lft/0 Jun 8 08:34 (ausnix5)john lft/0 Jun 8 08:34 (JIKey)
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/acctwtmp.htm#nqb8n1b1marthttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/acctwtmp.htm#nqb8n1b1marthttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/acctwtmp.htm#nqb8n1b1mart


15/33

mary lft/0 Jun 8 08:22 (machine.austin.ibm)jan pts4 Jun 8 09:19 (puff.wisc.edu)

4. To display the run-level of the local system node, type:

who -r


. run-level 2 Jun 8 04:15 2 0 s

5. To display any active process that is currently actively and has been previously

generated by init, type:

who -p


srcmstr . Jun 8 04:15 old 2896cron . Jun 8 04:15 old 4809uprintfd . Jun 8 04:15 old 5158

tctl Command

Purpose

Gives subcommands to a streaming tape device.

Syntax

tctl [ -fDevice ] [ eof| weof| fsf| bsf| fsr | bsr |rewind | offline | rewoffl |erase |

retension | reset | status ] [ Count]

tctl [ -bBlockSize ] [ -fDevice ] [ -pBufferSize ] [ -v ] [ -n ] [ -B ] { read |write }

Description

The tctl command gives subcommands to a streaming tape device. If you do not specify

theDevice variable with the -fflag, the TAPE environment variable is used. If the

environment variable does not exist, the tctl command uses the /dev/rmt0.1 device.(When the tctl command gives the status subcommand, the default device is /dev/rmt0.)

TheDevice variable must specify a raw (not block) tape device. The Countparameterspecifies the number of end-of-file markers, number of file marks, or number of records.

If the Countparameter is not specified, the default count is 1.

rewind Rewinds the tape. The Countparameter is ignored.

offline or Rewinds the tape and takes the tape drive offline. This will unload the tape
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef077endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eee932endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a272a9dchttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296394http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296394http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296394http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296395http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#ahn4900http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296396http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#ahn4901http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296397http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296397http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a305c11http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a305c11http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a305c11http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a305c11http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a1029639chttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a1029639dhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#iet5j2f6vpowhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a151c1163ahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#mkma0joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a272a9dchttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#clm60joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#zlm3a0joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#vps21c0sandhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#s1oog386harrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296387http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a347p9achttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a347p9achttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eef077endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds6/who.htm#a3b27eee932endrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a272a9dchttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296394http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296395http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#ahn4900http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296396http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#ahn4901http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296397http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a305c11http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a305c11http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a1029639chttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a1029639dhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#iet5j2f6vpowhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a151c1163ahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#mkma0joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a272a9dchttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#clm60joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#zlm3a0joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#vps21c0sandhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#s1oog386harrhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296387http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a347p9ac


16/33

rewofflwhen appropriate. The tape must be re-inserted before the device can be used

again.

erase Erases all contents on the tape and rewinds it.

read

Reads from the specified tape device (using the specified block size) until the

internal buffer is full, and then writes the data to standard output, continuing

to read and write this way until an end-of-file (EOF) mark is reached.

resetSends a bus device reset (BDR) to the tape device. The BDR will only be sent

if the device cannot be opened and is not busy.

retension

Moves the tape to the beginning, then to the end, and then back to the

beginning of the tape. If you have excessive read errors during a restoreoperation, you should run the retension subcommand. If the tape has been

exposed to environmental extremes, you should run the retension

subcommand before writing to tape. The 8 mm tape drive will not respond tothis command.

status Prints status information about the specified tape device.

Flags

-b BlockSize

Specifies, in bytes, the size of buffer used to read and write to the tape

device, and also specifies, in the absence of the -n flag, the tape block

size. If the block size is 0, variable-length blocks are used and the sizeof the tape buffer is 32,768. If the -b flag is not specified, the default

block size and the size of the tape buffer is 512 bytes.

-B

Writes the contents of the buffer each time the tape is read. Set this

flag when reading variable-length records that are not of a regular andconsistent size.

-fDevice Specifies the tape device.

-p BufferSizeSpecifies the size of the buffer to be used on standard input andstandard output. The default buffer size is 32,768 bytes. The

BufferSize value must be a multiple of the tape block size.

-v Verbose. Prints the sizes of each read and write to standard error.

-n

Examples

1. To rewind the rmt1 tape device, enter:

tctl -f /dev/rmt1 rewind

2. To move forward two file marks on the default tape device, enter:

tctl fsf 2
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a272a9dchttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a272a9dchttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296397http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296395http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296395http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a272a9dchttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296397http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296395


17/33

3. To write two end-of-file markers on the tape in /dev/rmt0.6, enter:

tctl -f /dev/rmt0.6 weof 2

4. To read a tape device formatted in 80-byte blocks and put the result in a file,

enter:

tctl -b 80 read > file

5. To read variable-length records from a tape device formatted in 80-byte blocks

and put the result in a file, enter:

tctl -b 80 -nread > file

6. To write variable-length records to a tape device using a buffer size of 1024 byes,

enter:

cat file | tctl -b 1024 -n-f/dev/rmt1 write

7. To write to a tape device in 512-byte blocks and use a 5120-byte buffer for

standard input, enter:

cat file | tctl -v-f /dev/rmt1 -p 5120 -b 512 write

Note: The only valid block sizes for quarter-inch (QIC) tape drives are 0 and 512.

8. To write over one of several backups on an 8 mm tape, position the tape at thestart of the backup file and issue these commands:

tctl bsf 1

tctl eof 1

crontab Command

Purpose

Submits, edits, lists, or removes cron jobs.

Syntax

crontab [ -e [UserName] | -l [UserName] | -r [UserName] | -v[UserName] |File ]

Description

The crontab command submits, edits, lists, or removes cron jobs. A cron job is a

command run by the cron daemon at regularly scheduled intervals. To submit a cron job,
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a272a9dchttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a272a9dchttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296394http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296394http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#mkma0joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296387http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#mkma0joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#vps21c0sandhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296387http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#mkma0joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#vps21c0sandhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a272a9dchttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a347p9achttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#zlm3a0joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a272a9dchttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#clm60joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#mkma0joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a347p9achttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#ahn4900http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296394http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/crontab.htm#a15991144jshttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/crontab.htm#a1599116fjshttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/crontab.htm#a15991170jshttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/crontab.htm#a325jvhjshttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/crontab.htm#a325jvhjshttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a272a9dchttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296394http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#mkma0joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296387http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#mkma0joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#vps21c0sandhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296387http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#mkma0joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#vps21c0sandhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a272a9dchttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a347p9achttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#zlm3a0joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a272a9dchttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#clm60joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#mkma0joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a347p9achttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#ahn4900http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds5/tctl.htm#a10296394http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/crontab.htm#a15991144jshttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/crontab.htm#a1599116fjshttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/crontab.htm#a15991170jshttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/crontab.htm#a325jvhjs


18/33

specify the crontab command with the -e flag. The crontab command invokes an editing

session that allows you to create a crontab file. You create entries for each cron job in

this file. Each entry must be in a form acceptable to the cron daemon. For information oncreating entries, see The crontab File Entry Format.

When you finish creating entries and exit the file, the crontab command copies it into the/var/spool/cron/crontabs directory and places it in a file named for your current user

name. If a file with your name already exists in the crontabs directory, the crontabcommand overwrites it.

Alternatively, you can create a crontab file by specifying theFile parameter. If the file

exists, it must be in the format the cron daemon expects. If the file does not exist, the

crontab command invokes the editor. If the EDITORenvironment variable exists, the

command invokes the editor it specifies. Otherwise, the crontab command uses the vieditor.

To list the contents of yourcrontab file, specify the crontab command with the -l flag.To remove an existing file, use the -r flag.

The optional UserName parameter can be used by the owner of the crontab file or by the

root user to edit, list, remove, or verify the status of the cron jobs for the specified user. If

the UserName is invalid, an error message is generated and the program exits.

If the optional UserName parameter is not specified, the crontab flags are available forthe root user and the current user.

Security

Only the root user or the owner of the crontab file can use UserName following the -e,

-l, -r, and -v flags to edit, list, remove, or verify the crontab file of the specified user.

The cron Daemon

The cron daemon runs commands according to the crontab file entries. Unless youredirect the output of a cron job to standard output or error, the cron daemon mails you

any command output or errors. If you specify a cron job incorrectly in yourcrontab file,

the cron daemon does not run the job.

The cron daemon examines crontab files only when the cron daemon is initialized.When you make changes to yourcrontab file using the crontab command, a message

indicating the change is sent to the cron daemon. This eliminates the overhead of

checking for new or changed files at regularly scheduled intervals.
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/crontab.htm#rrnpi36bmaryhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds1/crontab.htm#rrnpi36bmary


19/33

Controls on Using the crontab Command

The /var/adm/cron/cron.allow and /var/adm/cron/cron.deny files control which users

can use the crontab command. A root user can create, edit, or delete these files. Entriesin these files are user login names with one name to a line. If your login ID is associated

with more than one login name, the crontab command uses the first login name that is inthe /etc/passwd file, regardless of which login name you might actually be using. Also,to allow users to start cron jobs, the daemon attribute in the /etc/security/user file should

be set to TRUE , using the chuser command.

A user cannot use the crontab command if one of the following is true:

The cron.allow file and the cron.deny file do not exist (allows root user only).

The cron.allow file exists but the user's login name is not listed in it.

The cron.deny file exists and the user's login name is listed in it.

If neither the cron.allow nor the cron.deny file exists, only someone with root userauthority can submit a job with the crontab command.

Examples

1. To copy a file called mycronjobs into the /var/spool/cron/crontabs directory,

enter the following:

crontab mycronjobs

The file will be copied as:

/var/spool/cron/crontabs/

where is your current user name.

2. To write the time to the console every hour on the hour, enter:3. 0 * * * * echo The hour is `date` .

>/dev/console

4. To run the calendar command at 6:30 a.m. every Monday, Wednesday, and

Friday, enter:

30 6 * * 1,3,5 /usr/bin/calendar

5. To run the calendar command every day of the year at 6:30, enter the following:

30 6 * * * /usr/bin/calendar

6. To run a script called maintenance every day at midnight in August, enter the

following:


20/33

0 0 * 8 * /u/harry/bin/maintenance

7. To define text for the standard input to a command, enter:8. 0 16 * 12 5 /usr/sbin/wall%HAPPY HOLIDAY!%Remember to

turn in your time card.

The text following the % (percent sign) defines the standard input to the wallcommand as:

HAPPY HOLIDAY!Remember to turn in your time card.

lspv Command

Purpose

Displays information about a physical volume within a volume group.

Syntax

lspv

OR

lspv [ -L ] [ -l |-p |-M ] [ -n DescriptorPhysicalVolume] [-vVolumeGroupID]PhysicalVolume

Description

The lspv command displays information about the physical volume if the specificphysical volume name is specified. If you do not add flags to the lspv command, the

default is to print every known physical volume in the system along with its physical disk

name, physical volume identifiers (PVIDs), to which volume group (if any) the physicalvolume belongs, and the state of the volume group as active if the volume group is varied

on or concurrent if it is varied on in concurrent mode.

Examples

1. To display the status and characteristics of physical volume hdisk3, enter:

lspv hdisk3

2. To display the status and characteristics of physical volume hdisk5 by physical

partition number, enter:
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#lspvflaguplhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#a12898abhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#p21100carohttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#p21100carohttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#p21100carohttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#a12898aahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#a12898aahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#a12898achttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#a15099f3http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#a15099f3http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#lspvflaguplhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#a12898abhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#p21100carohttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#a12898aahttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#a12898achttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#a15099f3


21/33

lspv -p hdisk5

qchk Command

Purpose

Displays the status of a print queue.

Syntax

qchk[ -A ] [ -L | -W ] [ -PPrinter] [ -#JobNumber] [ -q ] [ -uUserName ] [ -wDelay ]

Description

The qchkcommand displays the current status information regarding specified print jobs,

print queues, or users. Use the appropriate flag followed by the requested name ornumber to indicate specific status information. If you run the qchkcommand with no

flags, the status of the default queue is returned.

-A Requests the status of all queues.

-L

Specifies information be displayed in long-form mode. This flag cannot be

used with the-W flag. If the -L flag and the -W flag are used simultaneously,the first one specified takes precedence.

-P Printer Requests the status of the printer specified by thePrintervariable.

-q Requests the status of the default print queue.

-u

UserName

Requests the status of all print jobs sent by the user specified by the

UserName variable.

-W

Specifies information be displayed in wide-form mode with longer queue

names, device names, and job numbers. Larger job number information isavailable on AIX 4.3.2 and later. This flag cannot be used with the -L flag. If

the -L flag and the -W flag are used simultaneously, the first one specified

takes precedence.

-w DelayUpdates requested status information at intervals, in seconds, as specified bytheDelay variable until all print jobs are finished.

Examples

1. To display the default print queue, enter:

qchk -q

2. To display the long status of all queues until empty, while updating the screen

every 5 seconds, enter:

qchk -A -L -w 5
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#p21100carohttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#ig7350rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a2269989http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a1qxzo8dvickhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#dh7210rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a2269988http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#fh760rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a6i7280rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#oi7360rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a1qxzo8dvickhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a1qxzo8dvickhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#fh760rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#ig7350rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a2269989http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#oi7360rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lspv.htm#p21100carohttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#ig7350rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a2269989http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a1qxzo8dvickhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#dh7210rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a2269988http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#fh760rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a6i7280rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#oi7360rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a1qxzo8dvickhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#fh760rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#ig7350rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a2269989http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#oi7360roll


22/33

3. To display the status for printerlp0, enter:

qchk -P lp0

4. To display the status for job number123, enter:

qchk -# 123

5. To display the status of all print jobs while restricting the queue status to only

printer lp0, enter:

qchk -A -P lp0

6. To display the wide status of the default print queue for AIX 4.2.1 or later, enter:

qchk -W -q

mount Command

Purpose

Makes a file system available for use.

Syntax

mount [ -f] [ -n node ] [ -o options ] [ -p ] [-r ] [ -v vfsname ] [ -t type | [ device |node:directory ] directory | all | -a ] [-V [generic_options]special_mount_points ]

Description

The mount command instructs the operating system to make a file system available for

use at a specified location (the mount point). In addition, you can use the mount

command to build other file trees made up of directory and file mounts. The mountcommand mounts a file system expressed as a device using the device ornode:directory

parameter on the directory specified by the directory parameter. After the mountcommand has finished, the directory specified becomes the root directory of the newlymounted file system.

Only users with root authority or are members of the system group and have write accessto the mount point can issue file or directory mounts. The file or directory may be a

symbolic link.

To list the mounted file systems, enter:mount

This command produces output similar to the following:
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#dh7210rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a2269988http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#ig7350rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#dh7210rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a1qxzo8dvickhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#fh760rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mount.htm#a144c184dhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mount.htm#a144c184ehttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mount.htm#a144c184fhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mount.htm#a144c1860http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mount.htm#a144c1861http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mount.htm#a144c1861http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mount.htm#a144c1863http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mount.htm#a144c1862http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mount.htm#a144c184chttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mount.htm#a144c184bhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mount.htm#mount_flag_bigvhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#dh7210rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a2269988http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#ig7350rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#dh7210rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#a1qxzo8dvickhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds4/qchk.htm#fh760rollhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mount.htm#a144c184dhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mount.htm#a144c184ehttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mount.htm#a144c184fhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mount.htm#a144c1860http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mount.htm#a144c1861http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mount.htm#a144c1863http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mount.htm#a144c1862http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mount.htm#a144c184chttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mount.htm#a144c184bhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/mount.htm#mount_flag_bigv


23/33

node mounted mounted over vfs date options---- ------- ------------ --- -------------------------------

/dev/hd0 / jfs Dec 17 08:04 rw, log=/dev/hd8

/dev/hd3 /tmp jfs Dec 17 08:04 rw, log=/dev/hd8

/dev/hd1 /home jfs Dec 17 08:06 rw, log=/dev/hd8

/dev/hd2 /usr jfs Dec 17 08:06 rw, log=/dev/hd8sue /home/local/src /usr/code nfs Dec 17 08:06 ro, log=/dev/hd8

For each file system, the mount command lists the node name, the device name, the

name under which it is mounted, the virtual-file-system type, the date and time it wasmounted, and its options.

lsdev CommandPurpose

Displays devices in the system and their characteristics.

Syntax

lsdev [ -C ][ -cClass ] [ -sSubclass ] [ -tType ] [ -fFile ] [ -FFormat |-rColumnName ] [ -h ] [ -H ] [ -l {Name | - } ] [ -pParent] [ -S State ]

lsdev-P [ -c Class ] [ -s Subclass ] [ -t Type ] [ -fFile ] [ -FFormat|-r ColumnName ] [-h ] [ -H ]

Description

The lsdev command displays information about devices in the Device Configuration

database. You can display information about all devices in the Customized Devicesobject class using the -C flag. Any combination of the -c Class, -s Subclass, -t Type, -lName, -pParent, and -S State flags selects a subset of the customized devices. You can

display information about all devices in the Predefined Devices object class using the -Pflag. Any combination of the -c Class, -s Subclass, and -t Type flags selects a subset of

the predefined devices.

You can display the default output one of the following ways:

From the Customized Devices object class using the -C flag

From the Predefined Devices object class using the -P flag

-c Class Specifies a device class name. This flag can be used to restrict output to devices
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsdev.htm#hal140joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsdev.htm#zal360joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsdev.htm#val40joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsdev.htm#val40joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsdev.htm#ddmjoychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsdev.htm#ddmjoychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsdev.htm#ydm360joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsdev.htm#rdm1c0joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsdev.htm#v1ma0joychttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds3/lsdev

aix command for certification

Documents