<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:st1 =
"urn:schemas-microsoft-com:office:smarttags"><HEAD><TITLE>Message</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.3790.4026" name=GENERATOR><!--[if !mso]>
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType name="country-region"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="City"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="place"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><!--[if !mso]>
<STYLE>st1\:* {
BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Fixedsys;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 72.0pt 90.0pt 72.0pt 90.0pt; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
FONT-WEIGHT: normal; COLOR: blue; FONT-STYLE: normal; FONT-FAMILY: Arial; TEXT-DECORATION: none; mso-style-type: personal-reply
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-GB vLink=purple link=blue>
<DIV dir=ltr align=left>
<DIV dir=ltr align=left><SPAN class=415385106-23052007><FONT face=Arial
color=#0000ff size=2>This might have to do with differences in the way Quiz and
QTP do their filehandling.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=415385106-23052007><FONT face=Arial
color=#0000ff size=2>It could have to do with file/record locking, see the
excerpt from the RMS manual below.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=415385106-23052007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=415385106-23052007><FONT face=Arial
color=#0000ff size=2>Mark</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN
class=415385106-23052007><!--StartFragment -->
<H4>FAB$V_SQO</H4><STRONG>Local File Accesses</STRONG>
<P>Sequential only; indicates that the file can be processed only in a
sequential manner, permitting certain processing optimizations. Any attempt to
perform random access results in an error. This option is restricted to
sequential files and is ignored for all other file organizations. The FAB$V_SQO
option is input to the Create and Open services. </P>
<P><STRONG>Remote DECnet Accesses</STRONG> </P>
<P>For OpenVMS DECnet operations, this option has an added meaning. When set for
a remote file access, it indicates that file transfer mode (FTM) should be used
for Get, Put, Read, and Write services. File transfer mode is a Data Access
Protocol (DAP) feature that allows several records to be transferred in a
single-network I/O operation to maximize throughput for sequential access file
transfers. </P>
<P>While the file transfer mode (FTM) feature for the SQO option is applied
regardless of file organization to remote accesses, FTM has restrictions to make
it consistent with the sequential only meaning applied to local accesses. For a
remote file access, FTM is restricted to sequential access; if FTM is requested
(FAB$V_SQO option set), a keyed or RFA record access will fail with an RMS-F-FTM
error (network file transfer mode precludes operation (SQO set)). For record
I/O, FTM is also restricted to Gets or Puts; Updates or Deletes, if attempted,
will fail with the RMS-F-FTM error. </P>
<P>The transmitting of records as a block of data, of course, results in
performance improvement; what is not as obvious is that some of the improvement
is due to the fact that the Data Access Protocol (DAP) eliminates much of its
messaging for the FTM feature. Messages are not sent between the local and
remote systems on a record-by-record basis but rather for the whole block of
records transferred. This can result in apparent inconsistencies in what a
reader sees when FTM is used. </P>
<P>While the RMS default locking behavior does not change when FTM is used, by
the time the record is in your buffer on the local system, the record may have
already been updated or deleted by another process that is not using FTM. If a
locking collision happens on the remote system when the records are being loaded
into the message buffer, then the locking error will not be returned until the
end of the transfer. When using the file transfer mode (SQO) feature with shared
write access to a remote file, you should expect to see the same kind of
inconsistencies in reading data as you see when the read-regardless (RRL) option
is set. To avoid the possibility of a hang that may be induced by retrying
remote accesses after a record lock error, you are advised to set both the
no-lock (NLK) and read-regardless (RRL) options in the RAB$L_ROP in applications
that use the file transfer mode (SQO) feature for remote file accesses. (The no
query locking (NQL) option is not supported by the DAP protocol for remote
files.) </P>
<P>This option corresponds to the FDL attribute FILE
SEQUENTIAL_ONLY.</P></SPAN></DIV></DIV><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B>
powerh-l-bounces+mark.debruin=tno.nl@lists.sowder.com
[mailto:powerh-l-bounces+mark.debruin=tno.nl@lists.sowder.com] <B>On Behalf Of
</B>Martijn Nabben (Fairfax)<BR><B>Sent:</B> Wednesday, May 23, 2007
01:53<BR><B>To:</B> powerh-l@lists.sowder.com<BR><B>Subject:</B> UPD RE:
Problem with overwriting subfile on another Vax node<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=533095123-22052007>It
appears, that this problem only occurs with Quiz, not QTP.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=533095123-22052007>QTP
overwrites the subfile perfectly fine.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=533095123-22052007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=533095123-22052007>Thanks,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=533095123-22052007>Martijn</SPAN></FONT></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B>
powerh-l-bounces+martijn.nabben=fairfaxnz.co.nz@lists.sowder.com
[mailto:powerh-l-bounces+martijn.nabben=fairfaxnz.co.nz@lists.sowder.com]
<B>On Behalf Of </B>Martijn Nabben (Fairfax)<BR><B>Sent:</B> Wednesday, 23
May 2007 11:34 a.m.<BR><B>To:</B> 'Joe Boyle';
powerh-l@lists.sowder.com<BR><B>Subject:</B> RE: Problem with overwriting
subfile on another Vax node<BR><BR></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=226000523-22052007>Thanks Joe,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=226000523-22052007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=226000523-22052007>That is indeed a work-around we had considered, but
it involves quite a few script changes - not to mention testing and change
control. We are aiming to simply redefine the logical without any software
changes.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=226000523-22052007>You're correct in saying, that date/time stamping
would not be necessary.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=226000523-22052007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=226000523-22052007>If
the PH List is unable to resolve the issue, we will have to go down the path
of deleting the subfile prior to creating it.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=226000523-22052007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=226000523-22052007>Thanks,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=226000523-22052007>Martijn</SPAN></FONT></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Joe Boyle
[mailto:atla38@dsl.pipex.com] <BR><B>Sent:</B> Wednesday, 23 May 2007
11:02 a.m.<BR><B>To:</B> 'Martijn Nabben (Fairfax)';
powerh-l@lists.sowder.com<BR><B>Subject:</B> RE: Problem with overwriting
subfile on another Vax node<BR><BR></FONT></DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial color=blue size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: blue; FONT-FAMILY: Arial">A work around
might be to simply run a dcl command like ' delete
RPY_DATA:INC-RUNS2*.*;*' as part of the
script.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=blue size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: blue; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=blue size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: blue; FONT-FAMILY: Arial">You can always
date and time stamp the subfile creation name if many processes can be
running against the same subfile at the same time - but this doesn't seem
likely from your description.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=blue size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: blue; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><FONT
face="Times New Roman" size=3><SPAN lang=EN-US style="FONT-SIZE: 12pt">
<HR tabIndex=-1 align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=MsoNormal><B><FONT face=Tahoma size=2><SPAN lang=EN-US
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT
face=Tahoma size=2><SPAN lang=EN-US
style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">
powerh-l-bounces+atla38=dsl.pipex.com@lists.sowder.com
[mailto:powerh-l-bounces+atla38=dsl.pipex.com@lists.sowder.com] <B><SPAN
style="FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Martijn Nabben
(<st1:City w:st="on"><st1:place
w:st="on">Fairfax</st1:place></st1:City>)<BR><B><SPAN
style="FONT-WEIGHT: bold">Sent:</SPAN></B> 22 May 2007 23:21<BR><B><SPAN
style="FONT-WEIGHT: bold">To:</SPAN></B>
'powerh-l@lists.sowder.com'<BR><B><SPAN
style="FONT-WEIGHT: bold">Subject:</SPAN></B> Problem with overwriting
subfile on another Vax node</SPAN></FONT><SPAN
lang=EN-US><o:p></o:p></SPAN></P></DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">We are in the process of
migrating a variety of systems from Vax to
Alpha.</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">The plan is to do a serial
migration of one system after another.</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">There are online interfaces
between these systems, where a program from the first system reads and
writes subfiles in another system's data
directory.</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">In order to maintain this
functionality we are currently trying to redefine the logicals to point to
the data directory on the other node. In other words defining logicals on
the Alpha that point to a data directory on the
Vax:</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><FONT face=Fixedsys size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Fixedsys">define RPY_DATA
YAK::DKA100:[RPY.WKP.DATA]</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">For reading subfiles and
writing brand new subfiles this seems to be working fine, but when
overwriting an existing subfile (using Quiz for instance), the
following error occurs:</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face=Fixedsys size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Fixedsys">> set subfile name
rpy_data:inc-runs2 keep at emp-id<BR>> go<BR>*W* The permanent subfile
RPY_DATA:INC-RUNS2 will be cleared.<BR><FONT color=red><SPAN
style="COLOR: red">*W* Data access error.
(RPY_DATA:INC-RUNS2)<BR>%RMS-F-FTM, network file transfer mode precludes
operation (SQO set)</SPAN></FONT></SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Our Vax Systems guy has
checked all necessary access/privilege settings, but they all seem to be
alright.</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Does this ring a bell with
anybody? Please let me know if you need more detailed info, that I haven't
considered as important at this stage.</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Alpha: OpenVMS V7.3-2
<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<DIV>
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Vax: OpenVMS
V7.3<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">PowerHouse:
7.10G1<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Thanks,<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Martijn
Nabben<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><st1:City w:st="on"><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Fairfax</SPAN></FONT></st1:City><FONT
face=Arial size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">
Media, <st1:place w:st="on"><st1:City w:st="on">Wellington</st1:City>,
<st1:country-region w:st="on">New
Zealand</st1:country-region></st1:place><o:p></o:p></SPAN></FONT></P></DIV></DIV></DIV></DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
<BR>
This e-mail and its contents are subject to the DISCLAIMER at http://www.tno.nl/disclaimer/email.html<BR>
</BODY></HTML>