Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

VMS 7.3-2 RMS V0300 Patch I need matching fix for Itanium 8.3

 
SOLVED
Go to solution
Liz Ball
Occasional Visitor

VMS 7.3-2 RMS V0300 Patch I need matching fix for Itanium 8.3

In RMS-V0300 there was patch to the EDF which corrected problems with the EDIT/FDL/ANALYSIS/NOINTERACTIVE causing problems when the file was then converted. I have applied this to our Alpha servers and issue corrected.

However I have the same issue on an Itanium running VMS 8.3, anyone know of a patch which contains this fix?

Thanks
9 REPLIES 9
Karl Rohwedder
Honored Contributor

Re: VMS 7.3-2 RMS V0300 Patch I need matching fix for Itanium 8.3

Liz,

the RMS V4.0 patch contains some hints to EDF, see here:
ftp://ftp.itrc.hp.com/openvms_patches/i64/V8.3/VMS83I_RMS-V0400.txt
The patch can be found there too.

regards Kalle
Liz Ball
Occasional Visitor

Re: VMS 7.3-2 RMS V0300 Patch I need matching fix for Itanium 8.3

Thanks I did see that but it didn't mention the specific issue so I haven't tried it but I will probably take a chance and do so.
Hein van den Heuvel
Honored Contributor

Re: VMS 7.3-2 RMS V0300 Patch I need matching fix for Itanium 8.3

That patch kit is from 2002.
Surely any correction to EDF is rolled into OpenVMS 8.3, not that is mentions any:

http://ftp.support.compaq.com.au/patches/public/vms/axp/v7.2-2/dec-axpvms-vms722_rms-v0300--4.README

Did you actually experience a problem on IPF 8.3 or just preparing?

>> EDIT/FDL/ANALYSIS/NOINTERACTIVE

The analysis switch needs a file, but you probably have that.

>> causing problems

Please elaborate, such that future reader can judge whether they have the same problem or now.
- specific errors messages?
- do you know what is broken in the output FDL when it is broken?
- always a problem for certain input FDL's?
- What _seems_ to be the trigger?

Hope this helps some,
Hein van den Heuvel (at gmail dot com)
HvdH Performance Consulting
Liz Ball
Occasional Visitor

Re: VMS 7.3-2 RMS V0300 Patch I need matching fix for Itanium 8.3

Hi,

On Alpha VMS we got the following issue through our application.
"Run-time error '-2147467259 (80004005)':

The UNIFACE operation invocation failed with return code -17, status 0 and activate error code 0: UNIFACE error -17, described as "NETERR_PIPE_BROKEN: Server is gone".

When the RMS file was converted with a known correct FDL the cluster size was amended and all was fine again.
This only seemed to occur for files around the 600,000 block size, the analysis was forcing the convert to change the cluster size.

We currently have the same issue on an Itanium but the error message is slightly different as it is using Uniface 8 rather than Uniface 7.
%CXXL-F-TERMINATE, terminate() or unexpected() called
Uniface error - 150. This is defined as "A hardware or software error occurred. Contact your Uniface representative

When I disable the edit/fdl/analysis on the overnight optimise routine then the file remains readable.

Hope this makes sense - new to this.
Hein van den Heuvel
Honored Contributor

Re: VMS 7.3-2 RMS V0300 Patch I need matching fix for Itanium 8.3

>> On Alpha VMS we got the following issue through our application.
"Run-time error '-2147467259 (80004005)':

That was on the Alpha.
Did you ever get that EXACT same issue under Itanium 8.3? I suspect not, but your message suggests it does.

>> The UNIFACE operation invocation failed with return code -17, status 0 and activate error code 0: UNIFACE error -17, described as "NETERR_PIPE_BROKEN: Server is gone".

So that was a secondary error.
Supposedly the server, before going, stumbled into an RMS error and hopefully reported that in a log file. Go hunt!

>> When the RMS file was converted with a known correct FDL the cluster size was amended and all was fine again.

That makes sense and yet it does not.
Here is why.

The CLUSTER size line is IGNORED on the actual convert... (as long as it is syntactically correct).
For the Convert the BUCKET size is all that matters.

The cluster size IS used by EDIT/FDL/NOINT in combination with the input file size (through the line DATA_RECORD_COUNT) to determining that BUCKET size.

There have been issues with a large cluster size tricking EDF (EDIT/FDL) into generating a large (63) bblock bucket size.
That itself _should_ be transparent to the application, but may cause memory usage issues.

>> This only seemed to occur for files around the 600,000 block size, the analysis was forcing the convert to change the cluster size.

Bad/imprecise wording, but that's ok.

>> We currently have the same issue on an Itanium but the error message is slightly different as it is using Uniface 8 rather than Uniface 7.
%CXXL-F-TERMINATE, terminate() or unexpected() called
Uniface error - 150. This is defined as "A hardware or software error occurred. Contact your Uniface representative

>> When I disable the edit/fdl/analysis on the overnight optimise routine then the file remains readable.

- Does the EDIT/FDL and subsequent CONVERT actually work? Check that log

>> Hope this makes sense - new to this.

Close enough, but lacking detail like the difference between a working and failing FDL. I would still be interested in seeing that. Send me an Email if you prefer.

Also, overnight 'optimises' are all to often poorly implements and more often than not a waste of a (little) time and an increase (proven here) in risk.
Specifically, it is probably using an ANALYZE/RMS which can be avoided.

Supposedly this application has been running for years. So by now it shoudl know what an optimal FDL is, and leave that in place. Reduce the overnight optimize to do just the CONVERT providing a knwon to be tuned and known to be working FDL.

Hope this helps some,
Hein van den Heuvel (at gmail dot com)
HvdH Performance Consulting