First problem:
SF99710 13037 Installed
This should be 13298. But don't feel too bad. This has been out less
than two weeks and I'm running the same level as you.
Your database and hiper group are one behind but they've only been
updated
within the last two weeks also.
SF99710/13298 is pending installation, but we only IPL once a week and
SF99707/7 is keeping this from being installed until MF99007 is installed.
Same thing applies for SF99709 and SF99701. I left the pending stuff off
what I showed for PTFs.
But, getting to the meat of the situation...
I could not find "select/omit not compatible with query". I did find a
close message, with a close RC11 in
CPI432D
11 - The access path contains static select/omit selection criteria
which
is not compatible with the selection in the query.
It referenced CPI432A and/or CPI432C. If you read CPI432A you will see
that a time out situation appears as it goes through access path
selection. This may help explain why some interfaces work and others do
not. "IF" CPI432D is preceeded by CPI432A and not CPI432C.
We're getting CPI432C. It shows:
CPI432C Information 00 11/12/13 14:27:00.864920
QQQOOODBOP QSYS *STMT QQQOOODBOP QSYS *STMT
From module . . . . . . . . :
QQQOOODBMS
From procedure . . . . . . :
QDBOPDUMPDEBUGMSGS
Statement . . . . . . . . . :
2157
To module . . . . . . . . . :
QQQOOOINV
To procedure . . . . . . . :
CALLDBMAINTFOROPENOROPTIMIZE
Statement . . . . . . . . . :
4715
Message . . . . : All access
paths were considered for file F0005L1.
Cause . . . . . : The query
optimizer considered all access paths built over
member F0005L1 of file F0005L1 in
library PRODCTL. The list below shows the
access paths considered. If file
F0005L1 in library PRODCTL is a logical
file then the access paths
specified are actually built over member F0005 of
physical file F0005 in library
PRODCTL. Following each access path name in
the list is a reason code which
explains how the optimizer considered the
access path. PRODCTL/F0005_2 4,
PRODCTL/F0005L52 4, PRODCTL/F0005L998 4,
PRODCTL/F0005L999 4,
PRODCTL/F0005L92 4, PRODCTL/F0005L93 4,
PRODCTL/F0005L95 4,
PRODCTL/F0005L97 4, PRODCTL/F0005_3 4,
PRODCTL/F0005L51 11,
PRODCTL/F0005L11 11, PRODCTL/F0005L25 11,
PRODCTL/F0005L24 11,
PRODCTL/F0005L23 11, PRODCTL/F0005L22 11,
PRODCTL/F0005L1 11,
PRODCTL/F0005_PK 0. The reason codes and their meanings
follow: 0 - The access path was
used to implement the query. 1 - Access path
was not in a valid state. The
system invalidated the access path. 2 - Access
path was not in a valid state.
The user requested that the access path be
rebuilt. 3 - Access path is a
temporary access path (resides in library
QTEMP) and was not specified as
the file to be queried. 4 - The cost to use
this access path, as determined
by the optimizer, was higher than the cost
associated with the chosen access
method. 5 - The keys of the access path
did not match the fields
specified for the ordering/grouping criteria. For
distributed file queries, the
access path keys must exactly match the
ordering fields if the access
path is to be used when ALWCPYDTA(*YES or *NO)
is specified. 6 - The keys of the
access path did not match the fields
specified for the join criteria.
7 - Use of this access path would not
minimize delays when reading
records from the file. The user requested to
minimize delays when reading
records from the file. 8 - The access path
cannot be used for a secondary
file of the join query because it contains
static select/omit selection
criteria. The join-type of the query does not
allow the use of select/omit
access paths for secondary files. 9 - File
F0005L1 contains record ID
selection. The join-type of the query forces a
temporary access path to be built
to process the record ID selection. 10 and
greater - View the second level
message text of the next message issued
(CPI432D) for an explanation of
these reason codes. Recovery . . . : The
user may want to delete any
access paths no longer needed.4 - The cost to use this access path, as
determined by the optimizer, was higher than the cost associated with
the chosen access method.
11 - The access path contains static select/omit selection criteria
which is not compatible with the selection in the query.
We have IGNORE_DERIVED_INDEXES set to *YES, but at V7R1 this doesn't
automatically send the query to the CQE, because the SQE can handle
select/omit indexes (that last part is from the help ticket with IBM). If
that's the case, I don't understand why we get an indication that the
select/omit is incompatible with the selection.
I searched the 7.1 PTF cover letters.
PTF Cover Letters
Search results
Search for: msgcpi432c AND logical
48 documents found
I guess I'll need to dig through these. I had used other parameters in my
own search, but by the time I eliminated errors caused by Join logicals,
errors in creating files, etc., I wasn't left with much. Certainly
nothing that would explain SQE being unable to read/use a LF because of
select/omit criteria. Maybe I'll have more luck with your search....
Andrew Lopez
Systems Analyst
Phone: 803-714-2037
Email: ALopez@xxxxxxxxxx
Please consider the environment before printing this e-mail.
This message and any attachments should be treated as proprietary to the sender
and confidential to the identified recipients and should not be disclosed to or
used by anyone other than the intended recipient unless pre arranged with the
sender. If you are not an addressee of this communication, have received this
e-mail by transmission error of the sender, recipient or due to another
originator by an error in transmission, you are hereby notified that any
disclosure, copying, use, distribution, or taking of any action in reliance on
the contents of this information is prohibited. In any such event, please
notify the sender immediately by contacting Spirax Sarco Inc., 803 714 2000 or
reply to this e-mail and then delete it from your system. Spirax Sarco Inc.
accepts no responsibility for software viruses and all recipients should check
for viruses before opening any attachments.
midrange.com
