× 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.



Marty,

 I'm looking to retain the interactive part, not just to have a log.  Also,
if I'm not mistaken, redirection of the output will remove it from view
while it's executing, right?  I'm also looking to avoid that result.

 On the /400, the way it reatins that info is via the "BATCHI" type job. 
The F12 Disconnect method from the QSH interactive session provides this. 
I'm just trying to find out how to do this programmatically.

 -mark

Original Message:
-----------------
From: Urbanek, Marty Marty_Urbanek@xxxxxxxxxxxx
Date: Thu, 2 Feb 2006 10:03:13 -0500
To: midrange-l@xxxxxxxxxxxx
Subject: RE: QSH question


Mark,

You could redirect the output to a file:

QSH CMD( 'Do qshell command > MyOutputFile 2>&1' )

and the append to it on subsequent commands:

QSH CMD( 'Do qshell command >> MyOutputFile 2>&1' )

-Marty

------------------------------

date: Wed, 01 Feb 2006 21:02:32 -0500
from: "M. Lazarus" <mlazarus@xxxxxxxx>
subject: QSH question

  Is there a way to programmatically mimic the F12 function in 
QSH?  Something like:

QSH CMD( 'Do qshell command ;ReturnWithoutEnding' )  so that going 
back into the session will still retain the log.

  -mark

--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .




As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.