Conference csc32::consolemanager

    I don't believe that the events get logged to disk and thus only have a 
    very short life span. Look for an enhancement in this area in the next
    release of PCM.
    
    Dave

    If the PSW 2.2 code behaves the same way as V1.0 and passes information
    to PCM via a pseudo-terminal (of "soft" console") then indeed PCM will
    treat it just as it would any node that has a physical console. This is
    the way it was done with VCS and PSW. I haven't seen those release
    notes or the new PSW stuff. I hope this particular interface still
    works the same way.

Hi,
   I wrote the PCM feed from PSW as an exercise to test my C programing and the 
two APIs. It was not really designed to be a great feeder between PWSW and
PCM. However, I simply use the call described in the PSW docs to read from 
stdout of the PSW actor and feed these packets into PCM via the
CMUserSendEvent() call. Most of the code in the program is to munge the
attributes from PSW into the attributes for PCM.

In the current version of PCM the external events (i.e. CMUserSendEvent() events
are not logged by PCM to disk, so there is no audit trail and no context as
there is for PCM events from the console.

In the next version of PCM ( hopefully ) we will have the ability to log the
context from these (external) events and provide an audit trail. In addition
Ack and Clear of All events will be logged.

Hope that clears up any misunderstandings.

Cheers Simon...

    >Hi,
    >  I wrote the PCM feed from PSW as an exercise to test my C programing
    >and the two APIs.
    
    Oh! That explains it then......;-}
    
    But seriously, we could probably take the old SNS$FEED_VCS.C file and
    adapt it pretty easily unless PSW no longer has the "mailbox set"
    interface. Simon, do you know if indeed the mailbox interface to PSW
    is still present?
    
    
    Regs,
       Dan

re: 287.3

Simon,

"next version" sounds good to me...Are there real plans for implementing the 
logging of "external" events and audit trails? When is the next version supposed 
to be available? 

This feature is quite would be very useful in the project I'm working for.

Thanks,
Adrian

Re .4
     Dan,
the routine I wrote was for pswx ( i.e. the UNIX version). I am not sure whether
the interface is the same for the VMS version. I could ask Christian-Jaques
Bonnetto about that. What I used was the documented interface from the "Actor"
interface for PSWX.

Re .5

Yes there are "Real Plans". Although the full formal spec for the next version
is not yet complete we have already done some work on the base code. This
includes a large rewrite of the Logging Mgt. Part of that includes the logging
of external events, both for systems managed by PCM and also hopefully for other
systems as well. Also the Acks and clears are logged by time and name of person
Acking and Clearing ( Side effect is that event files will grow from the current
version).

If you have any specific requirements in this area let us know Very Quick


Cheers Simon...

Within OSCint 2.0 for OpenVMS VAX, which is starting FT now, PSW (for VMS of
course) is integrated with PCM, in the sense that even the PSW editor (Motif 
& Character Cell) has been modified to perform the mapping between a PSW event 
and a PCM event. More precisely, this means that through the PSW editor, when 
you enter new data, for example a disk to be checked for free blocks, you can 
at the same time enter the PCM event name, PCM Class, PCM Sub-system, PCM 
Information, and PCM Priority. In the information field you have also the 
possibility to already enter the Repair Routine that would need to be triggered
to try to fix the specific problem. The Routine will then be triggered from 
PCM using the OSCint provided Repair action routine.
There is also a kind of 'alternative' possibility when you enter this mapping,
in the way you can according to a threshold number of event and a threshold
time interval, assign 2 different sets of values for the PCM name, class,
sub-syst, info and priority. This is for example interesting when you try an
automatic repair as the first alternatives, but if it occurs too many time
within a predefined period, you will then generate a second PCM event which
will let you know the problem.

OSCint 2.0 for OpenVMS VAX will be now ported on OpenVMS AXP and DEC OSF/1.
Phase 0 is starting this month, schedule will be known then.

Cheers,
Christian.
    

    Thanks for that information! It sounds wonderful! Now, exactly how does PSW
    pass information to PCM?
    
    Regs,
       Dan

    PSW Mailbox feature is used, and the feeder which is reading the
    mailbox, uses CMUserSendEvent() to feed PCM.
    
    Rgds,
    Christian.