| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
Should I be able to direct MCC output to a file on a command line
which invokes an MCC command file?
For example, I'm trying to do the following:
MCC> DO tsam_commands, to file=tsam_output.txt
Should this work?
Thanks--
Laurie
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 686.1 | One more thing ... | TOOK::FAIRBANKS | Wynonna Wannabe | Fri Feb 01 1991 15:58 | 9 |
BTW, the error message I get says
%MCC-W-EOSEXPECTED, an end-of-string is expected, but found this: ,
I get the same error if I remove the ',' from the command line.
| |||||
| 686.2 | not supported | GOSTE::CALLANDER | Wed Feb 06 1991 13:44 | 14 | |
Sorry, that isn't supported. You would have to put the
to file qualifier on each line of the command file or use the
command
use default qual to file=output.lis
This will cause all subsequent commands to send their output to
the file output.lis...unluckily right now this means a new version
of the fill will be created for each command.
I am going to qar the lack of support for the to qualifier on the
do command. This is qar 480 in the MCC_INTERNAL qar database.
| |||||
| 686.3 | semi work around | TOOK::DITMARS | Pete | Wed Feb 06 1991 16:19 | 12 |
while it's not the same thing, you can create a log file to capture the output of all commands in a command procedure... MCC> use logging file tsam_output.txt MCC> use logging on MCC> use verify on MCC> DO tsam_commands MCC> use logging off will result in all the output being sent to your screen *and* to a file. Logging and command procedure verification are new in V1.1 of FCL. | |||||
| 686.4 | parser error messages | TOOK::DITMARS | Pete | Wed Feb 06 1991 16:23 | 5 |
re: .1 The parsing of FCL's local commands does not expect qualifiers. If anything other than the verb and any required arguments are entered, the parser will complain in the manner you've noted. | |||||