• Xephyr (on Linux host) and VMS keyboard

    From JKB@21:1/5 to All on Tue Jun 10 12:16:06 2025
    Hello,

    I'm able to obtain a running VMS session with my VAX (simh). All but
    keyboard run fine. I only have an error in 'host'_1.log file:

    Executing run sys$system:decw$wsinit

    %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=1211100F, PC
    =80000010, PSL=03C00004

    I don't know which image returns this access violation.

    That being said, I have a french keyboard (Sun type7, azerty). Alt-gr key
    is not mapped and when I try to send alt-gr+à ('@'), vms host only
    receives 'à'.

    Same result for alt-gr+( ([) or alt-gr+) (]). VMS session receive
    receive ( and ) instead of [ and ].

    I launch Xephyr with folling command:
    Xephyr -ac :1 -screen 1024x768 -listen tcp -query fermat -keybd ephyr,,,xkbmodel=evdev,xkblayout=fr
    but if I replace '-query fermat' by '-query legendre', I can open a
    session on a NetBSD server that can receive '@'.

    Help will be welcome,

    JB
    --
    Si votre demande me parvient en code 29, je vous titiouillerai volontiers
    une réponse.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Simon Clubley@21:1/5 to JKB on Tue Jun 10 18:35:16 2025
    On 2025-06-10, JKB <JKB@hilbert.invalid> wrote:
    Hello,

    I'm able to obtain a running VMS session with my VAX (simh). All but
    keyboard run fine. I only have an error in 'host'_1.log file:

    Executing run sys$system:decw$wsinit

    %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=1211100F, PC
    =80000010, PSL=03C00004

    I don't know which image returns this access violation.


    Would turning on image accounting for a short time give you this information
    if you look at the image exit status in the accounting logs ?

    Simon.

    --
    Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
    Walking destinations on a map are further away than they appear.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lawrence D'Oliveiro@21:1/5 to JKB on Tue Jun 10 23:54:10 2025
    On Tue, 10 Jun 2025 12:16:06 -0000 (UTC), JKB wrote:

    %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=1211100F, PC =80000010, PSL=03C00004

    PC = 80000010 ... system space? Is there something legitimately there,
    or is this just code running off into the weeds?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From JKB@21:1/5 to All on Fri Jun 13 15:52:08 2025
    Le 10-06-2025, Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> a écrit :
    On 2025-06-10, JKB <JKB@hilbert.invalid> wrote:
    Hello,

    I'm able to obtain a running VMS session with my VAX (simh). All but
    keyboard run fine. I only have an error in 'host'_1.log file:

    Executing run sys$system:decw$wsinit

    %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=1211100F, PC
    =80000010, PSL=03C00004

    I don't know which image returns this access violation.


    Would turning on image accounting for a short time give you this information if you look at the image exit status in the accounting logs ?


    I only have in log:

    Executing run sys$system:decw$wsinit

    %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=1211100F, PC
    =80000010, PSL=03C00004

    Improperly handled condition, image exit forced.

    Signal arguments Stack contents

    Number = 00000005 9E41CE63
    Name = 0000000C 00000002
    00000001 7FE95EF0
    1211100F 7FE95ED8
    80000010 00000004
    03C00004 7FE95F10
    00000000
    00000000
    9FD17880
    03000001

    Register dump

    R0 = 03C00000 R1 = 1211100F R2 = 00000020 R3 = 00000000
    R4 = 002EA6C0 R5 = 00000000 R6 = 000034E0 R7 = 00000210
    R8 = 00000210 R9 = 00000001 R10= 7FFED7D4 R11= 7FFE2BDC
    AP = 7FE95E8C FP = 7FE95E4C SP = 7FE95EC8 PC = 80000010
    PSL= 03C00004


    Executing run sys$system:decw$session

    ...

    Regards,

    JB

    --
    Si votre demande me parvient en code 29, je vous titiouillerai volontiers
    une réponse.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Robert A. Brooks@21:1/5 to All on Fri Jun 13 14:08:21 2025
    On 6/13/2025 13:56, Simon Clubley wrote:
    No, it's the accounting logs you need to look at, after you have turned
    on image accounting and repeated the above procedure. Look at the exit
    status of the images until you find the ACCVIO one. That should tell you which image is exiting with an ACCVIO status.

    Don't forget to turn off image accounting when you are finished to avoid filling up your disk with accounting logs. :-)

    To be clear, there is no clear-text accounting log file on the system.
    The output you need is generated by the ACCOUNTING utility, which will
    read the binary file SYS$MANAGER:ACCOUNTNG.DAT

    $ HELP ACCOUNTING

    An example using the /FULL qualifier is here

    Of particular interest is the "Final status code" and/or the "Final status text"

    INTERACTIVE Process Termination
    -------------------------------
    Username: GRANT UIC: [VMS,GRANT]
    Account: VMS Finish time: 13-JUN-2025 13:32:48.54 Process ID: 538021C5 Start time: 13-JUN-2025 09:17:07.17 Owner ID: Elapsed time: 0 04:15:41.36 Terminal name: FTA233: Processor time: 0 00:00:00.07 Remote node addr: Priority: 4
    Remote node name: Privilege <31-00>: FFFFFFFF
    Remote ID: GRANT(LOCAL) Privilege <63-32>: FFFFFFFF
    Remote full name: something.eng.vmssoftware.com
    Posix UID: -2 Posix GID: -2 (%XFFFFFFFE)
    Queue entry: Final status code: 00000001
    Queue name:
    Job name:
    Final status text: %SYSTEM-S-NORMAL, normal successful completion
    Page faults: 972 Direct IO: 69
    Page fault reads: 166 Buffered IO: 528
    Peak working set: 5472 Volumes mounted: 0
    Peak page file: 200432 Images executed: 15


    --
    -- Rob

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Simon Clubley@21:1/5 to JKB on Fri Jun 13 17:56:17 2025
    On 2025-06-13, JKB <JKB@hilbert.invalid> wrote:
    Le 10-06-2025, Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> a crit:
    On 2025-06-10, JKB <JKB@hilbert.invalid> wrote:
    Hello,

    I'm able to obtain a running VMS session with my VAX (simh). All but >>> keyboard run fine. I only have an error in 'host'_1.log file:

    Executing run sys$system:decw$wsinit

    %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=1211100F, PC
    =80000010, PSL=03C00004

    I don't know which image returns this access violation.


    Would turning on image accounting for a short time give you this information >> if you look at the image exit status in the accounting logs ?


    I only have in log:

    Executing run sys$system:decw$wsinit

    %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=1211100F, PC
    =80000010, PSL=03C00004

    Improperly handled condition, image exit forced.

    Signal arguments Stack contents

    Number = 00000005 9E41CE63
    Name = 0000000C 00000002
    00000001 7FE95EF0
    1211100F 7FE95ED8
    80000010 00000004
    03C00004 7FE95F10
    00000000
    00000000
    9FD17880
    03000001

    Register dump

    R0 = 03C00000 R1 = 1211100F R2 = 00000020 R3 = 00000000
    R4 = 002EA6C0 R5 = 00000000 R6 = 000034E0 R7 = 00000210
    R8 = 00000210 R9 = 00000001 R10= 7FFED7D4 R11= 7FFE2BDC
    AP = 7FE95E8C FP = 7FE95E4C SP = 7FE95EC8 PC = 80000010
    PSL= 03C00004


    Executing run sys$system:decw$session


    No, it's the accounting logs you need to look at, after you have turned
    on image accounting and repeated the above procedure. Look at the exit
    status of the images until you find the ACCVIO one. That should tell you
    which image is exiting with an ACCVIO status.

    Don't forget to turn off image accounting when you are finished to avoid filling up your disk with accounting logs. :-)

    Simon.

    --
    Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
    Walking destinations on a map are further away than they appear.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Arne_Vajh=C3=B8j?=@21:1/5 to Robert A. Brooks on Fri Jun 13 22:29:43 2025
    On 6/13/2025 2:08 PM, Robert A. Brooks wrote:
    On 6/13/2025 13:56, Simon Clubley wrote:
    No, it's the accounting logs you need to look at, after you have turned
    on image accounting and repeated the above procedure. Look at the exit
    status of the images until you find the ACCVIO one. That should tell you
    which image is exiting with an ACCVIO status.

    Don't forget to turn off image accounting when you are finished to avoid
    filling up your disk with accounting logs. :-)

    To be clear, there is no clear-text accounting log file on the system.
    The output you need is generated by the ACCOUNTING utility, which will
    read the binary file SYS$MANAGER:ACCOUNTNG.DAT

    $ HELP ACCOUNTING

    An example using the /FULL qualifier is here

    /SINCE and /BEFORE can be used to select time interval.

    /TYPE=IMAGE can select only image records.

    If it is an older busy system, then no selection will result in
    a huge output.

    Arne

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Arne_Vajh=C3=B8j?=@21:1/5 to All on Fri Jun 13 22:31:37 2025
    On 6/13/2025 10:29 PM, Arne Vajhøj wrote:
    On 6/13/2025 2:08 PM, Robert A. Brooks wrote:
    On 6/13/2025 13:56, Simon Clubley wrote:
    No, it's the accounting logs you need to look at, after you have turned
    on image accounting and repeated the above procedure. Look at the exit
    status of the images until you find the ACCVIO one. That should tell you >>> which image is exiting with an ACCVIO status.

    Don't forget to turn off image accounting when you are finished to avoid >>> filling up your disk with accounting logs. :-)

    To be clear, there is no clear-text accounting log file on the system.
    The output you need is generated by the ACCOUNTING utility, which will
    read the binary file SYS$MANAGER:ACCOUNTNG.DAT

    $ HELP ACCOUNTING

    An example using the /FULL qualifier is here

    /SINCE and /BEFORE can be used to select time interval.

    /TYPE=IMAGE can select only image records.

    If it is an older busy system, then no selection will result in
    a huge output.

    And for a scripted solution I can suggest Groovy and VMSACCT
    library:

    import dk.vajhoej.vms.acct.*

    acctfile = new AcctFile("sys\$manager:accountng.dat")
    while(acctfile.more()) {
    acctrec = acctfile.read()
    if(acctrec.type.type == AcctRecType.ACR$K_IMGDEL) {
    tim = acctrec.systime
    for(pack in acctrec.packs) {
    if(pack.type.type == AcctPackType.ACR$K_RESOURCE) {
    stat = pack.status
    }
    if(pack.type.type == AcctPackType.ACR$K_IMAGENAME) {
    img = pack.imagename
    }
    }
    println("$tim : $img status=$stat")
    }
    }
    acctfile.close()

    does what it looks like it does.

    Arne

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lawrence D'Oliveiro@21:1/5 to All on Sat Jun 14 02:49:44 2025
    On Fri, 13 Jun 2025 22:31:37 -0400, Arne Vajhøj wrote:

    if(acctrec.type.type == AcctRecType.ACR$K_IMGDEL) {
    tim = acctrec.systime
    for(pack in acctrec.packs) {
    if(pack.type.type == AcctPackType.ACR$K_RESOURCE) {
    stat = pack.status
    }
    if(pack.type.type == AcctPackType.ACR$K_IMAGENAME) {
    img = pack.imagename
    }
    }
    println("$tim : $img status=$stat")

    Shouldn’t “stat” and “img” be initialized to something like “null” or
    “undef” (or whatever the Groovy equivalent is)? Unless you’re assuming they’ll always be defined for that record type.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Arne_Vajh=C3=B8j?=@21:1/5 to Lawrence D'Oliveiro on Sat Jun 14 10:01:50 2025
    On 6/13/2025 10:49 PM, Lawrence D'Oliveiro wrote:
    On Fri, 13 Jun 2025 22:31:37 -0400, Arne Vajhøj wrote:
    if(acctrec.type.type == AcctRecType.ACR$K_IMGDEL) {
    tim = acctrec.systime
    for(pack in acctrec.packs) {
    if(pack.type.type == AcctPackType.ACR$K_RESOURCE) {
    stat = pack.status
    }
    if(pack.type.type == AcctPackType.ACR$K_IMAGENAME) {
    img = pack.imagename
    }
    }
    println("$tim : $img status=$stat")

    Shouldn’t “stat” and “img” be initialized to something like “null” or
    “undef” (or whatever the Groovy equivalent is)? Unless you’re assuming they’ll always be defined for that record type.

    They should (Groovy uses null).

    An image activation record should always have a resource
    and imagename pack. But good defensive programming style
    say to initialize anyway.

    Arne

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From JKB@21:1/5 to All on Sat Jun 14 13:18:33 2025
    Le 13-06-2025, Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> a écrit :
    No, it's the accounting logs you need to look at, after you have turned
    on image accounting and repeated the above procedure. Look at the exit
    status of the images until you find the ACCVIO one. That should tell you which image is exiting with an ACCVIO status.


    I have tried
    $ accounting /image=sys$manager:decw$wsinit
    before logout/login again.

    $ accounting /since=14-JUN-2025 returns:
    14-JUN-2025 14:46:53 PROCESS INTERACTIVE BERTRAND 0000011B MBA40: 00000001
    14-JUN-2025 14:46:54 PROCESS NETWORK BERTRAND 0000011A 00000001
    14-JUN-2025 14:46:56 PROCESS SUBPROCESS TCPIP$XDM 00000119 00000001
    14-JUN-2025 14:47:03 PROCESS SUBPROCESS TCPIP$XDM 0000011D 00000003
    14-JUN-2025 14:51:57 PROCESS DETACHED SYSTEM 0000011C 02DB8204
    14-JUN-2025 14:54:30 PROCESS INTERACTIVE BERTRAND 00000124 FTA5: 0001C0F4
    14-JUN-2025 14:54:47 PROCESS INTERACTIVE BERTRAND 00000122 MBA57: 00000001
    14-JUN-2025 14:54:48 PROCESS INTERACTIVE BERTRAND 00000121 MBA55: 00000001
    14-JUN-2025 14:54:48 PROCESS INTERACTIVE BERTRAND 00000120 MBA53: 00000001
    14-JUN-2025 14:54:49 PROCESS INTERACTIVE BERTRAND 00000125 FTA6: 0001C0F4
    14-JUN-2025 14:54:50 PROCESS INTERACTIVE BERTRAND 00000123 MBA59: 10778088
    14-JUN-2025 14:54:50 PROCESS NETWORK BERTRAND 0000011F 00000001
    14-JUN-2025 14:54:52 PROCESS SUBPROCESS TCPIP$XDM 0000011E 00000001
    14-JUN-2025 14:59:52 PROCESS DETACHED SYSTEM 00000126 02DB8204

    $ accounting /full doesn't return any access violation error. Only a
    file read error:

    INTERACTIVE Process Termination
    -------------------------------
    Username: BERTRAND UIC: [BERTRAND]
    Account: Finish time: 14-JUN-2025 14:54:30.30 Process ID: 00000124 Start time: 14-JUN-2025 14:48:26.55 Owner ID: Elapsed time: 0 00:06:03.74 Terminal name: FTA5: Processor time: 0 00:01:17.79 Remote node addr: Priority: 4
    Remote node name: Privilege <31-00>: FFFFFFFF
    Remote ID: Privilege <63-32>: FFFFFFFF
    Remote full name:
    Queue entry: Final status code: 0001C0F4
    Queue name:
    Job name:
    Final status text: %RMS-F-RER, file read error

    Page faults: 1915 Direct IO: 717
    Page fault reads: 188 Buffered IO: 535
    Peak working set: 789 Volumes mounted: 0
    Peak page file: 4438 Images executed: 11

    and a few others with strange final status codes:

    INTERACTIVE Process Termination
    -------------------------------
    Username: BERTRAND UIC: [BERTRAND]
    Account: Finish time: 14-JUN-2025 14:54:50.46 Process ID: 00000123 Start time: 14-JUN-2025 14:48:16.48 Owner ID: Elapsed time: 0 00:06:33.97 Terminal name: MBA59: Processor time: 0 00:00:21.71 Remote node addr: Priority: 4
    Remote node name: Privilege <31-00>: 00108000
    Remote ID: Privilege <63-32>: 00000000
    Remote full name:
    Queue entry: Final status code: 10778088
    Queue name:
    Job name:
    Final status text: <no text>

    Page faults: 6491 Direct IO: 64
    Page fault reads: 114 Buffered IO: 3208
    Peak working set: 5558 Volumes mounted: 0
    Peak page file: 14179 Images executed: 3

    DETACHED Process Termination
    ----------------------------
    Username: SYSTEM UIC: [SYSTEM]
    Account: <start> Finish time: 14-JUN-2025 14:59:52.83 Process ID: 00000126 Start time: 14-JUN-2025 14:54:47.21 Owner ID: Elapsed time: 0 00:05:05.62 Terminal name: Processor time: 0 00:00:01.25 Remote node addr: Priority: 4
    Remote node name: Privilege <31-00>: 0010C000
    Remote ID: Privilege <63-32>: 00000000
    Remote full name:
    Queue entry: Final status code: 02DB8204
    Queue name:
    Job name:
    Final status text: <no text>

    Page faults: 735 Direct IO: 2
    Page fault reads: 64 Buffered IO: 46
    Peak working set: 1065 Volumes mounted: 0
    Peak page file: 9351 Images executed: 1

    Any idea for alt-gr key ?

    Best regard,

    JB

    --
    Si votre demande me parvient en code 29, je vous titiouillerai volontiers
    une réponse.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From hb0815@21:1/5 to JKB on Sat Jun 14 17:21:56 2025
    On 6/14/25 15:18, JKB wrote:
    Le 13-06-2025, Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> a écrit :
    No, it's the accounting logs you need to look at, after you have turned
    on image accounting and repeated the above procedure. Look at the exit
    status of the images until you find the ACCVIO one. That should tell you
    which image is exiting with an ACCVIO status.


    I have tried
    $ accounting /image=sys$manager:decw$wsinit
    before logout/login again.

    $ accounting /since=14-JUN-2025 returns:
    14-JUN-2025 14:46:53 PROCESS INTERACTIVE BERTRAND 0000011B MBA40: 00000001
    14-JUN-2025 14:46:54 PROCESS NETWORK BERTRAND 0000011A 00000001
    14-JUN-2025 14:46:56 PROCESS SUBPROCESS TCPIP$XDM 00000119 00000001
    14-JUN-2025 14:47:03 PROCESS SUBPROCESS TCPIP$XDM 0000011D 00000003
    14-JUN-2025 14:51:57 PROCESS DETACHED SYSTEM 0000011C 02DB8204
    14-JUN-2025 14:54:30 PROCESS INTERACTIVE BERTRAND 00000124 FTA5: 0001C0F4
    14-JUN-2025 14:54:47 PROCESS INTERACTIVE BERTRAND 00000122 MBA57: 00000001
    14-JUN-2025 14:54:48 PROCESS INTERACTIVE BERTRAND 00000121 MBA55: 00000001
    14-JUN-2025 14:54:48 PROCESS INTERACTIVE BERTRAND 00000120 MBA53: 00000001
    14-JUN-2025 14:54:49 PROCESS INTERACTIVE BERTRAND 00000125 FTA6: 0001C0F4
    14-JUN-2025 14:54:50 PROCESS INTERACTIVE BERTRAND 00000123 MBA59: 10778088
    14-JUN-2025 14:54:50 PROCESS NETWORK BERTRAND 0000011F 00000001
    14-JUN-2025 14:54:52 PROCESS SUBPROCESS TCPIP$XDM 0000011E 00000001
    14-JUN-2025 14:59:52 PROCESS DETACHED SYSTEM 00000126 02DB8204

    $ accounting /full doesn't return any access violation error. Only a
    file read error:

    INTERACTIVE Process Termination
    -------------------------------
    Username: BERTRAND UIC: [BERTRAND]
    Account: Finish time: 14-JUN-2025 14:54:30.30
    Process ID: 00000124 Start time: 14-JUN-2025 14:48:26.55
    Owner ID: Elapsed time: 0 00:06:03.74
    Terminal name: FTA5: Processor time: 0 00:01:17.79
    Remote node addr: Priority: 4
    Remote node name: Privilege <31-00>: FFFFFFFF
    Remote ID: Privilege <63-32>: FFFFFFFF
    Remote full name:
    Queue entry: Final status code: 0001C0F4
    Queue name:
    Job name:
    Final status text: %RMS-F-RER, file read error

    Page faults: 1915 Direct IO: 717
    Page fault reads: 188 Buffered IO: 535
    Peak working set: 789 Volumes mounted: 0
    Peak page file: 4438 Images executed: 11

    and a few others with strange final status codes:

    INTERACTIVE Process Termination
    -------------------------------
    Username: BERTRAND UIC: [BERTRAND]
    Account: Finish time: 14-JUN-2025 14:54:50.46
    Process ID: 00000123 Start time: 14-JUN-2025 14:48:16.48
    Owner ID: Elapsed time: 0 00:06:33.97
    Terminal name: MBA59: Processor time: 0 00:00:21.71
    Remote node addr: Priority: 4
    Remote node name: Privilege <31-00>: 00108000
    Remote ID: Privilege <63-32>: 00000000
    Remote full name:
    Queue entry: Final status code: 10778088
    Queue name:
    Job name:
    Final status text: <no text>

    Page faults: 6491 Direct IO: 64
    Page fault reads: 114 Buffered IO: 3208
    Peak working set: 5558 Volumes mounted: 0
    Peak page file: 14179 Images executed: 3

    DETACHED Process Termination
    ----------------------------
    Username: SYSTEM UIC: [SYSTEM]
    Account: <start> Finish time: 14-JUN-2025 14:59:52.83
    Process ID: 00000126 Start time: 14-JUN-2025 14:54:47.21
    Owner ID: Elapsed time: 0 00:05:05.62
    Terminal name: Processor time: 0 00:00:01.25
    Remote node addr: Priority: 4
    Remote node name: Privilege <31-00>: 0010C000
    Remote ID: Privilege <63-32>: 00000000
    Remote full name:
    Queue entry: Final status code: 02DB8204
    Queue name:
    Job name:
    Final status text: <no text>

    Page faults: 735 Direct IO: 2
    Page fault reads: 64 Buffered IO: 46
    Peak working set: 1065 Volumes mounted: 0
    Peak page file: 9351 Images executed: 1

    Any idea for alt-gr key ?

    Best regard,

    JB


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From hb0815@21:1/5 to JKB on Sat Jun 14 17:25:55 2025
    Sorry, pressed snd too soon ...

    On 6/14/25 15:18, JKB wrote:

    I have tried
    $ accounting /image=sys$manager:decw$wsinit
    before logout/login again.

    You need
    $ SET ACCOUNTING /ENABLE=IMAGE

    But you can also (I don't have access to a VAX, n Eisner, an Alpha system):

    $ sea sys$startup:decw*.com decw$wsinit
    %SEARCH-W-OPENIN, error opening ...
    -RMS-E-PRV, insufficient privilege or file protection violation

    ******************************
    SYS$COMMON:[SYSMGR]DECW$STARTAPPS.COM;1

    "sys$system:decw$wsinit.exe" "/OPEN/HEAD/SHARE"
    $ decw$sessioninit == "run sys$system:decw$wsinit"
    $


    $ sea sys$startup:decw*.com decw$sessioninit
    %SEARCH-W-OPENIN, error opening ...
    -RMS-E-PRV, insufficient privilege or file protection violation

    ******************************
    SYS$COMMON:[SYSMGR]DECW$STARTAPPS.COM;1

    $ decw$sessioninit == "run sys$system:decw$wsinit"
    $ define/system/exec/nolog DECW$SESSIONINIT "''decw$sessioninit'"

    ******************************
    SYS$COMMON:[SYSMGR]DECW$STARTSM.COM;1

    $sessioninit = F$TRNLNM("DECW$SESSIONINIT")
    $
    $ sea sys$startup:decw*.com sessioninit
    %SEARCH-W-OPENIN, error opening ...
    -RMS-E-PRV, insufficient privilege or file protection violation

    ******************************
    SYS$COMMON:[SYSMGR]DECW$STARTAPPS.COM;1

    $ decw$sessioninit == "run sys$system:decw$wsinit"
    $ define/system/exec/nolog DECW$SESSIONINIT "''decw$sessioninit'"

    ******************************
    SYS$COMMON:[SYSMGR]DECW$STARTSM.COM;1

    $if name .EQS. "LOGIN" then goto do_sessioninit
    $if name .EQS. "SESSIONINIT" then goto do_decw_sylogin
    $if comnegated .EQS. "TRUE" then GOTO do_sessioninit
    $if lgicmd .EQS. "" then GOTO do_sessioninit
    $ if F$SEARCH(lgicmd) .eqs. "" then goto do_sessioninit
    $do_sessioninit:
    $define/nolog decw$doing_session SESSIONINIT
    $sessioninit = F$TRNLNM("DECW$SESSIONINIT")
    $if sessioninit .EQS. "" then goto do_decw_sylogin
    $write sys$output "Executing ''sessioninit'"
    $'sessioninit
    $

    Here's your "Executing run sys$system:decw$wsinit". Assuming the command procedures on VAX are similar: edit DECW$STARTSM.COM and add a "$ set process/dump" before the "write".

    You should get a process dump of the image with the ACCVIO (probably decw$wsinit) in the current working directory. I don't know where that
    is. It depends on whether the decw$ command procedures changed it or
    not. The dump file is <image-name>.DMP. Usually you do an
    analyze/process <dump-file> to look at the dump. At least on
    Alpha(Eisner) analyze/crash works as well.

    The minimum of information you get should be the name of the image, as
    in <image-name>.DMP. Without the sources and map files you may get some
    hints but you may not get enough information to identify and/or work
    around the problem.

    And yes, sys$system:decw$wsinit (at least on Eisner) is linked with /notraceback so you only get a register dump and no information on the
    call frames.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lawrence D'Oliveiro@21:1/5 to All on Sun Jun 15 01:53:09 2025
    On Sat, 14 Jun 2025 17:25:55 +0200, hb0815 wrote:

    And yes, sys$system:decw$wsinit (at least on Eisner) is linked with /notraceback so you only get a register dump and no information on the
    call frames.

    Do you have the option to provide debug symbols in a separate package? On binary-based Linux distros, you see “-dbg” versions of just about every binary package -- and that includes shared libraries.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Arne_Vajh=C3=B8j?=@21:1/5 to All on Sun Jun 15 19:42:46 2025
    On 6/14/2025 10:01 AM, Arne Vajhøj wrote:
    On 6/13/2025 10:49 PM, Lawrence D'Oliveiro wrote:
    On Fri, 13 Jun 2025 22:31:37 -0400, Arne Vajhøj wrote:
          if(acctrec.type.type == AcctRecType.ACR$K_IMGDEL) {
              tim = acctrec.systime
              for(pack in acctrec.packs) {
                  if(pack.type.type == AcctPackType.ACR$K_RESOURCE) {
                     stat = pack.status
                  }
                  if(pack.type.type == AcctPackType.ACR$K_IMAGENAME) {
                      img = pack.imagename
                  }
              }
              println("$tim : $img status=$stat")

    Shouldn’t “stat” and “img” be initialized to something like “null” or
    “undef” (or whatever the Groovy equivalent is)? Unless you’re assuming >> they’ll always be defined for that record type.

    They should (Groovy uses null).

    An image activation record should always have a resource
    and imagename pack. But good defensive programming style
    say to initialize anyway.

    import dk.vajhoej.vms.acct.*

    acctfile = new AcctFile("sys\$manager:accountng.dat")
    while(acctfile.more()) {
    acctrec = acctfile.read()
    if(acctrec.type.type == AcctRecType.ACR$K_IMGDEL) {
    tim = acctrec.systime
    stat = ">>>> no resource packet found <<<<"
    img = ">>>> no imagename packet found <<<<"
    for(pack in acctrec.packs) {
    if(pack.type.type == AcctPackType.ACR$K_RESOURCE) {
    stat = pack.status
    }
    if(pack.type.type == AcctPackType.ACR$K_IMAGENAME) {
    img = pack.imagename
    }
    }
    println("$tim : $img status=$stat")
    }
    }
    acctfile.close()

    Arne

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From JKB@21:1/5 to All on Mon Jun 16 07:34:32 2025
    Le 14-06-2025, hb0815 <mw40171@mucweb.de> a écrit :
    Sorry, pressed snd too soon ...

    On 6/14/25 15:18, JKB wrote:

    I have tried
    $ accounting /image=sys$manager:decw$wsinit
    before logout/login again.

    You need
    $ SET ACCOUNTING /ENABLE=IMAGE

    I have set accounting before posting. Strangely, all ACCVIO are
    not loggued.

    DECW$WSINIT Image Termination
    -----------------------------
    Username: BERTRAND UIC: [BERTRAND]
    Account: Finish time: 14-JUN-2025 15:23:09.75 Process ID: 00000131 Start time: 14-JUN-2025 15:23:07.67 Owner ID: Elapsed time: 0 00:00:02.08 Terminal name: Processor time: 0 00:00:01.52 Remote node addr: Priority: 4
    Remote node name: Privilege <31-00>: 00108000
    Remote ID: Privilege <63-32>: 00000000
    Remote full name:
    Queue entry: Final status code: 1000000C
    Queue name:
    Job name:
    Final status text: %SYSTEM-F-ACCVIO, access violation, reason mask=!XB, virtual

    Page faults: 939 Direct IO: 8
    Page fault reads: 42 Buffered IO: 121
    Peak working set: 1482 Volumes mounted: 0
    Peak page file: 2578 Images executed: 3

    Image name: FERMAT$DUA0:[SYS0.SYSCOMMON.][SYSEXE]DECW$WSINIT.EXE

    But you can also (I don't have access to a VAX, n Eisner, an Alpha system):

    $ sea sys$startup:decw*.com decw$wsinit
    %SEARCH-W-OPENIN, error opening ...
    -RMS-E-PRV, insufficient privilege or file protection violation

    ******************************
    SYS$COMMON:[SYSMGR]DECW$STARTAPPS.COM;1

    "sys$system:decw$wsinit.exe" "/OPEN/HEAD/SHARE"
    $ decw$sessioninit == "run sys$system:decw$wsinit"
    $


    $ sea sys$startup:decw*.com decw$sessioninit
    %SEARCH-W-OPENIN, error opening ...
    -RMS-E-PRV, insufficient privilege or file protection violation

    ******************************
    SYS$COMMON:[SYSMGR]DECW$STARTAPPS.COM;1

    $ decw$sessioninit == "run sys$system:decw$wsinit"
    $ define/system/exec/nolog DECW$SESSIONINIT "''decw$sessioninit'"

    ******************************
    SYS$COMMON:[SYSMGR]DECW$STARTSM.COM;1

    $sessioninit = F$TRNLNM("DECW$SESSIONINIT")
    $
    $ sea sys$startup:decw*.com sessioninit
    %SEARCH-W-OPENIN, error opening ...
    -RMS-E-PRV, insufficient privilege or file protection violation

    ******************************
    SYS$COMMON:[SYSMGR]DECW$STARTAPPS.COM;1

    $ decw$sessioninit == "run sys$system:decw$wsinit"
    $ define/system/exec/nolog DECW$SESSIONINIT "''decw$sessioninit'"

    ******************************
    SYS$COMMON:[SYSMGR]DECW$STARTSM.COM;1

    $if name .EQS. "LOGIN" then goto do_sessioninit
    $if name .EQS. "SESSIONINIT" then goto do_decw_sylogin
    $if comnegated .EQS. "TRUE" then GOTO do_sessioninit
    $if lgicmd .EQS. "" then GOTO do_sessioninit
    $ if F$SEARCH(lgicmd) .eqs. "" then goto do_sessioninit
    $do_sessioninit:
    $define/nolog decw$doing_session SESSIONINIT
    $sessioninit = F$TRNLNM("DECW$SESSIONINIT")
    $if sessioninit .EQS. "" then goto do_decw_sylogin
    $write sys$output "Executing ''sessioninit'"
    $'sessioninit
    $

    Here's your "Executing run sys$system:decw$wsinit". Assuming the command procedures on VAX are similar: edit DECW$STARTSM.COM and add a "$ set process/dump" before the "write".

    Done:

    $do_sessioninit:
    $define/nolog decw$doing_session SESSIONINIT
    $sessioninit = F$TRNLNM("DECW$SESSIONINIT")
    $if sessioninit .EQS. "" then goto do_decw_sylogin
    $set process/dump
    $write sys$output "Executing ''sessioninit'"
    $write sys$output ""
    $'sessioninit
    $write sys$output ""

    Now, I'm trying to connect to xdm.

    $ show def
    DUA0:[000000]
    $ dir [...]*.dmp/time

    Directory DUA0:[SYS0.SYSEXE]

    ERRORLOG.DMP;1 23-OCT-2018 23:48:48.86
    SYSDUMP.DMP;1 23-OCT-2018 23:00:32.62

    Total of 2 files.

    No dump file is created.

    Regards,

    JB

    --
    Si votre demande me parvient en code 29, je vous titiouillerai volontiers
    une réponse.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Craig A. Berry@21:1/5 to JKB on Mon Jun 16 06:15:19 2025
    On 6/16/25 2:34 AM, JKB wrote:
    Le 14-06-2025, hb0815 <mw40171@mucweb.de> a écrit :

    Here's your "Executing run sys$system:decw$wsinit". Assuming the command
    procedures on VAX are similar: edit DECW$STARTSM.COM and add a "$ set
    process/dump" before the "write".

    Done:

    No dump file is created.

    I'm pretty sure process dumps are for post-VAX platforms only. Maybe
    someone else remembers what version first had them.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Craig A. Berry@21:1/5 to Craig A. Berry on Mon Jun 16 06:24:31 2025
    On 6/16/25 6:15 AM, Craig A. Berry wrote:

    On 6/16/25 2:34 AM, JKB wrote:
    Le 14-06-2025, hb0815 <mw40171@mucweb.de> a écrit :

    Here's your "Executing run sys$system:decw$wsinit". Assuming the command >>> procedures on VAX are similar: edit DECW$STARTSM.COM and add a "$ set
    process/dump" before the "write".

        Done:

        No dump file is created.

    I'm pretty sure process dumps are for post-VAX platforms only.  Maybe someone else remembers what version first had them.

    Never mind. I think I'm remembering that DUMP/PROCESS to get an
    immediate dump was Alpha only when it came out.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From hb0815@21:1/5 to JKB on Mon Jun 16 15:00:25 2025
    On 6/16/25 07:34, JKB wrote:
    ...
    Now, I'm trying to connect to xdm.

    $ show def
    DUA0:[000000]
    $ dir [...]*.dmp/time

    Directory DUA0:[SYS0.SYSEXE]

    ERRORLOG.DMP;1 23-OCT-2018 23:48:48.86
    SYSDUMP.DMP;1 23-OCT-2018 23:00:32.62

    Total of 2 files.

    No dump file is created.

    In the log file, is there any message about not being able to create a
    process dump?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From JKB@21:1/5 to All on Tue Jun 17 07:23:44 2025
    Le 16-06-2025, hb0815 <mw40171@mucweb.de> a écrit :
    On 6/16/25 07:34, JKB wrote:
    ...
    Now, I'm trying to connect to xdm.

    $ show def
    DUA0:[000000]
    $ dir [...]*.dmp/time

    Directory DUA0:[SYS0.SYSEXE]

    ERRORLOG.DMP;1 23-OCT-2018 23:48:48.86
    SYSDUMP.DMP;1 23-OCT-2018 23:00:32.62

    Total of 2 files.

    No dump file is created.

    In the log file, is there any message about not being able to create a process dump?


    Nope :-(

    $ type hilbert_1.log
    $ Set NoOn
    $ VERIFY = F$VERIFY(F$TRNLNM("SYLOGIN_VERIFY"))
    %SET-W-NOTSET, error modifying DUA0:
    -CLI-E-IVDEVTYPE, invalid device type - specify a mailbox device
    p1 = HILBERT:1
    p2 =
    Executing SYS$MANAGER:SYLOGIN
    Executing run sys$system:decw$wsinit

    %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=1211100F, PC
    =80000010, PSL=03C00004

    Improperly handled condition, image exit forced.

    ...

    Executing run sys$system:decw$session

    X Toolkit Warning: locale not supported by C library, locale unchanged
    X Toolkit Warning: Cannot convert string "-*-Menu-Medium-R-Normal--*-120-*-*-P-*
    -ISO8859-1" to type FontStruct
    X Toolkit Warning: Cannot convert string "-*-Menu-Medium-R-Normal--*-120-*-*-P-*
    -ISO8859-1" to type FontStruct
    X Toolkit Warning: Cannot convert string "-*-Menu-Medium-R-Normal--*-120-*-*-P-*
    -ISO8859-1" to type FontStruct


    System Menu Bar: Pseudo Mouse not available

    X Toolkit Warning: Cannot convert string "-*-Menu-Medium-R-Normal--*-120-*-*-P-*
    -ISO8859-1" to type FontStruct



    --
    Si votre demande me parvient en code 29, je vous titiouillerai volontiers
    une réponse.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From JKB@21:1/5 to All on Tue Jun 17 10:55:54 2025
    Le 17-06-2025, Volker Halle <volker_halle@hotmail.com> a écrit :
    Am 17.06.2025 um 09:23 schrieb JKB:
    ...
    Executing run sys$system:decw$wsinit

    %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=1211100F, PC
    =80000010, PSL=03C00004
    ...

    Can you run DECW$WSINIT standalone interactively ? Would it fail in the
    same way ?


    $ run sys$system:decw$wsinit
    Can't open display
    $ set display /create /transport=TCPIP /node=192.168.10.103 /server=1
    $ mcr sys$system:decw$clock
    clock displayed to Xephyr
    $ run sys$system:decw$wsinit
    Warning: Can't set help modifier
    %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=1211100F, PC
    =80000010, PSL=03C00004

    Improperly handled condition, image exit forced.

    Signal arguments Stack contents

    Number = 00000005 9E41CE63
    Name = 0000000C 00000002
    00000001 7FE95EF0
    1211100F 7FE95ED8
    80000010 00000004
    03C00004 7FE95F10
    00000000
    00000000
    9FD8FEC0
    03000001

    Register dump

    R0 = 03C00000 R1 = 1211100F R2 = 00000020 R3 = 00000000
    R4 = 002EA6D0 R5 = 00000000 R6 = 000034E0 R7 = 00000210
    R8 = 00000210 R9 = 00000001 R10= 7FFED7D4 R11= 7FFE2BDC
    AP = 7FE95E8C FP = 7FE95E4C SP = 7FE95EC8 PC = 80000010
    PSL= 03C00004

    $

    Regards,

    JB

    --
    Si votre demande me parvient en code 29, je vous titiouillerai volontiers
    une réponse.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Volker Halle@21:1/5 to All on Tue Jun 17 12:33:30 2025
    Am 17.06.2025 um 09:23 schrieb JKB:
    ...
    Executing run sys$system:decw$wsinit

    %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=1211100F, PC
    =80000010, PSL=03C00004
    ...

    Can you run DECW$WSINIT standalone interactively ? Would it fail in the
    same way ?

    Volker.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From JKB@21:1/5 to All on Tue Jun 17 11:52:52 2025
    $ set process/dump
    $ run sys$system:decw$wsinit
    %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=1211100F, PC
    =80000010, PSL=03C00004
    ...

    now creates a dump file.

    $ analyze /process_dump DECW$WSINIT.DMP
    ...
    %DEBUG-I-NOSOURCE, No source for address: 800000101


    --
    Si votre demande me parvient en code 29, je vous titiouillerai volontiers
    une réponse.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From JKB@21:1/5 to All on Tue Jun 17 15:14:12 2025
    Le 17-06-2025, Volker Halle <volker_halle@hotmail.com> a écrit :
    Am 17.06.2025 um 13:52 schrieb JKB:

    $ analyze /process_dump DECW$WSINIT.DMP
    ...
    %DEBUG-I-NOSOURCE, No source for address: 800000101

    Now try:

    EXA/INS 80000010

    This is a system space address and will show (you can also use SDA to
    examine the insturction at this address):

    exa/ins 80000010
    EXE$QIOW_3: CALLG 04(SP),(R1)

    And R1 contains an invalid address value, so the ACCVIO happens.

    $ analyze /process_dump DECW$WSINIT.DMP
    Condition signalled to take dump:
    %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=1211100F, PC
    =80000010, PSL=03C00004

    OpenVMS VAX Debug Version V7.3-017


    examine/instruction 2147483664
    2147483664: CALLG B^4(SP),(R1)
    display reg


    How can I display registers ?

    Best regards,

    JB

    --
    Si votre demande me parvient en code 29, je vous titiouillerai volontiers
    une réponse.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Volker Halle@21:1/5 to All on Tue Jun 17 16:33:24 2025
    Am 17.06.2025 um 13:52 schrieb JKB:

    $ analyze /process_dump DECW$WSINIT.DMP
    ...
    %DEBUG-I-NOSOURCE, No source for address: 800000101

    Now try:

    EXA/INS 80000010

    This is a system space address and will show (you can also use SDA to
    examine the insturction at this address):

    exa/ins 80000010
    EXE$QIOW_3: CALLG 04(SP),(R1)

    And R1 contains an invalid address value, so the ACCVIO happens.

    Volker.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From JKB@21:1/5 to All on Tue Jun 17 15:48:55 2025
    Le 17-06-2025, Volker Halle <volker_halle@hotmail.com> a écrit :
    CHARON $ mc decw$wsinit
    Can't open display

    CHARON $ set watch file/class=major
    CHARON $ mc decw$wsinit
    %XQP, Thread #0, Access (0,0,0) Status: 00000910
    %XQP, Thread #0, Access (0,0,0) Status: 00000910
    Can't open display

    I get these messages with or without SET DISPLAY/CREATE

    You turn off the XQP messages with $ SET WATCH FILE/CLASS=NOMAJOR

    In my case, I have a connection through xdm on hilbert:1. I only
    have set display to this X server and I can open a display from a
    telnet session to X session.

    JB

    --
    Si votre demande me parvient en code 29, je vous titiouillerai volontiers
    une réponse.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Volker Halle@21:1/5 to All on Tue Jun 17 17:27:09 2025
    CHARON $ mc decw$wsinit
    Can't open display

    CHARON $ set watch file/class=major
    CHARON $ mc decw$wsinit
    %XQP, Thread #0, Access (0,0,0) Status: 00000910
    %XQP, Thread #0, Access (0,0,0) Status: 00000910
    Can't open display

    I get these messages with or without SET DISPLAY/CREATE

    You turn off the XQP messages with $ SET WATCH FILE/CLASS=NOMAJOR

    Volker.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lawrence D'Oliveiro@21:1/5 to JKB on Tue Jun 17 22:11:50 2025
    On Tue, 17 Jun 2025 07:23:44 -0000 (UTC), JKB wrote:

    %SET-W-NOTSET, error modifying DUA0:
    -CLI-E-IVDEVTYPE, invalid device type - specify a mailbox device
    p1 = HILBERT:1
    p2 =

    That looks like a clue. Why is it expecting a mailbox device and
    getting a disk instead? Is there some confusion over logical names,
    perchance?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From JKB@21:1/5 to All on Wed Jun 18 08:04:33 2025
    Le 17-06-2025, Lawrence D'Oliveiro <ldo@nz.invalid> a écrit :
    On Tue, 17 Jun 2025 07:23:44 -0000 (UTC), JKB wrote:

    %SET-W-NOTSET, error modifying DUA0:
    -CLI-E-IVDEVTYPE, invalid device type - specify a mailbox device
    p1 = HILBERT:1
    p2 =

    That looks like a clue. Why is it expecting a mailbox device and
    getting a disk instead? Is there some confusion over logical names, perchance?

    It's a new installation. I haven't modified logical names.

    $ pipe show logical | search sys$input dua0
    "DISK$OVMSVAXSYS" = "FERMAT$DUA0:"
    "SYS$COMMON" = "FERMAT$DUA0:[SYS0.SYSCOMMON.]"
    "SYS$DISK" = "FERMAT$DUA0:"
    "SYS$SPECIFIC" = "FERMAT$DUA0:[SYS0.]"
    "SYS$SYSDEVICE" = "FERMAT$DUA0:"
    "SYS$SYSROOT" = "FERMAT$DUA0:[SYS0.]"
    $

    I don't know what could be wrong here...

    Regards,

    JB

    --
    Si votre demande me parvient en code 29, je vous titiouillerai volontiers
    une réponse.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Volker Halle@21:1/5 to All on Wed Jun 18 10:47:14 2025
    Am 18.06.2025 um 10:04 schrieb JKB:
    Le 17-06-2025, Lawrence D'Oliveiro <ldo@nz.invalid> a écrit :
    On Tue, 17 Jun 2025 07:23:44 -0000 (UTC), JKB wrote:

    %SET-W-NOTSET, error modifying DUA0:
    -CLI-E-IVDEVTYPE, invalid device type - specify a mailbox device

    There is probaly a SET TERM/INQUIRE in SYLOGIN.COM or LOGIN.COM, which
    does NOT check, whether it's being executed in INTERACTIVE mode.
    If run in BATCH oder NETWORK mode, SYS$INPUT points to the disk, on
    which your login directory is located and you get the above error.

    Try this:

    $ IF F$MODE().EQS."INTERACTIVE" THEN $ SET TERM/INQUIRE

    Volker.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From JKB@21:1/5 to All on Wed Jun 18 10:33:10 2025
    Le 18-06-2025, Volker Halle <volker_halle@hotmail.com> a écrit :
    Am 18.06.2025 um 10:04 schrieb JKB:
    Le 17-06-2025, Lawrence D'Oliveiro <ldo@nz.invalid> a écrit :
    On Tue, 17 Jun 2025 07:23:44 -0000 (UTC), JKB wrote:

    %SET-W-NOTSET, error modifying DUA0:
    -CLI-E-IVDEVTYPE, invalid device type - specify a mailbox device

    There is probaly a SET TERM/INQUIRE in SYLOGIN.COM or LOGIN.COM, which
    does NOT check, whether it's being executed in INTERACTIVE mode.
    If run in BATCH oder NETWORK mode, SYS$INPUT points to the disk, on
    which your login directory is located and you get the above error.

    Try this:

    $ IF F$MODE().EQS."INTERACTIVE" THEN $ SET TERM/INQUIRE

    Thanks, I have set term/inquire in sys$login:login.com. Modification
    done, but doesn't fix access violation error.

    Regards,

    JB

    --
    Si votre demande me parvient en code 29, je vous titiouillerai volontiers
    une réponse.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From hb0815@21:1/5 to JKB on Thu Jun 19 12:55:27 2025
    On 6/18/25 12:33, JKB wrote:
    ...
    Thanks, I have set term/inquire in sys$login:login.com. Modification
    done, but doesn't fix access violation error.
    ...

    I didn't expect this to fix the ACCVIO. To me, it only proves that your login.com is being executed here.

    $ analyze /process_dump DECW$WSINIT.DMP
    Condition signalled to take dump:
    %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=1211100F, PC
    =80000010, PSL=03C00004

    OpenVMS VAX Debug Version V7.3-017


    examine/instruction 2147483664
    2147483664: CALLG B^4(SP),(R1)
    display reg


    How can I display registers ?

    You already know their exact contents from the register dump.

    To match with the register dump and/or the above ACCVIO message:
    set rad hex

    To see all register contents
    ex %r0:r15

    The CALLG uses an argument list, which is on the stack. Maybe you can
    find something useful on the stack.

    In the log file, is there any message about not being able to create a
    process dump?


    Nope 🙁

    You connect to XDM on the VAX, correct? That is, DECW$WSINIT runs in the context of the TCPIP$XDM user. In case there is a resource problem, it
    may not be possible to write a process dump, just because doing so
    requires resources, too. It's not obvious whether that is the case or
    not. The fact that you get a process dump for the same ACCVIO when
    running DECW$WSINIT interactively, indicates that the underlying problem
    for the ACCVIO is not a resources problem.

    I have set accounting before posting. Strangely, all ACCVIO are
    not loggued.

    I'm not sure I understand what you mean.


    DECW$WSINIT Image Termination
    -----------------------------
    Username: BERTRAND UIC: [BERTRAND]
    Account: Finish time: 14-JUN-2025 15:23:09.75
    Process ID: 00000131 Start time: 14-JUN-2025 15:23:07.67
    Owner ID: Elapsed time: 0 00:00:02.08
    Terminal name: Processor time: 0 00:00:01.52
    Remote node addr: Priority: 4
    Remote node name: Privilege <31-00>: 00108000
    Remote ID: Privilege <63-32>: 00000000
    Remote full name:
    Queue entry: Final status code: 1000000C
    Queue name:
    Job name:
    Final status text: %SYSTEM-F-ACCVIO, access violation, reason mask=!XB, virtual

    Page faults: 939 Direct IO: 8
    Page fault reads: 42 Buffered IO: 121
    Peak working set: 1482 Volumes mounted: 0
    Peak page file: 2578 Images executed: 3

    Image name: FERMAT$DUA0:[SYS0.SYSCOMMON.][SYSEXE]DECW$WSINIT.EXE

    The ACCVIO is logged - as well as it can be logged by the accounting
    facility. The “Final status code” is translaated to “%SYSTEM-F-ACCVIO”, but information about the PC etc. is not available at the time the
    program terminates.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From JKB@21:1/5 to All on Thu Jun 19 12:03:52 2025
    Le 19-06-2025, hb0815 <mw40171@mucweb.de> a écrit :
    On 6/18/25 12:33, JKB wrote:
    ...
    Thanks, I have set term/inquire in sys$login:login.com. Modification
    done, but doesn't fix access violation error.
    ...

    I didn't expect this to fix the ACCVIO. To me, it only proves that your login.com is being executed here.

    $ analyze /process_dump DECW$WSINIT.DMP
    Condition signalled to take dump:
    %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=1211100F, PC
    =80000010, PSL=03C00004

    OpenVMS VAX Debug Version V7.3-017


    examine/instruction 2147483664
    2147483664: CALLG B^4(SP),(R1)
    display reg


    How can I display registers ?

    You already know their exact contents from the register dump.

    To match with the register dump and/or the above ACCVIO message:
    set rad hex

    To see all register contents
    ex %r0:r15

    Done:

    ex %r0:r15
    0\%R0: 03C00000
    0\%R1: 1211100F
    0\%R2: 00000020
    0\%R3: 00000000
    0\%R4: 002EA6D0
    0\%R5: 00000000
    0\%R6: 000034E0
    0\%R7: 00000210
    0\%R8: 00000210
    0\%R9: 00000001
    0\%R10: 7FFED7D4
    0\%R11: 7FFE2BDC
    0\%AP: 7FE95E58
    0\%FP: 7FE95F10
    0\%SP: 7FE95E58
    0\%PC: 80000010

    The CALLG uses an argument list, which is on the stack. Maybe you can
    find something useful on the stack.

    Unfortunately...
    show stack
    %DEBUG-W-BADSTACK, WARNING: stack corrupted; session integrity not guaranteed

    In the log file, is there any message about not being able to create a
    process dump?


    Nope 🙁

    You connect to XDM on the VAX, correct?

    Right.

    That is, DECW$WSINIT runs in the
    context of the TCPIP$XDM user. In case there is a resource problem, it
    may not be possible to write a process dump, just because doing so
    requires resources, too. It's not obvious whether that is the case or
    not. The fact that you get a process dump for the same ACCVIO when
    running DECW$WSINIT interactively, indicates that the underlying problem
    for the ACCVIO is not a resources problem.

    I have set accounting before posting. Strangely, all ACCVIO are
    not loggued.

    I'm not sure I understand what you mean.

    I have set accounting/image. Thus, all ACCVIO should be stored. To
    be clear, as DECW$WSINIT crashes with ACCVIO after xdm connection, I
    must have one new record with ACCVIO error after each connection.
    Only a few ACCVIO seem to be recorded.


    DECW$WSINIT Image Termination
    -----------------------------
    Username: BERTRAND UIC: [BERTRAND]
    Account: Finish time: 14-JUN-2025 15:23:09.75
    Process ID: 00000131 Start time: 14-JUN-2025 15:23:07.67
    Owner ID: Elapsed time: 0 00:00:02.08
    Terminal name: Processor time: 0 00:00:01.52
    Remote node addr: Priority: 4
    Remote node name: Privilege <31-00>: 00108000
    Remote ID: Privilege <63-32>: 00000000
    Remote full name:
    Queue entry: Final status code: 1000000C
    Queue name:
    Job name:
    Final status text: %SYSTEM-F-ACCVIO, access violation, reason mask=!XB, virtual

    Page faults: 939 Direct IO: 8
    Page fault reads: 42 Buffered IO: 121
    Peak working set: 1482 Volumes mounted: 0
    Peak page file: 2578 Images executed: 3

    Image name: FERMAT$DUA0:[SYS0.SYSCOMMON.][SYSEXE]DECW$WSINIT.EXE

    The ACCVIO is logged - as well as it can be logged by the accounting facility. The “Final status code” is translaated to “%SYSTEM-F-ACCVIO”,
    but information about the PC etc. is not available at the time the
    program terminates.

    Best regards,

    JB

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Simon Clubley@21:1/5 to JKB on Thu Jun 19 12:22:33 2025
    On 2025-06-18, JKB <JKB@hilbert.invalid> wrote:

    Thanks, I have set term/inquire in sys$login:login.com. Modification
    done, but doesn't fix access violation error.


    Are you running on physical VAX hardware, or on an emulator ?

    If it's an emulator, could it be an older version that might have
    emulation bugs in it, or something other than one of the well-known
    emulators ?

    Simon.

    --
    Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
    Walking destinations on a map are further away than they appear.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From JKB@21:1/5 to All on Thu Jun 19 14:38:50 2025
    Le 19-06-2025, Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> a écrit :
    On 2025-06-18, JKB <JKB@hilbert.invalid> wrote:

    Thanks, I have set term/inquire in sys$login:login.com. Modification
    done, but doesn't fix access violation error.


    Are you running on physical VAX hardware, or on an emulator ?

    I have several VAXen, but I do my tries on an emulated one (simh 4.0).
    For I long time, I have used this emulator without any trouble.

    JB

    --
    Si votre demande me parvient en code 29, je vous titiouillerai volontiers
    une réponse.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)