The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact email@example.com.
Basically the result of the following is probably PRT01:
where SYSTEM_VALUE_NAME = 'QPRTDEV';
And it probably doesn't exist in here:
from table(OBJECT_STATISTICS('QSYS', '*DEVD')) x
WHERE OBJATTRIBUTE LIKE 'PRT%'
Your admins might want to change that system value to a printer which actually exists. Probably a dummy one so that you only get printouts you actually want. Or they could create a dummy named PRT01 if they want. The dummy printer is "best practices". They probably don't run into this issue often because the general population there signs on to a 5250 screen and the individual has an initial program which sets the printer for their job. Since you're not using a 5250 screen it doesn't change your job, even if you have an initial program showing in:
select INITIAL_PROGRAM_NAME, INITIAL_PROGRAM_LIBRARY_NAME, PRINT_DEVICE, OUTPUT_QUEUE_NAME
where authorization_name = 'ROB';
Because that initial program is only fired off when you sign on to a green screen (aka 5250, telnet).
Minor issue though and may only be a distraction.
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: ACS System Debugger doesn't want to work, (continued)
This mailing list archive is Copyright 1997-2023 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.