×
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.
Do the CPYFs have to be run in sequence? Could your job submit them as separate jobs and let them run in parallel? You'd have to set up some sort of control to see when they finished... maybe look for locks on the destination files. Then your status message could say "28 CPYFs submitted.... nn Completed" and let the user watch the numbers.
How fast do the CPYFs run? Seconds? Minutes? Hours?
Could the CPYFs be run as SQL statements (even RUNSQLSTM with one or more source members)? That would eliminate the CPYF messages.
Paul E Musselman
PaulMmn@xxxxxxxxxxxxx
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of T. Adair
Sent: Thursday, January 03, 2019 2:53 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Hide command status updates
Thanks for the responses. Always appreciated.
The job does about 28 CPYFs and the timing is such that my SNDPGMMSG
shows on line 24 for about 1 microsecond before the next CPYF status
message stomps over it. I'm probably going to have to fidget with the
timing.
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
