Before you begin, you must complete Exercise 4.3: Submitting iSeries commands in the iSeries table view.
As you know already, you can run programs and commands from the Remote
Systems view or the iSeries Table view in three ways:
- In the Remote System Explorer communications server job.
This is the one you are using currently.
- In a batch job.
- In an interactive job (to test 5250 applications).
- In a server job
Using the first option lets you run the program in the same job as the
communications server. With batch and interactive jobs, you cannot
monitor the status as easily, however, you do not tie up your communications
server and you are notified when the program command ends. Batch jobs
work as you would expect and do not require any initial setup.
Interactive programs require a 5250 emulator, and you need to first run a
STRRSESVR connectionName command to associate the emulator with a particular
connection in the Remote System Explorer communications server. A
multi-threaded debug session creates a new server job and this way keeps the
RSE communications server job free for other tasks.
Starting an interactive connection
To start an interactive connection:
- Start a 5250-emulation session.
- Sign-on to the iSeries with your User ID and password.
- Note:
- Instead of the Enter key, you may have to use the Ctrl
key in your 5250-emulation session.

- In the command line, type the command
STRRSESVR connectionName
- Press Enter.
The connectionName parameter is the name of your connection defined in the
Remote Systems view. This associates the interactive job with the
Remote System Explorer communications server.
Running the payroll program
Now you are ready to run the program that you just compiled.
Return to the workbench.
To run the program:

- In the Remote Systems view, locate the PAYROLL program that you
created.
- Right-click the PAYROLL program.
- Click Run As > Interactive on the pop-up menu.
- Switch to your 5250-emulation session.
You will see the payroll program menu.

- Type x beside Employee Master Maintenance.
- Press Enter.
- Type 234 for the Employee Number.
- Type A for the Action Code to add employee
234.
- Press Enter.
- Type any information you like about the employee.
- Press Enter.
- Play in the application as much as you like.
- Press F3 to end the applications.
- To get control of the interactive job, right-click iSeries
Objects and click Release Interactive Job on the pop-up
menu.
You can also choose to disconnect a session. You would right-click
the connection and click Disconnect on the pop-up menu.
Now you are ready to review your knowledge of this module by taking the
quiz. You can also apply what you have learned in this module by
completing the practice tasks detailed in More practice.
Quiz
- The ______ tool checks for semantic (compile) errors on your workstation
so that you can guarantee a clean compile on the iSeries.
- Compile
- LPEX Editor
- Program Generator
- Program Verifier
- The ____________ view identifies each error with the severity level of the
error, the ID of the error, the message, the severity, the line in the source
member that caused the error, the location of the source member that produced
the error, and the connection name.
- Remote Systems
- Outline
- Navigator
- iSeries Error List
- You can sort the entries in the iSeries Error List view by:
- ID
- Message
- Severity
- Line
- Location
- Connection
- All of the above
- If you used the local program verifier, then your host compiles should be
successful; no wasted iSeries cycles. (T, F)
- A compile command can be run on an iSeries server from the Remote System
Explorer, and you can retrieve error feedback from the compile. (T, F)
- From the iSeries Table view you can:
- List and sort libraries, objects, and members
- Copy, rename, delete, edit, compile and run (for programs), open with and
browse (for members) in the view from the pop-up menu
- Transfer files from one system to another
- All of the above
- You can run programs and commands from the Remote Systems view or the
iSeries Table view in:
- A Remote System Explorer communications server job
- A batch job
- An interactive job
- Multi-threaded
- All of the above
- Interactive programs require a 5250 emulator, and you need to first run a
STRRSESVR connectionName command to associate the emulator with a particular
connection in the Remote System Explorer. (T, F)
More practice
Given your experience using the Program Verifier and Compile command, and
that you have your own source on your own iSeries system, try these new
tasks: Check out Compile (Prompt) Work with Compile commands.
Assuming you receive errors in your source (add some errors into your source
if you don't have any) when you verify your source, choose insert all
error messages into the editor from the Error list. Use the product
online help to assist you in these tasks.
Module recap
You have completed Module 4. Verifying and compiling source. You have learned how to:
- Check for semantic errors on your workstation
- Start the Program Verifier tool
- Use the iSeries Error list to locate each error in the source
- Use content-assist to fix an error
- Save your source
- Re-verify source
- Change compile preferences
- Invoke the compile command
- Change the current library using the Command field in the
iSeries Table view
- Start an interactive connection
- Invoke the payroll program
Now that you know how to verify and compile source from the Remote Systems
view and run the payroll program interactively, you can move onto debugging
your payroll program. Continue to Module 5. Debugging a program.
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.