Re: Finding large objects that are blowing up the system ASP

... written in '97 - when you had to wear a suit & tie to work in IT ...
(IBM blue of course)
PGM PARM(&LIB &DAYS &PREFIX) /* Delete journal +
030409
receivers in lib older than selected +
030409
#days. Prefix is file name or 1st +
030409
characters of name with an asterick. */
030409
DCL VAR(&LIB) TYPE(*CHAR) LEN(10)
970613
DCL VAR(&DAYS) TYPE(*DEC) LEN(5 0)
970613
DCL VAR(&PREFIX) TYPE(*CHAR) LEN(10)
970613
DCL VAR(&JOBDATE) TYPE(*CHAR) LEN(6)
970613
DCL VAR(&JDATE) TYPE(*CHAR) LEN(8)
970613
DCL VAR(&JDATE1) TYPE(*DEC) LEN(8 0)
970613
DCL VAR(&JDATE2) TYPE(*DEC) LEN(8 0)
970613
DCLF FILE(ZPRGJRND)
030409
RTVJOBA DATE(&JOBDATE) /* job date */
970613
CVTDAT DATE(&JOBDATE) TOVAR(&JDATE) TOFMT(*YYMD) +
970613
TOSEP(*NONE)
970613
CHGVAR VAR(&JDATE1) VALUE(&JDATE)
970613
CHGVAR VAR(&DAYS) VALUE(0 - &DAYS)
970613
CALL PGM(DATE02) PARM(&JDATE1 &DAYS &JDATE2) /* +
970613
Calc date #days prior to job date */
970613
CLRPFM FILE(ZPRGJRND)
030409
DSPOBJD OBJ(&LIB/&PREFIX) OBJTYPE(*JRNRCV) +
030409
OUTPUT(*OUTFILE) OUTFILE(ZPRGJRND)
030409
MONMSG MSGID(CPF0000) EXEC(GOTO CMDLBL($END))
970613
$READ: RCVF /* read file */
MONMSG MSGID(CPF0000) EXEC(GOTO CMDLBL($END))
CVTDAT DATE(&ODLDAT) TOVAR(&JDATE) FROMFMT(*MDY) +
TOFMT(*YYMD) TOSEP(*NONE)
CHGVAR VAR(&JDATE1) VALUE(&JDATE)
IF COND(&JDATE1 *LE &JDATE2) THEN(DO)
DLTJRNRCV JRNRCV(&ODLBNM/&ODOBNM)
MONMSG MSGID(CPF0000)
ENDDO

GOTO CMDLBL($READ)
$END: ENDPGM
sample call
CALL PGM(xxxPGM/ZPRGJRNC) PARM( 'XXXFIL' X'00090F' '*ALL')
CALL PGM(xxxPGM/ZPRGJRNC) PARM('QUSRSYS' X'000365F' 'QAUD*')

Jim Franz


On Wed, Apr 23, 2025 at 3:15 PM Vern Hamberg via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

James

That tooling gives a snapshot of disk space - it's a necessary tool.

But you describe a different problem - the on-the-fly problem of
reduction in disk space. I once worked for Centerfield Technology and
wrote a utility that monitored disk space using an MI function - very
fast to determine if space was going down fast, even at a 5 second
interval.

It was sold eventually to S4i, and I think they still have it - yeah,
https://solutionsfori.com/dasd-plus/ - spike detection is mentioned on
that page.

I believe Fortra has Robot/Space - same kind of thing.

And I think Alan Campin wrote something once - not sure if it's
available. There's a fine venerable site, https://www.think400.dk/ - and
the download link there has lots of stuff by Alan Campin - I didn't see
the disk space one, though.

The one I wrote would detect growth, then when your setting was passed,
it'd go looking for where, with fairly aggressive techniques as I knew
them at the time. S4i might have made it better, Fortra in their tool,
probably does well.

*Regards*

*Vern Hamberg*

IBM Champion 2025 <cid:part1.kiyCFph0.X5odzBjh@centurylink.net> CAAC
(COMMON Americas Advisory Council) IBM Influencer 2023

On 4/23/2025 1:16 PM, James H. H. Lampert via MIDRANGE-L wrote:

On 4/23/25 11:02 AM, Jack Woehr wrote:

https://www.ibm.com/support/pages/printing-disk-space-reports

Thanks. I've now put it on my bookmarks toolbar under the name
"Finding large objects on an AS/400.

I'll run the report once I've finished getting rid of a long-obsolete
Tomcat IFS directory. It's amazing just how much <expletive deleted> a
Tomcat server can accumulate.

--
JHHL

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.