% Librarian I01-47f0?gjk 5} /TRANSLATE8ADDCREATE1DELETE48EXIT4HELP6LISTR2PURGETREMOVEVpREPLACE-f 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$SHAR E:FILE1.EXE ! SYS$SHARE:FILE1 is added as a known imageF The first command in this example defines FILE1 as a logical nameE with an equivalence name of FILE1_EV6. However, because a deviceE (SYS$SHARE:) file type (.EXE) are supplied, INSTALL treats FILE1C as part of a file specification rather than as a logical name. 2.DEFINE FILE1 FILE1_EV6 $ INSTALL = "$INSTALL" $ INSTALL/TRANSLATEG INSTALL> ADD SYS$SHARE:FILE1.EXE ! SYS$SHARE:FILE1_EV6 is added as a known imageF The first command in this example defines FILE1 as a logical nameA with an equivalence name of FILE1_EV6. Because /TRANSLATE isD specified, INSTALL treats FILE1 as a logical name even though a7 device (SYS$SHARE:) file type (.EXE) are supplied.wwTf1 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-specF Names the file specification of an image to be installed as a knownD image. The file specification must name an existing executable or8 shareable image. If you omit the device and directoryB specification, the default SYS$SYSTEM is used. The default file type is .EXE.? The highest existing ve rsion 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-level accounting for selected images even if image= accounting is disabled on the local node (by using th e 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@ 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 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[,...])] /NOAUTHPRIVILEGESD 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 Sharea ble 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.); For examples of how to use ADD 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 remove the image only by a delete or remove operation. /RESIDENT% /RESIDENT[=([NO]CODE,[NO]DATA)]8 Causes image code segments/sections or read-only dataE segments/sections to be placed in the granularity hint regions andD compresses other image segments/sections, which remain located in@ process space. If you do not specify the /RESIDENT qualifier,B neither code nor data is installed resident. If you specify theC /RESIDENT qualifier without keyword arguments, code is installed0 resident, and data is not installed resident.D On x86-64, the image must be installed with /SHARED=ADDRESS_DATA.A On Alpha, the image must be linked using the /SECTION_BINDING= (CODE,DATA) qualifier. > An image installed with resident code or data is implicitly( installed header resident and shared./SHARED /SHARED=[NO]ADDRESS_DATA /NOSHARED? Installs the file as a shared known image and creates globalB sections for the image segments/sections that can be shared. An7 image  installed shared is implicitly installed open.G When you use the ADDRESS_DATA keyword with the /SHARED qualifier, P1G space addresses are assigned for shareable images. With the assignedF addresses, the Install utility can determine the content of addressE data when the image is installed rather than when it is activated,B reducing CPU and I/O time. A global section is created to allow9 shared access to address data image segments/sections. /WRITABLE /WRITABLE= [GALAXY[=IDENT]] /NOWRITABLED Installs the file as a writable known image when you also specifyA the /SHARED qualifier. The /WRITABLE qualifier applies only to= images with image segments/sections that are shareable andD writable. The /WRITABLE qualifier is automatically negated if the$ /NOSHARED qualifier is specified.> On Alpha, you can use the GALAXY keyword with the /WRITABLEB qualifier to place write shared image segments in Galaxy globalF sections. You can also use the IDENT keyword with GALAXY to includeD the image ident in the name of the Galaxy global section, so thatG 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]INFOSHRF The command in this example installs the INFOSHR file as a shared< known image and creates shared global sections for codeE segements/sections and read-only data segments/sections. BecauseC the command includes the ADDRESS_DATA keyword, address data is- also created as a shared global section.ww{f1 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-specF Names the file specification of an image to be installed as a knownD image. The file specification must name an existing executable or8 shareable image. 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@ 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 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 p"rivileges 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 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 installe%d 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 privileged im&age 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 the /NOPR 'IVILEGED 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 shareab (le 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 /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 /NOAU)THPRIVILEGES> 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 rem+ove the image only by a remove operation. /RESIDENT% /RESIDENT[=([NO]CODE,[NO]DATA)]8 Causes image code segments/sections or read-only dataE segments/sections to be placed in the granularity hint regions andD compresses other image segments/sections, which remain located in@ process space. If you do not specify the /RESIDENT qualifier,B neither code nor data is installed resident. If you specify theC /RESIDENT qualifier without keyword arguments, code is instal,led0 resident, and data is not installed resident.D On x86-64, the image must be installed with /SHARED=ADDRESS_DATA.A On Alpha, the image must be linked using the /SECTION_BINDING= (CODE,DATA) qualifier. > An image installed with resident code or data is implicitly( installed header resident and shared./SHARED /SHARED[=[NO]ADDRESS_DATA] /NOSHARED? Installs the file as a shared known image and creates globalB sections for the image segmen -ts/sections that can be shared. An7 image installed shared is implicitly installed open.G When you use the ADDRESS_DATA keyword with the /SHARED qualifier, P1G space addresses are assigned for shareable images. With the assignedF addresses, the Install utility can determine the content of addressE data when the image is installed rather than when it is activated,B reducing CPU and I/O time. A global section is created to allow9 shared access to address data image segments/se.ctions. /WRITABLE /WRITABLE=[GALAXY[=IDENT]] /NOWRITABLED Installs the file as a writable known image when you also specifyA the /SHARED qualifier. The /WRITABLE qualifier applies only to= images with image segments/sections that are shareable andD writable. The /WRITABLE qualifier is automatically negated if the$ /NOSHARED qualifier is specified.> On Alpha, you can use the GALAXY keyword with the /WRITABLEB qualifier to place write shared image segme/nts in Galaxy globalF sections. You can also use the IDENT keyword with GALAXY to includeD the image ident in the name of the Galaxy global section, so thatG 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 0 The command in this example installs the image file GRPCOMM asA 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> CREATE/LOG GRPCOMMC The command in this example installs the image file GRPCOMM asA a known image and then displays the new1ly created known file entry.< 4.INSTALL> CREATE/SHARED=ADDRESS_DATA WRKD$:[MAIN]INFOSHRF The command in this example installs the INFOSHR file as a shared< known image and creates shared global sections for codeD segments/sections and read-only data segments/sections. BecauseC the command 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 creates2 the STATSHR image with all privileges./ 6.INSTALL> CREATE STATSHR/PRIV=(OPER,SYSPRV)C The command in this 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.ww3f1 DELETEA Deletes a known image. The DELETE command is a synonym for the REMOVE command. Format 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 writ4ten back to disk& upon their removal as known images.D If a process is accessing global sections when the 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 image5& STATSHR from the known file list.wwf1 EXITC Terminates INSTALL and returns control to the DCL command level.5 You can also exit from INSTALL by pressing Ctrl/Z. Format EXITwwf1 HELP1 Displays information about how to use INSTALL. Format HELP [command] 2 ParametercommandB Specifies the name of a command for which help infomation is toB be displayed. If you omit a command name, a6 list of commands is5 displayed and you are prompted for a command name. 2 Examples 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 LISTJ For display of a one-line description of the specified known image,G or if no file is specified, then for all known images. Use with/ /FULL to obtain a multiline d7escription.2 Format: LIST [file-spec] /qualifier* QUALIFIER COMBINATION BEHAVIORD LIST [file-spec] List the known image for file-spec2 LIST List all entries( Additional information available: Qualifiers3 /FULL /GLOBAL /STRUCTURE /SUMMARYD The command in this example displays help information about the LIST command.wwf1 LISTA Displays a descri8ption of each specified known image or, if no' file is specified, 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-a9ccess count for an image may indicateD that system performance could benefit if the image were installed> /OPEN. Similarly, high entry-access counts for an image mayD indicate that installing the image /SHARED - that is, with globalD 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/F:ULLA 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 s;ections. 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 examp <le displays a single-line description; of all known images. The description includes the file9 specification of the known image and its attributes.) SYS$DISK:.EXE2 AUTHORIZE;1 (1) Open Prv (2). CDU;1 Open Hdr Prv( DCL;1 Open Hdr Shared* FAL;1 Open Hdr SharAddr. INSTALL;1 Prv. LOGINOUT;1 Open Hdr SharAddr Prv* MAIL;1 = Open Hdr SharAddr. MAIL_SERVER;1 Open Hdr SharAddr Prv. REQUEST;1 Prv. SET;1 Open Hdr SharAddr Prv. SETAUDIT;1 Prv. SETP0;1 Open Hdr SharAddr Prv. SETRIGHTS;1 Open Prv. SHOW;1 Open Hdr SharAddr Prv. SHWCLSTR;1 Open Hdr SharAddr Prv. SUBMIT;1 Open Hdr SharAddr Prv. SYSMAN;1 Open Prv>) SYS$DISK:.EXE CONVSHR;15 DCLTABLES;1 Open Hdr Shared Lnkbl . . .B LIBOTS;1 Open Hdr SharAddr Lnkbl ResidB LIBRTL;1 Open Hdr SharAddr Lnkbl Resid5 MAILSHR;1 Open Hdr SharAddr Lnkbl . . ./ (1) File specification of the known image/ (2) Attribute of known image, as follows: Attribute Meaning< ? Acnt Image accounting is enabled for the image! (/ACCOUNTING).D ArbSupp Image is installed with Access Rights Block (ARB)2 support options (/ARB_SUPPORT).E Authprv Image has authorized privileges (/AUTHPRIVILEGES).A Hdr Image header is permanently resident (/HEADER_ RESIDENT).A GlxIdent Image is writable with shared data in a Galaxy? global section identified by the @image ident, (/WRITABLE=GALAXY=IDENT).A GlxWrite Image is writable with shared data in a Galaxy; global section (/WRITABLE=GALAXY=IDENT).= Lnkbl Image is not executable; it is a shareable> (linkable) image set by the OpenVMS Linker.@ Nopurg Image cannot be removed by a purge operation;? it can only be removed by a delete or remove( operation (/NOPURGE).5 Open A 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.@ For more information about registered images,@ refer to the OpenVMS System Manager's Manual,( Volum Be 1: Essentials.- Shared Image is shared (/SHARED).H SharAddr Image has shared address data (/SHARED=ADDRESS_DATA).1 Wrt Image is writable (/WRITABLE).: Xonly Only execute access to image is allowed# (/EXECUTE_ONLY). 2.INSTALL> LIST/RESIDENTF The command in this example displays a single-line description ofB all resident images. The description includes the location inD memory, the size of the code segmentsC/sections, and the type of segment/section.% System Resident Sections) SYS$DISK:.EXE . . . DECC$SHR;1@ Base VA End VA Length TypeI FFFF8300.088E6000 FFFF8300.08D14137 00000000.0042E138 Resident CodeG FFFF8300.08D78000 FFFF8300.08DAAB17 00000000.00032B18 Unwind DataI FFFF8300.08DAC000 FFFF8300.08DB4A17 00000000.00008A18 Resident CodeI FFFFFFFF.85A16000 FF DFFFFFF.85A2C5BF 00000000.000165C0 Resident CodeJ 00000000.7BB76000 00000000.7BB81EBB 00000000.0000BEBC Writeable dataG 00000000.7BB82000 00000000.7BB8A0FF 00000000.00008100 Demand-zeroJ 00000000.7BB8C000 00000000.7BB8C028 00000000.00000029 Writeable dataJ 00000000.7BB8E000 00000000.7BB93BCB 00000000.00005BCC Read-only dataJ 00000000.7BB94000 00000000.7BB9B59B 00000000.0000759C Read-only data . . . LIBOTS;1@ Base VA End VA E Length TypeI FFFF8300.08610000 FFFF8300.08610012 00000000.00000013 Resident CodeI FFFF8300.08612000 FFFF8300.0861DFAF 00000000.0000BFB0 Resident CodeG FFFF8300.0861E000 FFFF8300.0861F247 00000000.00001248 Unwind DataI FFFF8300.08620000 FFFF8300.08620017 00000000.00000018 Resident CodeI FFFFFFFF.85A04400 FFFFFFFF.85A0590F 00000000.00001510 Resident CodeJ 00000000.7B2E8000 00000000.7B2E800F 00000000.00000010 Read-only data . . F . LIBRTL;1@ Base VA End VA Length TypeI FFFF8300.08443000 FFFF8300.08443597 00000000.00000598 Resident CodeI FFFF8300.08445000 FFFF8300.085E8BDF 00000000.001A3BE0 Resident CodeG FFFF8300.085FD000 FFFF8300.0860C6B7 00000000.0000F6B8 Unwind DataI FFFF8300.0860D000 FFFF8300.0860FFDF 00000000.00002FE0 Resident CodeI FFFFFFFF.85A00400 FFFFFFFF.85A0434F 00000000.00003F50 Resident CodeJ 00000000.7B2BE000 0000 G0000.7B2C190F 00000000.00003910 Writeable dataG 00000000.7B2C2000 00000000.7B2D8607 00000000.00016608 Demand-zeroJ 00000000.7B2DA000 00000000.7B2DA029 00000000.0000002A Writeable dataJ 00000000.7B2DC000 00000000.7B2DDADD 00000000.00001ADE Read-only dataJ 00000000.7B2DE000 00000000.7B2E689F 00000000.000088A0 Read-only data 3.INSTALL> LIST/FULL LOGINOUTD The command in this example displays a multiline description of the known image LOGINOUT.) SYS$DISK: H.EXE- LOGINOUT;1 Open Hdr SharAddr Prv+ Entry access count = 44 (1). Current / Maximum shared = 3 / 5 (2)+ Global section count = 15 (3)J Privileges = CMKRNL SYSNAM IMPERSONATE LOG_IO ALTPRI TMPMBX SYSPRV. SYSLCK AUDIT SECURITY (4)J Authorized = CMKRNL SYSNAM IMPERSONATE LOG_IO ALTPRI TMPMBX SYSPRV* SYSLCK AUDIT SECURITY) Resident section count = 0000 I ARB Support = READ_ONLYD (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 concurrentA accesses of the known file. The second number indicatesD the highest count of concurrent accesses of the file sinceD it was installed. This number appears only if the image is- installed with the /OPEN qualifier.? (3) Number of global secJtions created for the known file;A appears only if the image is installed with the /SHARED qualifier.F (4) Translation of the privilege mask; appears only if the image' is installed with privileges. 4.INSTALL> LIST/GLOBALA 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.' K System Global Sections (1) . . .7 SYS$DISK:DEC$BASRTL.EXE (2)J INS$812E2AE0_009(040003EA) (3) PRM SYS (4) Pgltcnt/Refcnt=115/0 (5)E INS$812E2AE0_008(040003EA) DZRO PRM SYS Pgltcnt/Refcnt=32/0E INS$812E2AE0_007(040003EA) DZRO PRM SYS Pgltcnt/Refcnt=16/0E INS$812E2AE0_006(040003EA) DZRO PRM SYS Pgltcnt/Refcnt=64/0G INS$812E2AE0_005(040003EA) PRM SYS Pgltcnt/Refcnt=1195/0D INS$812E2AE0_004(04000L3EA) PRM SYS Pgltcnt/Refcnt=5/0D INS$812E2AE0_003(040003EA) PRM SYS Pgltcnt/Refcnt=6/0 . . .J 570 Global Sections Used, 16340/85840 Global Pagelets Used/Unused (6)/ (1) Display of global sections in memory.C (2) Name of the image for which the following global sections" were created by INSTALL.F (3) Name of global section. The prefix identifies the creator ofD the section; for example, INS means the global sec Mtion wasD created by INSTALL. The number includes the address of the section.@ Version number (in hexadecimal) of global section; for; shareable images only, the high-order byte (04 inH INS$812E2AE0_nnn) contains major identification, and low-order: bytes (0003E8 in INS$812E2AE0_nnn) contain minorG identification determined by the programmer at link time. For? executable images, the number is a known unique value# N determined by the system.+ (4) Attributes of the global section:. DZRO Global section is demand-zero.? GRP Along with a group number indicates a groupwideB section, which would be created by a program other than INSTALL., PRM Global section is permanent.- SYS Global section is systemwide.D TMP Indicates a temporary global section, which would be8 created by a program other t Ohan INSTALL.+ WRT Global section is writable.D (5) Number of pagelets in the section and number of page table@ entries currently mapped to this global section. For a> more detailed discussion of mapping global sections,; refer to the OpenVMS Programming Concepts Manual.F (6) Number of global sections created, number of global pageletsE used, and number of global pagelets unused in local memory.B Note that, because of aritPhmetic rounding, the number ofD global sections created will sometimes be greater than theC SYSGEN parameter GBLSECTIONS. When the size of the systemE header is being computed, the values of the GBLSECTIONS andE SYSMWCNT parameters are combined with the size of the fixedE part of the process header. The result is rounded up to theB next page boundary. This rounding process sometimes addsD space to the global section table, depenQding on the valuesF of the two SYSGEN parameters and the amount of system pagingC 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 Sections . . .2 X86VMS$DKA0:EDTSHR.EXEE INS$81297980_009(00000000) PRM SYS Pgltcnt/Refcnt=48/0F INS$81297980_005(00000000) PRM SYS Pgltcnt/Refcnt=444/0E INS$81297980_004(00000000) PRM SYS Pgltcnt/Refcnt=17/0D INS$81297980_003(00000000) PRM SYS Pgltcnt/Refcnt=1/0- Owner: [SYSTEM] (1)< Protection: S:RWED,O:RWED,G:RE,W:RE (2) . . .0 (1) UIC of the owner of the global section. (2) TySpe of access allowed for the imageww g1 PURGEB Deletes all known file entries for images installed without the /NOPURGE qualifier.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 PURGE 2 Parameters None. 2 Description> The PURGE command deletes all known file entries for images, installed without theT /NOPURGE qualifier.C If a process is accessing global sections when the PURGE 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> PURGE@ The command in this example deletes all images except thoseB installed with the /NOPURGE qualifier. The image Ufiles remainB unaffected. Writable global sections are written back to disk( upon their removal as known images.ww g1 REMOVE@ 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 Nam Ves 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 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 the REMOVE command= is entered, the global sections are deleted only after theBW 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> REMOVE GRPCOMM@ The command in this example deletes the entry for the known2 image GRPCOMM from the known image file list.ww0?g 1 REPLACEB Replaces a known image entry with another version of the image, or with modified attributes.D RequiXres the CMKRNL privilege. Also requires the SYSGBL privilege? to create system global sections and the PRMGBL privilege to$ create permanent global sections. Format REPLACE file-spec 2 Parameter file-specF Names the file specification of an image to be installed as a knownD image. The file specification must name an existing executable or8 shareable image. If you omit the device and directoryB specification, the default SYS$SYSTEM is used. The default Yfile 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-level accounting for selected images even if image= aZccounting 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@ 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 o [bsolete kernel data cells are not maintained byD the system. 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 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 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 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 NotaesD 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 bwith 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 lo ccating 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 dwith 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 wriete 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)]8 C fauses image code segments/sections or read-only dataE segments/sections to be placed in the granularity hint regions andD compresses other image segments/sections, which remain located in@ process space. If you do not specify the /RESIDENT qualifier,B neither code nor data is installed resident. If you specify theC /RESIDENT qualifier without keyword arguments, code is installed0 resident, and data is not installed resident.D On x86-64, the image must be installed with /SHAREDg=ADDRESS_DATA.A On Alpha, the image must be linked using the /SECTION_BINDING= (CODE,DATA) qualifier. > An image installed with resident code or data is implicitly( installed header resident and shared./SHARED /SHARED[=[NO]ADDRESS_DATA] /NOSHARED? Installs the file as a shared known image and creates globalC sections for the image segements/sections that can be shared. An7 image installed shared is implicitly installed open.G When you ushe the ADDRESS_DATA keyword with the /SHARED qualifier, P1G space addresses are assigned for shareable images. With the assignedF addresses, the Install utility can determine the content of addressE data when the image is installed rather than when it is activated,B reducing CPU and I/O time. A global section is created to allow9 shared access to address data image segments/sections. /WRITABLE /WRITABLE=[GALAXY[=IDENT]] /NOWRITABLED Installs the file as a iwritable known image when you also specifyA the /SHARED qualifier. The /WRITABLE qualifier applies only to= images with image segments/sections that are shareable andD writable. The /WRITABLE qualifier is automatically negated if the$ /NOSHARED qualifier is specified.> On Alpha, you can use the GALAXY keyword with the /WRITABLEB qualifier to place write shared image segments in Galaxy globalF sections. You can also use the IDENT keyword with GALAXY to includeD the image idejnt in the name of the Galaxy global section, so thatG multiple versions of an image can be used simultaneously in a Galaxy system. 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