Harness the powerful capabilities of Operational Assistant to make life easier for system operators.
Brief: Operational Assistant (OA) is an integral part of OS/400 that provides an intuitive interface to many of the frequently used system operator commands. Because OA is so highly integrated, it is difficult to get a handle on who is using it, what controls it, when it changes, where it appears and how to control it. This article supplies you with the answers to these central questions and offers some perspectives on using OA to simplify system operators' tasks.
When the AS/400 was introduced in 1988, a diagram showing the S/36 and S/38 as merging arrows received plenty of coverage from IBM hypesters. "Here," they said, "is a computer that combines the state-of-the-art database capabilities of the S/38 with the legendary ease of use of the S/36." Midrange programmers applauded. We were so certain that we had found a way to have our cake and eat it too. But all too soon, clouds appeared on this happy horizon. S/36 shops accustomed to running the system with clerical staff, an occasional phone call to their software vendor and one guy who enjoyed messing around with the system were in big trouble. Those at the receiving end of their phone calls were in despair. How do you explain to an operator who calls for help when the paper jams in the printer how to handle routing printouts on an AS/400?
To its credit, IBM listened. In September 1990, IBM added Operational Assistant (OA) to the base operating system with V1R3 of OS/400. OA is a state of mind more than a specific product. It makes the interface to OS/400 commands less intimidating by hiding options and parameters that are not needed under average circumstances. To accomplish this goal, OA combines an easy-to-use menu system with pared-down displays for most frequently used system operator commands. This flexible approach allows a programmer to incorporate OA displays in a customized menu or to give operators access to one or more OA menus. As of V2R1M1 of OS/400, the OA interface covers printer output, jobs and job queues, messages, problem determination, library backup and system cleanup (message queues, job logs and so forth). V2R2 expands OA even further-see the sidebar on page 42 for details. The security rules of OS/400 remain fully in force, preventing operators from accessing or accidentally deleting objects without the proper authorization.
Perhaps the most difficult thing about OA is that it is too fully integrated into OS/400. The developers made a conscious decision to make the OA interface as seamless as possible. This is particularly obvious in the case of OA documentation. Don't go searching for an OA manual or even scanning the CD-ROM for "operational assistant." Most OA documentation is included in the New User's Guide and the Operator's Guide, with additional tidbits scattered throughout the remainder of the AS/400 manuals. An exception is online help which includes a high-level list of OA topics. Unfortunately, very little detail is provided.
Because OA is an integral part of OS/400, you may be using OA without knowing it. Conversely, OA defaults may interfere with your ability to access information in the most efficient way. This article examines how to activate OA (for the entire system or for specific users or commands), what the OA displays look like and some ideas for incorporating OA displays into your own applications.
Take Control
The system value, QASTLVL, determines the systemwide default level of displays for OS/400 commands like Work with Spooled Files (WRKSPLF). The valid entries are *BASIC (OA displays), *INTERMED (normal displays) and *ADVANCED (options and function keys are suppressed on displays). If a particular command does not have *BASIC and/or *ADVANCED displays, the normal *INTERMED displays are always used. The default value when OS/400 is shipped is *BASIC, encouraging all new AS/400 users to work with the OA versions of the command displays.
Setting the system value QATNPGM to the special value *ASSIST provides users with an Attention key interface to the main OA menu. This can be especially helpful for users with dual responsibilities such as accounting data entry and system operator. Setting QATNPGM to *ASSIST calls QSYS/QEZMAIN, which displays the ASSIST menu, when the Attention key is pressed.
Both the assistance level and the Attention key handling program can be set for individual users in the user profile. Assistance level can be set to *BASIC, *INTERMED, *ADVANCED or *SYSVAL. The Attention key handling program parameter allows the special values *ASSIST and *SYSVAL, or any of the callable OA programs may be coded explicitly.
Finally, the assistance level for specific commands can be set in two ways (1 lists the commands that offer OA displays).
Finally, the assistance level for specific commands can be set in two ways (Figure 1 lists the commands that offer OA displays).
The ASTLVL parameter can be entered as a command parameter, setting the assistance level only for the current execution of the command.
The user may press F21 from the display or work-with screen of a command to change the assistance level. This type of change remains in effect until it is explicitly changed using F21 or the default for the user profile is reset. (A word of caution: If your user profile assistance level is set to *SYSVAL, changing the system value will not reset your F21 assistance level values. You must actually reset the user profile parameter.)
Changes to the assistance level for either system value QASTLVL or the user profile take place immediately.
The *BASIC Perspective
Probably the easiest way to learn about OA is to set your user profile to assistance level *BASIC and type GO ASSIST on the command line. The menu illustrated in 2 will be presented. From this menu you can branch to all the other OA menus and jobs.
Probably the easiest way to learn about OA is to set your user profile to assistance level *BASIC and type GO ASSIST on the command line. The menu illustrated in Figure 2 will be presented. From this menu you can branch to all the other OA menus and jobs.
The main OA menu is designed to accommodate a user who has traditional system operator responsibilities. It branches to menus that work with printer output, jobs, messages, user profiles, devices and system problems. The menu options displayed are controlled by the user's class. For example, only users with a class of *SYSOPR or higher will see option 10 on the ASSIST menu.
Where Did That *#@!&%# Printout Go?
To new users, tracking down a report on the AS/400 can feel like a walk through the fun house at the fireman's carnival. Nothing is what it seems and the friend you are searching for always seems to be just around the corner. To give you an idea of how OA simplifies the process, let's take a look at the OA displays for spooled output.
When you choose option 1 from the menu shown in 2, OS/400 runs the WRKSPLF command. The display will look similar to 3 and can be toggled to show date, pages and form type by pressing F11. The default is to show spooled output only for the current user and to suppress all system output such as job logs. To change the file selections, press F14 and make your choices on the simple panel shown in 4.
When you choose option 1 from the menu shown in Figure 2, OS/400 runs the WRKSPLF command. The display will look similar to Figure 3 and can be toggled to show date, pages and form type by pressing F11. The default is to show spooled output only for the current user and to suppress all system output such as job logs. To change the file selections, press F14 and make your choices on the simple panel shown in Figure 4.
Once the output you are interested in is displayed, standard WRKSPLF options are available to change, hold, delete, display or release a spool file. Suggested actions are shown in parentheses next to entries that may require action. For example, on the panel in 3, the user is prompted to (use Opt 6) to release the held spool files. The secondary panels are also structured to eliminate unnecessary prompts as shown in the Change Printer Output panel (5). A nice feature of OA is illustrated by the list which is displayed if you press F4 in the "Printer to Use" parameter. OA lists the actual printers attached to the system with their status, forms and, optionally, their descriptions. This makes it easy to select the correct device even on an unfamiliar system.
Once the output you are interested in is displayed, standard WRKSPLF options are available to change, hold, delete, display or release a spool file. Suggested actions are shown in parentheses next to entries that may require action. For example, on the panel in Figure 3, the user is prompted to (use Opt 6) to release the held spool files. The secondary panels are also structured to eliminate unnecessary prompts as shown in the Change Printer Output panel (Figure 5). A nice feature of OA is illustrated by the list which is displayed if you press F4 in the "Printer to Use" parameter. OA lists the actual printers attached to the system with their status, forms and, optionally, their descriptions. This makes it easy to select the correct device even on an unfamiliar system.
OA's guidance through the maze of printed output doesn't end with the WRKSPLF display. F22 is enabled to switch from the spooled file display to the Work with Printers panel shown in 6. Again, suggested actions are given in parentheses and the display has been abridged to list only the most relevant information. All OA displays include F21 to change the assistance level so that an operator can easily expand any of the panels to include more detailed information. Best of all, when you select option 1 to start a printer, OA attempts to actually get the printer to ready status. In addition to running the Start Printer Writer (STRPRTWTR) command, OA also attempts to release the output queue and/or the writer if either is held, start the QSPL subsystem and release the QSPL job queue if necessary.
OA's guidance through the maze of printed output doesn't end with the WRKSPLF display. F22 is enabled to switch from the spooled file display to the Work with Printers panel shown in Figure 6. Again, suggested actions are given in parentheses and the display has been abridged to list only the most relevant information. All OA displays include F21 to change the assistance level so that an operator can easily expand any of the panels to include more detailed information. Best of all, when you select option 1 to start a printer, OA attempts to actually get the printer to ready status. In addition to running the Start Printer Writer (STRPRTWTR) command, OA also attempts to release the output queue and/or the writer if either is held, start the QSPL subsystem and release the QSPL job queue if necessary.
The net result of the OA interface to OS/400 printer support is that isolating the printout you need is much easier because unnecessary information is eliminated from the displays. This feature, coupled with the recommendations for action, simplified entry screens and multi-command options, makes controlling spool entries far more intuitive than under the normal OS/400 interface. I've used printer support as an example for two reasons. Many newcomers to the AS/400 struggle with it and, as a consequence, this is one of the areas where OA coverage is most complete.
If you have job accounting started on your AS/400, an additional display is available to show the status of completed printouts, including where they have printed. Under V2R2M0, the OA SETUP menu includes an option to start job accounting. For more information on job accounting, see "Job Accounting- OS/400's Built-in Watchdog," MC, October 1992.
OA offers similar features for managing batch jobs, messages and non-printer devices such as workstations, tape drives and diskette drives. With V2R2M0 of OS/400, OA has been expanded to include communications configuration support and disk space usage analysis.
Other Neat Stuff
OA menus have some special options that go beyond simplifying control of the system and deal with specific areas that are important to system operators. They include:
An uncomplicated Work with User Profiles (WRKUSRPRF) command automatically creates directory and office enrollment entries. The remove option prompts you to delete or reassign all objects owned by the profile before confirming its removal.
The print local device addresses option on the DEVICE-STS menu runs the Print Device Addresses (PRTDEV-ADR) command, which produces an easy-to- follow grid showing each controller configured for the system and all local devices assigned by address on each port. A sample printout is illustrated in 7.
The print local device addresses option on the DEVICE-STS menu runs the Print Device Addresses (PRTDEV-ADR) command, which produces an easy-to- follow grid showing each controller configured for the system and all local devices assigned by address on each port. A sample printout is illustrated in Figure 7.
Automatic cleanup of message queues, job logs, system journals and logs, and OfficeVision/400 calendar items can be set based on the age of the items. The setup panel for cleanup is shown in 8. Once the cleanup job is initiated using the Start Cleanup (STRCLNUP) command, cleanup will run at the specified time or at power down if the special value *SCDPWROFF is used. In most cases, STRCLNUP should be included in your startup program, but it can be run interactively or from the OA CLEANUP menu. You can also use OA to piggyback your own cleanup such as periodic history file purges. To use this support, refer to the instructions in 9.
Automatic cleanup of message queues, job logs, system journals and logs, and OfficeVision/400 calendar items can be set based on the age of the items. The setup panel for cleanup is shown in Figure 8. Once the cleanup job is initiated using the Start Cleanup (STRCLNUP) command, cleanup will run at the specified time or at power down if the special value *SCDPWROFF is used. In most cases, STRCLNUP should be included in your startup program, but it can be run interactively or from the OA CLEANUP menu. You can also use OA to piggyback your own cleanup such as periodic history file purges. To use this support, refer to the instructions in Figure 9.
Scheduling for power on/power off based on defaults for each day of the week which you can access from the POWER menu. An interactive panel lets you override the schedule for specific days to accommodate holiday and special maintenance schedules. The default power off option for OA is *IMMED. You can customize power off using a method similar to the cleanup customization shown in 9. The CL program to retrieve is QSYS/QEZPWROFF.
Scheduling for power on/power off based on defaults for each day of the week which you can access from the POWER menu. An interactive panel lets you override the schedule for specific days to accommodate holiday and special maintenance schedules. The default power off option for OA is *IMMED. You can customize power off using a method similar to the cleanup customization shown in Figure 9. The CL program to retrieve is QSYS/QEZPWROFF.
System and library backup can be selected from the OA BACKUP menu. The menu includes options to back up all user libraries, all IBM libraries, the entire system or user libraries based on a library backup list. The default library backup list contains all user libraries. You can select or deselect libraries using the panel shown in 10. When the backup is actually initiated, the operator is prompted for tape information and whether to include all objects or only changed objects. With V2R2M0, backup support has been greatly enhanced and includes daily, weekly and monthly scheduling options.
System and library backup can be selected from the OA BACKUP menu. The menu includes options to back up all user libraries, all IBM libraries, the entire system or user libraries based on a library backup list. The default library backup list contains all user libraries. You can select or deselect libraries using the panel shown in Figure 10. When the backup is actually initiated, the operator is prompted for tape information and whether to include all objects or only changed objects. With V2R2M0, backup support has been greatly enhanced and includes daily, weekly and monthly scheduling options.
Before You Call
OA provides a fairly complete interface to help users collect the information that IBM or applications programmers may need to resolve software problems. 11 illustrates the TECHHELP menu-most of the problem-determination help is on this menu. Problem support extends to starting and stopping copy screen (STRCPYSCN, ENDCPYSCN), working with PTFs and connecting to technical support via ECS. Authorized users can also display the system operator's message queue (QSYSOPR) using the OA version of the message displays via option 1 on TECHHELP. Option 10 on the USERHELP menu records information about a problem which automatically generates printed output, job logs, messages, active jobs and so forth.
OA provides a fairly complete interface to help users collect the information that IBM or applications programmers may need to resolve software problems. Figure 11 illustrates the TECHHELP menu-most of the problem-determination help is on this menu. Problem support extends to starting and stopping copy screen (STRCPYSCN, ENDCPYSCN), working with PTFs and connecting to technical support via ECS. Authorized users can also display the system operator's message queue (QSYSOPR) using the OA version of the message displays via option 1 on TECHHELP. Option 10 on the USERHELP menu records information about a problem which automatically generates printed output, job logs, messages, active jobs and so forth.
When, Where and How
If your shop has a full-time system operator, it makes sense to assign the main OA menu (ASSIST) as a sign-on menu. But if system operator is a part-time function for one or more people, you'll need to consider the best way to provide access to OA functions.
The easiest method is to use the Attention key as a toggle to the OA main menu. IBM provides two callable programs which can be specified as Attention key programs to display the ASSIST menu-QSYS/QEZMAIN (uses a group job) and QSYS/QEZAST. For more information about considerations for Attention key programs and the pros and cons of group jobs, see "At Ease With the Attention Key" and "Juggling Jobs" in the May 1992 issue of MC. Setting the Attention key program system value (QATNPGM) or user profile parameter (ATNPGM) to *ASSIST calls QSYS/QEZMAIN.
IBM also provides other callable programs to access specific parts of OA for operators who do not need all of its functions. You can find these programs in QSYS; all their names are prefixed with QEZ. The callable programs are listed in 12. OA offers a number of entry points for programmers who want to customize programs or incorporate their own backup or cleanup options. As we've shown in 9, you can easily modify OA, provided you ensure that the OA portions of the job complete successfully. There is nothing to prevent you from modifying OA's callable programs if the source is available.
IBM also provides other callable programs to access specific parts of OA for operators who do not need all of its functions. You can find these programs in QSYS; all their names are prefixed with QEZ. The callable programs are listed in Figure 12. OA offers a number of entry points for programmers who want to customize programs or incorporate their own backup or cleanup options. As we've shown in Figure 9, you can easily modify OA, provided you ensure that the OA portions of the job complete successfully. There is nothing to prevent you from modifying OA's callable programs if the source is available.
Finally, any command that supports *BASIC displays will select those displays based on the system value and user profile considerations discussed earlier. You can incorporate these commands into any application or provide them as options on your menus. The commands that have a *BASIC display as of V2R1M1 are: WRKSPLF, WRKWTR, WRKUSRJOB, DSPMSG, WRKMSG, WRKCFGSTS and WRKUSRPRF.
OA uses a series of commands to provide interfaces to the cleanup, backup (V2R2M0) and power off schedules. You'll find these commands on the system menus CMDCLNUP, CMDBCKUP and CMDPWR.
An OA Perspective on OS/400
Operational Assistant was originally designed to address specific problems for system operators and end users new to the AS/400, especially those who migrated from the S/36. It has since evolved to include many system administrator functions. It is the nature of powerful tools, whether for carpentry or programming, to be frightening and dangerous in the wrong hands. OA was incorporated as part of the base operating system to allow programmers to create a seamless interface to the system for all levels of user experience. If you use your tools wisely, your operators will be able to do their jobs easily and accurately, leaving you free to get your own job done.
What's New in V2R2 Operational Assistant
As one of the developers of V2R2 Operational Assistant, I'm excited to write about what we worked on. During development, the entire OA team could hardly wait to announce the enhancements because we really felt you, our customer, would find them very helpful. And, we hope you do!
Operational Assistant Menus: One of the changes you may notice right away is some of the menu options have been rearranged and new ones have been added. The rearrangement was a difficult decision because moved menu options, from a user's perspective, can be confusing. However, we decided to make the changes because the focus of each menu made more sense. The AS/400 Operational Assistant Menu (GO ASSIST) continues to focus on tasks performed by all users. The Manage Your System, Users, and Devices Menu (GO MANAGESYS) now focuses on tasks done more frequently by system operators. And, the new Customize Your System, Users, and Devices Menu (GO SETUP) focuses on tasks done periodically by administrators. A1 illustrates the OA menu structure in V2R2M0 of OS/400; the menus which have been changed or added are highlighted.
Operational Assistant Menus: One of the changes you may notice right away is some of the menu options have been rearranged and new ones have been added. The rearrangement was a difficult decision because moved menu options, from a user's perspective, can be confusing. However, we decided to make the changes because the focus of each menu made more sense. The AS/400 Operational Assistant Menu (GO ASSIST) continues to focus on tasks performed by all users. The Manage Your System, Users, and Devices Menu (GO MANAGESYS) now focuses on tasks done more frequently by system operators. And, the new Customize Your System, Users, and Devices Menu (GO SETUP) focuses on tasks done periodically by administrators. Figure A1 illustrates the OA menu structure in V2R2M0 of OS/400; the menus which have been changed or added are highlighted.
Automatic Backup: The purpose of the new backup support is to provide a basic backup strategy and an easy way to perform backup so systems, particularly small systems, will be more likely to back up information regularly. The intent was not to provide comprehensive, highly flexible backup and recovery support.
The new backup support is shipped with defaults so you can begin using it immediately. Once you dig into customizing OA backup, you will find you can change it quite a bit. A backup option for a daily, weekly and monthly backup saves the what, where, and how you want each of those backups to work. In addition to the library support in V2R1M1, OA backup now includes folders, configuration, security, mail and calendars. Rotating through sets of tapes is supported and you can schedule when you want the backups to run. The scheduling uses the new V2R2M0 job scheduler. (For more information on the job scheduler, see the AS/400 Work Management Guide, SC41-8078). Also, you can specify the name of a program to run before and after the backup. This can be used to stop activity on the system before the backup and then start it again afterwards.
To obtain access to this support, just type GO BACKUP or GOCMDBCKUP.
Communications Configuration: I don't know about you, but my communications expertise is limited to the telephone. So, I was very glad to see an
easier way to get two systems communicating or remote devices connected. Our intent was to get the systems and devices actually communicating by having you specify as few parameters as possible. To accomplish this, the support takes many defaults. This may mean you don't get an optimally performing communications configuration, but you do get a configuration that works!
The support has options to add to existing lines and controllers. While adding new communications configurations, you are taken step by step through what you need to specify. When you are finished configuring a remote AS/400 or S/36, you get printed instructions you can take to that remote system. The instructions take you through step by step and tell you what to specify to complete the configuration on the remote system.
Trying this support is as easy as typing GO CMNCFG.
Disk Space Information: I'd break into song about now-"Where has all my disk space gone..."-but I can't sing, so let's skip that. The question does remain, however, about where all your disk space has gone. This support is intended to help answer that question.
There are two key parts. The first collects the information into an externally described file. We chose an externally described file to store the information in so you can access the data any way you want. Since collecting this information can take a while and produce a large file, I'm including two sample systems to give you a feel for how long and how big. This will vary depending on your system size, model, memory, and whether or not you are running the collection on a dedicated system. Given these variances, please use the examples as rules of thumb and not as hard-and-fast commitments that you will meet these specific results.
The Model E25 with 64MB memory and 5933MB disk we ran this on took 32 minutes and produced a 4Meg file with 19,000 records. The Model D80 with 63MB memory and 8780MB disk we ran this on took two hours and 28 minutes to run and produced a 17MB file with 83,000 records. One 211-byte record is added to the file for each object on the system, plus another 40 records for the system information. The job that collects this data can be scheduled to run periodically, using the new V2R2M0 job scheduler.
The second part of the support provides reports based on the collected data. You can organize the information by library, folder, user or object. You can specify how to sort the data and what to include, such as the size of the smallest object and names.
The system summary section contains some interesting information, such as how much disk space will be affected if Reclaim Storage is run; how much disk space is used by printer output, history files, journal receivers, help, licensed internal code, and so on; and a categorization of space used by internal objects.
Go DISKTASKS or GO CMDDSK gets you to this support.
Signed-on Users: The new signed-on users support is a companion to the OA batch job support. During testing, we found that many users don't understand the difference between interactive and batch jobs. Jobs were usually thought of as batch jobs. So, OA job support only shows batch jobs.
From the new signed-on users display, you can see which users are signed on, send them messages, and sign them off (my favorite option).
Option 10 on the MANAGESYS menu is the way to access this support.
Displaying System Status: The intent of the *BASIC assistance level of the Work with System Status
(WRKSYSSTS) command was to provide an easy-to-understand status of the system. Paging rates and job transition rates can be difficult to understand and don't always answer some of the simpler questions.
This new support provides information about the percent of system storage used, how many users are currently signed on, how many batch jobs are running or waiting on messages or ended with printer output waiting to print, and so on. While we were building this support we managed to sneak in the Display System Status (DSPSYSSTS) command that some of you were looking for.
Getting to this support requires that you type GO MANAGESYS and take option 1.
Information Assistant: Even the information developers got in on the act with this release. The new Information Assistant Options Menu (GO INFO) provides options that explain the different types of information, when to use it, how it's organized, and where to look for information if you are just getting started. Other options also describe how to comment on information and what's new in the release.
The following manuals contain information about Operational Assistant:
AS/400 Basic Security Guide, SC41-0047
AS/400 New User's Guide, SC41-8211
AS/400 System Operator's Guide, SC41-8082
AS/400 System Operator's Quick Reference, SX41-9573
OS/400 Communications Configuration Reference, SC41-0001, appendix F
Speaking for the OA development team, we hope you enjoy the new support as much as we enjoyed building it for you!
Operational Assistant Lends a Hand
Figure A1 V2R2M0 OA menu structure (unable to display)
Operational Assistant Lends a Hand
Figure 1 V2R1M1 commands with OA support
Figure 1: V2R1M1 Commands With OA Support
Display Messages DSPMSG
Work with Configuration Status WRKCFGSTS
Work with Messages WRKMSG
Work with Spooled Files WRKSPLF
Work with User Jobs WRKUSRJOB
Work with User Profiles WRKUSRPRF
Work with Writers WRKWTR
Additional V2R2M0 Support
Display System Status DSPSYSSTS
Work with System Status WRKSYSSTS
Operational Assistant Lends a Hand
Figure 10 Set User Library Backup List panel
Figure 10: Set User Library Backup List
Change Library Backup List
System: MC PGMR
Type options below, then press Enter.
1=Select for backup 3=Do not back up 5=Display library contents
8=Display details
Selected
for Last
Opt Library Backup Backup Changed
_ $HOFSHA Yes 10/03/92 No
_ $JONMIK Yes 10/03/92 No
_ $MALERN Yes 10/03/92 No
_ $MELSHE Yes 10/03/92 No
_ $SHARIC Yes 10/03/92 No
_ #LIBRARY Yes 10/03/92 No
_ @PI Yes 10/03/92 No
_ ALTQSYS Yes 10/03/92 No
_ ALTQSYSSDD Yes 10/03/92 No
_ ATSACL1 Yes 10/03/92 No
_ ATSARG4 Yes 10/03/92 No
More...
F1=Help F3=Exit F5=Refresh F11=Display descriptions F12=Cancel
F17=Top F18=Bottom
Operational Assistant Lends a Hand
Figure 11 OA's TECHHELP menu
Figure 11: OA's TECHHELP Menu
TECHHELP Technical Support Tasks
System: MC PGMR
To select one of the following, type its number below and press Enter:
1. Display messages for the system operator
10. Work with problems with the system
11. Work with PTF(s)
12. Copy your screen on another display station
13. Stop copying your screen
20. Connect to technical support
21. Disconnect from technical support
80. Temporary sign-off
Type a menu option below
__
F1=Help F3=Exit F9=Command line F12=Cancel
(C) COPYRIGHT IBM CORP. 1980, 1991.
Operational Assistant Lends a Hand
Figure 12 Callable OA programs
Figure 12: Callable OA Programs
OA Attention key handling program QEZAST
(no group job)
Work with Jobs QEZBCHJB
OA Attention key handling program QEZMAIN
(uses a group job)
Work with Messages QEZMSG
Work with Printer Output QEZOUTPT
Saves information about a problem QEZSAVIN
Send Message QEZSNDMG
Operational Assistant Lends a Hand
Figure 2 Main Operational Assistant menu
Figure 2: Main Operational Assistant Menu
ASSIST AS/400 Operational Assistant
System: MC PGMR
To select one of the following, type its number below and press Enter:
1. Work with printer output
2. Work with jobs
3. Work with messages
4. Send messages
5. Change your password
10. Manage your system, users, and devices
75. Documentation and problem handling
80. Temporary sign-off
Type a menu option below
__
F1=Help F3=Exit F9=Command line F12=Cancel
Operational Assistant Lends a Hand
Figure 3 OA WRKSPLF display
Figure 3: OA WRKSPLF Display
Work with Printer Output
System: MC PGMR
User . . . . . . HOFSHA____ Name, *ALL, F4 for list
Type options below, then press Enter. To work with printers, press F22.
2=Change 3=Hold 4=Delete 5=Display 6=Release 7=Message
9=Work with printing status 10=Start printing 11=Restart printing
Printer/
Opt Output Status
EDTDSP01P1
__ 9227644500 Held (use Opt 6)
__ 9227644500 Held (use Opt 6)
__ 9227644500 Held (use Opt 6)
__ 9227644500 Held (use Opt 6)
__ 9227644500 Held (use Opt 6)
__ 9227644500 Held (use Opt 6)
SYSPRT01
__ 9227644500 Printed and kept (use Opt 6 to reprint)
Not Assigned
More...
F1=Help F3=Exit F5=Refresh F11=Dates/pages/forms F12=Cancel
F14=Select other printer output F22=Work with printers F24=More keys
Operational Assistant Lends a Hand
Figure 4 Modify spool file selection criteria
Figure 4: Modify Spool File Selection Criteria
Work with Printer Output
.......................................................................
: Select Other Printer Output :
: :
: Select the following printer output for the list. :
: :
: Type choices below, then press Enter. :
: :
: User . . . . . . . . . . HOFSHA____ Name, *ALL, F4 for list :
: :
: Printer . . . . . . . . . *ALL______ Name, *ALL, F4 for list :
: :
: Status . . . . . . . . . 1 1=All statuses :
: 2=Statuses requiring action :
: :
: Output . . . . . . . . . *ALL______ Name, *ALL :
: :
: :
: :
: :
: :
: F1=Help F5=Refresh F12=Cancel :
.......................................................................
Operational Assistant Lends a Hand
Figure 5 Change Printer Output panel
Figure 5: Change Printer Output Panel
Change Printer Output
User . . . . . . . . : HOFSHA Date . . . . . . . . : 10/02/92
Printer output . . . : 9227644500 Time . . . . . . . . : 12:58:12
Pages . . . . . . . : 1
Status . . . . . . . : Held
Type choices below, then press Enter.
Printer to use . . . . . . EDTDSP01P1 Name, F4 for list
Copies and pages:
Number of copies . . . . 1__ 1-255
First page to print . . 1____ Number
Last page to print . . . *LAST Number, *LAST
Type of forms . . . . . . *STD______ Form type, *STD
Print this output next . . N Y=Yes, N=No
Save printer output . . . Y Y=Yes, N=No
F1=Help F3=Exit F5=Refresh F12=Cancel
Operational Assistant Lends a Hand
Figure 6 Work with Printers
Figure 6: Work With Printers
Work with Printers
System: MC PGMR
User . . . . . : HOFSHA
Type options below, then press Enter.
1=Start 4=Stop 7=Message 8=Display output for printer 11=Restart
Opt Printer Form Type Status
__ EDTDSP01P1 Stopped (use Opt 1)
__ SYSPRT01 *ALL Ready for printing
Bottom
F1=Help F3=Exit F5=Refresh F6=Include all printers F9=Command line
F11=Display descriptions F12=Cancel F21=Select assistance level
Operational Assistant Lends a Hand
Figure 7 Print Local Device Addresses (unable to display)
Operational Assistant Lends a Hand
Figure 8 Change Cleanup Options panel
Figure 8: Cleanup Options Panel
Change Cleanup Options MC PGMR
10/04/92 11:13:41
Type choices below, then press Enter.
Allow automatic cleanup . . . . . . . . . . . . . Y Y=Yes, N=No
Time cleanup starts each day . . . . . . . . . . 22:00:00__00:00:00-
23:59:59,
*SCDPWROFF,
*NONE
Number of days to keep:
User messages . . . . . . . . . . . . . . . . . 7____ 1-366, *KEEP
System and workstation messages . . . . . . . . 4____ 1-366, *KEEP
Job logs and other system output . . . . . . . 7____ 1-366, *KEEP
System journals and system logs . . . . . . . . 30___ 1-366, *KEEP
OfficeVision/400 calendar items . . . . . . . . 30___ 1-366, *KEEP
F1=Help F3=Exit F5=Refresh F12=Cancel
Operational Assistant Lends a Hand
Figure 9 Adding user cleanup options
Figure 9: Adding User Cleanup Options
1. Retrieve the source for QSYS/QEZUSRCLNP, using
RTVCLSRC. (Be sure to save a copy of the unchanged
program.)
2. Add calls to your own cleanup options and recompile the program.
3. Replace your revised QEZUSRCLNP in a library above QSYS in the library
list. If you use QSYS, your changes may be overlaid when you install PTFs or a
new release.
Caution: If your cleanup requires user input, you should not use the
*SCDPWROFF value for the cleanup start time. If an operator is not present to
answer the message, power down will occur. The next morning, when the message
is answered, your system will power down (extremely inconvenient).
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
TRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online