Wow, in18 months you’ve made terrific progress.
Your company has been willing to train you and hang in there with you because you are showing a real appitutide.
It does get better, but there are days of utter panic and days escesty.
<i>I feel RPGLE will be much better for me and will allow me to do many more things that I have been unable to do with RPG IV. </i>
First, you always code RPGLE using RPG IV.
“RPGLE” would simply refer to the use of RPG in an ILE run-time environment. Since there are no compilers that can compile RPG III source code for ILE, there is a direct correspondence between “RPGLE” and “RPG IV”.
Technically, “RPGLE” only exists as a member type in PDM. It has no real meaning anywhere else. “RPG IV” is the language specification that supersede “RPG III”.
<i>Is this par for 18 months?</i>
Maybe. I’ve seen it done under decent circumstances. It requires supportive management and competent supervisors. But I’d also say that supportive management and competent supervisors might not be “par for the course”.
In any case, the huge amount of “stuff” available on AS/400s (and their successors — iSeries, System i…) will always be more than you’re going to keep up with.
<i>To tell you the truth i’m struggling, the syntax is foreign to me(as written many years ago and there are many Arrays and GoTO’s in there as well, the programme also uses the old RPG Cycle to read straight through the file with Primary file and L1 breaks , there are also data structures for the dates and not much notation! In Fact, i would say that there are about 20 numbered indicators that have no known notation</i>
Welcome to the world of businesses that have a history. That’s life.
Feel fortunate that you aren’t trying to maintain or to modernize DYL-260 or MARK-IV or other languages and constructs that have no current incarnations into modern structures. (Well, I guess MARK-IV still has a kind-of life, though I haven’t seen it for almost 35 years.)
You’re seeing what we had to work with ‘back then’. You’re seeing results of pressures to get things working in the shortest possible time with software tools that were primitive by today’s standards. You’re seeing results of tools that could be afforded by small business 20-30 years ago, not to mention the salaries that businesses were willing to pay.
You might not be aware that ILE has been around for 15+ years. You’d think by now that those old RPG III programs would already have been converted to RPG IV syntax at least. (The CVTRPGSRC does much of the work. 3rd-party tools can also be obtained.)
But it clearly hasn’t been done at your site. Yet, you have a management structure that provides training and encourages new technologies.
It seems to me that that puts a kind of scope on the big picture that you’re trying to see. How can those elements be reconciled?
Who in your organization can give an answer to that apparent paradox? Work out the answer to that question and then formulate a response to whatever comes back to you.
That looks to me to be a fundamental way to create a career.
Be sure not to undermine others. Get others to understand that you’re interested in long-term principles before short-term changes. Get others to be willing to contribute business knowledge rather than to resist an apparent attempt to rock the boat. Ideally, even get an old-timer or two to champion the effort.
Unfortunately, the Cycle, the Primary file and L1, the “20 numbered indicators”, all of those and more need to be addressed in some way. Someone actually has to do some work unless those programs are to be retired.
If you think your situation is messy, you should see what I went through while converting Autocoder being emulated on 370s into COBOL.
If you’re going to work for a company that has history, you will always have to dig your way through its old baggage. The alternative is to work for new upstarts and hope they survive.
Both ways can succeed.