openvms mgt tools, tips and tricks

OpenVMS System Management Techniques, Tools, and Tricks

Pre-Symposium Seminar 1024 HP ETS 2002 - St Louis, MO Slide 1

Seminar 1024


David J. [email protected]

DJE Systemshttp://www.djesys.com/



AgendaBasic DCL Concepts

CommandsCommand ProceduresVerbsSymbolsFlow Control (IF, GOTO, GOSUB, CALL)Useful Lexical Functions



AgendaLogical names

Logical name tablesLogical name table search order

Modifying the search order

Logical name typesSingle TranslationSearch list“Rooted” (Concealed) logical names

Lexical Function CaveatF$TRNLNM() differs from F$LOGICAL()



AgendaLogical names, cont’d

Cluster-wide logical namesCaveats

SYS$COMMON NotesCaveats (VMS$COMMON)

Site-Specific PathsOrganizing local system management

code



AgendaNetwork Topics

TCP/IPTCP/IP Services (fka UCX)MultinetTCPwareCMU/IP (VAX only)

DECnetAccess controlFAL logging



AgendaNetwork Topics, cont’d

Remote proceduresTypesSecurity concerns

Network AlertsOPCOM alerts for DECnet network

accessOPCOM alerts for FTP network access



AgendaSystem Startup

STARTUP phasesSTARTUP parametersSite-Specific startups

Logging SYSTARTUP_VMS.COMNode-specific startupsSaving a crash dump at start-up timeSoft-coding # of logins allowed at startup

SYSMAN and STARTUP



AgendaSystem Shutdown

SHUTDOWN parametersSHUTDOWN$xxxx logical namesAUTOGEN Shutdowns

AGEN$SHUTDOWN_TIME logical name

Cluster ShutdownREMOVE_NODEUsing SYSMAN



AgendaSystem/Startup File Caveats

Deprecated Lexical FunctionsLexical Function names misspelled

AUTOGENMODPARAMS.DATReports and outputs



AgendaOpenVMS Management Tools

StorageWorks Command Console (SWCC)OpenVMS Management StationAMDS

Accessibility Manager for Distributed Systems

Availability ManagerLike AMDS, runs on MS-Windows



AgendaOpenVMS Security

EssentialsUICs and File/Directory ProtectionAccess Control Lists (ACLs)Access Control Entries (ACEs)Rights Identifiers and ACEsPropagating ACEs and Default Protections



Seminar 1024

Basic DCLConcepts



Basic DCL Concepts

Command Elements

$ verb parameter_1 parameter_2

DCL commands consist of a verb and one or more parameters.



DCL Command Proc.’s$ @procedure_name

Top level (or terminal) is DEPTH 0.

Each new command procedure invoked is a new procedure DEPTH.

Maximum depth is still 32.



DCL Command Proc.’sParameters

$ @procedure_name p1 p2 p3 … p8

Notes:• Only eight(8) parameters are passed from

the command line, P1 through P8• Parameters with embedded spaces must

be quoted strings.• Parameters are separated by a space.



DCL Command Proc.’sParameters, cont’d

$ @procedure_name p1 p2 p3 … p8

Notes, Cont’d:• Reference parameters via the variable

names P1 through P8.• No built-in “shift” function. If you need it,

write it as a GOSUB.



DCL Verbs

Internal commandsASSIGN, CALL, DEFINE, GOSUB, GOTO, IF, RETURN, SET, STOP, others…

External commandsAPPEND, BACKUP, COPY, DELETE, PRINT, RENAME, SET, SUBMIT, others...



DCL Verbs, Cont’d

“Foreign” Commands$ symbol = value

Examples:$ DIR :== DIRECTORY/SIZE=ALL/DATE$ ZIP :== $ZIP/VMS



Command Qualifiers$ command/qualifier

$ command/qualifier=value$ command/qualifier=(value,value)

$ command/qualifier=keyword=value$ command/qualifier=-

(keyword=value,keyword=(value,value))



Non-positional QualifiersApply to the entire command, no matter

where they appear.

$ command param1/qual param2

Example:$ COPY A.DAT A.NEW/LOG$ DELETE/LOG C.TMP;



Positional QualifiersApply only to the object they qualify.

$ command param1/qual=value1 -param2/qual=value2

Examples:$ PRINT/COPIES=2 RPT1.LIS, RPT2.LIS$ PRINT RPT1.LIS/COPIES=1,-

RPT2.LIS/COPIES=3



Common QualifiersMany commands support a set of

common qualifiers:

/BACKUP /BEFORE /CREATED /EXCLUDE /EXPIRED /INCLUDE /MODIFIED /OUTPUT /PAGE /SINCE

See the on-line HELP for specifics.



DCL Statement Elements$ vbl = value

DCL statements are typically assignments where a variable receives a value.



Assignment Statements

$ vbl = F$lexical_function( params )

Examples:$ FSP = F$SEARCH(“*.TXT”)$ DFLT = F$ENVIRONMENT (“DEFAULT”)$ NODE = F$GETSYI(“NODENAME”)



Assignment Statements$ vbl = string_expression

Examples:$ A = “String 1 “ + “String 2”$ B = A - “String “ - “String “$ C = ‘A’

Maximum string length 255 bytes (<=V7.3)4096 bytes (>=V7.3-1)



Assignment Statements$ vbl = numeric_expression

Examples:$ A = 1$ B = A +1$ C = B + A + %X7F25$ D = %O3776



Assignment Statements$ vbl[start_bit,bit_count]=numeric_exp

Examples:$ ESC[0,8]=%X1B$ CR[0,8]=13$ LF[0,8]=10$ FF[0,8]=12$ CRLF[0,8]=13$ CRLF[8,8]=10



Assignment Statements$ ESC[0,8]=%X1B$ SHOW SYMBOL ESC ESC = "."$ CR[0,8]=13$ SHOW SYMBOL CR CR = "."$ LF[0,8]=10$ SHOW SYMBOL LF LF = "."



Assignment Statements$ FF[0,8]=12$ SHOW SYMBOL FF FF = "."$ CRLF[0,8]=13$ SHOW SYMBOL CRLF CRLF = "."$ CRLF[8,8]=10$ SHOW SYMBOL CRLF CRLF = ".."



Assignment StatementsDCL provides for substring replacement.$ A := abcde$ SHOW SYMBOL A “ABCDE”$ A[3,2]:=XX$ SHOW SYMBOL A “ABCXX”



Assignment Statements$ vbl = boolean_expression

Examples:$ MANIA = (“TRUE” .EQS. “FALSE”)$ TRUE = (1 .EQ. 1)$ FALSE = (1 .EQ. 0)$ YES = 1$ NO = 0



Assignment Statements

Local Assignment:$ vbl = value

Global Assignment:$ vbl == value



Assignment StatementsQuoted String:

$ vbl = “quoted string”Case is preserved.

Examples:$ PROMPT = “Press RETURN to continue “$ INVRSP = “% Invalid response!”



