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



Hi all,

I have a cl pgm, 
I have defined a display file with 3 formats (#Screen,#MSGF,#Screen2)
#Screen requires input from the user
#MSGF is a message subfile
#Screen2 is a display asking the user to wait will the processing continues.

I issue a SNDF to the #MSGF
A SNDRCVF to the screen
Then some validation (libs etc)
Then SNDF to #Screen2
Then a call to another CL pgm to do some work, with Screen2 displayed on the
screen.  

This works just dandy in one of my programs, where the called CL pgm has
quite a bit of work to do.

But,
In another pgm where the called CL finishes very quickly I inserted a
DLYJOB(5) after the SNDF #Screen2
But to no effect.
If I change the SNDF to SNDRCVF it seems to work ok

Does anyone know why this is so?

Another point of note is, that when using the SNDF there is a delay then
screen2 flashes on then off.
But using SNDRCVF screen2 appears almost immediately then there is a delay
(expected result).

Thanks in advance

Colin Thorpe   
+---
| 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:

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.