How many times a week do users complain because they've run a program that produces a report, but they can't find the listing? Maybe they think that somebody has deleted the spooled file or that the program doesn't work. Anyway, after investigating a bit and using a lot of your time (which is already in short supply), you find out that the program ran just fine and someone else took the report off the printer by accident.
I have something that can help. You can use the AS/400's job accounting capabilities to track completed printing. You first need to turn on the storing of completed printout information, which you can get to using the command GO SETUP.
Once in the menu that lets you customize the system, users, and devices, take option 1, which brings up the Change System Options screen. Roll down until you see Save job accounting information about completed printer output (see 7). Change the option to a Y and exit the screen. This will change the system value QACGLVL to *PRINT and create the necessary system accounting journals (QSYS/QACGJRN).
Once in the menu that lets you customize the system, users, and devices, take option 1, which brings up the Change System Options screen. Roll down until you see Save job accounting information about completed printer output (see Figure 7). Change the option to a Y and exit the screen. This will change the system value QACGLVL to *PRINT and create the necessary system accounting journals (QSYS/QACGJRN).
Once you make this change, the system will start tracking completed printouts for new jobs. You can see completed printouts by using the WRKSPLF command at the *BASIC assistance level. When you do, you'll see a new command key (F6) that will display completed printing. This saves a lot of time tracking down whether a report really printed or not.
- Jean-Jacques Risch
TechTalk: Use job accounting to help you keep track of spooled files that have printed.
Figure 7: The Change System Options Screen
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