#OpenVMS

0 Followers · 17 Posts

OpenVMS is a computer operating system for use in general-purpose computing. It is the successor to the VMS Operating System (VAX-11/VMS, VAX/VMS), that was produced by Digital Equipment Corporation, and first released in 1977 for its series of VAX-11 minicomputers

Official site.

Question Paul Coviello · Jan 5, 2021

I'm just clarifying that 2017.1 is viable on 8.4-1H1. can someone please confirm, also what kind of support would we receive if we upgraded to 8.4-2L1?  I know that 2015.2 works on it. yet it says it's not supported. 

we really need to get to 8.4-2L1.  any help would greatly be appreciated.

thanks

Paul

10
0 524
Question Paras Batheja · Oct 13, 2020

Hi team

We are migrating the Code set of VMS to Unix. 
In this process we are also taking care of all I/O operations of file. 
In VMS, whenever we create a file, it generates a Version # associated with the file. Best part is we have a common library which we use to OPEN/USE/CLOSE/DELETE/RENAME/COPY the file.
Now, when we talk about VMS on cache, if we two processes creates a file "ABC.TXT", for 1st process it will create the version #1 and for second it will create #2.
This versioning cache handles internally, like which cache process is referring to #1 and which one for #2

4
0 524
Question Paul Coviello · Jun 22, 2020

Hi  I'm trying to setup STUNNEL between my pc and the cache database on the server,  I'm trying to define port 1972 on my pc with out any luck.

has anyone done this?

thanks 

Paul

11
0 521
Question Richard Rayburn · Jul 11, 2019

All,

I'm using Cache 2014.1 in an openVMS environment.

If I have multiple RMS files to clean up, for example.

!DIR MEMBER_EXTRACT.*;*

MEMBER_EXTRACT.CSV;2                    MEMBER_EXTRACT.CSV;1
MEMBER_EXTRACT.PROC;1                   MEMBER_EXTRACT.TXT;3
MEMBER_EXTRACT.TXT;2                    MEMBER_EXTRACT.TXT;1

S FILE="MEMBER_EXTRACT.*;*"

Do ##class(%Library.File).ComplexDelete(FILE)

!DIR MEMBER_EXTRACT.*;*
 
MEMBER_EXTRACT.CSV;1                    MEMBER_EXTRACT.TXT;2
MEMBER_EXTRACT.TXT;1
 
Total of 3 files.

4
0 575
Question Alex Van Schoyck · Jan 30, 2019

Problem

I'm working on exporting data from an Intersystems Cache database through the Cache ODBC Driver. There is a particular table that is giving me an error message. The ODBC Driver crashes and reports an error from the Cache system. I think I was able to trace down where the error is coming from, but I do not know how to debug or fix the error.

The table I am trying to extract is called SEDMIHP.

Here's the Error:

[Cache Error: <<UNDEFINED>%0AmBd16^%sqlcq.PRD.3284 ^SEDMIHP(4,77)>]
[Location: <ServerLoop - Query Fetch>]

Research/Trial & Error

2
0 1659
Question Mack Altman · Mar 19, 2018

Currently, we are running 2014.1 on two different servers (OpenVMS, RHEL). The plan is to transition from OpenVMS to RHEL, but our Write Daemon is in a Troubled state on both servers.

On the OpenVMS server, we have a WIJ file that's 26G and can grow to 40G (size of database cache). Since it hasn't grown to 40G, we don't believe the size of the WIJ file to be the issue.

What else should we be looking at regarding the performance of the Write Daemon?

1
0 1019
InterSystems Official Andreas Dieckow · Feb 27, 2018

As previously announced, 2017.1 on VSI OpenVMS 8.4-1H1 is the final major version of Caché and Ensemble.  2017.1 will not be available for VSI OpenVMS versions beyond 8.4-1H1.

Maintenance releases of 2017.1 on VSI OpenVMS may be announced but only to deliver critical corrections.  2017.1 on VSI OpenVMS will be the Minimum Supported Version from July 1, 2019 through December 31, 2020.  After December 31, 2020, no further maintenance releases will be made available.  

0
0 758
Question Mack Altman · Oct 11, 2017

