Purpose
p_cat - Issues a parallel cat of files.
Syntax
p_cat [-w - | noderange | 'hostlist args'] file_name file_name ...
Flags
The p_cat command requires the first flag or parameter on the command line to be a specification of the hosts on which the command is to be executed.
Operands
Description
The p_cat command issues the AIX cat command on multiple hosts. p_cat uses dsh to execute the cat command on multiple hosts. The output of the cat command is written to standard output.
Files
|Environment Variables
|PSSP 3.4 provides the ability to run commands using secure remote |command and secure remote copy methods.
|To determine whether you are using either AIX rsh or rcp |or the secure remote command and copy method, the following environment |variables are used. |If no environment variables are set, the defaults are |/bin/rsh and /bin/rcp.
|You must be careful to keep these environment variables consistent. |If setting the variables, all three should be set. The DSH_REMOTE_CMD |and REMOTE_COPY_CMD executables should be kept consistent with the choice of |the remote command method in RCMD_PGM: |
|For example, if you want to run p_cat using a secure remote |method, enter:
|export RCMD_PGM=secrshell |export DSH_REMOTE_CMD=/bin/ssh |export REMOTE_COPY_CMD=/bin/scp
Security
|You must have access to the AIX remote commands or the secure remote |commands to run this command.
This command will automatically forward the DCE credentials if K5 is an enabled AIX authentication method and the user of the command has DCE credentials that can be forwarded. The special DCE credentials for root, called the machine or self host principal credentials, cannot be forwarded. To obtain DCE credentials that can be forwarded as a root user, a root user must issue dce_login -f.
Location
/usr/lpp/ssp/bin/p_cat
Related Information
PSSP commands: dsh, pexec
AIX commands: cat
Examples
To copy /.rhosts from each host1, host2, and host3 to the local /.rhosts file (described previously), enter:
p_cat -w host1,host2,host3 /.rhosts >> /.rhosts
Purpose
pcp - Specifies a parallel copy of local files and directories to other hosts.
Syntax
Flags
The pcp command requires the first flag or parameter on the command line to be a specification of the hosts on which the command is to be executed.
Operands
Description
|The pcp command copies files from the local host to one or |more others in parallel. It uses the defined remote copy method. |The -D, -r, and -p flags |are passed to the remote copy method. You must verify that your secure |copy program supports the flags passed.
|Permission denied
|messages from the nodes for which you are not authorized. |
|Environment Variables
|PSSP 3.4 provides the ability to run commands using secure remote |command and secure remote copy methods.
|To determine whether you are using either AIX rsh or rcp |or the secure remote command and copy method, the following environment |variables are used. |If no environment variables are set, the defaults are |/bin/rsh and /bin/rcp.
|You must be careful to keep these environment variables consistent. |If setting the variables, all three should be set. The DSH_REMOTE_CMD |and REMOTE_COPY_CMD executables should be kept consistent with the choice of |the remote command method in RCMD_PGM: |
|For example, if you want to run pcp using a secure remote |method, enter:
|export RCMD_PGM=secrshell |export DSH_REMOTE_CMD=/bin/ssh |export REMOTE_COPY_CMD=/bin/scp |pcp -wc55n02 /tmp/file1 /tmp/file2
Security
|You must have access to the AIX remote commands or the secure remote |commands to run this command.
If you specify the -D flag, this command will automatically forward the DCE credentials if K5 is an enabled AIX authentication method and the user of the command has DCE credentials that can be forwarded. The special DCE credentials for root, called the machine or self host principal credentials, cannot be forwarded. To obtain DCE credentials that can be forwarded as a root user, a root user must issue dce_login -f with a DCE principal other than a self host principal.
Location
/usr/lpp/ssp/bin/pcp
Related Information
PSSP commands: hostlist, pexscr
AIX commands: rcp
|Secure shell commands: scp
Examples
pcp -w host1,host2 /etc/fileq /etc/filen
pcp '-a' sysctl.acl /etc
hostlist -av -e badnode | pcp -w - -r /etc/new /etc/new
pcp "-av -e badnode" -r /etc/new /etc/new
Purpose
pdf - Displays file system statistics on multiple nodes in parallel.
Syntax
pdf [-w - | noderange | 'hostlist args'] [ file system1 [file system2 ... ]]
Flags
The pdf command requires the first flag or parameter on the command line to be a specification of the hosts on which the command is to be executed.
Operands
Acceptable parameters to the pdf command are zero or more blank-separated file system names to be displayed. If no parameters are supplied, all local file systems (on each specified node) are displayed.
Description
The pdf command displays file systems and their usage statistics on one or more nodes in parallel. pdf is similar to the df command, but does not use it. Differences are:
|Environment Variables
|PSSP 3.4 provides the ability to run commands using secure remote |command and secure remote copy methods.
|To determine whether you are using either AIX rsh or rcp |or the secure remote command and copy method, the following environment |variables are used. |If no environment variables are set, the defaults are |/bin/rsh and /bin/rcp.
|You must be careful to keep these environment variables consistent. |If setting the variables, all three should be set. The DSH_REMOTE_CMD |and REMOTE_COPY_CMD executables should be kept consistent with the choice of |the remote command method in RCMD_PGM: |
|For example, if you want to run pdf using a secure remote |method, enter:
|export RCMD_PGM=secrshell |export DSH_REMOTE_CMD=/bin/ssh |export REMOTE_COPY_CMD=/bin/scp
Security
Since pdf uses sysctl, proper authentication and authorization to issue these commands is necessary.
Location
/usr/lpp/ssp/bin/pdf
Related Information
Commands: hostlist, sysctl
Examples
pdf '-a'
pdf -w node1,node2 /tmp
Purpose
penotify - Adds, removes, or shows AIX error log notification objects.
Syntax
Flags
Operands
None.
Description
Use this command to add, remove, or show notification objects in the errnotify Object Data Management (ODM) class. The AIX errdemon matches logged errors to objects in this class to execute a method defined in the class object. The error class, error label, error type, alert, resource name, resource class, and resource type parameters are used for matching to logged errors. Refer to the AIX General Programming Concepts: Writing and Debugging Programs for descriptions of error notification object class fields.
When a match occurs, the errdemon executes the notify method passing up to nine ($1-$9) parameters related to the logged error.
If the -w parameter begins with a slash (/), it is interpreted as a file containing a list of nodes to execute the command on; otherwise, it can be a comma-delimited list of host names or a single-quoted, blank-delimited list of host names. If neither the -a nor -w parameters are used, the command defaults to the local node.
Security
The penotify command consists of a client script and a server procedure which is executed by the Sysctl facility. Sysctl callbacks perform access authorization according to the configuration of security services on the server nodes. The server uses the Sysctl ACL callback for granting access which requires the caller to have a principal entry in the log management ACL: /etc/logmgt.acl. This principal must log into the proper authentication service prior to using this command.
Location
/usr/lpp/ssp/bin/penotify
Related Information
The AIX Version 4 General Programming Concepts: Writing and Debugging Programs
The PSSP: Administration Guide
Examples
penotify -w k47n10,k47n12,k47n15 -f show
penotify -a -f remove -n HDISK0_ERR
penotify -w /tmp/nodelist -f add -n PEND_ERR -P \ -m'/spdata/sys1/EN_meth/EN_pend $1' -t PEND -c S
This adds a notification object named PEND_ERR to all nodes in the /tmp/nodelist file. The object will persist when the system is restarted, and will match error records of type PEND and class S. The method that is executed by errdemon when a matching error occurs will be /spdata/sys1/EN_meth/EN_pend, and it will be passed the $1 parameter (sequence number). The notification method must be accessible to each node.
Purpose
perspectives - Invokes the launch pad of the SP Perspectives graphical user interface (GUI).
Syntax
Flags
Operands
None.
Description
Use this command to invoke the SP Perspectives Launch Pad. The Launch Pad is a small, customizable GUI from which the user can start (or launch) executables associated with maintaining and monitoring an IBM RS/6000 SP.
The main window shows an icon for each executable that can be launched. Double-clicking on an icon launches the associated executable. To see descriptions of the applications that can be started from the Launch Pad select Options ... Show Application Details. To add, modify or delete applications select Options ... Customize Applications.
Preferences that define the look and layout of the Perspectives Launch Pad window are prioritized in the following order:
Files
The User's Preferences are read from and saved to $HOME/.perspectives(User Profile Name).
The System Preferences are read from and saved to /usr/lpp/ssp/perspectives/profiles/$LANG/.perspectives(System Profile name).
The Perspectives application resource file /usr/lpp/ssp/perspectives/app-defaults/$LANG/Perspectives.
Security
Any user can run the perspectives command. However, only the icons that the user has AIX execute permission for will be shown in the main window.
Implementation Specifics
This command is part of the IBM Parallel System Support Programs (PSSP) Licensed Program (LP).
Prerequisite Information
For information on using Perspectives, see the online help and the "Using SP Perspectives" chapter in the PSSP: Administration Guide.
Location
/usr/lpp/ssp/bin/perspectives
|Related Information
|Specific Perspective windows may be brought up directly by invoking the |following commands: spevent, sphardware, |spsyspar, and spvsd.
Examples
perspectives
perspectives -fontSize 14
Purpose
pexec - Specifies the parallel execution of a command.
Syntax
pexec [-w - | noderange | 'hostlist args'] command command_args
Flags
The pexec commands requires the first flag or parameter on the command line to be a specification of the hosts on which the command is to be executed.
Operands
Description
The pexec command issues a command on multiple hosts in parallel. The output is formatted so that distinct output is displayed only once. The pexec command uses dsh to execute the specified command on multiple hosts. The output of the ls command is written to standard output and formatted. The pls, prm, pmv, pfind, and pps commands are simply links to pexec.
Files
|Environment Variables
|PSSP 3.4 provides the ability to run commands using secure remote |command and secure remote copy methods.
|To determine whether you are using either AIX rsh or rcp |or the secure remote command and copy method, the following environment |variables are used. |If no environment variables are set, the defaults are |/bin/rsh and /bin/rcp.
|You must be careful to keep these environment variables consistent. |If setting the variables, all three should be set. The DSH_REMOTE_CMD |and REMOTE_COPY_CMD executables should be kept consistent with the choice of |the remote command method in RCMD_PGM: |
|For example, if you want to run pexec using a secure remote |method, enter:
|export RCMD_PGM=secrshell |export DSH_REMOTE_CMD=/bin/ssh |export REMOTE_COPY_CMD=/bin/scp
Security
|You must have access to the AIX remote commands or the secure remote |commands to run this command.
This command will automatically forward the DCE credentials if K5 is an enabled AIX authentication method and the user of the command has DCE credentials that can be forwarded. The special DCE credentials for root, called the machine or self host principal credentials, cannot be forwarded. To obtain DCE credentials that can be forwarded as a root user, a root user must issue dce_login -f.
Location
/usr/lpp/ssp/bin/pexec
Related Information
Commands: dsh, dshbak, hostlist
Examples
|pexec -w host1,host2,host3 ls /usr
hostlist -a -v -e badnode | pexec -w -cp -r /etc/new /etc/new
pexec "-a -v -e badnode" cp -r /etc/new /etc/new
Purpose
pexscr - Runs local and remote programs in parallel.
Syntax
pexscr
Flags
None.
Operands
None.
Description
|The pexscr command executes particular commands on |particular processors in parallel. It reads lines of the following |format from standard input:
|host_name: arbitrary_command
|and executes each arbitrary_command on the specified |host. All commands are run in parallel. The dsh command |is used to run the remote commands and local commands are run directly. |Host names can include any parameter that may be specified on the dsh |command, except the credential forwardability flags, -d or |-D, due to the automatic detection feature of credential |forwardability.
|Environment Variables
|PSSP 3.4 provides the ability to run commands using secure remote |command and secure remote copy methods.
|To determine whether you are using either AIX rsh or rcp |or the secure remote command and copy method, the following environment |variables are used. |If no environment variables are set, the defaults are |/bin/rsh and /bin/rcp.
|You must be careful to keep these environment variables consistent. |If setting the variables, all three should be set. The DSH_REMOTE_CMD |and REMOTE_COPY_CMD executables should be kept consistent with the choice of |the remote command method in RCMD_PGM: |
|For example, if you want to run pexscr using a secure remote |method, enter:
|export RCMD_PGM=secrshell |export DSH_REMOTE_CMD=/bin/ssh |export REMOTE_COPY_CMD=/bin/scp
Security
|You must have access to the AIX remote commands or the secure remote |commands to run this command.
This command will automatically forward the DCE credentials if K5 is an enabled AIX authentication method and the user of the command has DCE credentials that can be forwarded. The special DCE credentials for root, called the machine or self host principal credentials, cannot be forwarded. To obtain DCE credentials that can be forwarded as a root user, a root user must issue dce_login -f.
Location
/usr/lpp/ssp/bin/pexscr
Related Information
Commands: dsh, rsh
Examples
To remove a file on host1 and rename a file on host2 simultaneously, enter:
pexscr <<END host1: rm /tmp/shnozzola host2: mv /tmp/shnozzola /tmp/bozo END
Purpose
pfck - Displays file system statistics on multiple hosts in parallel based on usage criteria.
Syntax
Flags
The pfck command requires the first flag or parameter on the command line to be a specification of the hosts on which the command is to be executed.
These flags specify file system usage statistics criteria to be applied in searching for file systems to display. At least one of the flags must be specified. Multiple flags are allowed.
File system usage statistics criteria are logically ORed together when comparing against actual usage information. That is, if a file system meets any of the search criteria, it is displayed.
Operands
Description
The pfck command displays file systems and their usage statistics from one or more nodes in parallel based on usage criteria.
Since pfck uses sysctl, proper authentication and authorization to issue these commands is necessary.
|Environment Variables
|PSSP 3.4 provides the ability to run commands using secure remote |command and secure remote copy methods.
|To determine whether you are using either AIX rsh or rcp |or the secure remote command and copy method, the following environment |variables are used. |If no environment variables are set, the defaults are |/bin/rsh and /bin/rcp.
|You must be careful to keep these environment variables consistent. |If setting the variables, all three should be set. The DSH_REMOTE_CMD |and REMOTE_COPY_CMD executables should be kept consistent with the choice of |the remote command method in RCMD_PGM: |
|For example, if you want to run pfck using a secure remote |method, enter:
|export RCMD_PGM=secrshell |export DSH_REMOTE_CMD=/bin/ssh |export REMOTE_COPY_CMD=/bin/scp
Security
Since pfck uses sysctl, proper authentication and authorization to issue these commands is necessary.
Location
/usr/lpp/ssp/bin/pfck
Related Information
Commands: hostlist, sysctl
Examples
pfck -w node1,node2,node4 -pu 98
|pfck '-a' -pf 20
|In this example, the -a flag is a hostlist |arg.