Assignment StatementsUnquoted string:

$ vbl := unquoted stringCase is NOT preserved, becomes uppercase. Leading/trailing spaces are trimmed off.

Examples:$ SAY := Write Sys$Output$ SYSMAN :== $SYSMAN ! Comment



Foreign Commands

$ vbl := $filespec[ param[ param[ …]]]

“filespec” defaults to SYS$SYSTEM:.EXE

Maximum string length: 510 bytes (<=V7.3)4096 bytes (>=V7.3-1)



Symbol ScopeSET SYMBOL/SCOPE=

NOLOCALAll “outer” level local symbols are “invisible”

LOCALUndoes NOLOCAL

NOGLOBALAll “outer” level global symbols are

“invisible”

GLOBALUndoes NOGLOBAL



Symbol ScopeSET SYMBOL/GENERAL/SCOPE=xxxx

Specifies that the values of the /SCOPE qualifier pertain to the translation of all symbols except the first token on a command line.

/GENERAL is incompatible with /ALL or /VERB.



Symbol ScopeSET SYMBOL/VERB/SCOPE=xxxx

Specifies that the values of the /SCOPE qualifier pertain to the translation of the first token on a command line as a symbol before processing only. It does not affect general symbol substitution.

/VERB is incompatible with /ALL or /GENERAL.



Symbol ScopeSET SYMBOL/ALL/SCOPE=xxxx

Specifies that the values of the /SCOPE qualifier pertain both to the translation of the first token on a command line and to general symbol substitution.

/ALL is incompatible with /GENERAL or /VERB.



Conditional Expressions

$ IF condition THEN statement

Variations:$ IF condition THEN $ statement$ IF condition THEN -$ statement



Conditional Expressions$ IF condition$ THEN$ statement(s)$ ENDIF



Conditional Expressions$ IF condition$ THEN$ IF condition$ THEN$ statement(s)$ ENDIF$ ENDIF



Conditional Expressions$ IF condition$ THEN$ IF condition$ THEN$ statement(s)$ ENDIF$ statement(s)$ ENDIF



Conditional Expressions$ IF condition$ THEN statement(s)$ IF condition$ THEN$ statement(s)$ ENDIF$ ENDIFThis may not work in pre-V6 VMS!



Conditional Expressions

$ IF condition$ THEN$ statement(s)$ ELSE$ statement(s)$ ENDIF



Labels, GOTO$ GOTO label_1

.

.

.$label_1:



GOSUB, RETURN$ GOSUB label_1

.

.

.$label_1:$ statement(s)$ RETURN



GOSUB, RETURNEmulate UN*X/DOS shell SHIFT:

$SHIFT:$ P1 = P2$ P2 = P3$ P3 = P4$ P4 = P5$ P5 = P6$ P6 = P7$ P7 = P8$ P8 = ""$ RETURN



