Example 1
Request information on all remote systems entered in the partner list:
Short output:
|
Long output:
|
The information displayed is explained below:
NAME
Symbolic names of the remote systems entered in the partner list.
This field remains empty for dynamic partners (see the first line in the example).
STATE
Status of the partner system.
ACT
The partner system is active.
DEACT
The partner system is deactivated.
NOCON
The transport connection setup failed.
LUNK
The local system is unknown on the remote FT system.
RUNK
The partner system is unknown on the local transport system.
ADEAC
The partner system is active. It is deactivated if the connection cannot be established. This state is only displayed if STATE=*AUTOMATIC-DEACTIVATION has been specified; otherwise, these partner systems are maintained under the ACT status.
AINAC
The partner system was deactivated following several unsuccessful attempts to establish a connection. This status is only possible if STATE=*AUTOMATIC-DEACTIVATION has been specified.
LAUTH
The local system could not be authenticated in the partner system. A current, public key of the local openFT instance must be made available to the partner system.
RAUTH
The partner system could not be authenticated in the local system. A current, public key of the partner system must be imported to the SYSKEY library.
DIERR
A data integrity error was detected on the connection to the partner system. This can be due either to an error in the transport system, or to manipulation attempts along the transfer route. The connection was terminated but the affected request was not (if it is restartable).
NOKEY
The partner does not accept a connection without encryption, but no key is present in the local system. A new key must be created using FTCREKEY.
IDREJ
The partner or a go-between instance does not accept the instance ID sent from the local system. You must check to see if the local instance ID is consistent with the entry in the partner’s partner list.
SECLEV
Security level assigned to the remote system when it was entered in the partner list. These security levels apply only if the FTAC-BS2000 is also implemented. STD stands for the default security level set with the FTMODOPT command.
PRI
Priority of a partner with respect to the processing of requests. The possible values are NORM, LOW and HIGH.
TRACE
Trace setting. You may specify the values ON, OFF and FTOPT (if FTMODPTN is specified, TRACE=*BY-FT-OPTIONS).
LOC
Number of FT requests that have been submitted in the local system and that address the FT system specified with PARTNER.
REM
Number of FT requests that have been submitted in the remote FT system and addressed to the local FT system. The remote system is specified in PARTNER.
P-CHK
Type of sender checking for the current partner:
FTOPT
The global setting is valid.
T-A
The expanded sender checking is enabled for specific partners.
STD
The expanded sender checking is disabled for specific partners.
AUTH
With the aid of its public key in the SYSKEY library, the partner is subjected to an identity check (“authenticated”) by cryptographic means. The partner support the authentication level 2.
AUTH!
With the aid of its public key in the SYSKEY library, the partner is subjected to an identity check (“authenticated”) by cryptographic means. The partner support the authentication level 1.
NOKEY
No valid key is available from the partner system although authentication is required.
AUTHM
Authentication must be used.
ADDRESS
Partner address under which the remote system can be accessed. For more information on partner addresses, see section “Specifying partner addresses”.
IDENTIFICATION
Instance ID of the partner (also see the FTADDPTN command).
ROUTING
SESSION-ROUTING-INFO of the partner, where required (also see the FTADDPTN command).
INBND
State of the partner for inbound requests:
ACT
Inbound function is activated, i.e. requests issued remotely are processed.
DEACT
Inbound function is deactivated, i.e. requests issued remotely are rejected.
REQU-P
Operating mode for asynchronous outbound requests:
STD
Requests to this partner can be processed in parallel.
SERIAL
Requests to this partner are always processed serially.
RECOV
Restart function (recovery) for outbound requests:
FTOPT
The global setting is valid.
ON
The restart function for outbound requests to this partner system is activated.
OFF
The restart function for outbound requests to this partner system is deactivated.
Example 2
All partner entries in the partner list are to be saved in a form that will facilitate importing the entries into a different partner list as required. To do this, the output from the FTSHWPTN command is converted to the correct format using LAYOUT=*ZOS-PROC and piped to a file with the name PARTZOS.CLIST.
|
If the partner systems are to be entered in a partner list again, this can be done using the TSO command EXEC:
EXEC PARTZOS
This method also provides a simple way of importing partner entries from a z/OS partner list into a BS2000 partner list. To do this, LAYOUT=*BS2-PROC must be specified in FTSHWPTN and the file that is generated must be transferred to BS2000 and executed there. In the same way, a file created in BS2000 (as of openFT V9.0) using SHOW-FT-PARTNER can be used to enter partner systems in the z/OS partner list.