|
I've made an assumption here based on observations, and I may be incorrect (and most likely am), but I have no other explanation. Hopefully, in as kind of a manner as is usually displayed in this group, I can be corrected and put on the right path.
I've created an SQL based RPGLE program that I use to convert RPG IV to RPG Free. In it, I utilize the SYSTEM() function to compile the original source, copy the spooled file to a source file member, and search for various information like c-spec created variables. The problem is that when running the program using the RDI "user action", the compile spool file job number is not the same as the job number of the job that issued the "user action".
I don't know why, but it uses a job associated with my user id, but not one of the current active jobs. Not sure what job that is and why it uses it. Nor do I know how to discover what the spool file job number is.
I believe that this is also an issue with other development environments other that RDI, so I don't think it's an "RDI" problem, but one associated with SYSTEM() and similar. I haven't tried QCMDEXE to see if that is different. Maybe I should?
Any known answers?
Duane
CONFIDENTIALITY NOTICE: This electronic message transmission is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. If you have received this transmission, but are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this information is strictly prohibited. If you have received this e-mail in error, please contact NALC Health Benefit Plan at 703-729-4677 and delete and destroy the original message and all copies.
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.