×
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.
My first suggestion would be to have the batch job allocate an object, and then have the interactive job attempt to allocate the same object. Using an object lock means that the when the batch job ends for any reason, the interactive job will be free to go.
-----Original Message-----
From: Bob Cagle [mailto:bcagle@xxxxxxxxxxx]
Sent: Wednesday, May 18, 2016 1:46 PM
To: RPG400-L@xxxxxxxxxxxx
Subject: Technique critique?
This is more of a CL programming question:
Background: I have an interactive program that I need to have NOT run while a specific batch job is running. Currently the batch job updates a data area with a flag at the start of the job and then clears it at the end. Interactive jobs can then check for this flag before running.
I have this code in my CL:
CHECK:
/* Check data area to see if job is running */ Rtvdtaara DataArea rtnvar(&Check) If (&Check = '1') then( DO )
/* wait 30 seconds and then try again */ Dlyjob dly(30)
Goto CHECK
ENDDO
The GOTO is bothering me, so the question is - would you code this different? This seems simple and straight-forward, but in your opinion is there a better way?
Thanks
Bob Cagle
IT Manager
Lynk
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
