Quick in batch

[Ken Langendock]

IMHO,  DON'T DO IT.

Sooner or later someone will mess with that screen and screw up your
batch process.

OR, if you really must.
Create a ghost screen (regular quick in batch type screen) and call that
production screen passing a flag....in the production screen check the
flag and try to do everything you need in the initialize procedure like
you usually would.

FYI, I will never use a production screen in batch mode....unless I plan
on leaving the company and letting someone else handle the mess...lol
Ken



-----Original Message-----
From: powerh-l-bounces+ken.langendock=rogers.com at lists.sowder.com
[mailto:powerh-l-bounces+ken.langendock=rogers.com at lists.sowder.com] On
Behalf Of Pickering, John (NORBORD)
Sent: August 16, 2006 2:40 PM
To: Powerhouse List (E-mail)
Subject: Quick in batch


I regularly run Quick in batch -- but these are typically screens with
everything driven from the initialize procedure and NOTHING being
displayed
on the screen. Now I have a need to run a regular production screen in
batch. Is there a way that I can suppress the screen output or redirect
it
to the bit bucket?

This is for either Quick 7.29 or 8.49 on MPE/ix. 

And for the record, file stdlist=$null doesn't work :-(

Thanks in advance for any help,
JWP
-- 
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l at lists.sowder.com
Subscribe: "subscribe" in message body to
powerh-l-request at lists.sowder.com
Unsubscribe: "unsubscribe <password>" in message body to
powerh-l-request at lists.sowder.com
http://lists.sowder.com/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.
Add 'site:lists.sowder.com powerh-l' to your search terms to search the
list archive at Google.