| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
ALL-IN-1 V3.0 (no patch), VMS 5.5-1.
I've a problem with TRM....
Phases 1 and 2 seem to complete OK.
Some time early in phase 3 the job fails (see the following A1SUB.LOG
for the MASTER process).
MULTI- | MULTIBUFFER COUNTS | NETWORK
BLOCK | Indexed Relative Sequential | BLOCK
COUNT | Disk Magtape Unit Record | COUNT
Process 0 | 20 0 0 0 0 | 0
System 16 | 2 0 0 0 0 | 8
Prolog Extend Quantity
Process 0 0
System 0 80
Working Set /Limit= 1500 /Quota= 2880 /Extent= 50000
Adjustment enabled Authorized Quota= 2880 Authorized Extent= 50000
FCVR_SCHEDULE_REC = "1993022712150000"
FCVR_PHASE_TYPE = "MASTER"
Starting at 12:13 PM
12:13 PM Submitting slaves...
00001 _DSA10
00002 _DSA13
00003 _DSA16
00004 _DSA17
00004 _DSA17
00005 _DSA18
00006 _DSA19
00007 _DSA20
00008 _DSA28
00009 _DSA30
00010 _DSA31
00011 _DSA33
12:13 PM Processing...
OA_DAFA:[OA$SHARA]OA$DAF_A.DAT
OA_DAFB:[OA$SHARB]OA$DAF_B.DAT
OA_DAFC:[OA$SHARC]OA$DAF_C.DAT
OA_DAFD:[OA$SHARD]OA$DAF_D.DAT
OA_DAFE:[OA$SHARE]OA$DAF_E.DAT
OA$DATA:PENDING.DAT
Size of record invalid
On channel 14 for file DISK$HOT_FILES:[ALLIN1]SMLOG2.TMP;1 at user PC
0000846A
Invalid record size
From line 1 in DEF FNLOG2$ in module OA$SM_FCVR
From line 5500 in module OA$SM_FCVR00004 _DSA17
Unfortunatly, the controlling command procedure believes that the image
exited having successfully completed, and deletes the SMLOG1,2,3 files.
Does anyone have any ideas what may have caused this ?
Chris
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2341.1 | Some ideas for you to try! | WAYOUT::TALBOT | Trevor Talbot | Tue Mar 02 1993 16:21 | 23 |
Hi Chris, The channel number 14 is indeed the correct one for the smlog2.tmp file as opened by the oa$sm_fcvr program. I found that the DEF FNlog2$ is infact a code segment from the above program. The file is keyed on 30 bytes and allows a further 132 bytes for data. The data being written is type of string. The write maybe attempting to put more bytes than the code allows, try editing the oa$sm_fcvr_schedule.com and comment out the delete of the smlog2.tmp file for the next run and see what's in there! The only other ideas I can come up with are to increase pgflquota, watch out for global buffer problems, I've seen some very strange behaviour when these have been exhausted(esp. the GBL params!!!). The files in oa$data like pending etc will have them on... You could try set file/glo=0 on these and re-run just to make sure you not being bitten by this. -Trev | |||||