Initiating Data Transfers from an Operating System

Command Line Using Client Access Incoming Remote

Command Service
Important Note: This document discusses Client Access for Microsoft
Windows 95 and Windows NT, Client Access Express, and IBM iSeries
Access products. These names essentially refer to the same product;
however, the functionality and name changed over the last several
releases. For the purposes of this document, the terms Client Access,
Client Access Express, and iSeries Access may be used interchangeably.
Where a difference is important, the version of the product is used to
identify the differences.
This document describes a method of running data transfers on
Microsoft Windows 9x/ME and Microsoft Windows NT/2000 Pro/2003
Server/XP/Vista Business/Vista Enterprise/Vista Ultimate using the
RUNRMTCMD command and the Client Access Incoming Remote
Command Service.
Notes: In Windows NT/2000/2003/XP/Vista, this method requires that
only one user be logged on to the workstation and that the
RUNRMTCMD specify the same Microsoft Windows user account that is
logged on to the desktop. If the same user name exists as the domain
and the local account (for example, MyDomain\myUser and myUser),
the local account must be used or the fully qualified domain\user name
must be specified on the RUNRMTCMD user profile parameter. For other
methods of doing batch transfers in Windows NT/2000/2003/XP/Vista,
refer to the Alternatives section at the end of this document.
Furthermore, in Microsoft Windows Vista the service programs are
heavily restricted, including IRC, resulting in unfavorable results such as
cut-n-paste or copy-n-paste.
The first step in this process is to create and save a transfer program
which will successfully run in the interactive GUI transfer. That is done
using the Data Transfer From/To operating system programs.

Once you are to the point where you can get that transfer to run, test it
using the batch program executables. The batch executables will run the
saved transfer profiles with no user interaction. The batch executables
are located in the Client Access program directory. Usually that location
is C:\Program Files\IBM\Client Access\ and the programs themselves are
RTOPCB.EXE for transfers from the IBM System i products system to the
PC or RFROMPCB.EXE for transfers to the System i from the PC.

Notice that neither the saved transfer request nor the RTOPCB
command accept a user profile or password as a parameter. The
RTOPCB and RFROMPCB batch data transfer commands always run
using the user profile defined as the default profile for the System i. To
avoid prompting (or a hang due to the prompting in Windows
NT/2000/2003/XP/Vista) use Operations Navigator or iSeries Navigator
to verify that you have a default user ID defined for the System i. Open
Operations Navigator or iSeries Navigator, right-click on the System i
name, select Properties, and click on the Connection tab. Verify that Use
default user ID, Prompt as needed or Use Windows user name
and password, no prompting is selected. Sign on the System i once
to cache the password. Opening the System i in Operations Navigator or
iSeries Navigator will force a sign on if the password is not already
cached.
A user ID and password can be specified when the transfer request is
initiated if the RXFERPCB command is used instead of RTOPCB or
RFROMPCB .

The service for Client Access Remote Command must be started before
the remote command can be sent to the PC. By default, it is not started.

Windows 9x/ME
You must first configure the security options using the remote command
tab of the Client Access properties in the control panel. In the diagram

below any user from any system can run a remote command because of
the "*.*" entry. The entry for RCHASSC2.RCHLAND.IBM.COM and
RCUSER is an example of restricting access to a system and particular
user (the "*.*" entry would have to be removed for this entry to have
any affect). Note that system names must be the fully-qualified TCP/IP
host name of the System i.

Client Access Remote Command is started by running the command

CWBRXD.EXE. The remote command service can be configured to
autostart at boot up by checking the Automatically start incoming
remote command in the configuration shown above.

Windows NT/2000/2003/XP/Vista
System i Access for Windows Remote Command is started by accessing
Windows Control Panel > Administrative Tools , and then double-clicking
on the Services icon. If the service is to start at boot up, change the
Startup Type property to Automatic. To prevent hangs in Windows
NT/2000/2003/XP/Vista caused by invalid, missing, or expired
passwords, also check the Allow service to interact with desktop
option. In Windows 2000/2003/XP, the services panel will look like this:

Now that everything is configured, run the transfer. To start the data
transfer from the System i, run the RUNRMTCMD command from an
operating system command line or CL program. The parameters are
shown below:

Command: Contains the batch data transfer command.

Remote location: The remote location where you want to run this
transfer. A specific location must be specified. For TCP/IP-connected
workstations, this can be the PC host name (if configured in a Domain
Name Server) or a TCP/IP address. RUNRMTCMD does not allow you to
default to a remote location of the workstation running the
RUNRMTCMD . To run the PC command at the workstation
RUNRMTCMD is called from, use the STRPCCMD command or other
system APIs to retrieve the TCP/IP address or controller name.
Notes: The Remote user ID and password are the Windows Desktop
User ID and Password. To verify the name of the current user logged
on the workstation, press Ctrl+Alt+Delete, and read the logon
information. The User IDs must be the same or the transfer may appear
to hang. In addition, Windows passwords are case sensitive; therefore,
the password must be enclosed in single quotation marks (or use an
uppercase-only password).
If your spooled file reports message " 'c:\Program' is not recognized as
an internal or external command, operable program or batch file ", you
must use the 8 character naming in your RUNRMTCMD, for example,
replace command:
RUNRMTCMD CMD('"c:\Program Files\IBM\Client Access\rtopcb.exe" /s
C:\QCUSTCDT.DTF') RMTLOCNAME('9.10.53.112' *IP)

RMTUSER(V2KEA196) RMTPWD('Password')
with the following command:
RUNRMTCMD CMD('c:\Progra~1\IBM\Client~1\rtopcb.exe /s
C:\QCUSTCDT.DTF') RMTLOCNAME('9.10.53.112' *IP)
RMTUSER(V2KEA196) RMTPWD('Password')
In Windows 9x/ME, the user ID and password are those configured in
the Client Access remote command properties as shown above.
Press the Enter key. This runs the batch program on the PC. Successful
completion of the RUNRMTCMD command does not imply that the
actual transfer completed successfully. To verify that the transfer
completed successfully, run the WRKSPLF command, and view the last
QSYSPRT spooled file. It should look similar to the sample below:

The final lines of the output show the following:

Receive completed successfully .

Rows transferred: 12
Related Documents
Refer to the following Rochester Support Center Knowledgebase
document:
21115031, Alternatives to Batch Data Transfer: Data Transfer
Automation Objects; Import files with FTP/QNTC; ActiveX Data
Objects:
Support Line users who have access to Entitled/Restricted documents
can refer to Rochester Support Center Knowledgebase document
20583101, which details a more complex configuration that allows
unattended data transfers in Windows NT/2000/2003/XP/Vista.