× 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:

What version / release of OS/400 or IBM i are you doing this on? And what version / release is on your customers' machines?

As of V6R1 and above, you can specify:

PGMINFO(*PCML *MODULE)

and the compiler will store the PCML in the *MODULE, which will then be bound into the *PGM or *SRVPGM that you send to your customer's system. The QBNRPII API can be used to retrieve this stored information into a stream file on any system where the *PGM or *SRVPGM resides.

See http://archive.midrange.com/java400-l/201103/msg00097.html

At the end of this post, Barbara Morris provides a link to sample code for a DSPPCML command and its CPP.

Or, search for "Display PCML" and "Barbara Morris" and you should find several links.

HTH,

Mark S. Waterbury

> On 8/27/2013 3:36 PM, rick baird wrote:
hey all, quick question.

Is there a way to re-create a PCML file after the compile?

When we distribute a program, it could be put in any number of libraries on
a customer's box, and we don't really have a good means of distributing IFS
files to install on a client box.

The PCML generated at compile time might have this:

<program name="WS119" path="/QSYS.LIB/MYLIB.LIB/WS119.PGM">

but when installed on the client box, the program really could be in
THEIRLIB or ANOTHERLIB.

I could write a program to read and update the stream file after install,
but I'd rather just regenerate the PCML using the PGMINFO in the object.

suggestions?


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.