- Integrated Systems
- About Us
- Integrated Systems
- About Us
10-06-2008 06:13 AM
%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
10-06-2008 06:41 AM
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 ?
10-06-2008 06:58 AM
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.
10-06-2008 07:24 AM
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?
10-06-2008 07:29 AM
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.)
10-06-2008 07:33 AM
$ 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.
10-06-2008 02:45 PM
Did this DCL used to work and has just stopped working? Has the open statement changed?
$ucx show dev bg_digi/full
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
10-06-2008 04:23 PM
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.
10-07-2008 02:05 AM
Welcome to OpenVMS AXP (TM) Operating System, Version V6.2
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
10-07-2008 02:09 AM
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
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