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



Thanks for your reply Rob
Your answer is somewhat ironic as we are now planning to do just that - upgrade to 7.3 - starting with this particular machine - which is why we need to remove what we can BEFORE we attempt that
That is why I tried to run this query - to see what large objects are out there that shouldn't be - and possibly remove them

Things that make you go ----- hmmmmmmmmmmmmmmmmmmmm

Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
'If you're going through hell, keep going.'
Winston Churchill


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Thursday, August 03, 2017 7:34 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Extracting data from the QSYS2.OBJECT_STATISTICS

The usual rule of thumb is to make sure you are at the same or higher PTF level.
WRKPTFGRP and check your database group levels.

A search for OBJECT_STATISTICS in the APAR database shows 11 hits for 7.1 http://www-01.ibm.com/support/search.wss?q=OBJECT_STATISTICS&tc=SG16C&sortby=desc
The highest APAR there shows that the problem mentioned in that APAR was fixed by one ptf. The ptf cover letter for that PTF says it's out on cume
C7192710 but it also says it was superseded by
http://www-01.ibm.com/support/docview.wss?uid=nas3SI65121
which is not out on a cume yet. But it was just added to the group released last month
http://www-01.ibm.com/support/docview.wss?uid=nas4SF99701

Then again, you could always upgrade to 7.3


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: Alan Shore <ashore@xxxxxxxx>
To: "midrange-l@xxxxxxxxxxxx" <midrange-l@xxxxxxxxxxxx>
Date: 08/03/2017 07:18 AM
Subject: Extracting data from the QSYS2.OBJECT_STATISTICS
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Hi everyone
Before I forget - we are on V7r1

I ran the following SQL command
SELECT *
FROM TABLE (QSYS2.OBJECT_STATISTICS('*ALLUSR','FILE'))
as X

on all of our systems with no problem - EXCEPT ONE (isn't that always the
case)
This one particular system needs to purge/delete/remove some files as the
amount of available disk space is becoming smaller

When I run the above query, I receive
Query cannot be run. See lower level messages.

So taking F1 on that message, and then the job log, I see
Attributes of field OBJSIZE format FILEATTRIB not valid.

Then taking F1 on that message, I see
Message ID . . . . . . : CPD4308
Cause . . . . . : The type, length, decimal digits, decimal precision,
CCSID
(Coded Character Set Identifier), date or time format, or date or time
separator of field OBJSIZE query format FILEATTRIB is not valid. See the
DDS
topic collection in the Programming category in the IBM i Information
Center
book, http://www.ibm.com/systems/i/infocenter/, for valid field
attributes.


I have googled CPD4308 - but theres nothing much out there - well - unless
you are looking for some safety courses

Does anyone have any idea the underlying cause is and how to rectify this?

As always - any and all responses gratefully accepted

Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
'If you're going through hell, keep going.'
Winston Churchill


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.