× 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.



Non SQL, we currently have an AJS job that runs daily, to purge spoolfiles based on the number of days for that outq.

This is from old school.

Different outs had different purge number of days. (10, 45, 90, 999-not to be purged)
The issue we had was where to store the purge number of days so we could easily retrieve it.
We decided to store this in the outq User defined option USRDFNOPT . . . . . . 10
What would be a better choice to store the purge number of days?


Cause . . . . . : Command to execute was: DSPOBJD OBJ(*ALL/*ALL)
OBJTYPE(*OUTQ) DETAIL(*FULL) OUTPUT(*OUTFILE) OUTFILE(QGPL/OUTQPURGE) /*
Displays all Outqs on the system to an outfile (qgpl/outqpurge) */.

CALL PGM(QGPL/OUTQPURGE) PARM('*DELETE') /* *CHECK or *DELETE */

OUTQPURGE reads the file of outqs.

The problem was then how to retrieve U
We had to use a IBM API -

CALL PGM(QSPROUTQ) PARM(&RCVINF &RCVLEN &FORMAT +
&OBJLIB &APIERR) /* Retrieve Output Queue +
Information (QSPROUTQ) API */

Once we had the proper purge number of days for that outq

We then called TAATOOLs command - DLTOLDSPLF

DLTOLDSPLF OUTQ(&ODLBNM/&ODOBNM) FILE(*ALL) USER(*ALL) +
EXCLUDEUSR(*NONE) JOB(*ALL) +
EXCLUDEJOB(*NONE) FORMTYPE(*ALL) +
USRDTA(*ALL) STS(*ALL) ASPDEV(*) +
RETAINDAYS(&RETENTION) QPJOBLOG(999) +
QPSRVDMP(999) MOVTOOUTQ(*LIBL/*NONE) +
ACTION(&ACTION) COMPDATE(*CRTDAT) +
SUMMARY(*YES)

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Wednesday, March 29, 2017 10:47 AM
To: Midrange Systems Technical Discussion
Subject: Using a QCMDEXE function to purge spool files Was: SQL listing with final totals

We have a no holds barred policy when it comes to spool files. We delete everything over 90 days old. No exceptions.

Want to get really funky? Create your own QCMDEXC function. Sure, IBM already supplies a QCMDEXC stored procedure but here's why you may want a function.

Keeping this in mind
DLTSPLF FILE(FILE) JOB(JOBNBR/JOBUSER/JOBNAME) SPLNBR(SPLNBR) And keeping this in mind SELECT CREATE_TIMESTAMP, SPOOLED_FILE_NAME, JOB_NAME, FILE_NUMBER, SIZE, TOTAL_PAGES FROM QSYS2.OUTPUT_QUEUE_ENTRIES
WHERE DAYS(CURRENT_TIMESTAMP) - DAYS(CREATE_TIMESTAMP)>90
ORDER BY CREATE_TIMESTAMP;

Now you can combine the two. First, in test mode:
This only shows you the command you would run.

SELECT CREATE_TIMESTAMP, SPOOLED_FILE_NAME, JOB_NAME, FILE_NUMBER, SIZE, TOTAL_PAGES, 'DLTSPLF FILE(' concat SPOOLED_FILE_NAME concat ') JOB(' concat JOB_NAME concat
') SPLNBR(' concat FILE_NUMBER concat ')'
FROM QSYS2.OUTPUT_QUEUE_ENTRIES
WHERE DAYS(CURRENT_TIMESTAMP) - DAYS(CREATE_TIMESTAMP)>90
ORDER BY CREATE_TIMESTAMP;

Then in live mode. This still shows the command but since we've added the qcmdexc around it the command will actually execute.

SELECT CREATE_TIMESTAMP, SPOOLED_FILE_NAME, JOB_NAME, FILE_NUMBER, SIZE, TOTAL_PAGES, routines.qcmdexc('DLTSPLF FILE(' concat SPOOLED_FILE_NAME concat ') JOB('
concat
JOB_NAME concat ') SPLNBR(' concat FILE_NUMBER concat ')') FROM QSYS2.OUTPUT_QUEUE_ENTRIES
WHERE DAYS(CURRENT_TIMESTAMP) - DAYS(CREATE_TIMESTAMP)>90
ORDER BY CREATE_TIMESTAMP;

Anomaly: Always include an ORDER BY to ensure that the command executes throughout the data selection. Otherwise you'll get someone who doesn't roll down through the screen.

And now you will no longer get results in:
SELECT CREATE_TIMESTAMP, SPOOLED_FILE_NAME, JOB_NAME, FILE_NUMBER, SIZE, TOTAL_PAGES FROM QSYS2.OUTPUT_QUEUE_ENTRIES
WHERE DAYS(CURRENT_TIMESTAMP) - DAYS(CREATE_TIMESTAMP)>90
ORDER BY CREATE_TIMESTAMP;
as they have all been deleted.



How to create one:
Paste this into Run SQL Scripts.
We have a library called ROUTINES.

SET PATH *LIBL ;

CREATE FUNCTION ROUTINES.QCMDEXC (
CMD VARCHAR(32702) )
RETURNS CHAR(256)
LANGUAGE SQL
SPECIFIC ROUTINES.QCMDEXC
NOT DETERMINISTIC
MODIFIES SQL DATA
CALLED ON NULL INPUT
NOT FENCED
SET OPTION ALWBLK = *ALLREAD ,
ALWCPYDTA = *YES ,
COMMIT = *NONE ,
DECRESULT = (31, 31, 00) ,
DFTRDBCOL = *NONE ,
DLYPRP = *NO ,
DYNDFTCOL = *NO ,
DYNUSRPRF = *USER ,
RDBCNNMTH = *RUW ,
SRTSEQ = *HEX
BEGIN DECLARE RETCMD CHAR ( 256 ) ; DECLARE SQLCODE INTEGER ;
DECLARE CONTINUE HANDLER FOR SQLEXCEPTION BEGIN SET RETCMD = 'ERROR
SQLCODE=' || TRIM ( CAST ( SQLCODE AS CHAR ( 10 ) ) ) || ' ' || CMD ; END
; BEGIN DECLARE CMDLEN DEC ( 15 , 5 ) ; SET RETCMD = CMD ; SET CMDLEN =
LENGTH ( TRIM ( CMD ) ) ; CALL QCMDEXC ( CMD , CMDLEN ) ; END ; RETURN (
RETCMD ) ; END ;

GRANT ALTER , EXECUTE
ON SPECIFIC FUNCTION ROUTINES.QCMDEXC
TO ROB ;





Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.