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

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

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

Full-Screen Automation<br />

ATTACH CMD DUMP<br />

For the <strong>NetView</strong> commands NAME and DUMP, you can define a CMDSYN<br />

or embed the commands in a REXX procedure.<br />

Detaching V<strong>OS</strong>Ts<br />

V<strong>OS</strong>Ts can be detached explicitly or implicitly. In most cases, it is not necessary to<br />

explicitly detach a V<strong>OS</strong>T. As described in “Attaching V<strong>OS</strong>Ts” on page 319, if a<br />

V<strong>OS</strong>T was created without a NAME on the ATTACH command, the V<strong>OS</strong>T is<br />

detached when the procedure group terminates.<br />

Interacting with Virtual <strong>OS</strong>Ts<br />

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

However, both named and unnamed V<strong>OS</strong>Ts can be explicitly detached using the<br />

DETACH command. DETACH is the same as a LOGOFF on an end-user terminal.<br />

The simplest <strong>for</strong>m of the DETACH command is:<br />

DETACH<br />

Note: A DETACH with no keywords detaches one V<strong>OS</strong>T. Do not use DETACH<br />

without a name if you have more than one V<strong>OS</strong>T created within the<br />

procedure group. An unnamed DETACH, in the case of multiple V<strong>OS</strong>Ts in a<br />

procedure group, can cause unpredictable results. The V<strong>OS</strong>T intended might<br />

not be detached.<br />

If a name was not specified on an ATTACH, you can still detach using a DETACH<br />

NAME. Default attach names are the same as the command name. So, you can<br />

code: DETACH NPDA if you previously coded: ATTACH NPDA<br />

You can also use the STOP FORCE command to terminate a V<strong>OS</strong>T. However, STOP<br />

FORCE can end the V<strong>OS</strong>T be<strong>for</strong>e all V<strong>OS</strong>T processing completes. You can get<br />

unpredictable results.<br />

After starting the application using the ATTACH command, you are ready to<br />

interact with the application running on the V<strong>OS</strong>T. The VET command and PIPE<br />

stage are used to communicate with a V<strong>OS</strong>T.<br />

Hint: V<strong>OS</strong>TIO is synonymous with VET.<br />

VET has two <strong>for</strong>ms: a first stage <strong>for</strong>m and a <strong>for</strong>m that can be used as a subsequent<br />

stage or a command.<br />

In both <strong>for</strong>ms, the NAME keyword on the VET command permits interaction with<br />

a specific V<strong>OS</strong>T if you have more than one V<strong>OS</strong>T attached. The parameter<br />

specified on VET NAME must match the default name or the name specified on<br />

the NAME keyword of the ATTACH command. For example, if you attached two<br />

V<strong>OS</strong>Ts using the following commands:<br />

ATTACH NAME V<strong>OS</strong>T1 NPDA<br />

ATTACH NLDM<br />

The first ATTACH creates an independent V<strong>OS</strong>T named V<strong>OS</strong>T1 running NPDA.<br />

The second creates an unnamed, dependent V<strong>OS</strong>T running NLDM. If you want to<br />

interact with the NPDA application, include NAME V<strong>OS</strong>T1 in your VET stage<br />

specification.

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

Saved successfully!

Ooh no, something went wrong!