Conference csc32::consolemanager

    
    Stefan,-
    
    You don't ne-ed macro program. PCM creates FTA terminal for you and
    you can get OPCOM messages to this FTA terminal
    Here is command procedure for
    pseudo terminal we are using. We are using it to cath opcom
    messages of PCM system (AMDS events,etc)
    
$     set noon
$     wait 00:00:10
$     i = f$trnlnm("SYS$INPUT")
$     c = f$trnlnm("SYS$COMMAND")
$     o = f$trnlnm("SYS$OUTPUT")
$     set term 'o'/broad 
$     write sys$output "SYS$INPUT =''i' SYS$COMMAND = ''c' SYS$OUTPUT = ''o'"
$     write sys$output "Issuing $ REPLY/ENA"
$     reply/ena
$     write sys$output "Issuing $ REPLY/STAT"
$     reply/stat
$     wait 00:01:00
$ loop:
$     write sys$output "This is reply only terminal"
$     wait 01:00:00
$     goto loop

Thanks Olli,

/Stefan

Hi again,

There still seem to be some kind of a problem regarding the pseudoterminals
atleast in my VAX/VMS version. I am running PCM V1.5 ECO 1. 

What I have done is setting up 2 different systems to use Pseudoterminals. 
One of them is set up to run Edit/tpu as command and the other to use Ollis
commandprocedure in .1.

What happens is that a process is created for each system and they are named 
_HAMRA$FTAxx and a corresponding _HAMRA$FTAxx.COM is created in the CONSOLE$TMP
directory, but it never gets executed! So when I connect to the system i get
a $ prompt logged in to the system account.

What i wrong here? Did I miss something obvious or?

/Stefan

Stefan,

  How quickly are you connecting? The procedure should get
  executed, but it doesnt do so immediately, there is a few
  seconds delay.

Cheers,
Phil

    I have had this problem numerous times. In each case it was because
    a DCL command such as SET TERM/INQ was being executed in SYLOGIN.COM.
    SET TERM/INQ is usually the culprit as it chokes with the infamous
    "specify terminal or mailbox device" error when executed by the
    driver procedure that cranks up the pseduo-terminal command you 
    specified in editor and at thate time the processes permananet logicals
    are pointing at the driver command file and not a terminal.
    
    He're's how I worked around it in my login procedures:
    
    $ TT_DEVNAME = F$TRNLNM("TT")
    $ IF F$LOCATE("FTA",TT_DEVNAME) .NE. F$LENGTH(TT_DEVNAME) THEN GOTO SKIP_IT
       .
       . !SET TERM/INQ is done in this section.
       .
    $SKIP_IT:
    
    
    
    Regards,
       Dan

  Re: .5

    Yup, and this is documented too.

.5 is correct. 

I thought that I only did Set term/Inquire when I was logging in interactivly.
I guess theese processes are run in f$mode .eq. Interactive. Otherwise
my Sylogin.Com would have worked. Anyway I implemented the solution in .5 and
everything is working OK now.

/Stefan

Hello:

I am having the same problem described in .3 where the pseudo-terminal process
is created, the _node$FTAxx routine in CONSOLE$TMP is NOT executed and I can
connect to the pseudo-terminal and be left at a "$" prompt.

I have ensured that a SET TERM/INQ is not executed in SYLOGIN; the SYSTEM
account LOGIN.COM is not executed since it appears that the default login
directory is set to CONSOLE$TMP. I have also waited a considerable length of
time (30 minutes) with no luck (as indicated in reply .4).

Also, when I view the system, I see a single "@" after the dollar sign prompt,
almost as if PCM started to enter the command to execute the action routine,
but gave up part way through.

Here is how I configured the system in PCM:

	System Name         = ctupcm
	    Information     = PolyCentre Console Manager Pseudo-Terminal
	    Connection      = Pseudo-Terminal
	    Command         = @sys$manager:pcm_pseudo_terminal
	    Scan Profile    = ctupcm
	    Icon filename   = VAXSTATION_3100.XBM
	    Console line    = Enabled
	    Logging is enabled, directory = CONSOLE$LOGFILES

I am running PCM V1.5-006 on VMS 6.1 on a VAXstation 4000vlc. Any help would be
appreciated.
						Thank you very much,
							....... Vern.

    Hello again:
    
    I think I solved the problem. My SYLOGIN.COM was displaying some banner
    text that contained escape sequences. It appears that any escape
    sequence, whether displayed (like my banner) or not (like a SET
    TERM/INQ) causes PCM to choke like I described in .8.
    
    Some experimentation revealed that it was only escape sequences that
    caused the problem; a WRITE SYS$OUTPUT " " in SYLOGIN did not interfere
    with the startup. I would assume that plain text also will not
    interfere, though I did not test any text OR MULTIPLE WRITEs in my
    experiments.
    
    Hope this info is of use to anyone who is experiencing the same
    problem!
    						......... Vern.