SUBROUTINE - ENDSUB...$ CALL label_1[ param[ param[ …]]

.

.

.

$label_1: SUBROUTINE$ statement(s)$ END SUBROUTINE



Lexical FunctionsFunctions built into the DCL Lexicon

F$CONTEXT F$CSID F$CVSI F$CVTIME F$CVUI F$DEVICE F$DIRECTORY F$EDIT F$ELEMENT F$ENVIRONMENT F$EXTRACT F$FAO F$FILE_ATTRIBUTES F$GETDVI F$GETJPI F$GETQUI F$GETSYI F$IDENTIFIER F$INTEGER F$LENGTH F$LOCATE F$MESSAGE F$MODE F$PARSE F$PID F$PRIVILEGE F$PROCESS F$SEARCH F$SETPRV F$STRING F$TIME F$TRNLNM F$TYPE F$USER F$VERIFY



Common Lexical Functions$ vbl = F$CVTIME(string[, keyword[, keyword]])

“string” = Absolute time expression

“keyword” = (1st instance) is one of “ABSOLUTE”, “COMPARISION”, “DELTA”

“keyword” = (2nd instance) is one of “DATE”, “DATETIME”, “DAY”, “MONTH”, “YEAR”, “HOUR”, “MINUTE”, “SECOND”, “HUNDREDTH”, “WEEKDAY”



Common Lexical FunctionsF$CVTIME(), Continued…

Defaults:$ vbl = F$CVTIME(string, -

”COMPARISON”, -”DATETIME” )

Pre-defined date strings:TODAY, YESTERDAY, TOMORROW, BOOT



Common Lexical FunctionsF$CVTIME(), Continued…

Date Formats:Comparison

YYYY-MM-DD HH:MM:SS.CCAbsolute

DD-MMM-YYYY HH:MM:SS.CCDelta

+/-DDDDD HH:MM:SS.CC



Common Lexical Functions$ vbl = F$GETDVI( dev_name, keyword )

“dev_name” is a valid device name“keyword” is a quoted string

Examples:$ FBLK = F$GETDVI( “DUA0”,”FREEBLOCKS”)$ MNTD = F$GETDVI( “DKA500”,”MNT”)$ DVNM := DUA0:$ VLNM := VOLNAM$ VNAM = F$GETDVI( DVNM, VLNM )



Common Lexical Functions$ vbl = F$QETQUI( -

function,-item,-value,-keyword(s))

See the on-line help for descriptions.



Common Lexical Functions$ VBL = F$GETJPI( pid, keyword )

Examples:$ USN = F$GETJPI( 0, “USERNAME” )$ MOD = F$GETJPI( 0, “MODE” )



Common Lexical Functions$ vbl = F$GETSYI( item[, node[, csid]] )

Examples:$ NODE = F$GETSYI( “NODENAME” )$ FGP = F$GETSYI( “FREE_GBLPAGES” )$ FGS = F$GETSYI( “FREE_GBLSECTS” )



Common Lexical Functions$ vbl = F$ELEMENT( idx, delim, string )

Find the nth (delim) delimited element of a string.

Examples:$ A = F$ELEM( 2, “,”, “A,B,C,D,E,F” )$ B = F$ELEM( 1, “ ”, “Turn it off” )



Seminar 1024

OpenVMSLogical Names



Logical Names

A form of symbol with limited or system-wide scope.

$ show logical sys$sysroot "SYS$SYSROOT" = "DJAS01$DKA300:[SYS0.]" (LNM$SYSTEM_TABLE) = "SYS$COMMON:"1 "SYS$COMMON" = "DJAS01$DKA300:[SYS0.SYSCOMMON.]"

(LNM$SYSTEM_TABLE)



Logical Name TablesLNM$SYSTEM_DIRECTORY

LNM$JOB_xxxxxxxxLNM$GROUP_xxxxxxLNM$SYSTEM_TABLEDECW$LOGICAL_NAMES

LNM$PROCESS_DIRECTORY



Logical Name TablesSearch Order:$ sh log/tab=* lnm$file_dev "LNM$FILE_DEV" = "LNM$PROCESS"

(LNM$SYSTEM_DIRECTORY) = "LNM$JOB" = "LNM$GROUP" = "LNM$SYSTEM" = "DECW$LOGICAL_NAMES"



Logical Name TablesModifying the search order:$ DEFINE/TABLE=LNM$PROCESS_DIRECTORY -

LNM$FILE_DEV LNM$PROCESS,LNM_PRIVATE,-LNM$GROUP,LNM$SYSTEM,-DECW$LOGICAL_NAMES

Defines a new search list in supervisor mode.» Some software will only use “trusted” logical names in

certain directories or those DEFINEd in an “inner’ (more privileged) mode.



Logical NamesSingle translation

$ DEFINE lnm value

Search List$ DEFINE lnm value,value[,…]

Concealed Logical Names$ DEFINE lnm value/TRANS=CONCEAL

Rooted Logical Names$ DEFINE lnm ddcu:[dir.]/TRANS=CONCEAL



Logical NamesCreating

$ DEFINE lnm value$ ASSIGN value lnm

Deleting$ DEASSIGN lnm



Logical NamesAccess Modes

User DEFINE/USERSupervisor DEFINE (/SUPER is default)Executive DEFINE/EXECUTIVE,

requires CMEXEC privilege.Kernel Can only be created by using

the $CRELNM system service,requires CMKRNL privilege.

Executive and Kernel mode logical names are “trusted” since privilege is required to create them.



Logical NamesSingle Translation

$ DEFINE lnm value

Examples:"LNM$PROCESS" = "LNM$PROCESS_TABLE"

(LNM$PROCESS_DIRECTORY)"LNM$JOB" = "LNM$JOB_80D27B00" (LNM$PROCESS_DIRECTORY)"LNM$GROUP" = "LNM$GROUP_000030"

(LNM$PROCESS_DIRECTORY)"LNM$SYSTEM" = "LNM$SYSTEM_TABLE"

(LNM$SYSTEM_DIRECTORY)“SYS$LOGIN" = "DKA0:[DDACHTERA]" (LNM$JOB_80D27B00)



Logical NamesSearch Lists

$ DEFINE lnm value,value[,…]Examples:

$ sh log sys$sysroot "SYS$SYSROOT" = "DJAS01$DKA300:[SYS0.]" (LNM$SYSTEM_TABLE) = "SYS$COMMON:"1 "SYS$COMMON" = "DJAS01$DKA300:[SYS0.SYSCOMMON.]"

(LNM$SYSTEM_TABLE)$ sh log user_exe ! Presenter’s environment, not provided by VMS. "USER_EXE" = "USER_IMG:" (LNM$JOB_80D27B00) = "USER_COM:" = "SYS$SPECIFIC:[SYSEXE]" = "SYS$COMMON:[SYSEXE]"1 "USER_IMG" = "USER_ROOT:[EXE.ALPHA]" (LNM$JOB_80D27B00)1 "USER_COM" = "USER_ROOT:[EXE]" (LNM$JOB_80D27B00)



Logical NamesConcealed Logical Names

$ DEFINE lnm value/TRANS=CONCEAL

Example:$ sh log sys$sysdevice "SYS$SYSDEVICE" = "DJAS01$DKA300:" (LNM$SYSTEM_TABLE)$ sh log sys$sysdevice/full "SYS$SYSDEVICE" [exec] = "DJAS01$DKA300:" [concealed,terminal]

(LNM$SYSTEM_TABLE)



Logical Names“Rooted” Logical Names

$ DEFINE lnm ddcu:[dir.]/TRANS=CONCEAL

Examples:$ show logical sys$specific,sys$common,user_root "SYS$SPECIFIC" = "DJAS01$DKA300:[SYS0.]" (LNM$SYSTEM_TABLE)

"SYS$COMMON" = "DJAS01$DKA300:[SYS0.SYSCOMMON.]" (LNM$SYSTEM_TABLE)

"USER_ROOT" = "DKA0:[DDACHTERA.]" (LNM$JOB_80D27B00)



Logical NamesUsing rooted logical namesExamples:$ show logical sys$sysroot,user_root,user_com,user_img "SYS$SYSROOT" = "DJAS01$DKA300:[SYS0.]" (LNM$SYSTEM_TABLE) = "SYS$COMMON:"1 "SYS$COMMON" = "DJAS01$DKA300:[SYS0.SYSCOMMON.]"

(LNM$SYSTEM_TABLE)

"USER_ROOT" = "DKA0:[DDACHTERA.]" (LNM$JOB_80D27B00)

"USER_COM" = "USER_ROOT:[EXE]" (LNM$JOB_80D27B00)

"USER_IMG" = "USER_ROOT:[EXE.ALPHA]" (LNM$JOB_80D27B00)



Logical Names & LexicalsBeware:

F$LOGICAL() (deprecated) differs from F$TRNLNM().

F$LOGICAL() uses hard-coded search list internally: Process, Job, Group, System.

F$TRNLNM() uses LNM$FILE_DEV



Cluster-Wide Logical Names

New in V7.2.

Defined in table LNM$SYSCLUSTER

LNM$SYSTEM is now a search list:$ show log/tab=* lnm$system "LNM$SYSTEM" = "LNM$SYSTEM_TABLE" (LNM$SYSTEM_DIRECTORY) = "LNM$SYSCLUSTER"1 "LNM$SYSCLUSTER" = "LNM$SYSCLUSTER_TABLE"

(LNM$SYSTEM_DIRECTORY)



Cluster-Wide Logical Names

Caveat: There is no /CLUSTER qualifier for

DEFINE, ASSIGN or DEASSIGN. Use /TABLE= LNM$SYSCLUSTER



Logical NamesNotes:

VMS$COMMON usually not found in system logical names.It IS possible to have a system with a missing or corrupted VMS$COMMON.

OpenVMS upgrades will fail.Difficult to recover.Running in this condition is not supported.



Logical NamesLeave OpenVMS-provided logical names alone.

ReDEFINE-ing things like SYS$SYSROOT can jeopardize support position or system certification (Healthcare, etc.)If any of these are reDEFINEd, do it at the /PROCESS level, not system-wide and make sure to leave the system account “pristine”.



Logical NamesLeave OpenVMS-provided logical names alone.

Probably okay to do this in a privileged account other than SYSTEM. If these are needed at SYSTARTUP_VMS time, invoke a proc. to do the DEFINEs, then invoke the proc.’s that need the local logical names, then clean up using DEASSIGN/PROCESS.



Logical NamesIt is possible to organize your site-specific procedures and keep them separated from the OpenVMS files without reDEFINE-ing any logical names provided by OpenVMS.



Logical NamesOpenVMS Logical Names:

Usually contain a “$” (dollar sign).

User (Site-Specific) Logical NamesAvoid “$” – use underscore:

SYS_MANAGERSYS_BACKUPSYS_OPERATORSYS_HELPSYS_ROOT



Logical Names$ sho log sys_*(LNM$PROCESS_TABLE)(LNM$JOB_80D128C0)(LNM$GROUP_000030)(LNM$SYSTEM_TABLE) "SYS_BACKUP" = "SYS_ROOT:[BACKUP]" "SYS_HELP" = “SYS_ROOT:[SYSHLP]" "SYS_MANAGER" = "SYS_ROOT:[SYSMGR]" "SYS_OPERATOR" = "SYS_ROOT:[OPERATOR]” “SYS_ROOT“ = “SYS$SYSDEVICE:[XYZCORP.]” = ”SYS$SYSROOT:”



Logical NamesSite-specific logical names for system management can be organized in their own logical name tables.

User Logical name table can be added to LNM$FILE_DEV, but don’t do that system-wide – DEFINE things /PROCESS.

See the earlier example of how to modify the LNM$FILE_DEV search list for a process./PROCESS is the default for DEFINE and ASSIGN if not specified.



Logical NamesNone of us is immortal.

Remember to document your customizations THOROUGHLY!

If you get hit by a bus today, will someone else be able to come in and understand what you’ve done?



Seminar 1024

OpenVMSNetworking



NetworkingNetwork stacks for OpenVMS: TCP/IP DECnet

» Phase IV» Phase V (DECnet/OSI)

Utilities:LANCP (works without DECnet)SET HOST/MOP (Phase V - NET$CCR)



Networking - TCP/IPTCP/IP Services for OpenVMS

Formerly known as UCX (Ultrix Connection)Developed, sold and supported by HP, shares code base with Tru64 TCP/IP

Management interface somewhat weak.Some features (like adding secondary name server) require editing config. files manually. Access to non-volatile Database inconsistent: sometimes SET CONFIG, sometimes SET/PERMANENT.



Networking TCP/IPTCPware

Native to and developed on OpenVMS (originally on VAX/VMS, ported to Alpha).

Developed, sold and supported by Process Software, Inc.

Proprietary Management Interface, now similar to Multinet in some ways.

Slightly more functionality than (UCX), performs better than Multinet and *UCX).



