PC Command Link (PCL) Rules
(For troubleshooting PCL)
1. Make sure that version 1.20 or later of PC
Command Link (PCL) is installed on the PC. To determine the version,
launch it, then right click on the PCL icon in the status area of
the task bar. If you have an older version, contact ActionWare
support, we can send you an update. This update is included in
versions 6.01, 6.20 and 6.30 of ActionWare, and is backwards compatible back
to version 6.00.
Note: a later version of PCL, version 1.30, is now available for download from the website.
2. The same User Id must be logged on to PCL on the PC as is signed on to the iSeries emulation session. Depending on how iSeries Access is configured, the PCL monitor will either automatically run under the Windows logon, or will separately prompt the user for a logon when it is launched.
3. The User ID must be a maximum of 8 characters, and must also be enrolled in the System Distribution Directory. Use command WRKDIRE to establish this.
4. The iSeries User Id must be signed on at only one PC at a time. If the same user goes to a second PC and launches the PCL monitor, the iSeries will continue sending commands and data to the first PC.
5. The name of the iSeries as defined to iSeries Access must be the actual System name of the iSeries. To determine the System name, enter command DSPNETA. The System name is shown on the first line of the display. Note: The iSeries name can be a fully qualified name because PCL only looks at the data up to the first period. So the unqualified name ophelia (for example) will work exactly the same as the fully qualified name ophelia.smithcompany.com.
6. If you have more than one iSeries defined to iSeries Access, then the iSeries containing ActionWare must defined as the "Default system". Go to iSeries Navigator, select Environments from "My Connections", then click on Properties and select the correct machine as the default.
7. Make sure that you have a current iSeries Access Service Pack applied. At the very least, make sure you are not using the base release of iSeries Access with no Service Packs applied. To determine this, double click on the IBM iSeries Access for Windows icon normally located on the desktop. From that window, double click on the "iSeries Access for Windows Properties" icon. This will show you what version of iSeries Access you have installed, along with the Service [pack] level.
8. To verify what components of iSeries Access you have installed, double click on the IBM iSeries Access for Windows icon normally located on the desktop. From that window, double click on the Selective Setup icon. Proceed to the Selective Setup Options prompt. Choose the opt that says Ignore. I'm only going to uninstall components. (Actually you're not going to uninstall anything, you will cancel out of this sequence before you get that far.) Click Next. Next you will see the Component Selection window. Use this to determine which components of iSeries Access are installed. When finished, be sure to Cancel then Exit Setup.
9. Verify that the PC can connect to the iSeries Access
Servers running on the iSeries. The important server application used by
PCL is Data Queues. To verify, bring up a Command Prompt window.
This can be achieved by clicking on the Windows
--> Run --> cmd
--> [enter]. At the prompt enter the command cwbping [iseries
The iSeries name is the same name referred to in paragraph #5, that is the
actual System Name of the iSeries. This should produce output that looks
similar to this:
IBM iSeries Access for Windows
Version 5 Release 3 Level 0
Connection Verification Program
(C) Copyright IBM Corporation and Others 1984, 2003. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corp.
Licensed Materials - Property of IBM
To cancel the CWBPING request, press CTRL-C or CTRL-BREAK
I - Verifying connection to system ophelia...
I - Successfully connected to server application: Central Client
I - Successfully connected to server application: Network File
I - Successfully connected to server application: Network Print
I - Successfully connected to server application: Data Access
I - Successfully connected to server application: Data Queues
I - Successfully connected to server application: Remote Command
I - Successfully connected to server application: Security
I - Successfully connected to server application: DDM
I - Successfully connected to server application: Telnet
I - Connection verified to system ophelia