Tag Info

Hot answers tagged

7

One answer: OpenVMS Performance Management and maybe other stuff at HP OpenVMS Systems.


3

Pathworks for OpenVMS (if installed on VMS) provides integration with active directory. Security can be controlled with inter-domain trusts (Windows side) and ACLs with HOSTMAPs that map active directory names to OpenVMS accounts. You could limit the capabilities of the relevant OpenVMS accounts to match any security policy. OpenVMS files can have varying ...


3

Samba is the canonical system used to do this on Unix-like systems and did support VMS at one point. However I'm not sure that it still does in the main trunk - you could try an older version. Directories can be shared from the VMS server via the samba server or mounted off a Windows machine via smbmount. If you don't want to compile your own version, HP ...


3

DECWindows is X compliant. Try looking at the help for SET DISPLAY in particular /TRANSPORT /NODE /CREATE /SERVER /SCREEN e.g. SET DISPLAY/CREATE/TRANSPORT=TCPIP/NODE=your.client.ip.address RUN SYS$SYSTEM:DECW$CLOCK RUN SYS$SYSTEM:DECW$DTTERM In gerneral HELP on VMS is excellent. I'm not sure if the DECW$DTTERM is correct dir sys$system:decw$*.* for a ...


3

Have a look at VMS2linux it provides tools that may help.


1

You shouldn't have to change anything in the queues if you change how the names 600TCP, 650TCP, etc. are resolved on your network, either via DNS or in the local host database. And that assumes the printers themselves have changed IP address, which doesn't sound like the case from your description. I don't actually see how "Server" is involved at all ...


1

You didn't say if you are using a Unix or Windows client, but I am assuming Unix. I believe the Windows client has a way to change this, but I'm not certain and it's been a long time since I needed to use putty. As for remapping, no, there is no trivial way to do this. VMS has a way to define what is used for backspace, but not for CR, that I can find ...


1

Whether it's Samba or NFS, nothing in the Windows world is likely to compromise the VMS system - the chances of someone leaving malware on the share that could hurt the VMS system are insignificant. Or did you meant the other way? That something about the mapping could affect the Windows server? In that case, there'd be nothing more risky than any other ...


1

You could try setting up the OpenVMS system as an NFS server and the Windows 2008 server as an NFS client. The biggest problems with this approach are the fact that OpenVMS has versioned files (so that deleting a file only deletes the latest version) and the fact that OpenVMS filesystems are case-insensitive. From what I've read, OpenVMS NFS is also very ...



Only top voted, non community-wiki answers of a minimum length are eligible