Problem with overwriting subfile on another Vax node

[Joe Boyle]

How about if you remap the complete subfile spec as below; it might be worth
testing at both process and job logical levels, you may even need to add the
user /password qualifiers,

 

Define INC-RUNS2 RPY_DATA YAK::DKA100:[RPY.WKP.DATA] INC-RUNS2

 

 

  _____  

From: Martijn Nabben (Fairfax) [mailto:Martijn.Nabben at fairfaxmedia.co.nz] 
Sent: 23 May 2007 00:34
To: 'Joe Boyle'; powerh-l at lists.sowder.com
Subject: RE: Problem with overwriting subfile on another Vax node

 

Thanks Joe,

 

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.

You're correct in saying, that date/time stamping would not be necessary.

 

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.

 

Thanks,

Martijn

-----Original Message-----
From: Joe Boyle [mailto:atla38 at dsl.pipex.com] 
Sent: Wednesday, 23 May 2007 11:02 a.m.
To: 'Martijn Nabben (Fairfax)'; powerh-l at lists.sowder.com
Subject: RE: Problem with overwriting subfile on another Vax node

A work around might be to simply run a dcl command like ' delete
RPY_DATA:INC-RUNS2*.*;*' as part of the script.

 

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.

 


  _____  


From: powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com
[mailto:powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com] On Behalf Of
Martijn Nabben (Fairfax)
Sent: 22 May 2007 23:21
To: 'powerh-l at lists.sowder.com'
Subject: Problem with overwriting subfile on another Vax node

 

We are in the process of migrating a variety of systems from Vax to Alpha.

The plan is to do a serial migration of one system after another.

There are online interfaces between these systems, where a program from the
first system reads and writes subfiles in another system's data directory.

 

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:

define RPY_DATA YAK::DKA100:[RPY.WKP.DATA]

 

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:

 

> set subfile name rpy_data:inc-runs2 keep at emp-id
> go
*W* The permanent subfile RPY_DATA:INC-RUNS2 will be cleared.
*W* Data access error. (RPY_DATA:INC-RUNS2)
%RMS-F-FTM, network file transfer mode precludes operation (SQO set)

Our Vax Systems guy has checked all necessary access/privilege settings, but
they all seem to be alright.

 

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.

 

Alpha: OpenVMS V7.3-2 

Vax: OpenVMS V7.3

PowerHouse: 7.10G1

 

Thanks,

Martijn Nabben

Fairfax Media, Wellington, New Zealand

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sowder.com/pipermail/powerh-l/attachments/20070523/09e7c38f/attachment.html