×
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.
rick baird wrote:
<<SNIP>>
This is a software ptf distribution scenario - the idea was to
not have to save the physical if it wasn't changed, only sending
the changed or new logical. customer library structures are
generically named, while our library structure is version
specific - the logical on the source system is in a library and
based on a pf in another library that do not exist on the
destination system.
This is a new gig for me, I've never worked in a product software
house before, and my first official duties are to revamp,
streamline and modernize the version/ptf distribution process.
It looks like my only alternative is to save both LF and based on
PF from the same library, restore to a temporary library on SysB,
whereas the LF is then 'crtdupobj' to the ultimate destination
library - moving it's based on relationship to that lib's
physical.
<<SNIP>> If you think of something else, I'd appreciate it.
By "ptf" do you PTF as in CRTPTF? If so, then consider that
distributing database files in packaged products [RSTLICPGM] and via
PTF is not nearly as simple as for a *PGM. There are considerations
for differences between model files and user-data files for database
*FILE installs, and important requirements for using the LODPTF,
APYPTF, and RMVPTF if any database file has or might have logical
file(s). Unfortunately only by knowing how the files are used,
their relations, even sometimes definitions [e.g. constraints,
names, etc.], and their packaging, it is difficult to recommend what
approach(es) might work best to implement changes for any particular
database file [network].
The IBM DB2 for i database team provided consulting for products
with regard to their packaging, installing, upgrading, and PTFing
[discouraged] of database files, to try to limit difficulties &
errors. Difficulties would most often be encountered due to
inexperience in those features [install, packaging, upgrade, & PTF]
by product owners\fixers whose concentration was more on delivering
the function than on the install & serviceability which are too
often considered one-offs. Packaging and coding specifically with
the design kept in mind for install, upgrades, and PTFs better
ensures the ability to effect any changes how & when they are
eventually required. The design for the SQL catalog files in QSYS2
was an example of a horrible mess that I had to recover; today there
are likely still many systems with a bogus *PGM in QRECOVERY as a
side effect. For software houses\developers with Partners in
Development access [PID; IIRC ibm.com/partnerworld] such a
consultancy should be sought via that channel. I could probably
assist directly, but I would seem obtuse without detailed
information; the same type of information that a true consultancy
would require.
Regards, Chuck
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.