×
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.
As much as I value running things "with the training wheels attached"
until I have confidence that they won't blow up, I don't think
commenting out part of the command is necessary in this case.
But there were a few things that *did* have to change.
STRSQL didn't like "*CONCAT*"; it worked fine with "CONCAT" instead.
And of course, you need to reformat to fit the 68-character line. This
gives:
===> 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).
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: Quick question: mass-delete of spool files?, (continued)
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.