Our Help Desk often gets calls from users who get hung up in AS/400 applications, Operational Assistant, Working...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
with Spool Files, etc. I took last month's winning tip and made it more dynamic. Rather than just pressing enter and F9 to restart the DSPSCRN command to view a user's screen I set it up to view all users ACTIVE AS/400 screens. It also gives the MIS or Help Desk staff person the ability to refresh the screen to display user screens as they update their screens or navigate to other screens.
The RPG program CUGDSP calls a number of CLPs to build the ACTIVE list and omits SYSREQ or GROUP jobs. Selecting these types of jobs would make the original program hang. After a user screen has been selected to view, the program also requests permission to view the screen as well as identifying to the user the person viewing the screen. This is to prevent MIS or Help Desk staff of viewing user screens without the user knowing. If the user gives permission, then the MIS or Help Desk person can view the screen otherwise the program returns to the list active user screen and awaits another selection or F3 to exit the program. When enter is pressed the program will refresh the screen and display the current state of the user's screen. If F3 is pressed the screen exits and refreshes the list active user screen.
The program will also check to ensure that the user session selected to view is still ACTIVE and also omitting the session that CUGDSP is running on.
Other information available is device number, user profile, job number, user name, out queue, message notification, and whether the user has a group profile. This information all becomes very important when trying to troubleshoot problems.
Display screen of Active User Sessions