OS/400 Edition
Volume 11, Number 44 -- October 21, 2002

Admin Alert: Configuring PC5250 for Inactive Job Disconnection

by Joe Hertvik

I didn't expect my column on dealing with inactive jobs to become a continuing story. It started a few weeks ago, when I explained how to configure OS/400 to dispose of inactive jobs. A week later, reader Robert Boling suggested additional configuration parameters, but we also discovered that automatic job disconnection didn't work correctly for some Telnet sessions. In this column, I'll resolve the Telnet disconnection problem by demonstrating how to configure PC5250 for fixed device names.

Kudos are awarded to readers Douglas Meyer and Bill Roha for pointing us in the right direction for resolving the Telnet session disconnection dilemma. The problem is that inactive Telnet jobs--including Telnet sessions that are generated from the PC5250 software that comes with IBM's Client Access Express for Windows package--weren't being automatically disconnected when the inactive Telnet job passed the inactivity time-out system value (QINACTITV) and the inactive job message queue system value (QINACTMSGQ) was set to disconnect inactive jobs (*DSCJOB). Instead of being disconnected, these jobs were ended with the following messages showing in the target device's job log:

CPF1358 - "DSCJOB not allowed for Server jobs."
CPI1127 - "All jobs at work station device_name ended."

Both Douglas and Bill pointed out that these problems are limited to virtual 5250 devices (those with generated device names in the QPADEVxxxx format), rather than devices that have a fixed device name. This fact can be easily tested by going into a PC5250 session with a generated QPADEVxxxx name and typing in the Disconnect Job (DSCJOB) command.

For generated Telnet device sessions using the QPADEVxxxx naming format (QPADEV0001, QPADEV0002, etc.), you will receive a message similar to the ones listed above. The reason these jobs don't disconnect is unclear, but it is a definite symptom of generated Telnet session names.

To disconnect your PC5250 job by using DSCJOB (or *DSCJOB in the QINACTMSGQ system value), reconfigure your session to use a fixed device name. Do this by selecting Communication, then Configuration, from the PC5250 menu bar, which brings up the Configure PC5250 screen. On that screen, click the Specify Workstation ID radio button and enter a fixed device name (such as MIDSERVER) in the designated input box, and then restart your session. Once restarted, you will be able to disconnect your session by using the DSCJOB command. Using a fixed device name will also solve the problem with OS/400 automatically disconnecting--rather than ending--this session when it exceeds the QINACTITV timer value.

While hard-coding a specific device name will allow an inactive PC5250 session to automatically disconnect when it exceeds the QINACTITV timer, the act of assigning and configuring multiple (in some cases, several hundred) PC5250 sessions to use unique device names can be intimidating. There are enough unique configuration entries to configure and keep track of on a PC; you don't need one more to complicate matters. To get around hard-coding a unique device name for every single PC5250 session, you can configure PC5250 to use either your user's Windows user name or your Windows computer name to create a unique OS/400 session device name for your PC5250 sessions. Here's how it works with the PC5250 package that comes Client Access Express for Windows V5R1M0.

In the Configure PC5250 screen in your PC5250 session, there are several choices for the device name that your PC5250 sessions will use. If you want OS/400 to generate a QPADEVxxxx device, click the Specify Workstation ID radio button on the screen and leave the device name input box blank. To specify a hard-coded device name--as I already explained--click the Specify Workstation ID radio button and enter a unique name in the device name input box.

If you want to use your Windows computer name as your OS/400 device name, click the Use Computer Name radio button on the Configure PC5250 screen. Upon connecting, PC5250 and OS/400 will create a device that has the same name as your system's Windows computer name. The only difference in naming conventions is that OS/400 device names are limited to 10 characters and a Windows computer name can be longer than 10 characters; when the Windows computer name is longer than 10 characters, excess characters are truncated from the computer name to enter it as an OS/400 device name.

If you want to use the Windows user name of a user who is currently signed on, click the Use Windows User Name radio button. Again, the new device name will be truncated if it exceeds 10 characters.

To ensure that your device names are unique on the user's desktop and in your network, you can also click the Avoid duplicate names on this workstation and Avoid duplicate names with other workstations radio buttons on the Configure PC5250 screen. These buttons can be used in conjunction with either the Use Computer name or Use Windows user names settings. By activating these radio buttons, PC5250 will add unique identifying characters to the end of the device names. This will prevent device name conflicts between multiple sessions running on your desktop, or between your desktop device names and device names on other workstations connecting to the same iSeries or AS/400. If your generated device names are 10 characters long, these identifiers will be added to the device name in either the ninth or tenth character, overriding whatever characters may already be sitting in those positions.

While there are some twists and turns in the way you configure your client and OS/400 box to handle inactive jobs, configuration becomes easier once you know the proper techniques for modifying your setup.

Sponsored By

Replace pre-printed forms with digital documents delivered via print, email, and fax using Electronic Document Distribution (EDD) solutions for the iSeries 400 enterprise.

Engineered with Brooktrout intelligent technologies, these EDD solutions seamlessly integrate with major business applications and offer error-free creation, management, and automated delivery of mission-critical documents, electronic forms, MICR checks, and bar code labels, all with plug-and-play implementation.

Better Documents. Better Delivery. Better Together.




Maximum Availability
Quadrant Software
BCD Int'l
Electronic Storage Corp.
Cosyn Software
Affirmative Computer


IBM Says New iSeries Hardware, OS/400 Due in 2003

Driving Fast with Dr. Frank Soltis at the iSeries Nation Town Hall

A Conversation with IBM's New VP of iSeries Marketing

Admin Alert: Configuring PC5250 for Inactive Job Disconnection

Big Blue Rises Above the IT Market Downdraft

Jacada Studio Leverages RPG, COBOL Skills to Make New GUI Apps

As I See It: The Vision Thing

But Wait, There's More. . .

Timothy Prickett Morgan

Managing Editor
Shannon Pastore

Contributing Editors:
Dan Burger
Joe Hertvik
Kevin Vandever
Shannon O'Donnell
Victor Rozek
Hesh Wiener
Alex Woodie

Publisher and
Advertising Director:

Jenny Thomas

Advertising Sales Representative
Kim Reed

Contact the Editors
Do you have a gripe, inside dope or an opinion?
Email the editors:

Last Updated: 10/21/02
Copyright © 1996-2008 Guild Companies, Inc. All Rights Reserved.