?Session log wasn't open - Protocols

This is a discussion on ?Session log wasn't open - Protocols ; I have a process/job that uses the C-Kermit protocol to dial into and get data from a modem site. I have never worked with C-Kermit before, so please bear with me. The process runs normally, but then terminates with the ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: ?Session log wasn't open

  1. ?Session log wasn't open

    I have a process/job that uses the C-Kermit protocol to dial into and
    get data from a modem site. I have never worked with C-Kermit before,
    so please bear with me. The process runs normally, but then
    terminates with the error:

    ?Session log wasn't open

    I am thinking that some environment/configuration variable for C-
    Kermit has not been setup properly. Either that, or nothing is being
    written to this log. What do I need to check and do to try to resolve
    this problem?

    Thanks,

    Ken


  2. Re: ?Session log wasn't open

    "texasreddog" wrote in message
    > ?Session log wasn't open


    type help log to view / changes your session log settings.

    could be a permission / rights issue preventing the logfile from being
    created / written.



  3. Re: ?Session log wasn't open

    In article <1193173803.461402.65000@z24g2000prh.googlegroups.c om>,
    texasreddog wrote:
    >I have a process/job that uses the C-Kermit protocol to dial into and
    >get data from a modem site. I have never worked with C-Kermit before,
    >so please bear with me. The process runs normally, but then
    >terminates with the error:
    >
    >?Session log wasn't open
    >
    >I am thinking that some environment/configuration variable for C-
    >Kermit has not been setup properly. Either that, or nothing is being
    >written to this log. What do I need to check and do to try to resolve
    >this problem?


    Apparently, the sript driving the session has a 'close session-log' command
    that is preeeded by a 'log session' command.



+ Reply to Thread