We will be transitioning from a server running HP OpenVMS to one running RHEL 7. The main question some of the team had was what would be the best method for moving the globals to the new system.

Also, I was wondering if any others have transitioned from OpenVMS to RHEL. If so, were there any kinks that we should be aware of prior to transition?

2
0 982
InterSystems Official Andreas Dieckow · Aug 21, 2017
Project related quality assurance efforts have revealed a number of concerns for the current release of 2017.1.0 and 2017.1.1 on all OpenVMS platforms. In certain situations, the impact can be severe. InterSystems will address these issues with the upcoming 2017.1.2 release, and in the meantime, will remove all 2017.1.x kits for OpenVMS from our Download Servers.
 
If you have immediate needs correcting existing deployments of this version, please contact the InterSystems WRC (support@intersystems.com).
 
0
0 716
InterSystems Official Andreas Dieckow · Apr 27, 2017

The last version of Caché, Ensemble released for VSI OpenVMS is 2017.1. Unlike HP OpenVMS (Alpha and Itanium), VSI OpenVMS on Itanium continues to be supported. This means that critical corrections or changes required to support customer’s hardware purchases will all be based on 2017.1 or earlier versions.

Related announcement: https://community.intersystems.com/post/platform-compatibility-hp-open-…

0
0 959
Question Mack Altman · Jan 6, 2017

Currently, we have an application running in one namespace ("Database B") that has globals and routines mapped to another database ("Database A"). After enforcing clean up on Database A, we found that 90% of the disk is free. We would like to compact Database A and release the unused space. However, we are running OpenVMS, which seems to be the issue.

For databases consisting of only globals, we are able to use ^GBLOCKCOPY; however, we need to ensure that the routines and mappings are also copied.

What would be the best recommended way to do this?

8
0 1218
InterSystems Official Andreas Dieckow · Dec 7, 2016
Post has been edited for clarification: Both HP Open VMS versions (for Itanium and for Alpha)  are discontinued for future InterSystems releases.
 
Future product releases, beginning with the next major release after 2017.1, will no longer be offered for the following platforms:
 
HP OpenVMS  for Itanium
HP OpenVMS  for Alpha
 
Products: Caché, Ensemble
 
Expected Availability: next major release after 2017.1
1
0 1195
Question John Murray · Jan 30, 2017

Per the information at http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY… I am trying to use a call to $ZF("GETFILE") to obtain information about an OpenVMS file. But I get an <ILLEGAL VALUE> error.

For example:

w $zf("GETFILE",filename,"UIC")

reports:

<ILLEGAL VALUE>

My filename variable contains the full path and name of a file that I own. I hold the %All role in Cache.

This is 2012.1.5 on OpenVMS/IA64  V8.4

Any ideas what's going wrong?

4
0 556
Question Mack Altman · Jan 21, 2017

Can someone direct me to where in the documentation we can find how consumption may be calculated for global storage?

Caché Version 2010.1
Operating System HP OpenVMS 8.4

EDIT: After receiving some responses, it seems I was unclear in my initial inquiry. I am looking to determine our rate of consumption of storage; however, I am having some difficulty in doing that.

While utilizing ^%GSIZE, which is used by the %GlobalEdit class, the results appeared odd. I have provided my results below, which illustrate the global structure on the left and the usage indicated by ^%GSIZE on the right.

6
0 872
Question Bryan Cass · Jan 16, 2017

I realize that Cache Studio is the standard method to edit routines.  However, some clients make it difficult to access their server that supports Studio.  Is there an editor that can be run from the programmer prompt that allows simple WYSIWYG editing of routines?  I know there is a %Routine class that you can use to do command-line editing, but I am looking for a full screen editor.

What was the standard in OpenVMS Cache before there was Cache Studio?

Thanks!
Bryan

7
0 1607
InterSystems Official RB Omo · Aug 24, 2016

August 24, 2016 – Alert: Database Compaction

This is an addendum to the Alert published on October 14, 2015 – Alert: Database Defragmentation.

That alert indicated that the database defragmentation utility in 2014.1 and higher, on all platforms except OpenVMS, could cause database degradation and the correction JO2871 is available to clients upon request and would be included in future releases.  The correction was included in 2015.1.3, 2015.2.2 and 2016.1.

0
0 599