[Info-vax] CMS glitch

John Reagan xyzzy1959 at gmail.com
Sun Aug 26 12:21:33 EDT 2018


On Sunday, August 26, 2018 at 11:52:08 AM UTC-4, Marc Van Dyck wrote:
> I'm a long time VAXSET user and often issued the following command when
> I wanted to have a quick look at a CMS element :
> 
> $ cms fetch/out=tt: <CMS library element> ""
> 
> I have - see my previous topic - returned to development activities
> after a long pause, and when I issue that command, I now get the
> following error :
> 
> %CMS-F-BUG, there is something wrong with CMS or something it calls
> -CMS-F-NOQIO, $QIO failed
> -RMS-F-SYS, QIO system service request failed
> -SYSTEM-F-NOT64DEVFUNC, 64-bit address not supported by device for this 
> function
> 
> This is the VSI version of CMS and OpenVMS running on a BL870c-I4.
> 
> The terminal (tt:) is a Putty emulation running on Windows 7.
> 
> $ sh ter
> Terminal: _FTA29:     Device_Type: VT500_Series  Owner: MVD - Term 1
>                                               Username: VANDYCK
> 
>    Input:    9600     LFfill:  0      Width: 132      Parity: None
>    Output:   9600     CRfill:  0      Page:   40
> 
> Terminal Characteristics:
>    Interactive        Echo               Type_ahead         No Escape
>    Hostsync           TTsync             Lowercase          Tab
>    Wrap               Scope              No Remote          Eightbit
>    Broadcast          No Readsync        No Form            Fulldup
>    No Modem           No Local_echo      No Autobaud        No Hangup
>    No Brdcstmbx       No DMA             No Altypeahd       Set_speed
>    No Commsync        Line Editing       Insert editing     No Fallback
>    No Dialup          Secure server      No Disconnect      No Pasthru
>    No Syspassword     No SIXEL Graphics  No Soft Characters No Printer 
> Port
>    Application keypad ANSI_CRT           No Regis           No 
> Block_mode
>    Advanced_video     Edit_mode          DEC_CRT            DEC_CRT2
>    DEC_CRT3           DEC_CRT4           DEC_CRT5           No 
> Ansi_Color
>    VMS Style Input    <CTRL-H> Backspace
> 
> $ sh dev tt: /fu
> 
> Terminal FTA29:, device type VT500 Series, is online, record-oriented 
> device,
>     carriage control.
> 
>     Error count                    0    Operations completed            
>    1641
>     Owner process     "MVD - Term 1"    Owner UIC              
> [APLSCY,VANDYCK]
>     Owner process ID        21A9FE9D    Dev Prot              
> S:RWPL,O:RWPL,G,W
>     Reference count                4    Default buffer size             
>     132
> 
> $ sh sys/noproc
> OpenVMS V8.4-2  on node POLKA   21-AUG-2018 10:39   Uptime  7 17:52:15
> 
> It's the first time I do that since we migrated from Alpha to Itanium
> so I have no idea when this error appeared...
> 
> -- 
> Marc Van Dyck

I assume it works with /OUT=filename.ext ?

CMS has had some issues with 64-bit addresses.  It started using P2 heap several versions back and has issues with 32-bit vs 64-bit descriptors inside of CMS.  I don't know enough about the internals of CMS to survey the various $QIOs to see if there is some itemcode that needs changing if you start to pass in 64-bit pointers? 



More information about the Info-vax mailing list