INGSEND
Purpose
INGSEND routes commands to other domains using NetView RMTCMD.
You should use the TARGET parameter with system operations commands if possible.
Syntax
Parameters
- NETVASIS
- Prefix the INGSEND command with NETVASIS if you want to pass the command text in lower or mixed case.
- RESP
- Specifies whether you want to receive an asynchronous response
or acknowledgement when you issue the command. Valid options are:
- ACK
- If you use this option:
- A message is displayed on the operator's NCCF console stating whether or not the command executed successfully.
- If the command executed successfully, message AOF672I will be displayed.
- If the command executed but failed, message AOF671I will be displayed.
- If the command could not be delivered to the target domain or RMTCMD autotask, or was delivered and failed to begin execution, the appropriate NetView RMTCMD message will be displayed to explain the failure.
- NO
- Specifies that you do not want to receive any output from the command.
- YES
- Specifies that you want the output from the command displayed on your NCCF console.
- CORR
- Specifies that you want the output from the command to be displayed by the NetView WINDOW command. See Restrictions and Limitations on correlating command output.
- OPER
- Specifies the operator to use to issue the command. operator_ID can be defined using the customization dialog for each domain. If not defined, it will default to the issuing task ID.Notes:
- If the operator alias GATOPER or BASEOPER is specified, the operator ID will default to the issuing task ID.
- If orig.operid = target.operid in the OPER keyword, the command will be issued.
- TO
- Specifies the domain that the command is being issued to.
- [netid].domain
- Specifies the domain that the command is being issued to. It can be defined using the customization dialog. Netid is optional.
- FP
- Specifies that the command is to be routed to the current focal point.
Notes:- When INGSEND is issued on the current focal point, and TO=FP is specified, the command will be issued.
- If this parameter (TO=) is omitted, the current target domain (that is, the last domain you sent a command to) is used, if one is set. If none is set, error message AOF102I will be issued.
- CRM
- Specifies that the command routing mechanism to be used is the NetView RMTCMD command. Only CRM=RMTCMD is valid. The parameter is for compatibility only.
- CORRWAIT
- Specifies the CORRWAIT value (in seconds) to be used when INGSEND uses NetView PIPES. The Corrwait PIPE stage is necessary to trap asynchronous command output. A default for this value can be predefined for each target system, using the customization dialog. If not predefined, the default is 10 seconds. For more information on the use of this value, see the discussion of the PIPE command in NetView Operation.
- CMD
- Specifies the command to be executed. The length of the command can be up to 280 characters.
Restrictions and Limitations
- The INGSEND command will not execute under the primary POI task (PPT).
- INGSEND uses the NetView PIPE
command to trap the message output from the routed command. Not all
commands are PIPE-enabled, which means that the command may not be
treated as requested in the RESP keyword. Some examples of commands
that are not PIPE-enabled are:
- MVS commands on a NetView not exploiting EMCS.
- Commands that produce fullscreen output.
- A NetView command that is not PIPE-enabled.
For more information on RMTCMD and PIPE commands, see IBM Z NetView User's Guide.
Usage
If the command you are issuing contains either a space, a comma, or a delimiter, you should delimit the command.
You can delimit the command you are sending with either single quotation marks, double quotation marks, or '/'. If you want to include an occurrence of the delimiter character within the delimited string, the character must be preceded by another delimiter character. The delimiter character must appear as the first character of the string after the 'CMD='. INGSEND sends the command defined by the start and end delimiter. Examples of INGSEND with commands that use delimiters are shown in Examples.
Examples
The following examples show how INGSEND is used and correctly delimited:
- Consider the following example:
Command"INGSEND RESP=ACK,TO=CNM01,CMD=START TASK=DSILOG"START TASK=DSILOGwill be routed with the following:The following message will be issued to OPER2's NCCF console:Keyword Value Reason TO CNM01 Specified RESP ACK Specified OPER OPER4 Predefined CRM RMTCMD Default
OPER4 is defined using the customization dialog. The above example does not use delimiters."AOF672I COMMAND (START TASK=DSILOG) WAS EXECUTED IN DOMAIN CNM01 BY A RMTCMD COMMAND FROM OPERATOR OPER2" - The following example does not use delimiters as far as INGSEND
is concerned even though there are delimiter characters in it:
INGSEND RESP=ACK,TO=CNM01,CMD=MVS $D'RMF' - The following is correctly delimited:
INGSEND RESP=ACK,TO=CNM01,CMD='ACT CHP123' - The following example is also correctly delimited and contains
the delimiter character within the delimiters. This command is equivalent
to the second example:
INGSEND RESP=ACK,TO=CNM01,CMD='MVS $D'RMF' - The following example is also correctly delimited and is an alternative
way to type the previous example:
INGSEND RESP=ACK,TO=CNM01,CMD=/MVS $D'RMF'/ - The following example will be passed as correctly delimited but
only
'MVS $Dwill be sent because the end delimiter follows theDthus defining the command:INGSEND RESP=ACK,TO=CNM01,CMD='MVS $D'RMF' "
INGKYSND SA z/OS - Command Dialogs
Domain ID = IPUN8 ---------- INGSEND ---------- Date = 11/04/03
Operator ID = NETOPER Time = 16:58:22
Specify or revise the following parameters:
Response => YES Enter ACK, YES, NO or CORR
Operator id => Leave blank for default
Target (TO) => format: [netid.]domain
Corrwait =>
Command ...
Command ===>
PF1=Help PF2=End PF3=Return PF6=Roll PF12=Retrieve