Networking - TCP/IPMultinet

Developed from BSD V4.3 code by TGV, Inc. on VAX/VMS, ported to Alpha.Now developed, sold and supported by Process Software, Inc.

Proprietary Management Interface.

Functionality similar to TCPware.

Performance is somewhat better than (UCX), less than TCPware.



Networking - TCP/IP

Author’s opinion re: Marvel:TCP/IP Services for OpenVMS will probably be Marvel-ready sooner than Process Software’s products; however, TCPware and Multinet provide more robust functionality - should be worth waiting for on Marvel. (SMP considerations)



Networking - TCP/IPCMU/IP

Freeware, a bit old.Originally developed by TEK, released to Carnegie Mellon Univ. C.S. department - became freeware.VAX only - no known Alpha port.TCP/IP-V4 only.



Networking - DECnetDeveloped by Digital for PDP-11, migrated to VAX and ported to Alpha.

Phase-IV is in use widely.

Phase V used where it is needed. Also known as DECnet-Plus or DECnet/OSI.



Networking - DECnetDECnet Phase IV is very SysAdmin friendly, but takes some getting used to.

“Set it and forget it” - easily configured, does not issue a lot of OPCOM messages unless there is trouble on the line(s).

Specification was published, no longer publicly available on the web.



Networking - DECnetDECnet Phase IV

Permanent databaseDEFINE commands in NCP

Volatile databaseSET commands in NCP



Networking - DECnetDECnet Phase IV

Provides MOP Remote ConsoleCONNECT command in NCP

Provides MOP downline load, upline dumpLOAD and TRIGGER commands in NCP

Provides for remote management of other nodes.

SET EXECUTOR NODE command in NCP, requires privilege and remote password.



Networking - DECnetDECnet Phase V (DECnet-Plus)

More complicated to manage - management paradigm follows the OSI seven-layer model.Circuits are built from the bottom up, following the OSI seven-layer model.Management is performed using NCL (Network Control Language).Non-volatile database is .NCL files - no “permanent” database.



Networking - DECnetDECnet Phase V (DECnet-Plus)

OPCOM messages are more plentiful and more verbose than Phase IV.Allows for diagnosis of trouble in each layer.Provides some features not available in Phase IV.Complete specification is not published.



Networking - DECnetAccess Control

» Set up proxy records in SYS$SYSTEM:NET$PROXY.DAT using the AUTHORIZE program.

» Enable proxy access in NCP (Phase-IV): incoming, outgoing.

– Incoming proxy access, if disabled, defaults to the access control info of the target object instead of the source node/user.



Networking - DECnetAccess Control

» Create the proxy database if it doesn’t already exist. Use AUTHORIZE, CREATE/PROXY

» Set up proxy records in Authorize.» Enable proxy access in NCL (Phase-V):

See the SET SESSION CONTROL statements.



Networking - DECnetFAL Logging Two Logical Names:

» FAL$LOG» FAL$OUTPUT



Networking - DECnetFAL Logging FAL$LOG

In SYLOGIN or the DECnet object file: $ DEFINE FAL$LOG “1/disable=8”

This is an unsupported feature“1”: file name and file type access informationdisable=8 disables “Poor Man’s Routing”: dir node1::node2::node3::



Networking - DECnetFAL Logging FAL$LOG, cont’d

Produces copious output - use with discretion.

FAL$OUTPUTCan be used to specify the name of the log file to create in place of SYS$OUTPUT

$ DEFINE FAL$OUTPUT FAL.LOG



Networking - LATLAT - Local Area Transport Robust, Efficient

» Can package data for multiple sessions at the same MAC address into common packets.

Not routable» No routable info in the network layer

DEC-proprietary (licensed)» Specification published under license



Networking - LATLAT Control Program (LATCP) Managememt interface for LAT Controls services broadcast by an

OpenVMS node Used to create, manage and delete LTA

devices on OpenVMS nodes.



Networking MOPMaintenance Operation Protocol Not routable

» No routable info in the network layer DEC-proprietary (licensed)

» Specification published under license Remote Console facility Downline load, upline dump.



Networking MOPMaintenance Operation Protocol User interfaces - Remote Console:

» NCP (DECnet Phase IV)CONNECT NODECONNECT VIA circuit_id PHYS ADDR

mac_addr» LANCP

CONNECT NODE name/DEVICE=enet_dev:» SET HOST/MOP (DECnet Phase V)

SET HOST/MOP node_nameSET HOST/MOP/ADDR=mac_addr/CIRC=xxxx



Networking MOPMaintenance Operation Protocol User interfaces - Downline Load, Upline

dump:» NCP (DECnet Phase IV)

DEFINE/SET NODE name -ADDRESS xx-xx-xx-xx-xx-xx -SERVICE CIRCUIT xxx-n -LOAD FILE filespec -SECONDARY LOADER filespec -DUMP FILE filespec



Networking MOPMaintenance Operation Protocol User interfaces - Downline Load:

» LANCPDEFINE NODE name -

/ADDRESS=xx-xx-xx-xx-xx-xx-/FILE=filespec

– Mostly for use in booting LAVc nodes– LANCP does not provide for upline dump



