16.12.2012 Views

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

uucp<br />

Execute Files<br />

Execute files are data files containing commands that are created on other sites<br />

and copied to your site. The files are treated as execute files when they arrive at<br />

your site, where the commands are run by uuxqt.<br />

On UUCP sites, execute files are named as:<br />

X.remotX28A3003<br />

where remot is the first five characters of the destination site’s name, X is the job<br />

grade (execute files always have the grade X), and 28A3 is the sequence number.<br />

Each execute file contains one command, and the necessary information to run the<br />

command. The type of information on each line is identified by the first character in<br />

the line. Not all lines are used in all files, and not all UUCP implementations support<br />

all of these lines. The first line in an execute file must be a U line, and the last line<br />

must be a C line.<br />

# Indicates a comment. Comments and unrecognized commands are ignored.<br />

C command<br />

Requests that command be run. command is a string that includes the<br />

program and arguments. This line must be present and must be the last line<br />

in the execute file.<br />

E Processes the command with execve(). If the E line is present, uuxqt runs<br />

a fork()/ecec() sequence, unless the command contains a shell<br />

metacharacter. In that case, uuxqt invokes a shell to run the command.<br />

e Processes the command by the P<strong>OS</strong>IX shell. It is intended to handle<br />

commands that require special processing. If the e line is present, uuxqt<br />

invokes the defined shell to run the command.<br />

F filename [ xqtname ]<br />

Names filename, a file required for the command to be run. This is usually<br />

a file that is transferred from the site that uux was executed from, but it can<br />

also be a file from the local site or some other site. If filename is not from<br />

the local site, then it is usually a file in the spool directory. Multiple F lines<br />

are allowed. Any file other than the standard input file requires the xqtname<br />

argument and is copied to the execution directory as xqtname. If the<br />

standard input file is not from the local site, it appears in both an F<br />

command and an I command.<br />

I stdin Names the file that supplies standard input to the command. If the standard<br />

input file is not from the site running the command, the file is also in an F<br />

command. If there is no standard input file, behavior depends on the site<br />

implementation. uuxqt rejects the command; some <strong>UNIX</strong> implementations<br />

use /dev/null as the standard input. Only one I line can be present in an<br />

execute file; the corresponding F line must precede the file.<br />

N No mail message should be sent, even if the command failed.<br />

n Requests a mail message be sent if the command succeeded. Normally a<br />

message is sent only if the command failed.<br />

O stdout [ site ]<br />

Names the standard output file. The optional second argument names the<br />

site to which the file should be sent. If there is no second argument, the file<br />

should be created on the executing site. Only one O line can be present in<br />

an execute file; the corresponding F line must precede the O line.<br />

928 z/<strong>OS</strong> <strong>V1R9.0</strong> <strong>UNIX</strong> <strong>System</strong> <strong>Services</strong> <strong>Command</strong> Reference

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!