RE: File size warning

We have discussed other options with the customer. One of the options is a program to run to identify possible problems, increment the file 3 times and then monitor for a message about the file filling up, reuse deleted records and unlimited file size.

I suggested running RTVDSKINFO and PRTDSKINFO and look at large files as an option also.

Now it is up to the customer what should be done next.

Thanks for all the suggestion

Dave Willenborg
FNTS

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Martin Rowe
Sent: Wednesday, September 18, 2013 10:01 AM
To: Midrange Systems Technical Discussion
Subject: Re: File size warning

Dave

I run a periodic sweep for files in this state, doing just as you suggest.
It's just a simple CL that runs over the output of a DSPFD TYPE(*MBR) and doubles the size of files that are close to being full. The DSPFD file (called FILESIZES) is refreshed every day for all physicals & logicals, so we can see if any files get too big.

(MOVDIAGMSG & RSNESCMSG came from Tom Liotta's site which doesn't appear to be up - code at http://www.dbg400.net/foswiki/bin/view/DBG400/CmdSource )

Regards, Martin

PGM PARM(&TARGETLIB)
DCL VAR(&TARGETLIB) TYPE(*CHAR) LEN(10)
DCL VAR(&MORETOREAD) TYPE(*LGL) VALUE('1')
DCL VAR(&THRESHOLD) TYPE(*DEC) LEN(10 0)
DCL VAR(&NEWSIZE) TYPE(*DEC) LEN(10 0)
DCLF FILE(FILESIZES) RCDFMT(QWHFDMBR)
/*š**************************************************************************€*/
/*š GLOBAL MESSAGE MONITOR
€*/
/*š**************************************************************************€*/
MONMSG MSGID(CPF0000 RPG0000 QRG0000 RSF0000 +
MCH0000) EXEC(GOTO CMDLBL(##ERROR))
GOTO CMDLBL(##NOERROR)
##ERROR:
MOVDIAGMSG
MONMSG MSGID(CPF0000)
RSNESCMSG
MONMSG MSGID(CPF0000)
RETURN
##NOERROR:
/*š**************************************************************************€*/
/*š START OF MAINLINE CODE
€*/
/*š**************************************************************************€*/

RCVF RCDFMT(QWHFDMBR)
MONMSG MSGID(CPF0000) EXEC(CHGVAR VAR(&MORETOREAD) VALUE('0'))
DOWHILE COND(&MORETOREAD)
/*Once all the records for the requested library are read quit program*/
IF COND(&MBLIB *GT &TARGETLIB) THEN(LEAVE)
/*šOnly interested in physical files for the requested library€*/
IF COND((&MBLIB *EQ &TARGETLIB) *AND (&MBFTYP *EQ 'P')) THEN(DO)
/*Only interested in files with the default (or more) record capacity€*/
IF COND(&MBRCDC *GE 10000) THEN(DO)
/*šAssume file is near capacity if a 10% increase would push it over capacity€*/
CHGVAR VAR(&THRESHOLD) VALUE((&MBNRCD + &MBNDTR) * 1.1)
IF COND(&THRESHOLD *GT &MBRCDC) THEN(DO)
/*Double the capacity of the file, if it's available*/
CHGVAR VAR(&NEWSIZE) VALUE(&MBRCDC * 2)
ALCOBJ OBJ((&MBLIB/&MBFILE *FILE *EXCL)) WAIT(1)
MONMSG MSGID(CPF1002) EXEC(GOTO CMDLBL(READNEXT))
CHGPF FILE(&MBLIB/&MBFILE) SIZE(&NEWSIZE)
MONMSG MSGID(CPF0000)
DLCOBJ OBJ((&MBLIB/&MBFILE *FILE *EXCL))
ENDDO
ENDDO
ENDDO
READNEXT:
RCVF RCDFMT(QWHFDMBR)
MONMSG MSGID(CPF0000) EXEC(CHGVAR VAR(&MORETOREAD) VALUE('0'))
ENDDO
ENDPGM:
RETURN
ENDPGM


On 18 September 2013 15:45, <rob@xxxxxxxxx> wrote:

Gary,

However, he has a customer who asked for this feature. It's up to him
to determine if he can, and is willing to, and how to pass on the cost
of, this feature. Telling his customer he's micromanaging probably
won't go well.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: rob@xxxxxxxxx
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 09/18/2013 10:41 AM
Subject: RE: File size warning
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Gary has a point here. I guess I would only put a maximum extents on
files that have been known to be affected by runaway jobs.

There are several ways to query the system catalog for files(tables)
whose

members(partitions) whose size is huge, have a lot of deleted rows and
so on.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Gary Thompson <gthompson@xxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 09/18/2013 10:17 AM
Subject: RE: File size warning
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Maybe you or the customer are micro-managing file size ?

For example, we run our i Series so that file size is:

Member size SIZE
Initial number of records . . . . . . . . : 1147483646
Increment number of records . . . . . . . : 10000
Maximum number of increments . . . . . . : 3
Record capacity . . . . . . . . . . . . . . : 1147513646

Probably you will get strong opinions for/against, but not monitoring
the size of a bunch of files is >easier<.




-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of optional
info0rmation
Sent: Wednesday, September 18, 2013 7:54 AM
To: 'Midrange Systems Technical Discussion'
Subject: File size warning

I had a customer make a request of our monitoring software.



Please notify technical support when a physical file reaches 90 % of
capacity.



I checked with the monitoring tech support and currently that is not
an option.



I can write a program to display file information to a database file
and then run query over it looking for specific files over 90%.



Any ideas on how to do it easier?



Thanks in advance



Dave Willenborg

FNTS

Omaha NE

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



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


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


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

--
martin@xxxxxxxxxx http://www.dbg400.net
AS/400 | iSeries | System i Open Source/Free Software Debian GNU/Linux - http://www.debian.org Foswiki - The Free Open Source Wiki, http://foswiki.org/
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.