topic Re: %dcl-e-open in Operating System - OpenVMS

%dcl-e-open

nuno vitoria_1 — Mon, 06 Oct 2008 13:13:39 GMT

i have this error:

%DCL-E-OPENOUT, error opening BG_DIGI:[LOGIN] LAST_SETUP_DIGI.COM; as output
-RMS-E-WLK, device currently locked

INTERnet ACP AUXS failure status=%RMS-E-WLK

Re: %dcl-e-open

marsh_1 — Mon, 06 Oct 2008 13:41:58 GMT

Hi nuno,

it would be helpful if you could provide some more info, e.g operating system version,architecture, what it is you are doing when you get this error, is this new behaviour and if so what else has changed ?

Re: %dcl-e-open

Joseph Huber_1 — Mon, 06 Oct 2008 13:58:16 GMT

RMS-E-WLK: somebody tries to write to a read-only device, defined through the logical name BG_INI .

Internet AUXS indicates the process trying to write to the file is started as a TCPIP service.

Since BG_DIGI is not a base VMS name, if You don't know to which application-package it belongs, do a
TCPIP SHOW SERVICE
to see if one of the services refers to this name.

Re: %dcl-e-open

Hein van den Heuvel — Mon, 06 Oct 2008 14:24:33 GMT

What is being attempted when this error occurs? Did it ever work?

To investigate, start with: $HELP/MESS WLK.
It reads: "The hardware device specified for an RMS file system operation is write-locked for protection, and write access is attempted."

That device pretty much has to be whatever is pointed to by "BG_DIGI".
So do a: SHOW LOG BG_DIGI
As well as: $SHOW DEVICE BG_DIGI

Are you running something from a CD?

Cheers,
Hein.

Re: %dcl-e-open

Hoff — Mon, 06 Oct 2008 14:29:42 GMT

You can either debug the DCL command procedure involved here, or pass along a problem report to the individual or organization that is maintaining this DCL command procedure on your behalf.

If you're maintaining this DCL command procedure, enable verification (eg: $ SET VERIFY) or otherwise insert some debugging statements (eg: $ WRITE SYS$OUTPUT "debug message") or such.

In this case, it looks that the DCL command OPEN has failed here; that there is either some faulty prolog code, a change that has adversely effected the OPEN command, or a faulty OPEN command. Or there could be a system-level issue arising here, and one that could easily involve some sort of a configuration issue or hardware error; something that has locked a disk.

If you have a support contract, use it. If you don't have a support contract, call in a specialist and/or get a support contract. That, or you're going to be learning rather more about how to support OpenVMS and the hardware and the software involved here. (See above.)

Re: %dcl-e-open

Jess Goodman — Mon, 06 Oct 2008 14:33:57 GMT

To get some more details about the error, do
$ SHOW DEVICE/FULL BG_DIGI:

If, as would seem likely, the device physical name starts with BG then it is an IP socket. Depending on what TCP/IP stack you are using and what VMS version you are runnning (hint: tell us these things), you can get socket details with the command:

$ UCX SHOW DEVICE /FULL BGn

where BGn is the socket's physical device name that was output with the first command.

Re: %dcl-e-open

Richard J Maher — Mon, 06 Oct 2008 21:45:37 GMT

Hi,

Did this DCL used to work and has just stopped working? Has the open statement changed?

What does

$ucx show dev bg_digi/full

display?

I have attached an INETd (Auxillary Server) example which is probably of little use to you as it uses the $assign service from a 3GL rather than DCL OPEN (but it does have 2PC between Windows SQL Server and DECdtm/Rdb :-)

Cheers Richard Maher

Re: %dcl-e-open

Jess Goodman — Mon, 06 Oct 2008 23:23:16 GMT

Richard,

For some strange reason the UCX - TCP/IP services command UCX SHOW DEVICE does not allow you to use a logical name for the socket device - at least up through TCP/IP Services 5.4.

Re: %dcl-e-open

nuno vitoria_1 — Tue, 07 Oct 2008 09:05:51 GMT

Welcome to OpenVMS AXP (TM) Operating System, Version V6.2

Username: SYSTEM
Password:
Welcome to OpenVMS Alpha Operating System, Version V6.2 on node LITAX1
Last interactive login on Tuesday, 7-OCT-2008 08:53:31.67
Last non-interactive login on Tuesday, 7-OCT-2008 10:28:39.56
DEFAULT keypad definitions:
F17 = "@BG_GEN:[COM]SETUP DIGI"
F18 = "@BG_COM:SYSMGT"
F19 = "@BG_COM:VBACKUP_SUPERVISOR"
F20 = "@BG_GEN:[COM]SETUPEDD"

$ ucx show dev bg_digi/full
%UCX-E-INETERROR, Error accessing Internet
-UCX-E-INVSOCKNAM, Invalid socket name
$

Re: %dcl-e-open

nuno vitoria_1 — Tue, 07 Oct 2008 09:09:09 GMT

This station needs de server for to work.

IRIX (litsg3)

login: digi
Password:
IRIX Release 6.3 IP32 litsg3
Copyright 1987-1996 Silicon Graphics, Inc. All Rights Reserved.
Last login: segunda-feira 06 de outubro 2008 17:42:22 on :0

