|
|
|
A user who issues a SIGNON command to another system or who issues a ROUTE command to send a command to another system for execution establishes a ROF session. The user is logically logged on to the remote system and has user attributes and privileges as defined to the remote system.
If you enter:
ROUTE SOL2 SHOW USERS
from the OCS window command line, the SHOW USERS command is sent to the remote system known as SOL2 and executed under your ROF logon. The results of the command are returned and displayed on your real OCS window.
If you enter:
START PROC1
to start the process PROC1, which in turn issues the inline command:
ROUTE SOL2 SHOW USERS
the results are also returned to the real OCS window. In other words, the delivery of the results of inline commands is the same across a ROF session as it is within the one system. If a process executes an inline command either in its own system or by routing the command to another system, the results return to the owner of the NCL processing environment in which the process is executing; they do not return to the process itself.
Alternatively, if the process in the example issues the statement:
&INTCMD ROUTE SOL2 SHOW USERS
the results return to the PROC1 dependent response queue, and can be read back by PROC1 using the &INTREAD statement.
In summary, therefore, the delivery of command results is always the same, regardless of whether a process issues a command for execution in its own system or a remote one.
The ability of NCL processes to issue commands across ROF sessions, and to correlate the results, allows the development of monitoring and control processes that can operate unseen and communicate with the operator only when a problem occurs.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |