Download sysgem sysman utilities

Flexible and modular tools for monitoring and managing systems, administering user accounts and auditing security in one single screen - across Windows, UNIX/Linux, OpenVMS and IBM i​Now accessible in full functionality with SEM's Virtual UI using any web browser.SEM Application ModulesSEM offers the three core application modules Sysgem System Manager (SSyM), Sysgem Account Manager (SAcM) and Sysgem File Synchronizer (SFiS) which all run via the SEM framework SYSGEM SYSTEM MANAGER (SSyM) Unite, simplify and integrate core system administration solutions across a multi-platform environment SYSGEM ACCOUNT MANAGER (SAcM) Unify user account management across a multi-platform, multi-application environment SYSGEM FILE SAFEGUARD (SFiS)Manage the controlled distribution and deployment of configuration files across infrastructureSEM FeaturesUniteSimplifyIntegrateFull visibility of your system’s hardware and software capacity usage with intelligent alerting and analysis to prevent operational holdups, cleanup and reprocessing work - reducing your organization’s reliance on its IT help desk and sysadmin teams Identity and Access Management (IAM) tools designed not only for managing standard users’ identity and access but also to inherently control, track and safeguard privileged access across an organization’s network infrastructure Decrease security threats and protect your organization’s digital assets and their management with least privileged access management Streamline and secure the performance and health of your heterogeneous and integrated IT infrastructure independent of its heritage complexity with automated monitoring and reporting functionality Ensure full audit and regulatory compliance with cross-platform configuration management Manage, monitor and secure administrative access of MSPs and IT outsourcing vendors to your organizations Equally supporting heritage (legacy) IT environments critical to your organization’s operations by simplifying traditionally high-skilled and complex administration, adaptation and development workAccessible as a desktop application or anywhere with our new SEM virtual UILEARN MORE ABOUT SYSGEM'S PRODUCTS

Cluster. Similarly, operations on clusterwide logical names and tables operate clusterwide by design. Make sure that if you redefine the logical DCLTABLES, you do so in SYLOGICALS.COM, not in SYSTARTUP_VMS.COM or elsewhere. Otherwise, you will receive a command interpreter failure when executing a DO command on a remote node.Examples #1 SYSMAN> SET ENVIRONMENT/CLUSTER/NODE=NODE21SYSMAN> DO/OUTPUT SHOW DEVICE The first command in this example defines the management environment tobe the cluster where NODE21 is a member. The second command executes aDCL command on each node in the cluster. Output goes to the fileSYSMAN.LIS rather than to the terminal. #2 SYSMAN> SET ENVIRONMENT/NODE=NODE21SYSMAN> SET PROFILE /DEFAULT=[CJ.PROGRAMS] -_SYSMAN> /PRIVILEGES=NOSYSPRVSYSMAN> DO/OUTPUT @PROCESS_INFO The commands in this example define the environment as a single nodeand adjust the current privileges and directory. The DO commandexecutes the command procedure PROCESS_INFO.COM, located in directory[CJ.PROGRAMS] and writes any output to SYSMAN.LIS in the directory fromwhich SYSMAN is running. #3 $ CREATE/NAME_TABLE/PARENT=LNM$SYSTEM_DIRECTORY SYSMAN$NODE_TABLE$ DEFINE/TABLE=SYSMAN$NODE_TABLE ALPHA_NODES NODE21,NODE22,NODE23$ DEFINE/TABLE=SYSMAN$NODE_TABLE VAX_NODES NODE24,NODE25,NODE26$ RUN SYS$SYSTEM:SYSMANSYSMAN> SET ENVIRONMENT/NODE=ALPHA_NODES%SYSMAN-I-ENV, current command environment: Individual nodes: NODE21,NODE22,NODE23 Username BOUCHARD will be used on nonlocal nodesSYSMAN> DO INSTALL REPLACE SYS$LIBRARY:DCLTABLES.EXE%SYSMAN-I-OUTPUT, command execution on node NODE21%SYSMAN-I-OUTPUT, command execution on node NODE22%SYSMAN-I-OUTPUT, command execution on node NODE23SYSMAN> DO INSTALL REPLACE SYS$SYSTEM: COM_FORTRAN.EXE%SYSMAN-I-OUTPUT, command execution on node NODE21%SYSMAN-I-OUTPUT, command execution on node NODE22%SYSMAN-I-OUTPUT, command execution on node NODE23SYSMAN> SET ENVIRONMENT/NODE=VAX_NODES%SYSMAN-I-ENV, current command environment: Individual nodes: NODE24,NODE25,NODE26 Username BOUCHARD will be used on nonlocal nodesSYSMAN> DO INSTALL REPLACE SYS$LIBRARY:DCLTABLES.EXE%SYSMAN-I-OUTPUT, command execution on node NODE24%SYSMAN-I-OUTPUT, command execution on node NODE25%SYSMAN-I-OUTPUT, command execution on node NODE26SYSMAN> DO INSTALL REPLACE SYS$SYSTEM:FORTRAN$MAIN.EXE%SYSMAN-I-OUTPUT, command execution on node NODE24%SYSMAN-I-OUTPUT, command execution on node NODE25%SYSMAN-I-OUTPUT, command execution on node NODE26 This example shows how you can define logical names for VAX, Alpha, andI64 nodes in a multi-architecture heterogeneous cluster, so that youcan use the DO command to install architecture-specific images. #4

DOExecutes a DCL command or DCL command procedure on all nodes in thecurrent management environment.Requires the privileges of the DCL command being executed.FormatDO [command-line]Parametercommand-lineSpecifies a command string that SYSMAN passes to the command lineinterface (CLI) for execution.The command DO RUN SYS$SYSTEM:SYSMAN [SYSMAN-command] is not supported.Instead, follow these steps: Enter RUN SYS$SYSTEM:SYSMAN at the dollar ($) prompt. At the SYSMAN> prompt, set the environment to the selected node or nodes with the SET ENVIRONMENT command. Enter a SYSMAN command at the SYSMAN> prompt.For complete information about DCL command syntax, see theHP OpenVMS DCL Dictionary.Qualifiers/CONFIRMVerifies that you want to perform a DO command on each node you havespecified with the SYSMAN command SET ENVIRONMENT.When you use the /CONFIRM qualifier, the system prompts you as follows: Execute command for node ? [N]:The following responses are valid: YES NO QUIT ALL TRUE FALSE [Ctrl/Z] 1 0 [Ctrl/C] [Return]Usage Notes Affirmative answers are YES, TRUE, and 1. Negative answers are NO, FALSE, 0, and pressing the Return key. You can use any combination of uppercase and lowercase letters for word responses. You can abbreviate word responses to one or more letters (for example, T, TR, or TRU for TRUE), but these abbreviations must be unique. Entering QUIT or pressing Ctrl/C or Ctrl/Z indicates that you want to stop processing the command at that point. When you enter ALL, the command continues to process, but the system displays no further prompts. If you type a response that is not valid, SYSMAN issues an error message and redisplays the prompt./OUTPUT[=filespec]Records output from the command in the specified file, which is locatedon the node from which you are executing SYSMAN. Position the qualifierimmediately after the DO command. The default file specification isSYSMAN.LIS in the current device and directory. SYSMAN prefaces outputwith the message "%SYSMAN-I-OUTPUT, command execution on nodexxxxxx."/PAUSEControls

To modify.The UIC and process name together make the entry unique. Specify theUIC as it is displayed when you enter the DUMP_PRIORITY LIST command./NEWUICModifies the UIC of an entry that you specify by its process name andcurrent UIC. You can specify the /NEWUIC with an octal number (forexample, [377,377]) or in the identifier form (for example, [SYSTEM] or[VMS,USER]).Wildcards are allowed as follows: Wildcard Example Description /UIC = [*] To select processes with the specified name in any UIC. /UIC = [group,*] To select processes with the specified name in the group called "group". /UIC = [100,*] To select processes with the specified name in group 100>. NoteYou cannot use wildcards within identifier names or within UIC numbers.For example, /UIC=[USER*,*] or /UIC=[17*,100] are not allowed. /WILD_CARD/NOWILD_CARDThe /WILD_CARD qualifier, used together with the MODIFY command,modifies the wildcard setting on the entry that you are modifying. Ifyou omit /WILD_CARD, the current wildcard setting is retained.Example SYSMAN> DUMP_PRIORITY LIST%SYSMAN-I-OUTPUT, command execution on node VMS73Process name UIC Wild CardMSCP* [SYSTEM] YNETACP [SYSTEM] NSYSMAN> DUMP_PRIORITY MODIFY "MSCP*"/UIC=[SYSTEM]/NEWUIC=[TEST]/NOWILD_CARD (1)SYSMAN> DUMP_PRIORITY LIST%SYSMAN-I-OUTPUT, command execution on node VMS73Process name UIC Wild CardMSCP* [TEST] NNETACP [SYSTEM] NSYSMAN> DUMP_PRIORITY MODIFY "MSCP*"/UIC=[TEST]/NEWUIC=[*] (2)SYSMAN> DUMP_PRIORITY LIST%SYSMAN-I-OUTPUT, command execution on node VMS73Process name UIC Wild CardMSCP* [*] NNETACP [SYSTEM] NSYSMAN> DUMP_PRIORITY MODIFY "MSCP*"/UIC=[*]/WILD_CARD (3)%SYSMAN-I-OUTPUT, command execution on node VMS73Process name UIC Wild CardMSCP* [*] YNETACP [SYSTEM] N Refer to the numbers at the end of the DUMP_PRIORITY MODIFY commandlines in the example, which correspond to the numbered explanationsthat follow. (The DUMP_PRIORITY LIST command, after each MODIFYcommand, displays the results of the modifications in the System DumpPriority registry.)

$ RUN SYS$SYSTEM:SYSMANSYSMAN> SET ENVIRONMENT/CLUSTER%SYSMAN-I-ENV, current command environment: Clusterwide on local cluster Username STEIN will be used on nonlocal nodesSYSMAN> DO/CONFIRM SHOW TIMEExecute command for node EXPERT? [N]: Y [Return]%SYSMAN-I-OUTPUT, command execution on node EXPERT 22-MAR-2002 09:40:28Execute command for node MODERN? [N]: Y [Return]%SYSMAN-I-OUTPUT, command execution on node MODERN 22-MAR-2002 09:40:56Execute command for node IMPOSE? [N]: N [Return]Execute command for node ADU26A? [N]: Y [Return] . . . The commands in this example show how to control whether the systemdisplays time for each node in a cluster. #5 SYSMAN> DO/PAUSE SHOW TIME%SYSMAN-I-OUTPUT, command execution on node EXPERT 22-MAR-2002 09:40:13Press return to continue [Return]%SYSMAN-I-OUTPUT, command execution on node MODER 22-MAR-2002 09:40:41Press return to continue [Return]%SYSMAN-I-OUTPUT, command execution on node IMPOSE 22-MAR-2002 09:39:46Press return to continue [Return] . . . The commands in this example show how you can control the rate at whichinformation is displayed on your system.DUMP_PRIORITY ADD (Alpha and I64)On Alpha and I64 systems, adds an entry to the System Dump Priorityregistry file.The registry data file is the permanent database that survives reboots.It is loaded into memory during a boot. (You can use the DUMP_PRIORITYLOAD command at any time to load the contents of this file into memory.)When you add an entry to the registry file, you must specify both theprocess name and UIC. If you attempt to add an entry that alreadyexists, the system displays the following message: "SMI-I-SDPDUPIGN,duplicate record creation ignored."How Dump Priority WorksBUGCHECK uses the loaded contents of the System Dump Priority registryto select priority processes to dump early on during a selective dump.Adding a dump priority for a process increases the likelihood that theprocess will be included in a dump, if there is insufficient space forall processes. (The ADD command only adds an entry to the System DumpPriority registry permanent file. For BUGCHECK to be

The rate at which the system displays information. Using the/PAUSE qualifier causes the system to display information about onenode at a time; the system prompts you to press Return when you areready to display information about the next node.DescriptionThe DO command executes the accompanying DCL command or DCL commandprocedure on all nodes in the current environment. Each DO commandexecutes as an independent process, so no process context is retainedbetween DO commands. For this reason, you must express all DCL commandsin a single command string, and you cannot run a program that expectsinput.In an OpenVMS Cluster environment, SYSMAN executes the commandssequentially on all nodes in the cluster. Each command executescompletely before SYSMAN sends it to the next node in the environment.Any node that is unable to execute the command returns an errormessage. SYSMAN displays an error message if the timeout period expiresbefore the node responds.The system cannot display output returned from a command of more than2048 characters without concatenation.Three exceptions to be aware of when using the DO command in clustersare the following ones: In a multi-architecture heterogeneous cluster running OpenVMS VAX,Alpha, and I64 systems, some uses of the DO command may require specialhandling. For example, if you are installing images that are nameddifferently in each architecture, you can still use the DO command ifyou create logical name tables for VAX, Alpha, and I64 nodes. See theexample sequence that follows this description for an example. Some DCL commands, such as MOUNT/CLUSTER or SET QUORUM/CLUSTER, operate clusterwide by design. It is best to avoid using these kinds of commands with the DO command in SYSMAN when the environment is set to cluster. As alternatives, you could leave SYSMAN temporarily with the SPAWN command and execute these commands in DCL, or you could define the environment to be a single node within the