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

Conference vaxaxp::vmsnotes

Title:	VAX and Alpha VMS
Notice:	This is a new VMSnotes, please read note 2.1
Moderator:	VAXAXP::BERNARDO

Created:	Wed Jan 22 1997
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	703
Total number of notes:	3722

164.0. "F$IDENTIFIER mechanism ?" by PADKOA::COSTEUX (Le Plat Pays qui est le mien...) Mon Feb 10 1997 06:04

    Can somebody explain how works the F$IDENTIFIER lexical founction ?
    In a cluster a customer has changed a VAX system with an Alpha Server
    and the users disks have been 'transfered' from HSC disks to HSD50
    disks. Whereas during this operation (whereas the SYSUAF and RIGHTLIST
    were the same) the F$IDENTIFIER results were differents than the ones
    obtained before and after the 'migration' operation. 
    Before and after this 'migration' the F$IDENTIFIER results are the same
    now.
    Is the result of the F$IDENTIFIER also hardware dependant or is there
    other parameters (other than the UIC) which are taken in count to give
    the result ?
    
    Thanks in advance for any comment.
    
    Jean-Pierre

T.R	Title	User	Personal Name	Date	Lines
164.1	Problem During Conversion	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Mon Feb 10 1997 09:37`	13
	f$identifier is not platform-dependent; it's a lexical wrapper around the sys$idtoasc and sys$asctoid system service ID conversion routines. I'd look for a RIGHTSLIST logical name in the wrong mode or otherwise mis-defined, or for multiple RIGHTSLIST files. There can be (are typically) identifiers around that match the UIC group and UIC member, as well as various other sorts of identifiers. Since things are `back to normal', determining `what went wrong' will be somewhat of a problem.
164.2		AUSS::GARSON	DECcharity Program Office	`Mon Feb 10 1997 19:20`	8
	re .0 I am not clear on exactly what occurred and what you think is wrong. One thing to watch out for is that if you just copy around SYSUAF and RIGHTSLIST you have to make sure that every process that has one or both open gets the latest version. The easiest way to ensure this is to reboot.