Networking - Remote Access

Types of remote Access: DECnet

» SET HOST (CTERM)» Remote File Access» NML (NCP SET EXECUTOR NODE)

LAT» Connect (from terminal server or PC

w/LAT)» SET HOST/LAT



Networking - Remote Access

Types of remote Access, cont’d: TCP/IP:

» TELNET» Rshell» Rlogin



Networking - Remote Proc.’s

Types of Remote Procedures: DECnet

» DECnet objects» SUBMIT/REMOTE, PRINT/REMOTE

TCP/IP» RPC (Remote Procedure Call)» Secure Socket Layer (SSL)



Networking - Remote Proc.’s

Security Concerns DECnet objects like TASK Unsecured accounts by any access

method. (This is not a security presentation.)



Network AlertsOPCOM Alerts for network access SET AUDIT/ENABLE=CONNECTION

» DECnet (Phase IV)» $IPC» SYSMAN

SET AUDIT/ENABLE=LOGIN=» ALL, BATCH, DETACHED, DIALUP,

LOCAL, NETWORK, REMOTE, SUBPROCESS



Network AlertsAdditional OPCOM Alerts for FTP Add commands to the DCL proc.

associated with the FTP service.» Example: MULTINET:FTP_SERVER.COM

Can be as general or specific needed. See the documentation and example

code for your TCP/IP stack.



Seminar 1024

System StartupProcedure



System StartupDefault /STARTUP procedure: SYS$SYSTEM:STARTUP.COM Set using SYSBOOT, SYSGEN or

SYSMAN.



System StartupSTARTUP Phases: In SYS$STARTUP:VMS$VMS.DAT

» RMS Indexed file» Changes to this area of the startup are

*NOT* supported by HP.



System StartupSTARTUP Phases:$ TY SYS$STARTUP:VMS$VMS.DATBASEENVIRON DVMS$BASEENVIRON-050_VMS.COM E*BASEENVIRON DVMS$BASEENVIRON-050_SMISERVER.COM E*BASEENVIRON DVMS$BASEENVIRON-050_LIB.COM E*BASEENVIRON DDECDTM$STARTUP.COM E*BASEENVIRON DLICENSE_CHECK.EXE E*CONFIG DVMS$CONFIG-050_VMS.COM E*CONFIG DVMS$CONFIG-050_ERRFMT.COM E*CONFIG DVMS$CONFIG-050_CACHE_SERVER.COM E*CONFIG DVMS$CONFIG-050_CSP.COM E*CONFIG DVMS$CONFIG-050_OPCOM.COM E*CONFIG DVMS$CONFIG-050_AUDIT_SERVER.COM E*CONFIG DVMS$CONFIG-050_JOBCTL.COM E*CONFIG DVMS$CONFIG-050_LMF.COM E*CONFIG DVMS$CONFIG-050_SHADOW_SERVER.COM E*CONFIG DVMS$CONFIG-050_SECURITY_SERVER.COM E*DEVICES DVMS$DEVICE_STARTUP.COM E*INITIAL DVMS$INITIAL-050_VMS.COM E*INITIAL DVMS$INITIAL-050_LIB.COM E*INITIAL CVMS$INITIAL-050_CONFIGURE.COM E*LPBEGIN DVMS$LPBEGIN-050_STARTUP.COM E*PRECONFIG DIPC$STARTUP.COM E*PRECONFIG DVMS$SPIRALOG_STARTUP.COM E*



System Startup Phases, Files

INITIALDEVICES

SYCONFIGSYLOGICALSSYPAGSWPFILES

PRECONFIGCONFIG

SYSECURITYBASEENVIRONLPBEGIN

SYSTARTUP_VMSLPMAINLPBETAEND



System Startup Phases, Files

INITIALDEVICES

SYCONFIGThese files are alwaysSYLOGICALS executed, even during aSYPAGSWPFILES “MIN”-imum boot.

PRECONFIGCONFIG

SYSECURITYBASEENVIRONLPBEGIN

SYSTARTUP_VMSLPMAINLPBETAEND



System StartupSite-Specific STARTUPs: SYSTARTUP_VMS.COM in

SYS$MANAGER path. SYSTARTUP_V5.COM in V5.x SYSTARTUP.COM in V4 and earlier.



System StartupSTARTUP Parameters: STARTUP_P1

» blank - Normal System Startup» “MIN” - Minimal Startup

– No SYSTARTUP_VMS but– Most of the other SY*.COM proc.’s will still be

run.



System StartupSTARTUP Parameters: STARTUP_P2

» blank - Normal System Startup» “1”, “YES” or “TRUE” - Verify on

STARTUP_P3 thru _P8» Reserved for future use



System StartupSYSTARTUP_VMS : Author prefers to keep procedure

modular for easier maintenance, invoke modules from SYSTARTUP_VMS:$ SET NOON

.

.

.

$ @MOUNT_DISKS$ @DEFINE_GROUP_LOGICALS



System StartupSYSTARTUP_VMS : Author prefers to keep procedure modular

for easier maintenance, invoke node-specific proc.’s from SYSTARTUP_VMS:

$ FSP = F$SEARCH( -

“SYS$MANAGER:SYSTARTUP.COM” )$ IF FSP .NES. “” THEN @&FSP

» Avoids redundant, cut-and-paste code.



System StartupSYSTARTUP_VMS : Logging SYSTARTUP_VMS:

$ SET NOON$ DEFINE SYS$OUTPUT -

SYS$MANAGER:SYSTARTUP_VMS.LOG...

$ DEASSIGN SYS$OUTPUT



System StartupSaving/reporting a crash dump at System Startup time:

$ ANALYZE/CRASH_DUMP SYS$SYSTEM:SYSDUMP.DMPCOPY ddcu:<dir>:SAVEDUMP.DMP ! copy to wherever is convenient.SET OUTPUT SYS$MANAGER:SYSDUMP.LIS ! Set this as you likeREAD/EXEC! READ SYS$SYSTEM:SYSDEF ! For VAXREAD SYS$LOADABLE_IMAGES:SYSDEF ! For AlphaSHOW CRASHSHOW STACK /ALLSHOW SUMMARYSHOW PROCESS /PCB /PHD /REGISTERSSHOW SYMBOL /ALLEXIT



System StartupDEFINE-ing Group Logicals at Startup:

» SET up a DCL procedure to DEFINE (or assign) the needed logicals using /GROUP and whatever access mode is appropriate.

» Invoke that procedure as a detached process at system startup time.



System StartupDEFINE-ing Group Logicals at Startup:Example:

$ RUN SYS$SYSTEM:LOGINOUT.EXE-/UIC=[300,1]-/INPUT=GROUP_300_LOGICALS.COM-/OUTPUT=GROUP_300_LOGICALS.LOG

The UIC specified does not need to exist in the UAF.



System StartupDEFINE-ing Group Logicals at Startup:Alternate Example:

$ RUN SYS$SYSTEM:LOGINOUT.EXE-/UIC=[300,1]/INPUT=NLA0:/OUTPUT=NLA0:

» The UIC specified does not need to exist in the UAF.

» The example creates the LNM$GROUP_000300 table.

» Logical names can then be created in that table by any suitably privileged process.



System StartupSetting logins at Startup: Global DCL symbol (STARTUP

process) is set up during SYS$STARTUP:VMS$BASEENVIRON-050_VMS.COM:$startup$interactive_logins == 64



System StartupSetting logins at Startup, cont’d: Global DCL symbol (STARTUP

process) is used in SYS$STARTUP:VMS$LPBEGIN-050_STARTUP.COM:$set logins/interactive='startup$interactive_logins



System StartupSetting logins at Startup, cont’d: Change the value of

startup$interactive_logins during SYSTARTUP_VMS:

$ startup$interactive_logins == -F$GETSYI( “IJOBLIM” )



System StartupSetting logins at Startup, cont’d:$ startup$interactive_logins == -

F$GETSYI( “IJOBLIM” )Notes: Set the desired value for IJOBLIM in

MODPARAMS and run AUTOGEN, or change the CURRENT value using SYSMAN or SYSGEN. Change takes effect on next boot.



System StartupSetting logins at Startup, cont’d:$ startup$interactive_logins == -

F$GETSYI( “IJOBLIM” )Notes, cont’d: IJOBLIM is a dynamic parameter. The

SET LOGINS/INTERACTIVE command displays or varies its value. See the HELP.



System StartupSetting logins at Startup, cont’d:SET LOGINS/INTERACTIVE caveat: Largely undocumented, little known fact:

until this command is issued for the first time after a reboot, the job controller will not create interactive processes.

If used in SYSTARTUP_VMS, it may enable logins before the system is ready for users to log in.



System StartupSetting logins at Startup, cont’d:SET LOGINS/INTERACTIVE caveat: DO NOT USE THIS COMMAND IN

SYSTARTUP_VMS!!! …or any proc. that it invokes!!! Use the global DCL symbol instead

(STARTUP$INTERACTIVE_LOGINS).



System Startup - VMS Files Must never be changed unless software

documentation or VMS support instructs you to do so.

May be replaced when VMS or layered products are upgraded.

May use deprecated lexical functions (like F$LOGICAL()), or may contain misspelled function names (like F$GETSYS(), DCL sees only F$GETS).



System Startup - VMS Files Site-specific startups are usually found

in the SYS$MANAGER path.



Seminar 1024

SYSMAN andSTARTUP



SYSMAN & STARTUPSYSMAN can be used to modify the “user” portion of the startup database.

» Two database files used by SYSMAN:STARTUP$STARTUP_VMS

Used for the VMS startupDO NOT MODIFY !!!

STARTUP$STARTUP_LAYEREDWhen you add an item using SYSMAN it

goes here.



SYSMAN & STARTUPSYSMAN can be used to modify the “user” portion of the startup database.» Not as flexible the traditional method using

SYSTARTUP_VMS.» Not as widely used. Incoming SysAdmins

may be unware of previous modifications to the startup database using SYSMAN.

» Allows for specifying that some startup procedures run in BATCH, in-line (DIRECT) or in sub-processes (SPAWN).



SYSMAN & STARTUP» Allows for entering startup items that run

after SYSTARTUP_VMS.– SYSTARTUP_VMS is invoked during the

LPBEGIN phase.– Valid phases for SYSMAN STARTUP entries

are LPBEGIN, LPMAIN, LPBETA and END.– Premature logins are possible if

SYSTARTUP_VMS enables logins before startups in later phases (LPMAIN, LPBETA or END) have run.



Seminar 1024

Conversational Boot,Minimum Startup



Conversational BootMost Current Alphas, VAX 7000:

>>> boot –fl x,1VAX 6000

>>> BOOT boot_profile/R5=1>>> BOOT boot_profile/R5=x0000001

Older small VAXes>>> B/R5:1 or B/R5:x0000001

VAX 8000’sSee the manual



Minimum Boot>>> b –fl 10,1

SYSBOOT> SET STARTUP_P1 “MIN”SYSBOOT> CONTINUE

Use SET WRITESYSPARAMS 0 before CONTINUE for a one-time minimum boot.



Seminar 1024

System ShutdownProcedure



System Shutdown$ @SYS$SYSTEM:SHUTDOWN

» Prompts interactively for parameters» Parameters can also be specified on the

command line that invokes the procedure.– See the SHUTDOWN and REBOOT symbols in

SYS$MANAGER:LOGIN.TEMPLATE



System ShutdownSYS$SYSTEM:SHUTDOWN.COMParameters:

P1 = Minutes to final shutdownP2 = Reason for ShutdownP3 = Spin down disk volumes? (Y/N)P4 = Invoke SYSHUTDWN.COM? (Y/N)P5 = When will system be rebooted?P6 = Should auto. reboot be performed?

(Y/N)P7 = Options (SAVE_FEEDBACK, etc.)

– P5 and P6 are reverse order to the prompts.



Site-Specific Shutdown Proc.

SYSHUTDWN.COMFound in the SYS$MANAGER path.



System ShutdownSYS$SYSTEM:SHUTDOWN.COMLogical Names

SHUTDOWN$MINIMUM_MINUTESDefault value for minutes to final shutdown.

AGEN$SHUTDOWN_TIMEUsed by AUTOGEN as minutes to final SHUTDOWN or REBOOT.



Shutdown OptionsREBOOT_CHECKSAVE_FEEDBACKDISABLE_AUTOSTARTPOWER_OFF



Shutdown OptionsREBOOT_CHECK Performs a basic check for the

existence of files needed to reboot the system.

Not comprehensive - cannot detect a damaged boot block, corrupted bootstrap image, etc.



Shutdown OptionsSAVE_FEEDBACK Saves some vital statistics about the

system that can be used by AUTOGEN after the system comes back up.

Same as the SAVPARAMS phase of AUTOGEN.



Shutdown OptionsDISABLE_AUTOSTART Use this if needed to prevent

AUTOSTART queues on this node from being restarted once SHUTDOWN has STOPped them.



Shutdown OptionsPOWER_OFF If the system console supports it,

request that the machine power itself down once VMS has been SHUTDOWN.



Shutdown Options - Clusters

REMOVE_NODE for all but the last node.» Node exits the cluster gracefully.

CLUSTER_SHUTDOWN for the last cluster node to be shutdown.» If used on all nodes, each node waits for

other nodes to reach the point of exiting the cluster, then proceeds to shutdown (“dissolves” the cluster).



Every Shutdown Author recommends you always specify

option REBOOT_CHECK for all nodes. Has been helpful in preventing some

nasty surprises.



Seminar 1024

AUTOGEN



AUTOGENSYS$UPDATE:AUTOGEN.COM

DCL procedure supplied by OpenVMS as an aid in tuning the OpenVMS system.

Not a replacement for diligent system management.



AUTOGEN Applies changes to the default system

