Re: Embedded printer file compilation options

I have utility called iBuild (www.sourceforge.com/projects/ibuild) which
allows you to put strings into the header of a source member. The utility
reads the strings , formats variables and creates the objects(See the
Readme for examples).

On Thu, Sep 28, 2023, 7:29 AM Dan Bale <dan.bale@xxxxxxxxxxxxxxxxxxxxx>
wrote:

Bill, I don't know if you got the answer you were looking for, but I'd be
happy to share the utility I mentioned yesterday.

- Dan

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Dan
Bale
Sent: Wednesday, September 27, 2023 10:56 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Embedded printer file compilation options

Hi Bill,

I know that PTC/MKS Implementer change management saves the compile string
for each compilable object. Probably every change management software does
that.

I also seem to recall that RLU (remember that beast?) saves the compile
string as well.

I wrote a utility years ago that I haven't used in forever that looked for
strings in the source for precompile commands, compile command parameters,
and postcompile commands:
**#$%PRE: OVRDBF CUSTMAST TOFILE(SOMELIB/CUSTMAST)
**#$%COM: SIZE(*NOMAX) MAXMBRS(10)
**#$%PST: SNDMAIL TO(DAN) BODY(&&RESULT)

Does RDi's designer save this info for display and printer files?

- Dan

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Howie, Bill
Sent: Tuesday, September 26, 2023 3:49 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Embedded printer file compilation options

Hello,

This question may have been asked a thousand times here on the list. Is
there a native way to embed printer file compile options within the printer
file source so that one doesn't always have to look at the current printer
file object to see how it was compiled and then match that? It would be SO
much simpler. Thanks for any info!

Bill Howie

*** CONFIDENTIALITY NOTICE: The information contained in this
communication may be confidential, and is intended only for the use of the
recipients named above. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution, or
copying of this communication, or any of its contents, is strictly
prohibited. If you have received this communication in error, please return
it to the sender immediately and delete the original message and any copy
of it from your computer system. If you have any questions concerning this
message, please contact the sender. ***
--
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.