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

Conference csc32::consolemanager

Title:POLYCENTER Console Manager
Notice:Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:CSC32::BUTTERWORTH
Created:Thu Aug 06 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1541
Total number of notes:6564

871.0. "OPENVMS VAX 6.2 - Configuration file will not verify" by CSC32::BUTTERWORTH (Gun Control is a steady hand.) Mon Jul 17 1995 23:59

    Phil and Simon,
      It looks like fixed this for 1.6 but just in case anyone upgrades a
    PCM engine to OpenVMS VAX 6.2 and runs into it:
    
    The configuration will fail to verify on OpenVMS VAX 6.2 because it
    appears the DEC C RTL "stat" function is broken. This routine is
    called to verify the existence of the action routine command files
    and executables. In PCM 1.5 the rotuine was given a string with the
    filename extension wildcarded. For example, the Mail command specifies
    a command name of console$mail so the config editor calls "stat" to look
    for console$actions:console$mail.*. In OpenVMS VAX 6.2 the call returns
    a value of -1 which means the file was not found. PCM 1.6 is coded to
    look for files with both a .COM and .EXE extension so it works fine.
    The workaround for PCM 1.5 is to update the action routine records to
    use the correct file extension i.e, change the mail action so that
    the command field reads CONSOLE$MAIL.COM.
    
    Regards,
       Dan
T.RTitleUserPersonal
Name
DateLines
871.1OPG::PHILIPAnd through the square window...Tue Jul 18 1995 10:579
Dan,

  Yes, I specifically put the fix in, apparently pre-V6.2 of OpenVMS,
  the stat() function accepted wildcards. In order to make the stat
  function more like its UNIX equivalent, the C RTL folks changed its
  behaviour, hence our problem.

Cheers,
Phil
871.2CSC32::BUTTERWORTHGun Control is a steady hand.Tue Jul 18 1995 19:3411
    >In order to make the stat function more like its UNIX equivalent, the 
    >C RTL folks changed its behaviour, hence our problem.
    
    And why didn't they check with us before they made this change? We
    never said we wanted VMS to act like the U-word! ;-}
    
    What I do find rather amusing is that the VAX C RTL still accepts the
    wildcard.
    
    REgs,
      Dan