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



Thanks for the reply.

That's exactly where I have it. In Col 1. I did a shift F7 to move it over.

Thanks,

Gary

On 5 Oct 2010 at 23:28, Leif (Leif Guldbrand <rpg400-l@xxxxxxxxxxxx>) commented
about Re: Form-Type entry for main procedure not valid :

Yep....

And another thing crossed my mind at my work many moons ago ....
** DTA needs to be in col 1 (and not col 6). This was after using a
tool converting from RPG-something to RPG ILE.

You have somewhere an option (PDM) to show both lines and
source lines. That's where you leftify your **DTA to col. 1.

Not sure it helps, but it came into my mind :-)

Leif
----- Original Message -----
From: <jdavis@xxxxxxxx>
To: <rpg400-l@xxxxxxxxxxxx>
Cc: <rpg400-l@xxxxxxxxxxxx>; <rpg400-l-bounces@xxxxxxxxxxxx>
Sent: Tuesday, October 05, 2010 10:54 PM
Subject: Re: Form-Type entry for main procedure not valid or out of sequence.


The problem is where your O specs are at. The O specs need to be before
any the P specs in the program.
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.




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.