Conference csc32::consolemanager

>Now I read in Comet-database that there was an IPMT for this problem and
>a patch PCM.UNIX_307(A) has been created. Now, can anyone of the
>PCM-Engineers answer me the following questions:
>
>1) Is this patch still actual?
    
    Did you take a look in CSC32::PCM$KITS: per the conference
    announcement?
    
>2) What are the prerequisites to installing this patch?
    
    You'll need to install the ECO 2 kit DCROSF162.TAR using "setld".
    
>3) Where can I get the patch (its latest version)?
    
    Per the above look in CSC32::PCM$KITS: for everything that you need.
    V1.6-307 has been superceded several times. You will find
    PATCH312.TAR in the above location.

>and one more question, not directly related to this problem:

>4) How can one find out if any ECO-Kits are installed, and which they are?
>   Most README-files to the PCM-patches don't even contain any checksums of
>   their files.
    
    When you run any of the PCM applications they will announce their
    version number. If you are running V1.6-100 then you have V1.6
    with no ECO's installed.
    
    Once you have installed ECO2 and PATCH312.TAR you will be at
    V1.6-312 which is the latest for DUnix.

    Regs,
      Dan

    Hi, Dan,
    
    thank-you for the quick reply. I know copied the files dcrosf162.tar
    and patch312.tar from CSC32::PCM$KITS, but I can't find any
    Installation Instructions for this patches. Aren't there any?
    
    Regards,
    
    Corina

    typemissmatch in .2: know -> now
    

    Use "etld" on the DCROSF162.TAR. Restore the PATCH312.TAR to a
    temporary directory and you should find a README file that will tell
    you what to do.
    
    Regs,
      Dan

    Hi, Dan,
    
    when I do
    # tar xvf patch312.tar
    I get:
    x ./consoled, 548864 bytes, 1072 blocks
    x ./console_ensd, 442368 bytes, 864 blocks
    x ./console, 57344 bytes, 112 blocks
    x ./console_control, 393216 bytes, 768 blocks
    x ./console_conmon, 565248 bytes, 1104 blocks
    x ./console_watch, 393216 bytes, 768 blocks
    x ./console_archive, 425984 bytes, 832 blocks
    x ./console_extract, 409600 bytes, 800 blocks
    x ./console_dialog, 393216 bytes, 768 blocks
    x ./console_verify, 401408 bytes, 784 blocks
    x ./console_editcc, 606208 bytes, 1184 blocks
    x ./console_editm, 720896 bytes, 1408 blocks
    x ./console_eventsingle, 147456 bytes, 288 blocks
    x ./console_eventlist, 794624 bytes, 1552 blocks
    x ./console_status, 155648 bytes, 304 blocks
    x ./console_c3, 1138688 bytes, 2224 blocks
    x ./console_eventlist_en_GB.uid, 114688 bytes, 224 blocks
    x ./console_eventlist_en_US.uid, 114688 bytes, 224 blocks
    x ./console_history_en_GB.uid, 16384 bytes, 32 blocks
    x ./console_history_en_US.uid, 16384 bytes, 32 blocks
    x ./console_startup, 5542 bytes, 11 blocks
    x ./libconsole.a, 1780058 bytes, 3477 blocks
    
    None of this files looks like some README-file to me:
    # file console*
    console:        data
    console_archive:        data
    console_c3:     data
    console_conmon: data
    console_control:        data
    console_dialog: data
    console_editcc: data
    console_editm:  data
    console_ensd:   data
    console_eventlist:      data
    console_eventlist_en_GB.uid:    data
    console_eventlist_en_US.uid:    data
    console_eventsingle:    data
    console_extract:        data
    console_history_en_GB.uid:      data
    console_history_en_US.uid:      data
    console_startup:        /sbin/sh script
    console_status: data
    console_verify: data
    console_watch:  data
    consoled:       data
    # file lib*
    libconsole.a:   archive
    
    So I still have to bother you with the question: where's the README?
    
    Regards,
    
    Corina

    Corina,
      Your right of course. I did not build those kits. Send mail to
    ALEXWS::LASER and ask him to send it to you and me so that I can place
    it in the kit area.
    
    Regards,
       Dan

    Hi, Dan,
    
    I have to bother you again. I didn't get the READMEs from ALEXWS::LASER
    by now. Still waitig for them. But now I have another question. I found
    out that an ECO3-kit exists. I think that's the most recent. But it's
    agian without documentation! (*%&@*%!!%$#*) Now I'm not so sure if I
    should give it to the customer. Can/should/must I install ECO3 upon
    ECO2. Or shoud I give up ECO2 and install directy ECO3 upon PCM
    1.6-100? And then Patch 312? I don't see the relation btw. this kits
    and patches. To the latest versions complete or replace the former
    ones? Can you give me a littel enlightment on this, please?
    
    Best regards,
    
    Corina

>    Hi, Dan,
>    
>    I have to bother you again. I didn't get the READMEs from ALEXWS::LASER
>    by now. Still waitig for them. But now I have another question. I found
>    out that an ECO3-kit exists. I think that's the most recent. But it's
>    agian without documentation! (*%&@*%!!%$#*) Now I'm not so sure if I
>    should give it to the customer. Can/should/must I install ECO3 upon
>    ECO2. Or shoud I give up ECO2 and install directy ECO3 upon PCM
>    1.6-100? And then Patch 312? I don't see the relation btw. this kits
>    and patches. To the latest versions complete or replace the former
>    ones? Can you give me a littel enlightment on this, please?
>    
>    Best regards,
>    
>    Corina
    
    Patch312 is basically ECO4. If you install the DCROSF162.TAR (this is
    ECO 2) and then lay down PATCH312 you will be at what is basically ECO
    4. I say basically ECO 4 as we have a kit that is ECO 4 for OpenVMS but 
    it has not been built yet for DUnix. PATCH312.TAR is functionally
    equivalent to the ECO 4 for OpenVMS.
    
    
    Regs,
       Dan