[an error occurred while processing this directive]

HP OpenVMS Systems

Ask the Wizard
» 

HP OpenVMS Systems

OpenVMS information

» What's new on our site
» Upcoming events
» Configuration and buying assistance
» Send us your comments

HP OpenVMS systems

» OpenVMS software
» Supported Servers
» OpenVMS virtualization
» OpenVMS solutions and partners
» OpenVMS success stories
» OpenVMS service and support
» OpenVMS resources and information
» OpenVMS documentation
» Education and training

Quick Links

» Non-javascript page
» Ask the Wizard
» OpenVMS FAQ

Test Drive OpenVMS

» OpenVMS I64 test drive
» Java test drive

Other information resources available to you include:

» OpenVMS freeware
» ECO kits, software and hardware support, prior version support
» Alpha SRM, ARC, and AlphaBIOS firmware updates
» ENCOMPASS - HP user group
» OpenVMS software downloads, OpenVMS freeware CD-ROM
» OpenVMS firmware locations
» DECconnect passive adaptor charts
» Cables reference guide
» MicroVAX console commands
» OpenVMS student research

Select a topic below to see Questions Frequently Asked by partners

» Using the online documentation library(installing BNU from the asap SDK)
» Global sections(how to create and use.)
» xx$CREATE_BUFOBJ system service(usage)
» Ethernet address(methods of determination)
» Shareable images(cookbook approach to creating one)
» Sharing data/code at absolute addresses(a guide with examples)
» Determining the Alpha microprocessor
» Using GETSYI to get hardware status

Evolving business value

» Business Systems Evolution
» AlphaServer systems transition planning
» Alpha RetainTrust program

Related links

» HP Integrity servers
» HP Alpha systems
» HP storage
» HP software
» HP products and services
» HP solutions
» HP support
disaster proof
HP Integrity server animation
HP Integrity server animation
Content starts here

Ask the Wizard Questions

RMS: File inconsistancy

The Question is:

Question #1:
Using ANALYZE/FDL gives area 0 block size allocation of
18,397,707 blocks, for a file that is currently:
ANH.DAT;1                     File ID:  (11,2,0)
Size:      1854162/1854162    Owner:    [500,500]
Created:  30-JAN-1996 01:39:02.61
Revised:   3-APR-1996 15:17:55.82 (48039)
Expires:   
Backup:    
File organization:  Indexed, Prolog: 3, Using 2 keys
                             In 3 areas
File attributes:    Allocation: 1854162, Extend: 65535, Maximum bucket size: 12
                    Global buffer count: 0, No version limit
                    Contiguous best try
Record format:      Variable length, maximum 2500 bytes
Record attributes:  Carriage return carriage control
RMS attributes:     None
Journaling enabled: None
File protection:    System:RWED, Owner:RWED, Group:RWE, World:RE
Access Cntrl List:  None

We have applied Kit Name: VAXRMS09_U2055 that was supposed
fix this issue, but are still getting the bogus area 0
allocation.

What gives, how can we get the correct information from
analyze?

Question #2:
Also,  is there a way to retrieve the file extend
allocation with a lexical function (f$file_attributes).
What I want is the extend value of the actual file.
I see that this information is stored in the area 0
extension of the fdl.

Question #3:

When using AUTHORIZE, and showing a user record,  the
owner information displays the UIC [xxx,xxx] ([xxx,rightlist_id]).

Is this information stored in the UAF file record? How can I
retrieve it.  I've written a C program that displays most of
the relevant information from a user record, but I can't
seem to find doc on how to get this info from UAF.

Thanks for your assistance, Wiz.


The Answer is:


Hi,	Can you perhaps show me the full ANAL/RMS/FDL output which
	showed 18,397,707 blocks allocted when DIR shows 1854162.

	I'd like to determine whether it is ANAL/RMS having a problem
	displaying the cvalue or perhaps RMS maintaining it.

	The output from DUMP/BLOCK=COUN=4 would help too.

>We have applied Kit Name: VAXRMS09_U2055 that was supposed
>fix this issue, but are still getting the bogus area 0
>allocation.

	I am not aware of an anal/rms fix in there other the total
	data byte count. Hmmm, you would not happen to refer to a
	funky value in an FDL file after an EDIT/FDL/NOINTER run?

> What gives, how can we get the correct information from
> analyze?

	May I ask... why do you think you need the ANAL/RMS output?
	For larger files such as this one, it seems a lot of energy
	to get data that has limited use. For optimization purposes
	I personally prefer to simple use on old anal/fdl output and
	adjust the data record count to the value expected for the
	next incarnation of the file. The anal/rms time is IMHO much
	better spend converting the file! (possibly overdue for the
	file shown!). IN the extreme I use commands like
	$EDIT/FDL/NOINT/ANAL=hand-editted/OUT=tuned standard
	Here standard is a plain FDL describing the file without stats.
	hand-editted would be a file with just the following stats:


IDENT "wizard's minimal template for EDIT/FDL/NOINTERACTIVE analyze input"
FILE;    	    CLUSTER_SIZE            12
ANALYSIS_OF_KEY 0;  MEAN_DATA_LENGTH        123
                    DATA_RECORD_COUNT       1234


    The cluster size would be a happy middle of the road value.
    The record count and mean data length can be obtained using ANAL/RMS on
    am older (backup copy of the) data file but why bother getting it all
    the time? the convert /stat output also gives a useful record count!.


Question #2:
Also,  is there a way to retrieve the file extend
allocation with a lexical function (f$file_attributes).
What I want is the extend value of the actual file.
I see that this information is stored in the area 0
extension of the fdl.

	There is no single file extend quantity! each of the (3) areas
	has its own. F$FILE(filename,"DEQ") may provide what you need.

>
>Question #3:
>When using AUTHORIZE, and showing a user record,  the
>owner information displays the UIC [xxx,xxx] ([xxx,rightlist_id]).
>Is this information stored in the UAF file record? How can I

What? the numbers or the text? You've tried SYS$GETUAI already right?
or are you using SYS$GETJPI? You may need to add a call to SYS$IDTOASC ?!