|
wdsci-l-bounces@xxxxxxxxxxxx wrote on 02/06/2006 02:00:55 PM: > That's it in a nutshell, but i'd think that WDSC would do something other > than 'ignore' it... I doubt that they are ignoring it or even that your program is not being run. Your validity checker probably has code to detect if the command is running in a batch or interactive job. In WDSC, the job would be batch. If you try to open a display file in a batch job you get a hard error, so usually you either condition your code to check the job type and skip opening the file, or I suppose you could handle the error in your code. > This is all very new to me and we're just looking to find out the impact of > moving our programmers from greenscreen to WDSC. One big impact is going to be anything in your "process" that requires a green screen. In most cases, that screen is not going to exist. Mark _____________________________________________________________________________ Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs. _____________________________________________________________________________
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.