parameters as specified in the fileSYS$SYSTEM:MODPARAMS.DAT

Is invoked during installs and upgrades, sometimes more than once.

Can be used to help size the swap and page files.



AUTOGEN - MODPARAMSSYS$SYSTEM:MODPARAMS.DAT This is where changes to the default

values are made so they persist from one AUTOGEN to the next.

Entries look like this:parameter_name = needed_valueMIN_parameter_name = needed_valueMAX_parameter_name = needed_valueADD_ parameter_name = needed_value



AUTOGEN - MODPARAMSparameter_name = needed_value Provides a hard-coded value for the

parameter.SCSNODE = “ALPHAONE”GBLPAGES = 121589

AUTOGEN calculations do not over-ride hard-coded values.



AUTOGEN - MODPARAMSMIN_parameter_name = minimum_value Provides a minimum value for the

parameter.MIN_GBLPAGES = 121589

AUTOGEN may calculate and use a higher value, but will always use the MIN_ if it calculates a lower value.



AUTOGEN - MODPARAMSMAX_parameter_name = maximum_value Provides a maximum value for the

parameter.MAX_GBLPAGES = 12158900

AUTOGEN may calculate and use a lower value, but will always use the MAX_ if it calculates a higher value.



AUTOGEN - MODPARAMSADD_parameter_name = addtl_value Provides an addition to the default value

for the parameter.ADD_GBLPAGES = 81920

AUTOGEN can use feedback to calculate a new value, then adds the specified value to the calculated value.



AUTOGEN - PhasesSAVPARAMS - Collects FeedbackGETDATA - Collects all other dataGENPARAMS - Generates new parametersTESTFILES - Calculates new sys file sizesGENFILES - Generates new system filesSETPARAMS - Creates new boot param.’sSHUTDOWN - Shutdown the systemREBOOT - Reboot the system

HELP - Displays AUTOGEN info



AUTOGEN - PhasesSAVPARAMS

Saves dynamic feedback from the running system.

Same as SAVE_FEEBACK option of SHUTDOWN.



AUTOGEN - PhasesGETDATA

Collects all data to be used in AUTOGEN calculations.Includes existing feedback data if it is not over 30 days old.Includes MODPARAMS info.



AUTOGEN - PhasesGENPARAMS

Performs calculations and generates the new system parameters (but does not yet set them into the “Current” parameters).Creates the new list of installed images based on the state of the currently running system.



AUTOGEN - PhasesTESTFILES

Calculates new page and swap file sizes, but does not apply any changes.



AUTOGEN - PhasesGENFILES

Generates new swap and page files based on AUTOGEN calculations.Use entries in MODPARAMS to override:DUMPFILE=0SWAPFILE=0PAGEFILE=0



AUTOGEN - PhasesSETPARAMS

Creates the new boot-time (“current”) parameters.Changes take effect on the next boot.



AUTOGEN - PhasesSHUTDOWN

Shutdown the system and leave it ready for a manual boot or other console-level operations.



AUTOGEN - PhasesREBOOT

Reboot the system using the newly generated parameters and/or system files.



AUTOGEN - PhasesHELP

Display HELP information for how to use AUTOGEN.

Useful to output this to a file:$ @SYS$UPDATE:AUTOGEN-

/OUTPUT=AGEN_HELP.LIS HELP



AUTOGEN - PhasesTypical uses:

See if current MODPARAMS settings are suitable:$ @SYS$UPDATE:AUTOGEN -

SAVPARAMS TESTFILESGenerate new system parameters for next boot:$ @SYS$UPDATE:AUTOGEN -

SAVPARAMS SETPARAMSAUTOGEN using previously saved feedback:$ @SYS$UPDATE:AUTOGEN -

GENPARAMS SETPARAMS



AUTOGEN - PhasesTypical uses:

AUTOGEN ignoring feedback:$ @SYS$UPDATE:AUTOGEN -

GENPARAMS SETPARAMS NOFEEDBACK

AUTOGEN using previously saved feedback, if it is valid:$ @SYS$UPDATE:AUTOGEN -

GENPARAMS SETPARAMS - CHECK_FEEDBACK



AUTOGEN - ReportSYS$SYSTEM:AGEN$PARAMS.REPORT Generated on each run of AUTOGEN during

the GENPARAMS phase. Indicates any MODPARAMS errors detected

by AUTOGEN. Indicates the results of AUTOGEN

calculations and resulting changes to system parameters.



AUTOGEN - LoggingAUTOGEN issues useful information on SYS$OUTPUT, also.

Some SysAdmins find this useful:$ @SYS$UPDATE:AUTOGEN/OUT=AGEN.LOG -

start_phase end_phase



Seminar 1024

Useful Tips and Tricks



Useful Tips and TricksAn “uptime” command:$ SHOW SYSTEM/NOPROCESS

$ UPT*TIME :== SHOW SYSTEM/NOPROCESS



Useful Tips and TricksAn simple command to show usage:$ SHL :== -

PIPE SHOW USERS/FULL | -(READ SYS$PIPE P9 ; -WRITE SYS$OUTPUT P9 ; -READ SYS$PIPE P9 ; -WRITE SYS$OUTPUT P9 ; -SET LOGINS)



Seminar 1024

OpenVMS SystemManagement Tools



System Management Tools

Supplied as no-charge additional software, licensed with OpenVMS.

StorageWorks Command Console(SWCC)

OpenVMS Management Station(“TNT” or “Argus”)

Accessibility Manager for Distributed Systems (AMDS), Availability Manager



Seminar 1024

StorageWorksCommand Console



StorageWorks Cmd Console

Provides MS/Win GUI for management of StorageWorks storage array controllers.» HSJ (CI)» HSZ (SCSI)» HSG (FC-SF)

Uses TCP/IP to communicate with server agent on OpenVMS.

Behaves like other “Explorer” software.




Limitations: PC’s IP address must back-translate

» DHCP is o.k. so long as DNS is updated when address lease is obtained / renewed.

Does not work over WAN unless PC’s DNS name is “visible” outside of firewall and firewall allows the TCP ports.

OpenVMS server agent will only run on one node of a cluster.




Limitations, cont’d: Unit names and storage-set names are

assigned randomly and arbitrarily.» Some names can be changed manually

using the CLI. Can hold onto the virtual console so that

other access means are denied:» SET HOST/DUP, SET HOST/SCSI




Limitations, cont’d: Disks falling into the Failed Set are

detected and reported as warnings; however, CLI messages are not passed through to the GUI - you must still connect to the CLI to get them.» “Other controller restarted”» Cache battery alerts




Limitations, cont’d:

No provisions for running HSx utilities and diagnostics.

No performance data available via the GUI - use the CLI to run VTDPY.




Management Considerations PCs must be authorized to access

OpenVMS server agent. Use the SWCC configuration utility supplied with the OpenVMS-side software.

Controllers and/or controller pairs must be set up using the SWCC configuration utility supplied with the OpenVMS-side software.




