RTP Series - RTP57
File Variables
Reader's Clinic - Volume Pointer Record
REVMEDIA Revisted
Utility Diskette # 4
QTIPS - DOS File Names
DOS Interfacing (Part II)
VERBatim - V116
@ATTACK - @Pri.File
@ATTACK - @Rollout.File
File Variables
How Indexes Are Updated
Index Record Layouts
QTIPS - File Variable of File In SELECT Statement
QTIPS - Amending non-Attached Files
LINEAR HASH FILE STRUCTURES - Part 1
Index Flush
QTIPS - File Handle Structure
Reader's Clinic - Volume Pointer Record
RTP Series - RTP17
QTIPS - PERFORM Arguments and FMT Specifications
What's New (and un(der)documented!) In 2.12
RTP Series - RTP27
QTIPS - Printing Large Variables from the Debugger
VERBatim - V87
@ATTACK - @HW
Reader's Clinic - Volume Pointer Record
REVMEDIA Revisted
File Variables
LINEAR HASH FILE STRUCTURES - Part 1
QTIPS - File Handle Structure
QTIPS - Using @Upper.Case and @Lower.Case with Foreign Languages
@ATTACK - @Lower.Case
@ATTACK - @Upper.Case
Sorting out Collation Sequences by Mike Pope
REVMEDIA Revisted
SecureUser
VERBatim - V25
@ATTACK - @Files.System
Advanced Revelation Initialisation Sequence (Overview) by Mike Pope
REVMEDIA Revisted
Playing with Scan Codes
QTIPS - Compiling Protection Code
QTIPS - Invalid Code and Command
QTIPS - Code/Command Help
Compiling 64K on a Shoestring by Blaise Wrenn (LexStat Systems Ltd)
Reader's Clinic - Page Marks in Windows
Capture Playback and Convert.Keystrokes
@ATTACK - @SVM
Utility Diskette # 4
Version 3 Technical Highlights - Customising NewApplication Creation
File Variables
Argument passing - Subroutines and Functions - Mike Pope
RevTech Replies - Mike Pope (RevTech UK Ltd)
Symbol Table Structure
@ATTACK - @Modal
RTP Series - RTP49
Reader's Clinic - Volume Pointer Record
RTP Series - RTP49
VERBatim - V18
QTIPS - Amending non-Attached Files
Set_Attach_Sub and Attach images
Reader's Clinic - Functions and Subroutines
Argument passing - Subroutines and Functions - Mike Pope
Utility Diskette # 4
Utility Diskette # 3 - Part I
Utility Diskette # 3 - Part II

RevMedia FKB

DocumentV2I8A1
TitleReader's Clinic - Volume Pointer Record
KeywordsVOLUME
W559
POINTER
RTP49
MFS
BFS
TextA reader writes "I've been USING the tips FROM the December issue of
REVMEDIA on creating Volume file VARIABLES and I keep getting a W559 error
message"

ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ Cannot continue ³
³ An attempt was made to execute a null ("") program ³
³ Press any key to contine ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ

This problem occurs when the Volume pointer in Voc is modified to establish
Volume MFSs (It is possible to have an MFS apply to every file on a volume
by inserting the MFS name before the BFS name (@VM delimited) in the Volume
pointer ) When this happens the structure of the volume file variable
changes slightly In this case the @VMs in the Filing System list must be
converted to @SVMs Thus the code given on page 11 of issue 7 would be
modified to be

FS = VOL_REC<4>
DOS = VOL_REC<5>
CONVERT @VM TO @SVM IN FS
FILE_VAR = FS : @VM : DOS

Alternatively if the Volume has not been attached another way of getting
all of the information required to create a volume file variable is to make
a DIRECT call to RTP49 (the routine used by the V18 ATTACH processor) This
is a subroutine taking four parameters (A B C D) where A is the volume
name B is a flag (set to 0) C is the Volume Record returned and D is the
Volume Pointer Record returned C has five fields the fifth of which is the
Map file variable D has three fields the second of which is the FS list
Thus

CALL RTP49(A B C D)
DOS = C<5>
FS = D<2>
CONVERT @VM TO @SVM IN FS
FILE_VAR = FS : @VM : DOS


(Volume 2 Issue 8 Page 3)
[revmedia/copyrigh.htm]

Page last modified: 30/01/03