- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: DCL and SYSMAN
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-11-2008 07:59 AM
тАО06-11-2008 07:59 AM
DCL and SYSMAN
Clusterwide on local cluster
Username GPEREIRA will be used on nonlocal nodes
how can I have this not display?
Here is an example of what I am doing:
$ SET NOON
$ message_setting = F$ENVIRONMENT("MESSAGE")
$ set message /nofacility /noseverity /noidentification /notext
$ mcr sysman
do set message /nofacility /noseverity /noidentification /notext
set e/c
set prof/def=sysmgr$scratch
do @last_lta_device
exit
$ message_setting = F$ENVIRONMENT("MESSAGE")
$exit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-11-2008 08:15 AM
тАО06-11-2008 08:15 AM
Re: DCL and SYSMAN
your 2 commands before
$ mcr sysman
are executed on the local node, not on the other Cluster nodes, so it is not used
Your command
do set message /...
is a command doing set message and terminating, so nothing happens, and it is not executed in the context of the next commands.
May be there is a Sysman logical name for this, but I am not aware of it.
You could try to use RCOM, an improved Sysman, written long ago by Nick Brown.
Why do you want to avoid this display ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-11-2008 08:16 AM
тАО06-11-2008 08:16 AM
Re: DCL and SYSMAN
this text is not a message, but simply direct output from the SYSMAN utility. You could use
$ DEFINE/USER SYS$OUTPUT NLA0:
before invoking SYSMAN, but then the rest of the output provided by the commands executed in SYSMAN would also not display on ther terminal.
You could also direct SYS$OUTPUT to a file and then read and parse the file and only output the information your use should see.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-11-2008 08:26 AM
тАО06-11-2008 08:26 AM
Re: DCL and SYSMAN
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-11-2008 08:35 AM
тАО06-11-2008 08:35 AM
Re: DCL and SYSMAN
Each DO command you use in SYSMAN is executed in a new process, even when you have SET ENVIRONMENT to a single node. Therefore any DO command whose only purpose is to affect the process environement is useless because that process is gone as soon as that DO command completes.
You must combine these DO commands with your other DO command in a command file.
$ TYPE TEMP.COM
$ set message /nofacility /noseverity /noidentification /notext
$ @last_lta_device
$ exit
$ mcr sysman
set enviroment/cluster
set profile/default=sysmgr$scratch
do @temp.com
exit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-11-2008 08:50 AM
тАО06-11-2008 08:50 AM
Re: DCL and SYSMAN
In addition to RCOM mentioned earlier, the TELL.COM (freeware) or analogous DECnet tool such as XQPTYPE, or maybe node-specific batch queues might be a better choice here, depending on what you're up to.
http://mvb.saic.com/freeware/freewarev60/tell/
http://mvb.saic.com/freeware/freewarev80/hoffman_examples/xqtype.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-11-2008 05:25 PM
тАО06-11-2008 05:25 PM
Re: DCL and SYSMAN
PIPE is your friend.
You can pipe commands into SYSMAN, capture the output and do whatever you like with it. This can be especially useful if you want to substitute symbols into your SYSMAN commands, or process the output.
Consider:
$ PIPE @generate_sysman_commands | -
MCR SYSMAN @SYS$PIPE: | -
@parse_sysman_output
Your output parser could skip everything up to %SYSMAN-I-OUTPUT, then do whatever you want with the remainder of the output.
I've included an example procedure that demonstrates the principle. It accepts commands as P1 through P7, executes all commands on all nodes across the cluster, tags each line of output with the node it came from, and sorts the output into blocks from each node. The extraneous output from SYSMAN SET commands is skipped.