Re: Bob Hallucinations or a real thing?

Greetings,   Looks like you are using the Base version of Bob.  When dealing with IBM i related questions and activities, you need to use the Premium Package for i.  Within that support we have built in the ability for Bob to easily leverage IBM. Documentation for these sort of queries. When I asked this same question I get the correct answer, based on the info that is  outline in the documentation.

Thanks  Tim


[logo_128.png]   Tim Rowe  timmr-r/[email protected]
STSM - Application Development & System Management
IBM i ISV Council
IBM i Development Lab, Rochester MN
507-250-1293

Navigator - http://ibm.biz/IBMi_Nav4i

message: 3
date: Wed, 29 Jul 2026 16:20:36 +0000 (UTC)
from: cesco via MIDRANGE-L <[email protected]>
subject: Re: Bob Hallucinations or a real thing?

Have you tried to direct the LLM to "check for relevant documentation to support the answer and give me supporting evidence" or direct it to the link...
just to see if retracts ...
LLM have a lot of "steerability" and also incorporated memory...
I don't have bob... try to ask also " give me your model cut-off date " if it answers ...








On Wednesday, July 29, 2026 at 01:54:11 PM GMT+2, Gad Miron <[email protected]> wrote:





Hello sages

I need some advice here.

Reaching a system limit for maximum MBR size
(SQL7062 warning ? partition data space exceeds 90% of the 1.7 TB limit
(Limit ID 15003)
got me looking into Partitioned tables of DB2 Multisystym - Option 27 of
5770SS1.

IIRC this is a kind of a multi MBR file with some automatic "jumping"
between MBRs

Asking Bob
"After converting a PF to a partitioned table,
Can an RPGLE program read all records in this partitioned table without
issuing an OVRDBF command?"
got me a surprising answer:

The answer is yes ? unconditionally. Here is the precise technical
explanation:

Why No OVRDBF Is Needed
1. The Partitioned Table Looks Identical to a Regular PF
>From the RPG runtime's point of view, nothing changed. The program opens
the same library/file name it always did.
2. Db2 Multisystem Handles Partition Routing Transparently
The partition layer lives entirely inside the Db2 engine, below the
record-format / file-open level. When RPG issues an OPEN, Db2 opens a
logical handle that spans all partitions. Every subsequent native I/O
operation (READ, READP, READE, CHAIN, SETLL, WRITE, UPDATE, DELETE) is
routed to the correct partition automatically.
3. Full Sequential Read Behaviour
RPG Op-code Behaviour on partitioned table
READ Reads records sequentially across all partitions in partition order
READP Reads backwards across partitions
READE Reads equal-key records; Db2 locates the correct partition via the key
SETLL / SETGT Positions the file pointer; Db2 resolves to the correct
partition
%EOF Returns *ON only after the last record of the last partition is
exhausted
CHAIN Random access by key ? Db2 uses partition pruning to go directly to
the right partition
%EOF correctly fires once, after all partitions are exhausted ? not once
per partition.

This contradicts the info here
https://www.ibm.com/docs/en/i/7.4.0?topic=tables-traditional-system-interface-considerations

Now, this looks too good to be true
is Bob pulling my leg?

TIA
Gad
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: [email protected]
To subscribe, unsubscribe, or change list options,
visit: https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.midrange.com_mailman_listinfo_midrange-2Dl&d=DwICAg&c=BSDicqBQBDjDI9RkVyTcHQ&r=ZU3ZIY43VrBBIpLSMzvXRgDD5OJLykt0EaCJu4c8ib4&m=8rkjgZFT7WaNWAjsHqtQ4qcSJruJYNN1Gg0PRc3coZXDqTisPW7oRTml1czgAamm&s=GhV9OCAXCS6dNxFqmRm8It0VFKGn0HWU-BXVIWRp5eA&e=
or email: MIDRANGE-L-request-+hD5IHI5Xscn3HwCXmMcX9BPR1lH4CV8@public.gmane.org
Before posting, please take a moment to review the archives
at https://urldefense.proofpoint.com/v2/url?u=https-3A__archive.midrange.com_midrange-2Dl&d=DwICAg&c=BSDicqBQBDjDI9RkVyTcHQ&r=ZU3ZIY43VrBBIpLSMzvXRgDD5OJLykt0EaCJu4c8ib4&m=8rkjgZFT7WaNWAjsHqtQ4qcSJruJYNN1Gg0PRc3coZXDqTisPW7oRTml1czgAamm&s=7j1dB9DnXfjF-IRcv53sMEBPTyaAPvfvu2SZqxa4V0Q&e= .

Please contact support-FMtJrHiV//lnDLsaKlm4mFaTQe2KTcn/@public.gmane.org for any subscription related questions.

You can help support midrange.com by visiting https://urldefense.proofpoint.com/v2/url?u=https-3A__donate.midrange.com&d=DwICAg&c=BSDicqBQBDjDI9RkVyTcHQ&r=ZU3ZIY43VrBBIpLSMzvXRgDD5OJLykt0EaCJu4c8ib4&m=8rkjgZFT7WaNWAjsHqtQ4qcSJruJYNN1Gg0PRc3coZXDqTisPW7oRTml1czgAamm&s=CVYVyxBCes1q0EsqnnIJu7x1AZgR2VSBg2HTY2BCcis&e=  and making a contribution.



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

Please contact support-FMtJrHiV//lnDLsaKlm4mFaTQe2KTcn/@public.gmane.org for any subscription related questions.

You can help support midrange.com by visiting https://donate.midrange.com and making a contribution.