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

Conference iosg::all-in-1_v30

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

1850.0. "DCL LOGOUT hangs your process" by VELI::KORKKO (Used to be VMS mangler, now ALL-IN-1...) Wed Nov 25 1992 11:58

On our cluster EEMELI (VAX 6000-440, VAX 6000-560, VAX 6000-440) running
VMS V5.5-2, ALL-IN-1 V3.0 finnish, DECnet/VAX Phase IV+ Extensions Wave 1,
MR 3.2 etc. the following hangs your process.

Invoke ALL-IN-1 from any account. Then type (at ALL-IN-1 menu)

	$LOGOUT

or GOLD $ and then LOGOUT.

The subprocess dies but ALL-IN-1 main process stays forever on LEF state, 
apparently waiting an EF to be set. Unfortunately there is nobody around to
set the EF so...

Our CSC has analysed situation using SDA and this is what he sent to me:

---
----------------------------------------------------------------
Process status:  02040001   RES,PHDRES

PCB address              81A2C7E0    JIB address              83C65130
PHD address              8A351A00    Swapfile disk address    00000000
Master internal PID      0026004D    Subprocess count                0
Internal PID             0026004D    Creator internal PID     00000000
Extended PID             20C04C4D    Creator extended PID     00000000
State                       LEF      Termination mailbox          0000
Current priority                9    AST's enabled                KESU
Base priority                   4    AST's active                 NONE
UIC                [00150,000006]    AST's remaining                93
Mutex count                     0    Buffered I/O count/limit      100/100
Waiting EF cluster              1    Direct I/O count/limit        100/100
Starting wait time       1B001B18    BUFIO byte count/limit      59872/59872
Event flag wait mask     EFFFFFFF    # open files allowed left      80
Local EF cluster 0       E0000001    Timer entries allowed left     50
Local EF cluster 1       E4000000    Active page table count         0
Global cluster 2 pointer 00000000    Process WS page count        1541
Global cluster 3 pointer 00000000    Global WS page count         1197
----------------------
        Call Frame Generated by CALLS Instruction

Condition Handler       7FE82708  00000000
SP Align Bits = 00      7FE8270C  207C0000
   Saved  AP            7FE82710  7FE8275C
   Saved  FP            7FE82714  7FE82738
   Return PC            7FE82718  000BFD7C
        R2              7FE8271C  0002D610
        R3              7FE82720  000251A0
        R4              7FE82724  0002CF88
        R5              7FE82728  7FFEDFF8      SYS$SETAST
        R6              7FE8272C  000C5321
Align Stack by 0 Bytes =>
Argument List           7FE82730  00000001
                        7FE82734  0000003C
SDA> e/i 000BFD7C-30;30
%SDA-W-INSKIPPED, unreasonable instruction stream - 2 bytes skipped
000BFD4E:  BICB2   #08,(R3)
000BFD51:  CLRQ    -(SP)
000BFD53:  CLRQ    -(SP)
000BFD55:  CLRL    -(SP)
000BFD57:  PUSHAB  000BFCD2
000BFD5B:  CLRQ    -(SP)
000BFD5D:  CLRL    -(SP)
000BFD5F:  MOVZBL  #A3,-(SP)
000BFD63:  PUSHL   00022654
000BFD69:  CLRL    -(SP)
000BFD6B:  CALLS   #0C,@#SYS$QIOW
000BFD72:  PUSHL   04(R3)
000BFD75:  CALLS   #01,@#SYS$WAITFR
000BFD7C:  PUSHL   04(R3)

Any ideas what is happening here?

veli
T.RTitleUserPersonal
Name
DateLines
1850.1KERNEL::OTHENJFri Nov 27 1992 12:349
    Hello,
    
    	I also have a customer with this problem, but I cannot reproduce it. 
    The VMS group have analysed the problem, and said it looks as if the 
    problem is in the ALL-IN-1 code, not the users quotering etc.
    
    	Any ideas???
    
    			Julie
1850.2Can't see anything from .0IOSG::TALLETTGimmee an Alpha colour notebook...Mon Nov 30 1992 08:2116
    
    	I don't think notes is the right medium for getting this fixed.
    	I think you should put it through the normal escalation channels
    	and get someone to take a look at the customers system.
    
    	It would save effort if you could get whoever looks at it in touch
    	with the VMS people who say its an ALL-IN-1 problem and make sure
    	if it is, it gets logged in the engineering bug database. Also,
    	posting a summary here would be good.
    
    	To resolve the problem you really would need a link map and work
    	out the call stack and where and what the code is doing. It sounds
    	like the VMS group have already partly analysed the problem.
    
    Regards,
    Paul