|
Hi,
Thanks very much...
But I have below questions for this MODULE_INF file (LF) and for it's PF
(QSQPTABL)
1) when I do DSPFD on this file for QSYS2. MODULE_INF what is the reason it
just shows total records as '1' and same for it's related physical file in
QSYS2. QSQPTABL.
2) SELECT * FROM QSYS2. MODULE_INF shows multiple records with multiple
fields.
3) SELECT * FROM QSYS2. QSQPTABL shows just one record:- like below
INTEGER_COLUMN
1
So if the Physical file here contains this one record with only one field
then how it's dependent logical file above showing multiple fields (though
can see that view is created in DSPFD there as " CREATE VIEW
BOUND_MODULE_INFO (PROGRAM_LIBRARY FOR PGM_LIB,.......)))AS D " with
multiple records and does not match with DSPFD command in terms of total
records specially ?
I could understand that logical file showing multiple fields based on this
view created inside it's definition based on above DSPFD on this LF.
But what is the reason this LF shows just 1 record only in 'current number
of records' where as in actually there are multiple records in it and the
same can be verified from above SQL QUERY (point number 2 above) ?
Note:-
Most importantly the PF on which this whole LF is based is also showing
'current number of records' as just '1'.
But it's showing correctly this total records in terms of 1) DSPFD and 2)
SQL Select query from point number 3 as mentioned above.
Just curious to know as ideally all we know LF is just reflection of based
PF but main PF it self has just one field one record so how is depedent LF
here showing so many records for point number 2) SQL query above ?
Could someone please explain above ?
Thanks very much...
On Fri, Jul 14, 2023, 21:55 Birgitta Hauser <Hauser@xxxxxxxxxxxxxxx>
wrote:
Check the BOUND_MODULE_INFO User Defined Functionsthem
https://www.ibm.com/docs/en/i/7.5?topic=services-bound-module-info-view
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
Modernization – Education – Consulting on IBM i
IBM Champion since 2020
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training
and keeping them!"they
"Train people well enough so they can leave, treat them well enough so
don't want to. " (Richard Branson)joe
"Learning is experience … everything else is only information!" (Albert
Einstein)
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Sent: Friday, 14 July 2023 18:11all
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Fwd: Command to get the list of associated modules for all *PGM
objects.
++ Midrange-l.
Thanks.
---------- Forwarded message ---------
From: joe <joe.planet21@xxxxxxxxx>
Date: Fri, Jul 14, 2023, 21:30
Subject: Command to get the list of associated modules for all *PGM
objects.
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Hi,
Is there any command apart from DSPPGM which could provide the list of
associated modules from the PGM object for all the programs which are
present in a specfic ibm i environment?
For example DSPPGMREF could give this information for all the associated
file, dataarea and PGM objects in outfile.
Similarly I did not find an option in DSPPGM command to get that
information( for associated modules with respect to program names ) for
the *PGM objects to get it in *OUTFILE.list
So how to get that information here in a single command like DSPPGMREF
(for
all object types, for all objects and for all the libraries) for DSPPGM
command?
Any suggestions are highly appreciated.
Thanks.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,list
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
As an Amazon Associate we earn from qualifying purchases.
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.