|
Joe, To recreate my own written tools I put the compile instructions in a source file. To compile one tool I wrote a command that check the existance of that source (it has the same name as the tool), compiles that programme in QTEMP and runs that newly complied programme. This runs in batch. Especially handy when recompiling the ILE-stuff. Just an alternative. To save/restore a DTAQ you can write your own tools to store the DTAQ messages in a file, a user space or a user index. A file is simpler, as you can create one at runtime, after receiving the length of the DTAQ. Of course, the DTAQ should not be keyed then, as the key should also be stored some where. Regards, Carel Teijgeler *********** REPLY SEPARATOR *********** On 24-9-02 at 10:38 Joe Pluta wrote: >I'm finishing the automated upgrade utility for PSC400. Unfortunately you >can't do a save/restore on a data queue, so I'm designing my own object >management, and I was hoping not to have to have a separate little update >program for every non-program object. The ability to execute a few CL >commands in a source member on the fly would have been perfect.
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.