|
What happens if you create the T1 command to simply call a prompted CL: ?? Call T1CL ?Parm(' ' ' ') or something like that. That will flow to the job log I believe. You'll want to study the choices you have with the question marks. A better choice in my mind would be to put the CL choice on a menu. I get nervous about command lines for users. Also, you may want to add the ability to save the user's last entry and display that as the opening default. --------------------------------------------------------- Booth Martin http://www.MartinVT.com Booth@xxxxxxxxxxxx --------------------------------------------------------- -------Original Message------- From: Midrange Systems Technical Discussion Date: Monday, February 17, 2003 13:07:11 To: 'midrange-l@xxxxxxxxxxxx' Subject: Retrieving Command like F9 I have a need in a CL program to capture the complete command that was entered to execute the CL program. What I think I am looking for is a way to programmatically "press F9" and capture the result. I cannot find any interface to do this .... is it possible? Some obscure API maybe? A bit more information ... there is a command definition for this CL program that includes prompting for optional operands. The user enters the command name and is prompted for the other operands; in the job log only the "originally" entered operands are present; those that were optional are not in the job log, so since F9 uses the joblog to retrieve previous command, it seems F9 would not retrieve all operands, however, this seems to be in conflict with normal interactive operation. For this specific case: operator enters "T1 DEVICE(TAP02)" and is prompted for OPTION. Joblog shows T1 DEVICE(TAP02)" but as CL program begins it is with "T1 DEVICE(TAP02) OPTION(A)" because operator was prompted for OPTION and filled it in. Thanks for any advice ... Chester Hood
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.