Management Considerations HSZ and HSG controller pairs present

only a single virtual device for remote access - cannot connect to an individual controller by name using the CLI window.

You will still need to access the physical console terminal port from time to time, as when a controller fails out of the pair.



Seminar 1024

OpenVMS Management

Station



OpenVMS Mgt StationProvides an MS/Win GUI for management

of some areas of OpenVMS: User records and identifiers OpenVMS storage Printer (but not batch) queues. Uses TCP/IP to communicate between

Windows client and OpenVMS Server.



OpenVMS Mgt StationConsiderations: No interfaces for application-specific

user setups. Provides only for “traditional” OpenVMS

printer queues - no provisions for TCP/IP considerations.

V3.0 is still available for Alpha/NT. Later versions are Intel only.



OpenVMS Mgt StationConsiderations: Runs on W/NT and W2K, W/98, and

W/95, but needs Internet Explorer V3.02 or later to provide some support.

V3.2 Server needs OpenVMS V6.2 or later.



OpenVMS Mgt Station



OpenVMS Mgt StationSet up Wizard



OpenVMS Mgt Station



OpenVMS Mgt StationLogon to a managed system



OpenVMS Mgt StationAccounts Window



OpenVMS Mgt StationAccountDetail



OpenVMS Mgt StationPrinters and other Symbiont Queues



OpenVMS Mgt StationDetail of Printers / Symbiont Queues



OpenVMS Mgt StationOpenVMS Storage



OpenVMS Mgt StationOpenVMS Storage Detail



OpenVMS Mgt Station OpenVMS Server reads OMS

configuration when it starts.

Storage configured in OMS and not yet MOUNTed gets MOUNTed (if enabled).

Symbiont queues configured in OMS and not yet STARTed get STARTed.



OpenVMS Mgt Station OpenVMS Server builds a DCL

procedure that can be used to MOUNT your storage, even if the server cannot be started for whatever reason:TNT$EMERGENCY_MOUNT.COM



OpenVMS Mgt Station

Can be useful to ease certain system management tasks that would otherwise require the use of command-line utilities, but is not a replacement for those utilities.



OpenVMS Mgt Station

Download URL:http://www.openvms.compaq.com/openvms/products/argus/download.html



Seminar 1024

Accessibility Manager forDistributed Systems

(AMDS) andAvailability Manager



AMDSProvides DECwindows interface for system or cluster management, someperformance monitoring. Warnings can be issued when

performance metrics go out of spec. - you determine the thresholds for your environment.

Can (maybe) be used to “un-hang” a cluster (force quorum adjustment).



AMDSConsiderations: Uses a proprietary, non-routable

network protocol. For optimum availability management,

needs to run on a separate OpenVMS workstation (not a cluster member).

AMDS workstation must be on same LAN segment as cluster nodes or protocol must be bridged bt segments.



AMDSConsiderations: AMDS workstation can be accessed

remotely (X on Linux, Solaris or *BSD; Reflection/X or Exceed, etc. on MS Win; DECwindows on OpenVMS).



AMDSLicensing:

AMDS license is now included in the OpenVMS base license (as of AMDS V7.1).

Software Kit:On the OpenVMS binary CD.On the OpenVMS website.



AMDSStartup Procedure:

$ @SYS$STARTUP:AMDS$STARTUPSpecify START as the first parameter.



AMDSLogical Names:

Defined in AMDS$SYSTEM:AMDS$LOGICALS.COM

AMDS$GROUP_NAME is the node information display group, default is DECAMDS

Define a group name for each cluster

AMDS$DEVICE defines the network device to use if multiple LAN connections are present.



Availability MgrAvailability Manager An MS Windows tool (W/NT, W2K) Does not require an X-server on the PC. Uses the same non-routable protocol as

AMDS - similar restrictions. Could be accessed remotely using

PCAnywhere, or maybe Citrix.



AMDSAMDS Screen shots follow.

Many display objects can be selected to “drill down” for more information.



AMDS



Seminar 1024

OpenVMS Security Elements




An OpenVMS system is only as secure as the SysAdmin makes it.Understanding and using the elements of OpenVMS Security is the best way to help ensure the security and integrity of an OpenVMS system.




Points to remember:TELNET and FTP sessions are not encrypted, passwords are sent as clear text. Use Secure Shell and Secure FTP for best security.LAT and DECnet are not encrypted, passwords are sent as clear text.




User Identification Codes[group,user]

Similar to UN*X UIDs, except digits are always octal.Users belong to only one UIC group. Use Rights Identifiers to grant additional access.




Protection MasksBased on the UIC.Four classes of permission:

SystemOwner GroupWorld

UN*X only has Owner, Group, World




Levels of Permission in each class:Files

Read - Open read onlyWrite - Open write onlyExecute - Run (if it’s a program/proc.)Delete - Delete the file

(Requires write access to parent directory.)




Levels of Permission in each class:Directories

Read - List filesWrite - Create/delete filesExecute - Traverse the directory

(Look up files)Delete - Delete the directory

(Requires Write access to parent).




Levels of Permission in each class:Devices

READWRITELOGICAL I/OPHYSICAL I/O




Levels of Permission in each class:Queues

READ - Display queue, jobsMODIFY - Modify queue, jobsSUBMIT - SUBMIT/PRINT jobsDELETE - Delete jobs or the queue




Access Control ListsSpecify access control beyond the UIC based protections.Consist of access control entries.




Access Control EntriesAssociate access control with UICs or Rights IdentifiersLevels of access:

READ DELETEWRITE CONTROLEXECUTE

Object owner always has CONTROL




Rights IdentifiersCreated using AUTHORIZE.Can be associated with a resource (disk file - to control disk quotas).GRANTed to or REVOKEd from users using AUTHORIZE.Can be dynamic – non-privileged users can acquire and release using SET RIGHTS_LIST in DCL.




Propagating ACEs, Default ProtectionsSet an ACE on a directory with the DEFAULT attribute.Default Protection ACE is set on a directory.Will be applied to new files, or use SET SECURITY/DEFAULT to propagate to existing files.




Set ACEs in the proper sequenceFirst matching ACE determines access.Enter ACEs from least restrictive to most restrictive. EDIT/ACL can be helpful.ACL takes priority over UIC based protection mask.



Seminar 1024

Closing Comments,Q & A



Freeware Sources» The OpenVMS Freeware CDs are online at

the OpenVMS website.» The DFWCUG DECUS CD-ROM Archive:

ftp://ftp.montagar.com/decus/» DFWCUG OVMS Freeware V3 Archive:

ftp://ftp.montagar.com/freeware-v3/» DJE Systems OpenVMS Freeware archive:

http://www.djesys.com/freeware/vms/» OpenVMS FAQ

http://www.openvms.compaq.com/wizard/faq/vmsfaq.html



Seminar 1024Thanks for coming!

Disclaimer: All information is correct to the best of the author’s knowledge.

Please fill out the evaluation forms, if available.

openvms mgt tools, tips and tricks

Documents