% Librarian I01-42¸Ƹcd 5} /TRANSLATEVADDCREATE1DELETE3EXIT4HELP6LISTN|PURGEPREMOVESREPLACEC<Ƹ 1 /TRANSLATED The /TRANSLATE qualifier forces INSTALL to attempt a logical name* translation of a file that you specify.& NOTE> before you use the /TRANSLATE qualifier, you must invoke# INSTALL as a foreign command: $ INSTALL = "$INSTALL" Format /TRANSLATE 2 DescriptionA Within OpenVMS, when you specify a file name without a device,> directory, or file type, OpenVMS usually attempts a logical> name translation of the file name before it applies device,> directory, or file type defaults. However, if you specify a> device, directory, or file type, OpenVMS does not attempt a logical name translation.= Using the /TRANSLATE qualifier forces INSTALL to attempt a@ logical name translation even if a device, directory, or file type are specified. 2 Examples 1.DEFINE FILE1 FILE1_EV6 $ INSTALL = "$INSTALL" $ INSTALLE INSTALL> ADD SYS$SHARE:FILE1.EXE ! SYS$SHARE:FILE1 is added as a known imageA The first command in this example defines FILE1 as a logicalA name with an equivalence name of FILE1_EV6. However, becauseA a device (SYS$SHARE:) file type (.EXE) are supplied, INSTALL@ treats FILE1 as part of a file specification rather than as" part of a file specification. 2.DEFINE FILE1 FILE1_EV6 $ INSTALL = "$INSTALL" $ INSTALL/TRANSLATEG INSTALL> ADD SYS$SHARE:FILE1.EXE ! SYS$SHARE:FILE1_EV6 is added as a known imageA The first command in this example defines FILE1 as a logicalC name with an equivalence name of FILE1_EV6. Because /TRANSLATE> is specified, INSTALL treats FILE1 as a logical name even@ though a device (SYS$SHARE:) file type (.EXE) are supplied. wwC<Ƹ1 ADD> Installs the specified image file as a known image. The ADD/ command is a synonym for the CREATE command.D Requires the CMKRNL privilege. Also requires the SYSGBL privilege? to create system global sections and the PRMGBL privilege to$ create permanent global sections. Format ADD file-spec 2 Parameter file-spec> Names the file specification of an image to be installed as> a known image. The file specification must name an existingB executable or shareable image, which must have been linked withC the /NOTRACEBACK qualifier. If you omit the device and directoryB specificati on, the default SYS$SYSTEM is used. The default file type is .EXE.? The highest existing version of the file is used by default.D However, you can specify another version of the file as the knownB version of the image. Even if other versions of the file exist,B the version that you specify will be the version that satisfies( all known file lookups for the image. 2 Qualifiers /ACCOUNTING /ACCOUNTING /NOACCOUNTING (default)C Enables image-lev el accounting for selected images even if image= accounting is disabled on the local node (by using the DCL? command SET ACCOUNTING/DISABLE=IMAGE). When image accounting< is enabled on the local node, it logs all images, and the) /NOACCOUNTING qualifier has no effect. /ARB_SUPPORT /ARB_SUPPORT=keyword< On Alpha and I64 systems, overrides the system parameter ( ARB_SUPPORT for this installed image.D The following table shows the keywords you can use with the /ARB_ SUPPORT qualifier: Keyword BehaviorC None The obsolete kernel data cells are not maintained byC the system. Fields are initialized to zero or set to4 invalid pointers at process creation.@ Clear The obsolete kernel data cells are cleared or setB to invalid pointers when the code would have set up1 values for backward compatibility.@ Read-only The obsolete cells are updated with corresponding A security information stored in the current Persona= Security Block (PSB) when a $PERSONA_ASSUME is issued.; Full Data is moved from the obsolete cells to theD (default) currently active PSB on any security-based operation.A For more information about obsolete kernel cells, refer to the/ ARB_SUPPORT system parameter in online help. /AUTHPRIVILEGES) /AUTHPRIVILEGES[=(priv-name[,...])] /NOAUTHPRIVILEGES D Installs the file as a known image with the authorized privileges specified. Usage NotesD o If a privileged image is not located on the system volume, the* image is implicitly installed /OPEN.D o The set of privileges for a privileged image can be empty. YouA must, however, list each privilege every time you define or redefine privileges.> o The /AUTHPRIVILEGES qualifier applies only to executable images.? o You cannot specify this qualifier for an executable image+ linked with the /TRACEBACK qualifier.B o You cannot assign privilege names with the /NOAUTHPRIVILEGES qualifier.B You can specify one or more of the privilege names described inA detail in an appendix to the OpenVMS Guide to System Security. (ALL is the default.) /EXECUTE_ONLY /EXECUTE_ONLY /NOEXECUTE_ONLY (default)C The /EXECUTE_ONLY qualifier is meaningful only to main programs.@ It allows the image to activate shareable images to which theC user has execute access but no read access. All shareable images? referenced by the program must be installed, and OpenVMS RMSD uses trusted logical names (those created for use in executive or kernel mode).C You cannot specify this qualifier for an executable image linked! with the /TRACEBACK qualifier. /HEADER_RESIDENT /HEADER_RESIDENT /NOHEADER_RESIDENTA Installs the file as a known image with a permanently resident> header (native mode images only). An image installed header. resident is implicitly also installed open. /LOG /LOG /NOLOG (default): Lists the newly created known file entry along with any: associated global sections created by the installation. /OPEN /OPEN /NOOPEN7 Installs the file as a permanently open known image. /PRIVILEGED% /PRIVILEGED[=(priv-name[,...])] /NOPRIVILEGED@ Installs the file as a known image with the active privileges specified. Usage NotesD o If a privileged image is not located on the system volume, the* image is implicitly installed /OPEN.@ o The set of privileges for a privileged image can be empty.D o You must list each privilege every time you define or redefine privileges.B o The /PRIVILEGED qualifier applies only to executable images.? o You cannot specify this qualifier for an executable image+ linked with the /TRACEBACK qualifier.> o You cannot assign privilege names with the /NOPRIVILEGED qualifier. Installing Shareable ImagesA Installing an image with privileges declares that the image is> trusted to maintain system integrity and security properly.? To maintain that trust, any routine called by the privilegedD image must also be trusted. For this reason, any shareable imagesB activated for use by a privileged image must be installed. Only? trusted  logical names (names defined in executive and kernelA mode) can be used in locating shareable images to be used by a privileged image.< Interaction of /PRIVILEGED and /AUTHPRIVILEGES QualifiersB When you create a new entry, the privileges you assign are alsoC assigned for Authorized Privileges if you do not assign specific< authorized privileges with the /AUTHPRIVILEGES qualifier.> When you replace an image, any privileges assigned with theC /PRIVILEGED qualifier are not repeated as Authorized Privileges.B Also, if you use the REPLACE command with the /NOAUTHPRIVILEGES> qualifier, the Authorized Privileges become the same as the< Default Privileges (set using the /PRIVILEGED qualifier).B You can specify one or more of the privilege names described inA detail in an appendix to the OpenVMS Guide to System Security. (ALL is the default.) /PROTECTED /PROTECTED /NOPROTECTED (default)< Installs the file as a known image that is protected fromA user-mode and supervisor-mode write access. You can write into? the image only from executive or kernel mode. The /PROTECTED; qualifier together with the /SHARE qualifier are used to; implement user-written services, which become privileged shareable images. /PURGE /PURGE (default) /NOPURGEC Specifies that the image can be removed by a purge operation; ifB you specify /NOPURGE, you can remove the image only by a delete or remove operation. /RESIDENT% /RESIDENT[=([NO]CODE,[NO]DATA)]D On Alpha and I64 systems, causes image code sections or read-onlyA data sections to be placed in the granularity hint regions andC compresses other image sections, which remain located in process@ space. If you do not specify the /RESIDENT qualifier, neitherD code nor data is installed resident. If you specify the /RESIDENTC qualifier without keyword arguments, code is installed resident,& and data is not installed resident.B The image must be linked using the /SECTION_BINDING=(CODE,DATA)> qualifier. An image installed with resident code or data is3 implicitly installed header resident and shared. /SHARED /SHARED=[NO]ADDRESS_DATA /NOSHARED? Installs the file as a shared known image and creates global? sections for the image sections that can be shared. An image1 installed shared is implicitly installed open.D When you use the ADDRESS_DATA keyword with the /SHARED qualifier,A P1 space addresses are assigned for shareable images. With theD assigned addresses, the Install utility can determine the content@ of an address data section when the image is installed ratherA than when it is activated, reducing CPU and I/O time. A globalB section is created to allow shared access to address data image sections. /WRITABLE /WRITABLE=[GALAXY[=IDENT]] /NOWRITABLED Installs the file as a writable kno wn image when you also specifyA the /SHARED qualifier. The /WRITABLE qualifier applies only toB images with image sections that are shareable and writable. The@ /WRITABLE qualifier is automatically negated if the /NOSHARED qualifier is specified.A You can use the GALAXY keyword with the /WRITABLE qualifier to? place write shared image sections in Galaxy global sections.@ You can also use the IDENT keyword with GALAXY to include the@ image ident in the name of the Galaxy global section, so that@ multiple versions of an image can be used simultaneously in a Galaxy system. 2 Examples1 1.INSTALL> ADD/OPEN/SHARED WRKD$:[MAIN]STATSHRC The command in this example installs the image file STATSHR as, a permanently open, shared known image.8 2.INSTALL> ADD/OPEN/PRIVILEGED=(GROUP,GRPNAM) GRPCOMMC The command in this example installs the image file GRPCOMM asB a permanently open, known image with the privileges GROUP and  GRPNAM.> Any process running GRPCOMM receives the GROUP and GRPNAMA privileges for the duration of the execution of GRPCOMM. TheB full name of GRPCOMM is assumed to be SYS$SYSTEM:GRPCOMM.EXE. 3.INSTALL> ADD/LOG GRPCOMM@ The command in this example installs the image file GRPCOMMB as a known image and then displays the newly added known file entry.9 4.INSTALL> ADD/SHARED=ADDRESS_DATA WRKD$:[MAIN]INFOSHR? The command in this example installs the INFOSHR file as a> shared known image and creates shared global sections forC code sections and read-only data sections. Because the commandD includes the ADDRESS_DATA keyword, address data is also created as a shared global section. wwcƸ 1 CREATEA Installs the specified image file as a known image. The CREATE, command is a synonym for the ADD command.D Requires the CMKRNL privilege. Also requires the SYSGBL privilege? to create system global sections and the PRMGBL privilege to$ create permanent global sections. Format CREATE file-spec 2 Parameter file-spec> Names the file specification of an image to be installed as> a known image. The file specification must name an existingB executable or shareable image, which must have been linked withC the /NOTRACEBACK qualifier. If you omit the device and directoryB specification, the default SYS$SYSTEM is used. The default file type is .EXE.? The highest existing version of the file is used by default.D However, you can specify another version of the file as the knownB version of the image. Even if other versions of the file exist,B the version that you specify will be the version that satisfies( all known file lookups for the image. 2 Qualifiers /ACCOUNTING /ACCOUNTING /NOACCOUNTING (default)> Enables image-level accounting for the specified image even@ if image accounting is disabled (by using the DCL command SET> ACCOUNTING/DISABLE=IMAGE). When image accounting is enabled? on the local node, it logs all images, and the /NOACCOUNTING qualifier has no effect. /ARB_SUPPORT /ARB_SUPPORT=keyword< On Alpha and I64 systems, overrides the system parameter ( ARB_SUPPORT for this installed image.D The following table shows the keywords you can use with the /ARB_ SUPPORT qualifier: Keyword BehaviorC None T he obsolete kernel data cells are not maintained byC the system. Fields are initialized to zero or set to4 invalid pointers at process creation.@ Clear The obsolete kernel data cells are cleared or setB to invalid pointers when the code would have set up1 values for backward compatibility.@ Read-only The obsolete cells are updated with correspondingA security information stored in the current Persona= ! Security Block (PSB) when a $PERSONA_ASSUME is issued.; Full Data is moved from the obsolete cells to theD (default) currently active PSB on any security-based operation.A For more information about obsolete kernel cells, refer to the/ ARB_SUPPORT system parameter in online help. /AUTHPRIVILEGES) /AUTHPRIVILEGES[=(priv-name[,...])] /NOAUTHPRIVILEGESC Installs the file as a known image installed with the authorized pri"vileges specified. Usage NotesD o If a privileged image is not located on the system volume, the* image is implicitly installed /OPEN.D o The set of privileges for a privileged image can be empty. YouA must, however, list each privilege every time you define or redefine privileges.> o The /AUTHPRIVILEGES qualifier applies only to executable images.? o You cannot specify this qualifier for an executable image+ linked with the /TRACEBACK q#ualifier.B o You cannot assign privilege names with the /NOAUTHPRIVILEGES qualifier.B You can specify one or more of the privilege names described inA detail in an appendix to the OpenVMS Guide to System Security. (ALL is the default.) /EXECUTE_ONLY /EXECUTE_ONLY /NOEXECUTE_ONLY (default)C The /EXECUTE_ONLY qualifier is meaningful only to main programs.@ It allows the image to activate shareable images to which theC user has execute acce$ss but no read access. All shareable images? referenced by the program must be installed, and OpenVMS RMSD uses trusted logical names (those created for use in executive or kernel mode).C You cannot specify this qualifier for an executable image linked! with the /TRACEBACK qualifier. /HEADER_RESIDENT /HEADER_RESIDENT /NOHEADER_RESIDENTA Installs the file as a known image with a permanently resident> header (native mode images only). An image instal%led header) resident is implicitly installed open. /LOG /LOG /NOLOG (default): Lists the newly created known file entry along with any: associated global sections created by the installation. /OPEN /OPEN /NOOPEN7 Installs the file as a permanently open known image. /PRIVILEGED% /PRIVILEGED[=(priv-name[,...])] /NOPRIVILEGED< Installs the file as a known image with active privileges@ specified. If a privi&leged image is not located on the system3 volume, the image is implicitly installed /OPEN. Usage Notes@ o The set of privileges for a privileged image can be empty.D o You must list each privilege every time you define or redefine privileges.B o The /PRIVILEGED qualifier applies only to executable images.? o You cannot specify this qualifier for an executable image+ linked with the /TRACEBACK qualifier.> o You cannot assign privilege names with t 'he /NOPRIVILEGED qualifier. Installing Shareable ImagesA Installing an image with privileges declares that the image is> trusted to maintain system integrity and security properly.? To maintain that trust, any routine called by the privilegedD image must also be trusted. For this reason, any shareable imagesB activated for use by a privileged image must be installed. Only? trusted logical names (names defined in executive and kernelA mode) can be used in locating ( shareable images to be used by a privileged image.1 Interaction of /PRIVILEGED and /AUTHPRIVILEGESB When you create a new entry, the privileges you assign are alsoC assigned for Authorized Privileges if you do not assign specific< authorized privileges with the /AUTHPRIVILEGED qualifier.> When you replace an image, any privileges assigned with theC /PRIVILEGED qualifier are not repeated as Authorized Privileges.B Also, if you use the REPLACE command with the /NOAUTH)PRIVILEGES> qualifier, the Authorized Privileges become the same as the< Default Privileges (set using the /PRIVILEGED qualifier).B You can specify one or more of the privilege names described inA detail in an appendix to the OpenVMS Guide to System Security. (ALL is the default.)> For examples of how to use CREATE commands with /PRIVILEGESC qualifiers, see the Examples section at the end of this command. /PROTECTED /PROTECTED /NOPROTECTED (default)*< Installs the file as a known image that is protected fromA user-mode and supervisor-mode write access. You can write into? the image only from executive or kernel mode. The /PROTECTED; qualifier together with the /SHARE qualifier are used to; implement user-written services, which become privileged shareable images. /PURGE /PURGE (default) /NOPURGEC Specifies that the image can be removed by a purge operation; ifB you specify /NOPURGE, you can r+emove the image only by a remove operation. /RESIDENT% /RESIDENT[=([NO]CODE,[NO]DATA)]D On Alpha and I64 systems, causes image code sections or read-onlyA data sections to be placed in the granularity hint regions andC compresses other image sections, which remain located in process@ space. If you do not specify the /RESIDENT qualifier, neitherD code nor data is installed resident. If you specify the /RESIDENTC qualifier without keyword arguments, code is in,stalled resident,& and data is not installed resident.B The image must be linked using the /SECTION_BINDING=(CODE,DATA)> qualifier. An image installed with resident code or data is3 implicitly installed header resident and shared. /SHARED /SHARED[=[NO]ADDRESS_DATA] /NOSHARED? Installs the file as a shared known image and creates global? sections for the image sections that can be shared. An image1 installed shared is implicitly installed open.D- When you use the ADDRESS_DATA keyword with the /SHARED qualifier,A P1 space addresses are assigned for shareable images. With theD assigned addresses, the Install utility can determine the content@ of an address data section when the image is installed ratherA than when it is activated, reducing CPU and I/O time. A globalB section is created to allow shared access to address data image sections. /WRITABLE /WRITABLE=[GALAXY[=IDENT]] /NOWRITABLED Ins .talls the file as a writable known image when you also specifyA the /SHARED qualifier. The /WRITABLE qualifier applies only toB images with image sections that are shareable and writable. The@ /WRITABLE qualifier is automatically negated if the /NOSHARED qualifier is specified.A You can use the GALAXY keyword with the /WRITABLE qualifier to? place write shared image sections in Galaxy global sections.@ You can also use the IDENT keyword with GALAXY to include the@ image i/dent in the name of the Galaxy global section, so that@ multiple versions of an image can be used simultaneously in a Galaxy system. 2 Examples4 1.INSTALL> CREATE/OPEN/SHARED WRKD$:[MAIN]STATSHRC The command in this example installs the image file STATSHR as+ a permanently open shared known image.; 2.INSTALL> CREATE/OPEN/PRIVILEGED=(GROUP,GRPNAM) GRPCOMMC The command in this example installs the image file GRPCOMM asA a permanently open known imag0e with the privileges GROUP and GRPNAM.> Any process running GRPCOMM receives the GROUP and GRPNAMA privileges for the duration of the execution of GRPCOMM. TheB full name of GRPCOMM is assumed to be SYS$SYSTEM:GRPCOMM.EXE. 3.INSTALL> CREATE/LOG GRPCOMMC The command in this example installs the image file GRPCOMM asA a known image and then displays the newly created known file entry.< 4.INSTALL> CREATE/SHARED=ADDRESS_DATA WRKD$:[MAIN]INFOSHR?1 The command in this example installs the INFOSHR file as a> shared known image and creates shared global sections forC code sections and read-only data sections. Because the commandD includes the ADDRESS_DATA keyword, address data is also created as a shared global section.! 5.INSTALL> CREATE STATSHR/PRIVC The command in this example creates the STATSHR image with all privileges./ 6.INSTALL> CREATE STATSHR/PRIV=(OPER,SYSPRV)C The command in 2this example creates the STATSHR image with the OPER and SYSPRV privileges.' 7.INSTALL> CREATE STATSHR/PRIV=NOALLB The command in this example creates the STATSHR image with an empty set of privileges.# 8.INSTALL> CREATE STATSHR/NOPRIV: The command in this example creates the STATSHR image# explicitly with no privileges. wwsƸ 1 DELETEA Deletes a known image. The DELETE command is a synonym for the REMOVE command. F3ormat DELETE file-spec 2 Parameter file-spec1 Names the file specification of a known image. 2 DescriptionD The DELETE command deletes an entry from the known file list. The? image's entry on the known file list and any global sections< created for the image are deleted. The image file remains@ unaffected. Writable global sections are written back to disk& upon their removal as known images.D If a process is accessing global sections when th4e DELETE command= is entered, the global sections are deleted only after theB operation initiated by the process completes. However, once theD command is entered, no additional processes can access the global1 sections because they are marked for deletion. 2 Example$ INSTALL> DELETE WRKD$:[MAIN]STATSHR@ The command in this example deletes the entry for the image& STATSHR from the known file list. wwsƸ1 EXITC Terminates INSTALL and re5turns control to the DCL command level.5 You can also exit from INSTALL by pressing Ctrl/Z. Format EXIT wwsƸ1 HELP1 Displays information about how to use INSTALL. Format HELP [command] 2 Parameter commandB Specifies the name of a command for which help infomation is toB be displayed. If you omit a command name, a list of commands is5 displayed and you are prompted for a command name. 2 Examples6 1.INSTALL> HELPB The command in this example displays a list of INSTALL topicsC and a Topic? prompt. Any topic from the list can be entered at the prompt. 2.INSTALL> HELP LIST LISTL For display of a one-line description of the specified known image,I or if no file is specified, then for all known images. Use with1 /FULL to obtain a multiline description.4 Format: LIST [file-spec] /qualifier, QU7ALIFIER COMBINATION BEHAVIORF LIST [file-spec] List the known image for file-spec4 LIST List all entries* Additional information available: Qualifiers5 /FULL /GLOBAL /STRUCTURE /SUMMARYD The command in this example displays help information about the LIST command. wwsƸ1 LISTA Displays a description of each specified known image or, if no' file is specified8, all known images. Format LIST [file-spec] 2 Parameter file-spec@ Names the file specification of an image installed as a knownB image. If you omit the file specification, INSTALL displays all known images. 2 DescriptionC You can use the LIST command with the /FULL qualifier to displayA information that is useful in tuning the known image database.C For example, a high entry-access count for an image may indicateD that system perform9ance could benefit if the image were installed> /OPEN. Similarly, high entry-access counts for an image mayB indicate that installing the image /SHARED-that is, with globalB sections-could improve performance. For a description of global@ sections and global pages, including information about how to> estimate the size of installed images, refer to the OpenVMS$ System Services Reference Manual. 2 Qualifiers /FULLA Displays a multiline description of the specified : known image,= including the number of accesses, the number of concurrentA accesses, and the number of global sections created. The /FULL? qualifier with the /GLOBAL qualifier shows information aboutC global sections, plus the current owner and protection codes and access control entries. /GLOBALB Lists global sections for any specified shared image, or if you? omit the file specification, lists all global sections. If a? global section is created by INSTALL to; support a particular( image, that image is also identified. /RESIDENT1 Displays a description of each resident image. /STRUCTURE2 Lists addresses of known image data structures. /SUMMARY? Used with the /GLOBAL qualifier, displays the global sectionB and global page usage on the system for local and shared memory global sections. 2 Examples 1.INSTALL> LISTC The command in this example displays a single-line description; of <all known images. The description includes the file9 specification of the known image and its attributes.+ SYS$DISK:.EXE+ ANALIMDMP;1 1 Prv 2, AUTHORIZE;1 Prv, CDU;1 Open Hdr Prv7 DCL;1 Open Hdr Shar Lnkbl( FAL;1 Open Hdr Shar, INSTALL;1 Prv, LOGINOUT;1 Open Hdr Shar Prv( MAIL =;1 Open Hdr Shar, MAIL_SERVER;1 Open Hdr Shar Prv, REQUEST;1 Prv, SET;1 Open Hdr Shar Prv, SETAUDIT;1 Prv, SETP0;1 Open Hdr Shar Prv, SETRIGHTS;1 Prv, SHOW;1 Open Hdr Shar Prv, SHWCLSTR;1 Open Hdr Shar Prv, SUBMIT;1 Open Hdr Shar Prv, SYSMAN;1 Prv+ SYS$DISK:>.EXE, ANALIMDMPSHR;1 Prv CONVSHR;17 DCLTABLES;1 Open Hdr Shar Lnkbl . . .D LIBOTS;1 Open Hdr Shar Lnkbl ResidD LIBRTL;1 Open Hdr Shar Lnkbl Resid7 MAILSHR;1 Open Hdr Shar Lnkbl . . .- 1 File specification of the known image- 2 Attribute of known image, as fol ?lows: Attribute Meaning< ACNT Image accounting is enabled for the image! (/ACCOUNTING).D CMODE Image is in compatibility mode, set by the VAX-11 RSX Linker.A HDR Image header is permanently resident (/HEADER_ RESIDENT).= LNKBL Image is not executable; it is a shareable> (linkable) image set by the OpenVMS Linker.@ NOPURG Image cannot be rem @oved by a purge operation;? it can only be removed by a delete or remove( operation (/NOPURGE).5 OPEN Image is permanently open (/OPEN).> PROT Image contains protected code (/PROTECTED).6 PRV Image has privileges (/PRIVILEGED).1 RESID Image is resident (/RESIDENT).B SAFE Image is a privileged image registered as beingB compatible with the running version of OpenVMS.@ A For more information about registered images,@ refer to the OpenVMS System Manager's Manual,( Volume 1: Essentials.- SHAR Image is shared (/SHARED).1 WRT Image is writable (/WRITABLE).: XONLY Only execute access to image is allowed# (/EXECUTE_ONLY). 2.INSTALL> LIST/RESIDENT= The command in this Alpha example displays a single-lineA description of all resident images. TBhe description includesC the location in memory, the size of the code sections, and the type of section. System Resident Sections+ SYS$DISK:.EXE CMA$TIS_SHR;10 Base VA End VA Length Type9 80490000 80490A00 00000A00 Resident Code3 7FC04000 7FC04A00 00000A00 Linkage: 7FC14000 7FC14200 00000200 Writeable data: 7FC34000 7FC34200 00000200 WrCiteable data DECC$SHR;10 Base VA End VA Length Type9 80548000 805D1C00 00089C00 Resident Code9 805D2000 805D2400 00000400 Resident Code3 7FE34000 7FE4B800 00017800 Linkage: 7FE54000 7FE59A00 00005A00 Writeable data: 7FE64000 7FE64800 00000800 Read-only data: 7FE84000 7FE84200 00000200 Writeable data7 7FE94000 7FE94200 00000200 Demand-zero7D 7FEA4000 7FEA7000 00003000 Demand-zero: 7FEB4000 7FEB5800 00001800 Writeable data DPML$SHR;10 Base VA End VA Length Type9 80492000 80547600 000B5600 Resident Code: 7FC44000 7FC6FA00 0002BA00 Read-only data3 7FC74000 7FC88200 00014200 Linkage: 7FC94000 7FC94400 00000400 Writeable data: 7FCA4000 7FCCE600 0002A600 Read-only data: 7FD940E00 7FD95000 00001000 Writeable data LIBOTS;10 Base VA End VA Length Type9 80482000 8048F600 0000D600 Resident Code: 7FBC4000 7FBC6600 00002600 Read-only data3 7FBD4000 7FBD5A00 00001A00 Linkage: 7FBF4000 7FBF4200 00000200 Writeable data LIBRTL;10 Base VA End VA Length Type9 80400000 80481A00 00081A00 Resident Code3 7F FB54000 7FB64800 00010800 Linkage: 7FB74000 7FB75000 00001000 Writeable data: 7FB84000 7FB8D600 00009600 Read-only data: 7FB94000 7FB94200 00000200 Writeable data7 7FBA4000 7FBA5000 00001000 Demand-zero: 7FBB4000 7FBB5400 00001400 Writeable data 3.INSTALL> LIST/FULL LOGINOUTD The command in this example displays a multiline description of the known image LOGINOUT.+ SYS$DISK:.EXE1 LOGINOUT;3 Open Hdr Shar Priv0 Entry access count = 44 13 Current / Maximum shared = 3 / 5 2/ Global section count = 2 3A Privileges = CMKRNL SYSNAM TMPMBX EXQUOTA SYSPRV 4B 1 Number of times known file entry has been accessed by this% node since it swas installed.> 2 First number indicates the current count of concurrent? accesses of the known Hfile. The second number indicatesB the highest count of concurrent accesses of the file sinceB it was installed. This number appears only if the image is+ installed with the /OPEN qualifier.= 3 Number of global sections created for the known file;? appears only if the image is installed with the /SHARED qualifier.D 4 Translation of the privilege mask; appears only if the image% is installed with privileges. 4.INSTALL> LIST/GLOIBALA The command in this example displays all global sections forD shared images. Global sections created by INSTALL (prefix INS$)? for a specific image are listed following the name of that image.- 1 Display of global sections in memory.A 2 Name of the image for which the following global sections were created by INSTALL.D 3 Name of global section. The prefix identifies the creator ofB the section; for example, INS means the global J section wasB created by INSTALL. The number includes the address of the section.> 4 Version number (in hexadecimal) of global section; forA shareable images only, the high-order byte (01 in CRFSHR_? 003) contains major identification, and low-order bytes; (0003E8 in CRFSHR_003) contain minor identificationA determined by the programmer at link time. For executableD images, the number is a known unique value determined by the K system.) 5 Attributes of the global section:, DZRO Global section is demand-zero.= GRP Along with a group number indicates a groupwide@ section, which would be created by a program other than INSTALL.* PRM Global section is permanent.+ SYS Global section is systemwide.B TMP Indicates a temporary global section, which would be6 created by a program other than INSTALL.) WRT Global secti Lon is writable.A 6 Number of pages (VAX) or pagelets (Alpha and I64) in the B section and number of page table entries currently mapped B to this global section. For a more detailed discussion of B mapping global sections, refer to the OpenVMS Programming  Concepts Manual.A 7 Number of global sections created, number of global pages@ used, and number of global pages unused in local memory.@ Note that, because of arithmetic rounding, t Mhe number ofB global sections created will sometimes be greater than theA SYSGEN parameter GBLSECTIONS. When the size of the systemC header is being computed, the values of the GBLSECTIONS andC SYSMWCNT parameters are combined with the size of the fixedC part of the process header. The result is rounded up to the@ next page boundary. This rounding process sometimes addsB space to the global section table, depending on the valuesD of t Nhe two SYSGEN parameters and the amount of system pagingA that preceded the running of INSTALL to create all of the global sections. 5.INSTALL> LIST/GLOBAL/FULL? The command in this example displays a complete listing of@ global sections for shared images. The /FULL qualifier adds/ owner and protection codes to the display. System Global SectionsJ NM_MAILSHR_003 (741A6919) PRM SYS Pagcnt/Refcnt=10/0I NM_MAILSHR_002 (7O41A6919) PRM SYS Pagcnt/Refcnt=1/0J NM_MAILSHR_001 (741A6919) PRM SYS Pagcnt/Refcnt=11/0* Owner: [1,4] 1> Protection: S:RWED,O:RWED,G:RWED,W:RE 2 . . .. 1 UIC of the owner of the global section, 2 Type of access allowed for the image wwƸ1 PURGEB Deletes all known file entries for images installed without the /NOPURGE qualifier.D RequiPres the CMKRNL privilege. Also requires the SYSGBL privilege? to create system global sections and the PRMGBL privilege to$ create permanent global sections. Format PURGE 2 Parameters None. 2 Description> The PURGE command deletes all known file entries for images, installed without the /NOPURGE qualifier.C If a process is accessing global sections when the PURGE command= is entered, the global sections are deleted only after theB operationQ initiated by the process completes. However, once theD command is entered, no additional processes can access the global1 sections because they are marked for deletion. 2 Example INSTALL> PURGE@ The command in this example deletes all images except thoseB installed with the /NOPURGE qualifier. The image files remainB unaffected. Writable global sections are written back to disk( upon their removal as known images. wwƸ 1 REMOVE@ R Deletes a known image. The REMOVE command is identical to the DELETE command.D Requires the CMKRNL privilege. Also requires the SYSGBL privilege? to create system global sections and the PRMGBL privilege to$ create permanent global sections. Format REMOVE file-spec 2 Parameter file-spec1 Names the file specification of a known image. 2 DescriptionD The REMOVE command deletes an entry from the known file list. The? image's entry on th Se known file list and any global sections< created for the image are deleted. The image file remains@ unaffected. Writable global sections are written back to disk& upon their removal as known images.D If a process is accessing global sections when the REMOVE command= is entered, the global sections are deleted only after theB operation initiated by the process completes. However, once theD command is entered, no additional processes can access the global1 sections because Tthey are marked for deletion. 2 Example INSTALL> REMOVE GRPCOMM@ The command in this example deletes the entry for the known2 image GRPCOMM from the known image file list. wwƸ 1 REPLACEB Replaces a known image entry with another version of the image,D or with modified attributes. The REPLACE command is a synonym for the DELETE command.D Requires the CMKRNL privilege. Also requires the SYSGBL privilege? to create system global sectiUons and the PRMGBL privilege to$ create permanent global sections. Format REPLACE file-spec 2 Parameter file-spec@ Names the file specification of an image installed as a known image. 2 Qualifiers /ACCOUNTING /ACCOUNTING /NOACCOUNTING (default)C Enables image-level accounting for selected images even if image= accounting is disabled on the local node (by using the DCL? command SET ACCOUNTING/DISABLE=IMAGE). VWhen image accounting< is enabled on the local node, it logs all images, and the) /NOACCOUNTING qualifier has no effect. /ARB_SUPPORT /ARB_SUPPORT=keyword< On Alpha and I64 systems, overrides the system parameter ( ARB_SUPPORT for this installed image.D The following table shows the keywords you can use with the /ARB_ SUPPORT qualifier: Keyword BehaviorC None The obsolete kernel data cells are not maintained byD the syste Wm. Fields are initialized to zero (or set to5 invalid pointers) at process creation.A Clear The obsolete kernel data cells are cleared (or setC to invalid pointers) when the code would have set up1 values for backward compatibility.@ Read-only The obsolete cells are updated with correspondingA security information stored in the current Persona= Security Block (PSB) when a $PERSONA_ASSUME is X issued.; Full Data is moved from the obsolete cells to theD (default) currently active PSB on any security-based operation.A For more information about obsolete kernel cells, refer to the/ ARB_SUPPORT system parameter in online help. /AUTHPRIVILEGES) /AUTHPRIVILEGES[=(priv-name[,...])] /NOAUTHPRIVILEGESC Installs the file as a known image installed with the authorized privileges specified. Usage NotesD o If a privileged imagYe is not located on the system volume, the* image is implicitly installed /OPEN.D o The set of privileges for a privileged image can be empty. YouA must, however, list each privilege every time you define or redefine privileges.> o The /AUTHPRIVILEGES qualifier applies only to executable images.? o You cannot specify this qualifier for an executable image+ linked with the /TRACEBACK qualifier.B o You cannot assign privilege names with the /NO ZAUTHPRIVILEGES qualifier.< Interaction of /PRIVILEGED and /AUTHPRIVILEGES QualifiersB When you create a new entry, the privileges you assign are alsoC assigned for Authorized Privileges if you do not assign specific< authorized privileges with the /AUTHPRIVILEGES qualifier.> When you replace an image, any privileges assigned with theC /PRIVILEGED qualifier are not repeated as Authorized Privileges.B Also, if you use the REPLACE command with the /NOAUTHPRIVILEGES> [ qualifier, the Authorized Privileges become the same as the< Default Privileges (set using the /PRIVILEGED qualifier).B You can specify one or more of the privilege names described inA detail in an appendix to the OpenVMS Guide to System Security. (ALL is the default.) /EXECUTE_ONLY /EXECUTE_ONLY /NOEXECUTE_ONLY (default)C The /EXECUTE_ONLY qualifier is meaningful only to main programs.@ It allows the image to activate shareable images to which theC\ user has execute access but no read access. All shareable images? referenced by the program must be installed, and OpenVMS RMSD uses trusted logical names, those created for use in executive or kernel mode.C You cannot specify this qualifier for an executable image linked! with the /TRACEBACK qualifier. /HEADER_RESIDENT /HEADER_RESIDENT /NOHEADER_RESIDENTA Installs the file as a known image with a permanently resident> header (native mode image]s only). An image installed header) resident is implicitly installed open. /LOG /LOG /NOLOG (default): Lists the newly created known file entry along with any: associated global sections created by the installation. /OPEN /OPEN /NOOPEN7 Installs the file as a permanently open known image. /PRIVILEGED% /PRIVILEGED[=(priv-name[,...])] /NOPRIVILEGED@ Installs the file as a known image installed with the worki^ng privileges specified. Usage NotesD o If a privileged image is not located on the system volume, the* image is implicitly installed /OPEN.D o The set of privileges for a privileged image can be empty. YouA must, however, list each privilege every time you define or redefine privileges.B o The /PRIVILEGED qualifier applies only to executable images.? o You cannot specify this qualifier for an executable image+ linked with the /TRACEBACK qua_lifier.> o You cannot assign privilege names with the /NOPRIVILEGED qualifier.B You can specify one or more of the privilege names described inA detail in an appendix to the OpenVMS Guide to System Security. (ALL is the default.) /PROTECTED /PROTECTED /NOPROTECTED (default)< Installs the file as a known image that is protected fromA user-mode and supervisor-mode write access. You can write into? the image only from executive or kernel mode.` The /PROTECTED; qualifier together with the /SHARE qualifier are used to; implement user-written services, which become privileged shareable images. /PURGE /PURGE (default) /NOPURGEC Specifies that the image can be removed by a purge operation; ifB you specify /NOPURGE, you can remove the image only by a delete or remove operation. /RESIDENT% /RESIDENT[=([NO]CODE,[NO]DATA)]D On Alpha and I64 systems, causes image code sections or a read-onlyA data sections to be placed in the granularity hint regions andC compresses other image sections, which remain located in process@ space. If you do not specify the /RESIDENT qualifier, neitherD code nor data is installed resident. If you specify the /RESIDENTC qualifier without keyword arguments, code is installed resident,& and data is not installed resident.B The image must be linked using the /SECTION_BINDING=(CODE,DATA)> qualifier. An image installed with rebsident code or data is5 implicitly installed /HEADER_RESIDENT and /SHARED. /SHARED /SHARED[=[NO]ADDRESS_DATA] /NOSHARED? Installs the file as a shared known image and creates global? sections for the image sections that can be shared. An image1 installed shared is implicitly installed open.D When you use the ADDRESS_DATA keyword with the /SHARED qualifier,A P1 space addresses are assigned for shareable images. With theD assigned addresses, the Insctall utility can determine the content@ of an address data section when the image is installed ratherA than when it is activated, reducing CPU and I/O time. A globalB section is created to allow shared access to address data image sections. /WRITABLE /WRITABLE /NOWRITABLEB Installs the file as a writable known image as long as you also> specify the /SHARED qualifier. The /WRITABLE qualifier only? applies to images with image sections that are shareable andD writable. The /WRITABLE qualifier is automatically negated if the$ /NOSHARED qualifier is specified. 2 Example, INSTALL> REPLACE GRPCOMM /ACCOUNTING/NOOPENA The command in this example replaces the known image GRPCOMM? with the latest version of the image, while enabling imageB accounting and removing the OPEN attribute from this version.= The full name of the file specification is assumed to be SYS$SYSTEM:GRPCOMM.EXE.ww