Re: IBM i 7.1 SYSTOOLS.PTF_GROUP_CURRENCY question

And this was part of my pmr also:

<snip>
Make sure the appropriate PTF is applied.
HIPER PTF SI64490 for IBM i 7.1
HIPER PTF SI64491 for IBM i 7.2
HIPER PTF SI64492 for IBM i 7.3
</snip>

So this is probably Larry's concern about the communication changed.


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 Berendt <rob@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 01/23/2018 10:02 AM
Subject: Re: IBM i 7.1 SYSTOOLS.PTF_GROUP_CURRENCY question
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Had this same issue on 7.3. Had to rebuild a view. Known issue.

First, start out by reading the steps at the end, but before the comments,

at
https://www.ibm.com/developerworks/community/
wikis/home?lang=en#!/wiki/IBM%20i%20Technology%20Updates/
page/SYSTOOLS.GROUP_PTF_CURRENCY%20view


<snip>
Development asked that you tell us the results of the following SQL
statement:
select cast(long_comment as varchar(100)) from qsys2.systables
where table_name = 'GROUP_PTF_CURRENCY' and table_schema =
'SYSTOOLS'

Then to reset the view, run in SQL: comment on table
systools.group_ptf_currency is ''
and later from the command line at a time of low Database use: CALL
QSYS/QSQSYSIBM
</snip>
Basically the comment tells them version info.
Then you reset the comment to null.
Then you call that program to rebuild it.
In my case the comment at the beginning was the proper version, it just
needed to be rebuilt.

Here's my results (I used Run SQL Scripts):
<snip>
select cast(long_comment as varchar(100)) from qsys2.systables
where table_name = 'GROUP_PTF_CURRENCY' and table_schema =
'SYSTOOLS' ;

DB2 FOR IBM i SUPPLIED OBJECT VERSION 07300010003

comment on table systools.group_ptf_currency is '';

cl: CALL QSYS/QSQSYSIBM;
CPC2206: Ownership of object SYSLIMTBL in QSYS2 type *FILE changed.
PROCESSING QSYS2/QSQPDTBL CPC2206: Ownership of object QSQPDTBL in
QSYS2 type *FILE changed. CPCA087: Object copied.VIEW SYSTOOLS.
GROUP_PTF_CURRENCY (*UNKNOWN) WILL BE REPLACED WITH VERSION 07300010003
CPC2206: Ownership of object GRPPTFCUR in SYSTOOLS type *FILE changed.
CPC2206: Ownership of object SERV_INFO in QSYS2 type *FILE changed.
PROCESSING QSYS/QSQSYSIBM(QSQDBNAV)QSQSYSIBM PROCESSING SUCCESSFUL FOR
523 COMPONENTS.

select cast(long_comment as varchar(100)) from qsys2.systables
where table_name = 'GROUP_PTF_CURRENCY' and table_schema =
'SYSTOOLS' ;

DB2 FOR IBM i SUPPLIED OBJECT VERSION 07300010003

SELECT P.*
FROM systools.group_ptf_currency P
ORDER BY ptf_group_level_available - ptf_group_level_installed desc;

PTF_GROUP_CURRENCY
no longer says PSP INFORMATION NOT AVAILABLE
but instead shows the correct information.
</snip>



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: Mark S Waterbury <mark.s.waterbury@xxxxxxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Date: 01/23/2018 09:16 AM
Subject: IBM i 7.1 SYSTOOLS.PTF_GROUP_CURRENCY question
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Where does the IBM SYSTOOLS.PTF_GROUP_CURRENCY get its information from?

When I run this SQL query on IBM i 7.1:

select * from SYSTOOLS.PTF_GROUP.CURRENCY

I see:
PSP INFORMATION NOT AVAILABLE

for every row for the first column ("PTF_GROUP_CURRENCY".

Where does it get that information from, and what does "PSP information
not available" really mean?

Thanks in advance,

Mark S. Waterbury
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD