× 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 support@midrange.com.



On 7/25/24 2:00 PM, James H. H. Lampert wrote:

===> select spooled_file_name, job_name, file_number,
     'DLTSPLF FILE(' CONCAT SPOOLED_FILE_NAME CONCAT ') JOB('
     CONCAT JOB_NAME CONCAT ') SPLNBR(' CONCAT FILE_NUMBER
     CONCAT ')' as cmd, qcmdexc('DLTSPLF FILE(' CONCAT
     SPOOLED_FILE_NAME CONCAT ') JOB(' CONCAT JOB_NAME
     CONCAT ') SPLNBR(' CONCAT FILE_NUMBER CONCAT ')') as
     cmd_result from qsys2.OUTPUT_QUEUE_ENTRIES
     where job_name like '%/WTCPVERIFY' and
     spooled_file_name = 'QPRINT'


And finally, you do have to go through the result-set. You don't need to page down; you can do a "+1000" a few times. But in STRSQL, if it doesn't display, it doesn't happen (which supplies a set of training wheels in and of itself).

Back in July, we were discussing a way to mass-delete a bunch of spool files. The above was what Rob and I finally came up with.

Now, I find myself needing to do the same thing with another customer box, but when I paste the above into a STRSQL session on another customer box with a similar problem (*something* is pounding on a proprietary port with a steady stream of HTTP requests), STRSQL gives me an error message:

QCMDEXC in *LIBL type *N not found.

The box in question is on V7R4M0.

Any idea why this worked back in July, on a different box, but not today on this one?

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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 [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.