[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference cookie::sls

Title:	Storage Library System

Moderator:	COOKIE::REUTER

Created:	Sun Oct 13 1991
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2270
Total number of notes:	7850

2237.0. "SLS$TAPMGRRQ reporting RMS-F-IFI, SLS-E-UTLCONERR & RMS-F-CCR errors in OPCOM" by CX3PST::WSC217::SWANK (David) Fri Apr 04 1997 10:14

VAX 6640
OpenVMS V5.5-2
SLS V2.6

The RQ process is reporting the following errors when operators use SLSOPER's
"Initialize Volumes" item.  The customer reports that the there is nothing
wrong with the SLS$ROOT disk (no ANAL/DISK errors) and that there is no
concurrent access to the file in question by any other process (see show
device/files command below).

What could cause RQ to have any problems creating the command file for the
UT process at 3PM in the afternoon? 

\Any help or insight would be greatly appreciated, David
\

	%%%%%%%%%%  OPCOM   3-APR-1997 15:03:03.54  %%%%%%%%%%%
	(from node SOFI at  3-APR-1997 15:03:01.70)
	Message from user SLS on SOFI
	SLS$TAPMGRRQ, %SLS-E-UTLCREERR, error creating utility file
	SLS$DATA:009B23C89695CDF1.TAPMGRUT;

	%%%%%%%%%%%  OPCOM   3-APR-1997 15:03:03.55  %%%%%%%%%%%
	(from node SOFI at  3-APR-1997 15:03:01.71)
	Message from user SLS on SOFI
	SLS$TAPMGRRQ, -RMS-F-IFI, invalid internal file identifier (IFI) value

	%%%%%%%%%%%  OPCOM   3-APR-1997 15:03:03.57  %%%%%%%%%%%
	(from node SOFI at  3-APR-1997 15:03:01.73)
	Message from user SLS on SOFI
	SLS$TAPMGRRQ, %SLS-E-UTLCONERR, error connecting utility file
	SLS$DATA:009B23C89695CDF1.TAPMGRUT;

	%%%%%%%%%%%  OPCOM   3-APR-1997 15:03:03.64  %%%%%%%%%%%
	(from node SOFI at  3-APR-1997 15:03:01.80)
	Message from user SLS on SOFI
	SLS$TAPMGRRQ, -RMS-F-CCR, cannot connect RAB


	%%%%%%%%%%%  OPCOM   3-APR-1997 15:03:08.20  %%%%%%%%%%%
	(from node SOFI at  3-APR-1997 15:03:06.36)
	Message from user SLS on SOFI
	Please unload drive _$2$MUA3:

SOFI$ sd sls$data
SOFI$ show dev/files

Files accessed on device DSA35: on  3-APR-1997 15:03:47.85

Process name      PID     File name
                00000000  [000000]INDEXF.SYS;1
                00000000  [PAGE_SWAP]SOFI_PAGE3.SYS;1
SLS$TAPMGRDB    23000264  [SLS$FILES.DATA.SOFI]TAPMGRDBXEQ.LOG;280
SLS$TAPMGRDB    23000264  [SLS$FILES.SYSTEM]TAPMGRDBXEQ.COM;3
SLS$TAPMGRDB    23000264  [SLS$FILES.SYSTEM]SLS$TAPMGRDB.EXE;3
SLS$TAPMGRDB    23000264  [SLS$FILES.PRIMAST]TAPEMAST.DAT;17
SLS$TAPMGRDB    23000264  [SLS$FILES.PRIMAST]SLOTMAST.DAT;1
SLS$TAPMGRDB    23000264  [SLS$FILES.PRIMAST]POOLAUTH.DAT;2
SLS$TAPMGRDB    23000264  [SLS$FILES.PRIMAST]SLS$MAGAZINE_MASTER_FILE.DAT;1
SLS$TAPMGRDB    23000264  [SLS$FILES.DATA.SOFI]SLS$SCRATCH_AUDIT.LOG;33
--RDserver--    23000266  [SLS$FILES.TTI_RDEV]RDSERVER_SOFI.LOG;33
--RDserver--    23000266  [SLS$FILES.TTI_RDEV]RDEV_SERVER.COM;1
--RDserver--    23000266  [SLS$FILES.TTI_RDEV]RDSERVER_V55.EXE;2
                00000000  [SLS$FILES.TTI_RDEV]RDEV_CONTROL_SHR_V55.EXE;2
--RDclient--    23000269  [SLS$FILES.TTI_RDEV]RDCLIENT_SOFI.LOG;33
--RDclient--    23000269  [SLS$FILES.TTI_RDEV]RDEV_CLIENT.COM;1
--RDclient--    23000269  [SLS$FILES.TTI_RDEV]RDCLIENT_V55.EXE;2
SLS$TAPMGRRQ    2300026A  [SLS$FILES.DATA.SOFI]TAPMGRRQXEQ.LOG;84
SLS$TAPMGRRQ    2300026A  [SLS$FILES.SYSTEM]TAPMGRRQXEQ.COM;3
SLS$OPCOM       2300026D  [SLS$FILES.SYSTEM]SLS$OPCOM_SERVER.EXE;2
SLS$TAPMGRRQ    2300026A  [SLS$FILES.SYSTEM]SLS$TAPMGRRQ.EXE;3
SLS$OPCOM       2300026D  [SLS$FILES.DATA.SOFI]SLS$OPCOM_SERVER.LOG;41
SLS$TAPMGRRQ    2300026A  [SLS$FILES.DATA.SOFI]TAPEUSE.DAT;1
SLS$TAPMGRRQ    2300026A  [SLS$FILES.DATA.SOFI]009B23B320E586F1.TAPMGRUT;1
SLS_LIB         23000CA6  [SLS$FILES.SYSTEM]INITTAPES.COM;4

T.R	Title	User	Personal Name	Date	Lines
2237.1	suggestions..	COOKIE::MCCLELLAND	Marty, SLS/MDMS Engineering	`Mon Apr 07 1997 12:11`	19
	Hi David, Your customer's vms and sls versions are old, so it might be difficult to track down the cause. The UTLCREERR error follows an RQ attempt to create file SLS$DATA:009B23C89695CDF1.TAPMGRUT using the $CREATE RMS Service. But your show dev/files does indicate a channel is open to the file. Maybe it had been opened during an earlier failure? Or, since $CREATE does an implicit $OPEN and $DISPLAY, the IFI error may have occurred on the $DISPLAY. Check to see what you get from the dcl $CREATE command of the same file in the same directory. Also check if there are numerous .tapmgrut files hanging around in SLS$DATA. They are temporary files and should be deleted each time tapmgrut runs. You may have to restart the rq process to close the file. hope this helps, Marty
2237.2	two different .TAPMGRUT files...	CX3PST::WSC217::SWANK	David	`Tue Apr 08 1997 09:15`	27
	RE .1; \Hi Marty, \ >The UTLCREERR error follows an RQ attempt >to create file SLS$DATA:009B23C89695CDF1.TAPMGRUT using the $CREATE >RMS Service. But your show dev/files does indicate a channel is >open to the file. The file RQ attempts to open is 009B23C89695CDF1.TAPMGRUT, however, the file that it hass opened from the show device/files command is 009B23B320E586F1.TAPMGRUT, two different file names. >Check to see what you get from the dcl $CREATE command of the same >file in the same directory. Also check if there are numerous .tapmgrut >files hanging around in SLS$DATA. Will reply back with above information after the customer has provided same. This only occures when the operators use the SLSOPER menue to initialize volumes. I don't know all the circumstances that the .TAPMGRUT files are created but I can't imagine that this is the only one. If not and initializing volumes is the only circumstance with a problem then is there something unique with regard to how it goes about creating the .TAPMGRUT file that differs from other circumstances that the file is created? \ \Thanks for your assistance so far, David
2237.3	Creating .TAPMGRUT file and what's in SLS$DATA	CX3PST::WSC217::SWANK	David	`Wed Apr 09 1997 12:43`	215
	re .1 (additional information) >>Check to see what you get from the dcl $CREATE command of the same >>file in the same directory. Also check if there are numerous .tapmgrut >>files hanging around in SLS$DATA. > >Will reply back with above information after the customer has provided same. \Marty, \ Here is what the customer send as far as creating the .TAPMGRUT file and what was in SLS$DATA:; SOFI$ sd sls$data SOFI$ show def SLS$ROOT:[DATA.SOFI] SOFI$ create 009b23c89695cdf1.tapmgrut SOFI$ dir/date/size=all SLS$ROOT:[DATA.SOFI] 009B23C89695CDF1.TAPMGRUT;2 0/0 8-APR-1997 13:54:30.93 009B23C89695CDF1.TAPMGRUT;1 0/0 8-APR-1997 13:01:40.48 20402D6A.MAIL;1 1/3 29-JUL-1993 13:37:07.74 2040E542.MAIL;1 0/0 20-AUG-1993 10:32:17.68 2040F9F1.MAIL;1 1/3 19-AUG-1993 09:08:15.55 23C02D23.MAIL;1 1/3 21-MAR-1994 16:35:39.10 23E05445.MAIL;1 1/3 18-APR-1994 16:59:04.91 2660932F.MAIL;1 1/3 1-OCT-1994 06:10:13.72 26609EF0.MAIL;1 1/3 4-OCT-1994 14:30:01.33 2661BC05.MAIL;1 1/3 2-NOV-1994 13:49:50.33 28C0A707.MAIL;1 1/3 1-DEC-1994 16:37:40.68 CLEANUP.LOG;2187 38/39 8-APR-1997 04:24:32.87 CLEANUP.LOG;2186 38/39 7-APR-1997 10:47:15.26 SLS$OPCOM_SERVER.ERR;50 0/0 2-APR-1997 14:29:35.41 SLS$OPCOM_SERVER.ERR;49 0/0 22-MAR-1997 18:40:59.76 SLS$OPCOM_SERVER.ERR;48 0/0 15-MAR-1997 17:59:57.55 SLS$OPCOM_SERVER.LOG;41 0/0 2-APR-1997 15:02:08.49 SLS$SCRATCH_AUDIT.LOG;33 264/324 2-APR-1997 15:01:40.26 TAPEUSAGE.RPT;72 13/15 1-APR-1997 05:06:44.49 TAPEUSAGE.RPT;71 13/15 1-MAR-1997 05:08:01.50 TAPEUSAGE.RPT;70 13/15 1-FEB-1997 05:06:55.16 TAPEUSE.DAT;1 31354/32973 13-MAR-1991 14:01:09.10 TAPMGRDBXEQ.LOG;280 8/81 2-APR-1997 15:01:32.65 TAPMGRRQXEQ.LOG;84 25/81 2-APR-1997 15:01:58.87 TAPMGRUTXEQ.LOG;8457 1/3 8-APR-1997 04:40:23.48 TAPMGRUTXEQ.LOG;8456 10/12 8-APR-1997 04:25:40.90 TAPMGRUTXEQ.LOG;8455 3/3 8-APR-1997 00:00:01.62 TUSE_19910401.DAT;1 4/6 1-APR-1991 05:00:04.02 TUSE_19910501.DAT;1 20/21 1-MAY-1991 05:00:06.77 TUSE_19910601.DAT;1 553/555 1-JUN-1991 05:00:04.37 TUSE_19910701.DAT;1 552/552 1-JUL-1991 05:00:04.47 TUSE_19910801.DAT;1 607/609 1-AUG-1991 05:00:05.32 TUSE_19910901.DAT;1 671/672 1-SEP-1991 05:00:06.43 TUSE_19911001.DAT;1 735/735 1-OCT-1991 05:00:07.06 TUSE_19911101.DAT;1 798/798 1-NOV-1991 05:00:07.55 TUSE_19911201.DAT;1 799/801 1-DEC-1991 05:00:06.34 TUSE_19920101.DAT;1 696/696 1-JAN-1992 05:00:05.66 TUSE_19920201.DAT;1 775/777 1-FEB-1992 05:00:06.53 TUSE_19920301.DAT;1 811/813 1-MAR-1992 05:00:08.37 TUSE_19920401.DAT;1 853/855 1-APR-1992 06:17:32.96 TUSE_19920501.DAT;1 840/840 1-MAY-1992 05:00:09.76 TUSE_19920601.DAT;1 340/342 1-JUN-1992 06:44:07.42 TUSE_19920701.DAT;1 295/297 1-JUL-1992 05:00:05.98 TUSE_19920801.DAT;1 313/315 1-AUG-1992 09:47:24.85 TUSE_19920901.DAT;1 327/327 1-SEP-1992 05:00:09.95 TUSE_19921001.DAT;1 329/330 1-OCT-1992 05:00:20.90 TUSE_19921101.DAT;1 345/345 1-NOV-1992 05:00:06.11 TUSE_19921201.DAT;1 370/372 1-DEC-1992 09:47:32.36 TUSE_19930101.DAT;1 478/480 1-JAN-1993 05:32:37.67 TUSE_19930201.DAT;1 588/588 1-FEB-1993 05:00:05.67 TUSE_19930301.DAT;1 622/624 1-MAR-1993 05:00:14.62 TUSE_19930401.DAT;1 692/693 1-APR-1993 05:00:09.87 TUSE_19930501.DAT;1 902/903 1-MAY-1993 05:08:31.97 TUSE_19930601.DAT;1 1003/1005 1-JUN-1993 05:00:13.34 TUSE_19930701.DAT;1 1103/1104 1-JUL-1993 05:00:13.31 TUSE_19930801.DAT;1 1071/1071 1-AUG-1993 17:14:11.70 TUSE_19930901.DAT;1 1398/1398 1-SEP-1993 05:04:18.60 TUSE_19931001.DAT;1 1431/1431 1-OCT-1993 05:00:04.26 TUSE_19931101.DAT;1 1519/1521 1-NOV-1993 05:00:03.38 TUSE_19931201.DAT;1 1525/1527 1-DEC-1993 05:00:06.09 TUSE_19940101.DAT;1 1559/1560 1-JAN-1994 05:00:05.03 TUSE_19940201.DAT;1 1811/1812 1-FEB-1994 05:00:10.61 TUSE_19940301.DAT;1 1875/1875 1-MAR-1994 05:00:10.58 TUSE_19940401.DAT;1 1888/1890 1-APR-1994 05:00:05.47 TUSE_19940501.DAT;1 2259/2259 1-MAY-1994 17:37:39.24 TUSE_19940601.DAT;1 2010/2010 1-JUN-1994 05:00:07.79 TUSE_19940701.DAT;1 2437/2439 1-JUL-1994 05:00:08.79 TUSE_19940801.DAT;1 2505/2505 1-AUG-1994 05:00:09.98 TUSE_19940901.DAT;1 2639/2640 1-SEP-1994 05:00:10.61 TUSE_19941001.DAT;1 2550/2550 1-OCT-1994 05:05:26.16 TUSE_19941101.DAT;1 2415/2415 1-NOV-1994 05:00:10.38 TUSE_19941201.DAT;1 3193/3195 1-DEC-1994 05:00:11.20 TUSE_19950101.DAT;1 3677/3678 1-JAN-1995 19:49:20.79 TUSE_19950201.DAT;1 4284/4284 1-FEB-1995 05:00:10.11 TUSE_19950301.DAT;1 4535/4536 1-MAR-1995 05:02:09.10 TUSE_19950401.DAT;1 5282/5283 1-APR-1995 05:14:53.31 TUSE_19950501.DAT;1 5577/5577 1-MAY-1995 05:00:08.54 TUSE_19950601.DAT;1 5572/5574 1-JUN-1995 05:45:09.85 TUSE_19950701.DAT;1 4704/4704 1-JUL-1995 08:54:29.93 TUSE_19950801.DAT;1 5706/5706 1-AUG-1995 05:34:29.53 TUSE_19950901.DAT;1 5600/5601 1-SEP-1995 05:48:56.09 TUSE_19951002.DAT;1 4806/4806 2-OCT-1995 10:06:14.88 TUSE_19951101.DAT;1 6113/6114 1-NOV-1995 05:12:47.76 TUSE_19951201.DAT;1 6235/6237 1-DEC-1995 05:00:08.25 TUSE_19960101.DAT;1 6720/6720 1-JAN-1996 05:00:09.13 TUSE_19960201.DAT;1 6932/6933 1-FEB-1996 05:00:05.59 TUSE_19960301.DAT;1 7222/7224 1-MAR-1996 05:00:07.21 TUSE_19960401.DAT;1 7669/7671 1-APR-1996 05:00:06.07 TUSE_19960501.DAT;1 7726/7728 1-MAY-1996 05:00:05.39 TUSE_19960601.DAT;1 8213/8214 1-JUN-1996 05:00:05.66 TUSE_19960701.DAT;1 7875/7875 1-JUL-1996 05:00:05.40 TUSE_19960801.DAT;1 8868/8868 1-AUG-1996 05:00:07.88 TUSE_19960901.DAT;1 7896/7896 1-SEP-1996 18:45:52.60 TUSE_19961001.DAT;1 9698/9699 1-OCT-1996 05:00:08.20 TUSE_19961101.DAT;1 8964/8964 1-NOV-1996 05:00:06.20 TUSE_19970101.DAT;1 9367/9369 1-JAN-1997 05:00:05.50 TUSE_19970201.DAT;1 10373/10374 1-FEB-1997 05:00:05.75 TUSE_19970301.DAT;1 10110/10110 1-MAR-1997 05:00:05.42 TUSE_19970401.DAT;1 10344/10344 1-APR-1997 05:00:07.84 _BILL.RESTOR;9 3/3 22-AUG-1994 20:47:07.13 _ELAINE.RESTOR;2 3/3 19-AUG-1993 09:07:22.86 _JOHN.RESTOR;3 3/3 20-JUL-1994 10:22:03.07 _THERESA.RESTOR;13 3/3 11-JUL-1995 22:00:37.23 _THERESA.RESTOR;12 3/3 28-FEB-1995 16:00:51.67 _USMGXH.RESTOR;3 3/3 20-AUG-1993 10:21:37.45 Total of 105 files, 272380/274284 blocks. \ \Regards, David
2237.4	Does .2 & .3 give any clues?	CX3PST::WSC217::SWANK	David	`Fri Apr 18 1997 11:23`	5
	\Marty, \ Have you had a change to review .2 & .3? Customer looking for inputs. \ \Thanks, David
2237.5	Morew suggestions..	COOKIE::MCCLELLAND	Marty, SLS/MDMS Engineering	`Mon Apr 21 1997 10:03`	24
	Hi David, As I said before, this problem is probably version-dependent and the old versions make it difficult to justify spending a lot of time. But I'm willing to go a step further. Let's change the troubleshooting approach and focus on what's happening from the Init Volumes menu... It calls INITTAPES.COM which invokes the command $ STORAGE SET VOLUME 'REEL' /DENSITY="''INIT_DENSITY'"/INITIALIZE="''F$TIME()'" This command asks rq to modify the initialization date for the first (and all) volumes in the volume set being initialized. The error messages are coming from the rq routine that opens the .tapmgrut file which is used later for freeing the volumes. So, try turning verifiy on in INITTAPES.COM. This will at least identify which volume set is generating the error. Then try the same command interactively using the same volume id. You should get the same errors; if you don't, we're on the wrong track. Then, use STOR SHOW VOL to look closely at the volume set being initialized. Any clues? Marty