|
Brad wrote: > In the meantime, I just created the following CL to run in a continuous > loop, which creates a file that changes every thirty seconds which can be > queried from SQL Server. That will do the trick but one problem with this approach is that the number of spooled files attached to your NEP will keep growing and eventually max out, causing the job to crash. A simple alternative instead of looping round after the delay is to have the job submit another copy of itself, although you need to be sure that the next incarnation of the job will become active immediately. Perhaps a better method would be to have the looping CL repeatedly call an RPG program which could retrieve the data area and update a single record file. If the data area is just a simple switch, yet another option might be to have three versions of your single record file: an "off" version, an "on" version and a "current" version. The CL NEP could then retrieve the data area and depending on the value returned execute a CPYF with MBROPT (*REPLACE) from either the "on" or "off" file to the "current". SQL Server then simply queries the "current" version. Dave... ------------------------------------- Any opinions expressed are my own and not necessarily those of my employer.
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.