28.11.2012 Views

IBM Tivoli NetView for z/OS Programming: Pipes - IBM notice

IBM Tivoli NetView for z/OS Programming: Pipes - IBM notice

IBM Tivoli NetView for z/OS Programming: Pipes - IBM notice

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

PIPE QSAM<br />

198 <strong>Programming</strong>: <strong>Pipes</strong><br />

of the same PDS. When this situation occurs, the QSAM stage issues message<br />

DSI084I and a return code of 16. In this case, the system issues the message<br />

"IEC143I 213-30".<br />

v If you omit the FILE operand, a unique ddname with a name of SYSnnnn is<br />

assigned by dynamic allocation and then returned in the CNM272I message. Do<br />

not specify the FILE operand unless a specific ddname must be allocated. This<br />

prevents allocations failing because of ddname conflicts. It also prevents problems<br />

caused by deallocating a data set that is shared by multiple <strong>NetView</strong> tasks. Each<br />

<strong>NetView</strong> task must allocate the file with a unique ddname. If one task deallocates<br />

its ddname, the other tasks do not lose their access to the file.<br />

v If you allocate a partitioned data set as an input data set and specify a member<br />

name that does not exist, the ALLOCATE command completes successfully with<br />

a return code of 0. However, you receive an OPEN error when you attempt to<br />

open the data set <strong>for</strong> input.<br />

v Allocate the files with the FREE operand whenever possible. The files are then<br />

deallocated automatically when they are closed. This reduces virtual storage use.<br />

There is also an MVS limit of 1635 concurrent allocations. When this limit is<br />

reached, deallocate resources to do additional allocations. Allocating files with<br />

the FREE operand helps to keep the allocations below the limit. This procedure<br />

also minimizes the time that critical data sets, volumes, and units are tied up.<br />

System output data sets also are spooled immediately when the files are closed,<br />

instead of when the <strong>NetView</strong> program ends.<br />

v If you specify the same operand more than once on the ALLOCATE command,<br />

the last one specified is used and the previous operands are ignored.<br />

v The <strong>NetView</strong> LISTA command displays the ddnames and dsnames of currently<br />

allocated files.<br />

v For disk files, the following operands are ignored by dynamic allocation:<br />

COPIES HOLD | NOHOLD<br />

DEN OUTLIM<br />

DEST P<strong>OS</strong>ITION<br />

FORMS WRITER<br />

v For tape files, the following operands are ignored by dynamic allocation:<br />

BLOCK | TRACK | CYLINDERS KEYLEN<br />

CONTIG | MXIG | ALX MSVGP<br />

COPIES OUTLIM<br />

DEST RELEASE<br />

DIR ROUND<br />

FORMS SPACE<br />

HOLD | NOHOLD WRITER<br />

v The QSAM stage uses one or more QSAM read or write operations. The<br />

<strong>NetView</strong> program uses the QSAM GET macro to per<strong>for</strong>m read operations and<br />

the QSAM PUT macro to per<strong>for</strong>m write operations. See the appropriate QSAM<br />

documentation <strong>for</strong> more in<strong>for</strong>mation about the QSAM GET and the QSAM PUT.<br />

If the <strong>NetView</strong> program is running under z/<strong>OS</strong> Version 1.10 or earlier, and if a<br />

QSAM read operation is per<strong>for</strong>med on a newly allocated data set that is not<br />

managed by SMS be<strong>for</strong>e any write, the read operation might return residual data<br />

from the previously deleted data set. If this previously deleted data set had a<br />

different record size, the QSAM read operation fails with message

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

Saved successfully!

Ooh no, something went wrong!