[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

3183.0. "Can't display a message in the log file in batch mo" by DV780::MADDOXJ (Digital Alien) Tue Aug 24 1993 05:19

    This has probably been discussed but several DIR/TITLE= searches didn't
    reveal a discussion.
    
    I'm having trouble displaying a message from a script run in batch
    mode.  I've tried GET OA$DISPLAY = "STRING\FORCE" (actually the display
    is happening in a FOR loop and the force was terminating the loop
    prematurely as discussed before so I tried GET OA$FUN= "FORCE") and
    OA$FAO "Message !AS", OA$DISPLAY, #SYMBOL.  The trace shows the
    function is being invoked but nothing appears in the log file.
    
    Any ideas?
    
    Thanks,
    
    Joe
T.RTitleUserPersonal
Name		DateLines
3183.2Sorry, my mistakeDV780::MADDOXJDigital AlienTue Aug 24 1993 15:2022
    Martin,
    
    Thanks for the suggestion but the problem is with my note not the
    script.  The code is actually in an IF statement within a FOR loop and
    looks more like:
    
    for whatever do -
       jumble \\ -
       .if whatever then -
          more jumble \\\\ -
          get oa$display = "String" \\\\ -
          force \\\\ -
          even more jumble
    
    Should I need the FORCE for the DISPLAY to work?  Is there some trick
    to displaying a message in the log file in batch mode?  I'm invoking
    ALL-IN-1 with a /NOINIT and then invoking OA$INI_INITIALIZE in case
    that matters.
    
    Thanks,
    
    Joe
3183.3hummmm?BOOZER::MARTIN::BELLMartin Bell, NTCC, Birmingham UKTue Aug 24 1993 16:0239
Joe,

i think that you need to check your DO loop and IF code to ensure
that it is actually executing how you think it is!

I just created the following simple DCL command file ...

$!------------------
$allin1/noinit
for oa$table:"ONE,TWO,THREE" do get oa$display="Hello World"
exit
$exit


... and when it ran it produced the following logfile ...

$allin1/noinit
for oa$table:"ONE,TWO,THREE" do get oa$display="Hello World"
%OA-I-LASTLINE, Hello World
%OA-I-LASTLINE, Hello World
%OA-I-LASTLINE, Hello World
exit

	BELL finished using ALL-IN-1 at 24-Aug-1993 15:54

... which implies that what you are trying to do should work, assuming
that the GET OA$DISPLAY is actually being executed. Note that i didn't
even have to include the \\FORCE.


Try replacing your FOR loop and IF expression with conditions that
will ALWAYS succeed, to check whether you syntax is correct (although
it looks ok).

mb

p.s.

i am on ALL-IN-1 v3.0
3183.4Still tryingDV780::MADDOXJDigital AlienTue Aug 24 1993 17:009
    Martin,
    
    The trace indicates the code is being executed.  When I had the FORCE
    in place of the GET OA$FUN = "FORCE" the FOR loop was terminated early
    but the message was displayed in the log file.  Once I fixed the FORCE
    problem so that the FOR loop executed properly, the message was no
    longer displayed.
    
    Joe
3183.5EurekaDV780::MADDOXJDigital AlienTue Aug 24 1993 23:318
    The problem was caused by an ALL-IN-1 WAIT function that was dispatched
    by a command procedure which was invoked in the aforementioned IF
    statement.  I changed the command procedure to test for batch mode and
    skip the WAIT function.  All is now well.
    
    Thanks,
    
    Joe