Client: litsg3
Server: litax1

Software version: DIGI V9.4.1 (dd. 1-FEB-1999 10:49)
Maintenance Pack 4 (dd. 17-NOV-1999 09:45)

Software downloaded: yes

Locale "pt" used for: Operating System
Typography

litsg3 1%

Re: %dcl-e-open

Richard J Maher — Tue, 07 Oct 2008 09:31:39 GMT

Hi nuno,

As Jess kindly pointed out UCX doesn't seem to like logical names so, as per his note, you need a two step process: -

>>>>>>>>>>>>>>>>>>>
To get some more details about the error, do
$ SHOW DEVICE/FULL BG_DIGI:

If, as would seem likely, the device physical name starts with BG then it is an IP socket. Depending on what TCP/IP stack you are using and what VMS version you are runnning (hint: tell us these things), you can get socket details with the command:

$ UCX SHOW DEVICE /FULL BGn
<<<<<<<<<<<<<<<<<<<<

Is it posible to see the DCL OPEN command that is triggering this error and a few lines above taht?

Cheers Richard Maher

Re: %dcl-e-open

nuno vitoria_1 — Tue, 07 Oct 2008 09:41:23 GMT

Hi Richard,

i donÂ´t understand to mach this system but if you can help me thanks.

i send you a report what i do.

cheers Nuno

Re: %dcl-e-open

Karl Rohwedder — Tue, 07 Oct 2008 09:59:39 GMT

Look at the status:

Volume Status: subject to mount verification, allocation inhibited because of
error on bitmap, write-back caching enabled.

There is an error in the bitmap and the allocation of space is inhibited, i.e. no new files, hence the WLK error.

You may try a
$ ANAL/Disk/Repair DKB0:

but you should make a backup before.

regards Kalle

Re: %dcl-e-open

nuno vitoria_1 — Tue, 07 Oct 2008 10:11:14 GMT

Hi Kalle,

i do the command and i put the report.

cheers

Re: %dcl-e-open

Hein van den Heuvel — Tue, 07 Oct 2008 11:51:44 GMT

"-SYSTEM-F-PARITY, parity error"
The disk is going bad.

Switch over to a new disk.
This may involve restoring a backup.
This may involve loss of data.

If you are lucky all you have to do is find a spare drive (push in a fresh brick) for example DKB100. Now $backup/image dbk0: dkb100:. Dismount DKB0, Mount DKB100, redefine logicals name like bg_digi to point to to new drive. Hint: $SHOW LOG */OUT=logicals.tmp ... $SEARCH logicals.tmp DKB

Over time you may want to put th enew drive in the old slot, or not.

Good luck!
Hein.

Re: %dcl-e-open

nuno vitoria_1 — Tue, 07 Oct 2008 12:16:42 GMT

$ search logicals.tmp dkb
%SEARCH-W-OPENIN, error opening SYS$COMMON:[SYSMGR]LOGICALS.TMP; as input
-RMS-E-FNF, file not found
%SEARCH-E-NOFILE, no file found
$ sho dev d

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
DNFS0: Online 0
DNFS1: Mounted 0 litsg1:/ 0 1 0
DNFS2: Mounted 0 litsg2:/ 0 1 0
DNFS3: Mounted 0 litsg:/disk2 0 1 0
LITAX1$DKA0: Mounted 0 AXPVMSSYS 583060 425 1
LITAX1$DKA400: Online wrtlck 0
LITAX1$DKB0: Mounted 9 DISK2 5630778 2 1
LITAX1$DKB400: Mounted 0 DISK3 3510765 1 1
LITAX1$DKB500: Mounted 0 DISK4 4284234 1 1
LITAX1$DVA0: Online 0
$ backup/image dkb0: dkb400:
%BACKUP-F-MOUNTFOR, DKB400:[SYSMGR]*.*;* must be mounted /FOREIGN
$ show log */out=logicals.tmp

this weekend we had light lack and never more I connect with the server.

Re: %dcl-e-open

nuno vitoria_1 — Tue, 07 Oct 2008 12:20:28 GMT

display...in attach

Re: %dcl-e-open

nuno vitoria_1 — Tue, 07 Oct 2008 14:48:50 GMT

hi everybody thanks for your help it is now working.

best regards
Nuno

Re: %dcl-e-open

Hein van den Heuvel — Tue, 07 Oct 2008 14:50:06 GMT

Dear Nuno,

"take your fingers from that keyboard and slowly step away from the computer"

Please go careful, and try to get some more experienced help.

The commands I suggested were rough directions, not verbatim.
Judging by the output posted you are out of your 'comfort zone' with this set up and risk creating further damage.
Please escalate the problem, internally or externally (vendor, hp, consultant, whatever.).

Good luck!
Hein.

Re: %dcl-e-open

Hein van den Heuvel — Tue, 07 Oct 2008 14:52:18 GMT

I guess I spoke to soon!
It sure looked scary there for a moment!
Good to hear it worked out, and thanks for letting us know.
Cheers,
Hein.