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.

queuedefs<br />

This file indicates that the a queue, for at jobs, can have a maximum of five jobs<br />

running simultaneously. crontab runs the jobs with a nice value of 3. Because<br />

there is no nwait field for this queue, if cron cannot run a job because too many<br />

other jobs are running, it waits 60 seconds before trying to run it again.<br />

This file also states that the b queue, for batch jobs, can have a maximum of three<br />

jobs running simultaneously. cron runs the jobs with a nice value of 1. If cron<br />

cannot run a job because too many other jobs are running, it waits 90 seconds<br />

before trying to run it again. All other queues can run up to 100 jobs simultaneously;<br />

cron runs these jobs with a nice value of 2 and, if it cannot run a job because too<br />

many other jobs are running, it waits 60 seconds before trying to run it again.<br />

Related Information<br />

The at, batch, and crontab commands.<br />

tags — Format of the tags file<br />

Description<br />

When you use the vi :tag or ex :tag command, or the ex –t, more –5, vi –t, option,<br />

that utility looks for a file called tags in the current directory. This lets you quickly<br />

locate various points of interest in a C program which may span more than one<br />

source file. These points of interest are tags.<br />

The tags file contains tags for function definitions, preprocessor macro definitions,<br />

and typedef definitions.<br />

For each tag, the tags file contains one line in the following form:<br />

tagname sourcefile address<br />

The tagname field is the name of the C function, macro, or typedef. The sourcefile<br />

field has the name of the source file containing the tag named tagname. The<br />

address field is an editor address within sourcefile to reach the tag definition. This<br />

is either a line number in the file or a regular expression (enclosed in ? or /<br />

characters) that uniquely matches the line of source code where the tag appears. A<br />

tab character separates each field.<br />

For vi or more to use the tags file correctly, it must be sorted by tagname using the<br />

P<strong>OS</strong>IX locale’s collation sequence.<br />

Related Information<br />

The more, sort, and vi commands.<br />

tar — Format of tar archives<br />

Description<br />

tar reads and writes headers in either the original TAR format from <strong>UNIX</strong> systems<br />

or the USTAR format defined by the P<strong>OS</strong>IX 1003.1 standard.<br />

The pax command reads and writes headers in any of the tar formats.<br />

The tar command supports both the older <strong>UNIX</strong>-compatible tar formats and the<br />

extended USTAR format. The –X option needs to be used to enable extended<br />

922 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!