| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 663.1 | | WARABI::ZORBAS | NULL Junior | Mon May 11 1992 06:09 | 7 |
|
<<<FOR loop and it appears that the file is not being closed (until I
I should add that the file not being closed is the SCRIPT.
Stuart.
|
| 663.2 | Need to change the algorithm | SHALOT::NICODEM | Who told you I'm paranoid??? | Mon May 11 1992 16:20 | 17 |
| A Script mode script file is not closed until either a specific script
directive is encountered that closes it (e.g., .EXIT, .ABORT), or until some
part of the application goes for input and encounters an EOF. For instance, if
I have an application that requires exactly three pieces of input, and no more,
and I write a Script mode script containing that input and then run the appli-
cation, the script file will still be open. The *next time* I need input,
though, ALL-IN-1 will go to the script file, get an end-of-file, and close the
script. (BTW, putting a .EXIT after the third piece of input won't work either,
since it won't be encountered until the application goes back form more input.)
So in effect, what you're doing is nesting your script files. Each time
you go through your FOR loop and execute another SCRIPT function, you are
leaving the previous script file open -- even though it is basically at end-of-
file -- and starting a new script. (You might try a OA$SCP_STACK_DUMP to look
at your script stack and verify this.)
F
|
| 663.3 | Scriptures | SNOC02::ZORBASSTUART | NULL Junior | Tue May 12 1992 01:23 | 10 |
|
Frank,
So, in short, you're saying "bad luck, it won't work that way".
Any other suggestions?
Cheers,
Stuart
|
| 663.4 | DO it all from within a single script? | SHALOT::DUNCAN | Joe - CIS/EIC Doc. Mgmt. Solution Set Consultant | Tue May 12 1992 15:55 | 4 |
| Why not put the for inside the script script, and not have to leave the
script at all, until all the files have been processed?
Joe Duncan @ OPA
|
| 663.5 | | SNOC02::ZORBASSTUART | NULL Junior | Wed May 13 1992 02:37 | 7 |
|
Sounds good Joe.
Unfortunately, the script is being called near the end of a long line of
DO calls.
Stuart.
|
| 663.6 | Grasping at straws... | SHALOT::DUNCAN | Joe - CIS/EIC Doc. Mgmt. Solution Set Consultant | Wed May 13 1992 16:12 | 6 |
| Stuart,
How about embedding the DO calls in the script script? Do the DO
scripts collect user input? That could complicate things somewhat.
Joe Duncan @ OPA
|
| 663.7 | Prompt? | SNOC02::ZORBASSTUART | NULL Junior | Fri May 15 1992 01:39 | 11 |
|
I upped all my personal quotas (including FILLM) and it made no
difference; could be a system parameter (perhaps SRA related Joe!).
Anyway, what I did was to issue a prompt every 100 transactions. This
effectively closes the script scripts. So all I do now is start the job
and hit RETURN a couple of hundred times and let it run...
Cheers,
Stuart
|
| 663.8 | | PAULUS::BAUER | Richard - ISE L10N Center Frankfurt | Wed Jul 01 1992 13:43 | 18 |
| Hi !
The following script worked for me, no hitting RETURN necessary:
oa$tra_set all,script,scrchr,symbol,mess,input,log
for cab$ with .folder eqs "TEST" THEN -
cab select .%key:30,.%key:6:30\\-
script testudp.scp\\edit oa$curdoc_filename,,,"WPSPLUS"\\-
prompt\\oa$scp_stack_dump
oa$tra_set off,log
This was done on V2.4. The key is to use the PROMPT as said before. The
OA$TRA_SET are just for debugging of course, but the OA$SCP_STACK_DUMP
shows clearly that the stacking level is lowered.
Maybe it still helps
Richard
|