Output information on RFA connections
Component: | RFA |
Functional area: | Pubset and MRSCAT management |
Domain: | MULTI-CATALOG-AND-PUBSET-MGMT |
Privileges: | STD-PROCESSING |
This command is only available to users who have the software product RFA (see “RFA” manual [31]).
Function
The SHOW-RFA-CONNECTIONS command allows the user to request information on all existing RFA connections. The information is output to SYSOUT. The user receives an output line for the local processor (beginning with “LOCAL HOST”) and one output line for each existing RFA connection (beginning with “CONNECTION”) containing the following information:
catalog ID to which the RFA connection exists (for RFA connections only)
indication of whether the RFA connection is local or remote
processor name to which the RFA connection is set up
user ID of the AFR partner task or of the local task
task sequence number (TSN) of the AFR partner task or the local task
The RFA connection is displayed once only per catalog ID, even if more than one SET-RFA-CONNECTION command was issued for the catalog ID. A maximum of 16 RFA connections can exist for different catalogs.
The command supports structured output in S variables (see "Output in S variables").
Format
SHOW-RFA-CONNECTIONS |
CATALOG-ID = *ALL / <cat-id 1..4> |
Operands
CATALOG-ID = <cat-id 1..4> / *ALL
Catalog ID of an RFA connection for which information was requested. Specifying *ALL produces information on all RFA connections.
Return codes
(SC2) | SC1 | Maincode | Meaning |
|---|---|---|---|
0 | RFA0002 | Command executed | |
32 | RFA0019 | Output incomplete | |
32 | RFA0020 | Error in outputting to SYSOUT | |
32 | CMD2009 | Error during generation of output variables | |
64 | RFA0017 | No RFA connection exists | |
64 | RFA0018 | No RFA connection exists for the specified catalog ID |
Output format
The information is output in table form. The first line contains information on the local processor (without catalog ID) and begins with “LOCAL HOST:”. This is followed by one information line for each existing RFA connection. These lines each begin with “CONNECTION:” and are output in ascending order of catalog ID. The information is split up into the following 5 output columns:
Output column | Meaning |
|---|---|
CATID | Catalog ID to which the RFA connection exists. Only one RFA connection is displayed per catalog ID. No catalog ID is displayed in the information line for the local processor. |
STATE | LOCAL is displayed for a catalog ID assigned to the local processor or, for a shared pubset, to the master processor. REMOTE is displayed for a catalog ID assigned to a remote processor or, for a shared pubset, to a slave processor. |
HOST | BCAM name of the processor to which the RFA connection exists. |
USERID | User ID of the AFR partner task (when STATE is shown as REMOTE) or of the local task (when STATE is shown as LOCAL). |
TSN | Task sequence number of the AFR partner task or of the local task. |
Output in S variables
Output information | Name of the S variable | T | Contents | Condition |
|---|---|---|---|---|
Catalog ID to which the RFA connection exists | var(*LIST).CAT-ID | S | <cat-id 1..4> | |
Type of information | var(*LIST).INDICATOR | S | *CONN | |
Name of the processor to which the RFA connection exists | var(*LIST).PARTNER-NAME | S | <alphan.-name 1..8> | |
RFA connection status | var(*LIST).PUBSET-STA | S | *LOC | |
TSN of the AFR partner task or the local task | var(*LIST).TSN | S | <name 1..4> | |
User ID of the AFR partner task or the local task | var(*LIST).USER-ID | S | <name 1..8> |
Example
/show-rfa-connections
% CATID STATE HOST USERID TSN %LOCAL HOST: LOCAL D017ZE11 USER2 0C1R %CONNECTION: 2OSG REMOTE D016ZE04 USER2 2PQT %CONNECTION: 2OS6 REMOTE D016ZE04 USER2 2PQT
In the dialog job with the task sequence number 0C1R and the user ID USER2, the user issues the SHOW-RFA-CONNECTIONS command to request information on existing RFA connections.
The output shows the local processor D017ZE11.
Two remote RFA connections to the processor D016ZE04 with catalogs 2OSG and 2OS6 are shown.
On the remote processor D016ZE04 there is one partner task active under the user ID USER2 and the task sequence number 2PQT.