### High performance remote commands using TCP/IP (optional)

Remote command submission is available when Remote E/C/D is installed on the workstation. The default remote command submission facility uses
and is available when all normal Remote E/C/D host and workstation setup and configuration steps have been followed. You should verify that this has been done and is working correctly before proceeding.

A second remote command facility (high performance command facility) is also available for use when TCP/IP and NFS are used for host communications. The high performance command facility is optional. It typically has better performance than the standard facility which uses
but requires additional configuration.

The high performance command facility uses an APPC/MVS transaction to execute remote commands. The workstation
invokes a clist (IGYFINIT) on the host which starts the APPC transaction (IGYFSERV) to act as a host server which will execute MVS commands issued from the workstation via TCP/IP. (This means APPC is NOT required on the workstation as it communicates with IGYFSERV via TCP/IP.)

This section describes the additional host and workstation configuration required to enable the high performance command facility, these steps are only required if the intent is to use the high performance command facility.

The high performance command facility is supported only when using TCP/IP and NFS for host access. Each workstation may have at most one active connection to one host at a time.

##### NOTE to APPC administrators on OS/390 R3

The high performance command facility uses an APPC transaction to execute the remote commands. There is currently an APPC problem on OS/390 R3 such that both partners of an APPC conversation may not be on the same system (i.e. both partners are using a blank partner_LU name). The APPC/MVS APAR number is OW26216. The fix is PTF UW37792.

There is a workaround if you have two LPARs sharing the system (as in USERIDS, RACF, DASD, etc). You'll need to find and modify the partner_LU specification in IGYFINIT and in IGYFSERV. IGYFINIT's partner should be the secondary machine (the system pointed to by the user's MVSINFO.DAT file is the primary machine). IGYFSERV's partner should be the primary machine and the transaction (IGYFTPAD) should be defined on the secondary machine.

If you are using OS/390 R3 and do not have two LPARS sharing the same system, the high performance command facility cannot be enabled until PTF UW37792 is installed.

#### Host configuration for high performance command facility

The following parts must be available on the host system:

- IGYFTPAD (Sample JCL - defines the APPC server transaction)
- IGYFINIT (REXX CLIST - to start the command server)
- IGYFSERV (REXX CLIST - the command server)

The above CLISTs are in the SIGYCLST data set, and the above sample JCL is in the SIGYSAMP data set. These data sets are supplied with either the host product IBM COBOL for OS/390 & VM V2R1 (with the fix for APAR PQ13212 applied), or the host product IBM COBOL for MVS & VM V1R2 (with the fix for APAR PQ13211 applied),

The first step is to define the APPC transaction that will act as a command server for VisualAge for COBOL. The IGYFTPAD sample JCL, (Figure 1) can be used to define the APPC transaction.

It is expected that the following things have already been done by your system programmer or APPC Administrator and are in place on your system.

- Use the ASCHPMxx member of SYS1.PARMLIB to define scheduling information for the APPC/MVS transaction scheduler.
- Control the dispatching priority of the IGYFSERV transaction program by using SRM parameters to associate it with a domain and performance group. IGYFSERV issues TSO commands; it should be assigned to a TSO performance group.
- All other configuration and setup required on the host for Remote E/C/D using TCP/IP has been done.

#### Workstation Setup for high performance command facility

On the workstation you need to insure that:

- The SIGYCLST line in the MVSINFO.DAT file includes the data set where IGYFINIT and IGYFSERV can be found (the SYSPROC data set on line 20 of the sample JCL).
- The mvscomm line in the MVSINFO.DAT file is set to yes. (The default is no due to the additional setup required.)

Once the above is done (along with the rest of the setup for Remote E/C/D), you can verify the high performance MVS commands facility by doing

After the drives have been successfully connected, you should see some messages (a couple of dozen or so) about setting up APPC. The last message should end with CONFIRMED succeeded.

#### Trouble-shooting

The following list points out some of the things to look for if you are unsuccessful in using High Performance Command Facility:

- If you don't see the messages about setting up APPC, it's most likely one of the following:
  - The MVSINFO.DAT SIGYCLST line is set the wrong host data set.
  - the MVSINFO.DAT mvscomm line is not set to yes.
  - You don't have read authority to the SIGYCLST data set.
  - TCP/IP is not active.
- If you see the messages but don't see the confirmed succeeded message, it's most likely the APPC server transaction was unable to start. Some of the likely causes are:
  - It was unable to allocate SYSPROC or SYSTSPRT.
  - It's pointing to the wrong SYSPROC (SYSPROC needs to point to the SIGYCLST data set).
  - It couldn't open/access the message_data_set.
  - There aren't enough APPC Scheduler Initiators available.
  - APPC or ASCH address spaces are not active.