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



David has said that code.midrange.com really isn't for code distribution...

It's just for snippets so that email doesn't mangle the code into an
unreadable mess...

The Midrange wiki is an ok choice for small complete code..
https://wiki.midrange.com/index.php/Main_Page

Probably the best option now-a-days is Github, either as an actual repo or
as a gist..

Charles



On Thu, Apr 23, 2020 at 4:09 PM Mark Waterbury <
mark.s.waterbury@xxxxxxxxxxxxx> wrote:

Duane,
Here's one way:
You can upload code to http://code.midrange.com and then post the
generated link(s) in an e-mail to these lists ...


Mark S. Waterbury

On Thursday, April 23, 2020, 6:06:47 PM EDT, Duane Scott <
dscott@xxxxxxxxxxx> wrote:

I'd make it available right now if I wasn't scared of people making fun
of my poor coding. That Jon Paris can be downright cruel sometimes. (JK,
Jon).

What's the best way to send the source? I haven't been paying attention.

Duane



-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Vernon
Hamberg
Sent: Thursday, April 23, 2020 5:13 PM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: QCMDEXE behavior modification

Sounds cool, Duane - I'll have to check out the compile listing sometime
to see just what it tells us.

Sounds like too much fun - will you be making it all available sometime?

Cheers
Vern

On 4/23/2020 3:00 PM, Duane Scott wrote:
Vern,

Ascertaining the C-spec created variables:

What I really wanted (originally) was to use the compile list to
indicate which file variables are actually referenced in the program. My
thought was to use the cross reference in the compile listing. A secondary
bonus (based on my lack of foresight) also gave me the C-spec generated
variables so that I could add them to the XREF file that I use during the
translation. The translation also contains the field sizes and thus I use
that information to convert move and adds to 'eval'-less statements ONLY if
the size and type match. Else, I leave them alone and make it up to the
programmer to modify that move or add spec.

I started this project over a year ago and it has morphed several times
with fixes here and there. I probably know enough now not to have to rely
on the compile print to get what I need, but since this seems to work
(mostly), I don't want to change that part.

If you want to learn even more about it, I'm willing to talk more about
it. As you can tell, I like to say things. A lot.

Duane

-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Vernon Hamberg
Sent: Thursday, April 23, 2020 12:53 PM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: QCMDEXE behavior modification

Hi Duane

Some things get submitted - and compiles can be one of those things.
It's a guess on my part, however. I mean, PDM options should not have an
effect on the actual CRT commands.

Now RDI does have a setting in what, the Commands subsystem, to run
things in batch, hence, a different job.

I wonder about the assumption - QCMDEXE does keep things at the same
call level, IIRC, but it doesn't start a different job.

Do you know the job number? Can you DSPJOB using that number?

I'm also curious about doing the compile - C-spec created variables can
be ascertained just by scanning the source, right? I've not had reason to
look, so I ask, what does the compile give you that is more informative?
That would be cool stuff to learn about!

Regards
Vern

On 4/23/2020 10:35 AM, Duane Scott wrote:
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.

--
This is the RPG programming on IBM i (RPG400-L) mailing list To post a
message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit:
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.midrange.com_mailman_listinfo_rpg400-2Dl&d=DwICAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=LifWsbmXTz4aXbMMEwOi1aJ3sWD5nsP_QI4reJ8MbDM&m=Gmez_DTnONnwqdfGRVT3EV3hzl_H8XFAXl-8Q3Fev5s&s=GgOJX6UIxD2VQAskTXplDlyOqSzsZa9BZZ8bSHnZwCo&e=
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://urldefense.proofpoint.com/v2/url?u=https-3A__archive.midrange.com_rpg400-2Dl&d=DwICAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=LifWsbmXTz4aXbMMEwOi1aJ3sWD5nsP_QI4reJ8MbDM&m=Gmez_DTnONnwqdfGRVT3EV3hzl_H8XFAXl-8Q3Fev5s&s=vWnPWwFtFb2cK_Yq7Sn9FFBgMmUUTj3BD4e42HAgocs&e=
.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support
https://urldefense.proofpoint.com/v2/url?u=http-3A__midrange.com&d=DwICAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=LifWsbmXTz4aXbMMEwOi1aJ3sWD5nsP_QI4reJ8MbDM&m=Gmez_DTnONnwqdfGRVT3EV3hzl_H8XFAXl-8Q3Fev5s&s=mJKglHp6nnxxzzWmKtxXFMdep15BCtw5yOIPS5F9quQ&e=
by shopping at
https://urldefense.proofpoint.com/v2/url?u=http-3A__amazon.com&d=DwICAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=LifWsbmXTz4aXbMMEwOi1aJ3sWD5nsP_QI4reJ8MbDM&m=Gmez_DTnONnwqdfGRVT3EV3hzl_H8XFAXl-8Q3Fev5s&s=M2AENAHNek6-ZbSAaCjx_Bt1O5osRceAiIq8xco_zd8&e=
with our affiliate link:
https://urldefense.proofpoint.com/v2/url?u=https-3A__amazon.midrange.com&d=DwICAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=LifWsbmXTz4aXbMMEwOi1aJ3sWD5nsP_QI4reJ8MbDM&m=Gmez_DTnONnwqdfGRVT3EV3hzl_H8XFAXl-8Q3Fev5s&s=ofVdu-F5HIF8q2SFI7jdRMefqY-1DQudKytjBUTMwTs&e=

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


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.