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


  • Subject: Re: Stupid RPG cycle question
  • From: Jim Langston <jlangston@xxxxxxxxxxxxxxxx>
  • Date: Mon, 22 May 2000 08:12:15 -0700
  • Organization: Conex Global Logistics Services, Inc.

I wound up setting on a new indicator in my first time block and
doing the       10
            OR   OF
thing which worked while waiting for answers.

Well, I see 1P isnt' going to work for me since there is data I
fill into the header from the calc specs.  I'll try the 'F'etch in the
next program of this ilk I need to modify which is... today!  Another
program they want me to do the same thing to.

I would go ahead and convert to RPG IV and then make modifiations,
but as it turns out this system is not going to be used anymore by the
end of the year anyway.  We went through a merger, and the company
we merged with has their own systems, luckily for me they use AS/400's
also.  They just use off the shelf AS/400 software.  Buy rather than build
is their motto.  So, by the end of the year I think this AS/400 is going to
be sitting here idleing, or just being used for Passthroughs.

So, why bother to modernize everything if it's just going hasta la bye bye
anyway?

Regards,

Jim Langston

Douglas Handy wrote:

> Jim,
>
> >1P?  I have never seen that in a single program on my system,
> >nor have I seen it in any documentation.  I didn't know it existed!
>
> That works *if* the headings do not need any fields derived from
> calcs, including the "first time block".  If you look at the cycle
> charts, 1P processing occurs before any of your calcs.  If your
> headings include the time of day, then that field won't be initialized
> either.
>
> As an alternative, do like your first inclination and condition the
> line strictly by OF.  Force on OF in your first time block, just like
> you did.  The step you missed is to code your first detail time O spec
> with a F in column 16 for "fetch overflow".  This tells the cycle to
> first check for overflow prior to printing the line.
>
> Once you have done this, you can also seton OF anytime you want to
> force a new page; possible on a calc conditioned by a Lx indicator.
>
> My standard report headings in RPG II were conditioned just by OF,
> with OF forced on in the first time block.   The first detail or excpt
> output included F for fetch overflow, as did any other line which may
> otherwise print too far down the page.

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@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.