═══ 1. About... ═══ Title GIME Version 1.11 (C) Copyright IBM Corp. 1990, 1993. All rights reserved. ═══ 2. Introduction ═══ No longer will the overworked OS/2 LAN user have to remember archaic and cryptic resource names, or have to worry about which drive letter is free. GIME will do this and so much more for you. GIME has been tested and works well under OS/2 1.1 EE through OS/2 1.30.1 EE, and OS/2 2.x systems running IBM LAN Requester, and OS/2 TCP/IP. ═══ 3. Syntax ═══ The following describes the GIME syntax: ┌──────────────────┐  │ gime ───────┬────────────┬───────┬──────────┬──────┬───────────┐ │ │ │ │ │ │ ├──┘ ├─ resource ─┤ └─ device ─┘ └─ /option ─┘ │ │ └───── ? ────┘ ═══ 4. Resource Alias Resolution ═══ GIME provides the user with the ability to setup aliases for commonly used server resources. GIME also autmatically searches all servers in the current domain for a shared resource which matches a specified resource alias. This This section discusses the way in which GIME resolves resource aliases, and how the user may setup Resource Alias Definition Files. If the resource netname specified by a GIME parameter is not a UNC resource, then it is a resource alias which must be resolved. The resolution strategy follows: 1. All NETALIAS.LST files along the DPATH and the NETALIAS.PATH are searched until a match is found or until all files are exhausted. See the "Resource Alias Definition Files (NETALIAS.LST)" for further details. 2. If a match is not found in the NETALIAS.LST files, then GIME compares the alias against all shared resources of all accessible servers in the current domain, until a match is found or until all shared resources are exhausted. ═══ 5. Resource Alias Definition Files (NETALIAS.LST) ═══ By default, the resource alias definitions should be placed in the file NETALIAS.LST, which should be in a subdirectory specified in your DPATH. A sample NETALIAS.LST file is given below: CORE \\YKCOS01\CORE01 /D=C: /P=CONFID Core alias num 1 OS2TOOLS \\OS2TOOLS\OS2TOOLS /P=OS2PASS OS2 Tools Alias 3812 \\PRNTSERV\3812QUE /D=LPT1 OS2 Tools Alias MYALIAS \\MYSERVER\MYALIAS Alias on myserver RS6000 myrs6000:/home/user /FS=NFS RS-6000 NFS alias OS213 OS213 /FS=SERVICE /P=CONFID SRVIFS alias Note: Each entry consists of the alias, followed by one or more spaces, followed by the actual resource, followed by one or more spaces, followed by one or more optional options parameters, followed by an optional comment. A user may have multiple NETALIAS.LST files in their DPATH. For example, a user may have a personal NETALIAS.LST file which has only a few entries in one subdirectory in the DPATH, and a public NETALIAS.LST file (on a file server) which has many entries. GIME will attempt to resolve a resource alias by searching all NETALIAS.LST files it finds along the DPATH, stopping at the first resolution or once all files have been exhausted. ═══ 6. Environment Variables ═══ A user may override or set GIME options and characteristics by using the following environment variables: o NETALIAS.FILE The default NETALIAS.LST file name may be overridden by either the /A= command parameter, see the Syntax section for further details, or via the environment variable NETALIAS.FILE. The NETALIAS.FILE environment variable may specify a full file spec (eg d:\path\file.ext) or a file name only. If only the file name is given, the file will be searched for along the DPATH. The NETALIAS.FILE environment variable also overrides the /A parameter. Note: Throughout this document the resource alias definition file will be referred to as the NETALIAS.LST file. Keep this in mind if you are using a different file name. o NETALIAS.PATH The NETALIAS.PATH environment variable may be used to specify where the NETALIAS.LST file(s) may be found. If the NETALIAS.PATH environment variable exists, it will be searched before the DPATH. o GIME.USE. The GIME.USE. can be used to define the attach command for any IFS. For example, the attach command for NFS might look like the following: SET GIME.USE.NFS=mount {drive} {alias} You may specify multiple GIME.USE. environment variables to fully profile all installed file system attach commands. Note: The GIME.USE. environment variable setting may include the following strings which will be replaced as follows: {drive} - Replaced by drive to be used in the attachment. {alias} - Replaced by resource to be attached to. {password} - Replaced by password specified. o GIME.DROP. The GIME.DROP. can be used to define the drop command for any IFS. For example, the drop command for NFS might look like the following: SET GIME.DROP.NFS=umount {drive} You may specify multiple GIME.DROP. environment variables to fully profile all installed file system drop commands. Note: The GIME.DROP. environment variable setting may include the following strings which will be replaced as follows: {drive} - Replaced by drive to be dropped. {alias} - Replaced by resource to be dropped. {password} - Replaced by password specified. Note: Any of the above environment variables may be set by default in the GIME Control File. Environment variable defaults will override Control File defaults, thus allowing users to personalize GIME via environment variables while simultaneously allowing a network administrator to setup GIME defaults via a remote GIME.CTL file. See the Sample Control File section for further details. ═══ 7. Sample Control File ═══ GIME will search for the Control File, GIME.CTL, along the DPATH when it is executed. The Control File may include default GIME Environment Variable settings. Actual environment variable settings will override anything profiled in the GIME.CTL file. The following displays the contents of a sample GIME.CTL file which profiles the GIME environment variables for describing alternate File System attach and drop commands: GIME.USE.SERVICE=srvattch {device} {alias} GIME.DROP.SERVICE=srvattch {device} /D GIME.USE.NFS=mount {device} {alias} GIME.DROP.NFS=umount {device} GIME.USE.LCSF=drvattch {device} {alias} GIME.DROP.LCSF=drvdetch {device} Note: View the Environment Variables section for a full description of all supported GIME environment variables. ═══ ═══ Provide limited on-line help. ═══ ═══ Specifies the resource to assign. The resource parameter may be either a UNC Resource or a GIME Resource Alias. The definition for each resource type follows: UNC Resource Any resource which has the form \\server\\alias. For example: \\YKCOS01\CORE01 GIME Resource Alias Any resource which does not start with the '\\' characters. GIME resolves this resource alias to a UNC resource if it can be found in the NETALIAS.LST file. See the Resource Aliases section for further details. ═══ ═══ May be any of the following: A: - Z: If a drive letter is given, GIME will assign the specified resource to the specified drive letter. COMx: If a COM port is given, GIME will assign the specified resource to the specified serial communications port. LPTx: If an LPT port is given, GIME will assign the specified resource to the specified parallel communications port. If no device parameter is specified, GIME will assume that you are assigning a resource which requires a drive and assign it to the first available drive it finds (searching from the end of the drive list). ═══ ═══ The options field may contain any 'sensible' combination of the following: /A Used to display aliases profiled in NETALIAS.LST files. If used as the sole parameter to GIME, the contents of all found NETALIAS.LST files will be displayed. If used in conjunction with a use or drop request, only those aliases found up to the resolved alias will be displayed. Use this feature as a way to debug from which NETALIAS.LST file an alias is being resolved. /A=filename Used to override the default alias name of NETALIAS.LST. The filename entry may specify a full file spec (eg d:\path\file.ext) or a file name only. If only the file name is given, the file will be searched for along the DPATH. See the Resource Aliases section for further details. /B Used to override the default free drive search strategy. If specified, this option will force the search to start at the beginning of the drive list. /D Instructs GIME to drop the specified resource or device. If no resource or device has been specified, GIME will interactively allow you to drop all LAN resources currently in use. /F Forces GIME to perform whatever you are telling it to do. This is necessary if you want GIME to assign a preassigned drive resource to another drive. /FS=installable file system Used to specify a resources Installable File System (IFS) type. The default type is LAN. GIME has been enhanced to perform attachments and drops for any number of Installable File Systems. However, GIME really only knows how to perform attachments and drops for LAN resources. For other IFS types, the required attach and drop commands must be profiled either via environment variables or the GIME Control File, GIME.CTL. See the Environment Variables section for further details on the profiling of FS attach and drop commands. /P=password When using resources from domains other than the logon domain it is required that you specify a password if your password on said domain is different than the password used for logon. The password field is case insensitive. Note: LAN resource passwords should be considered IBM Confidential. /Q Instructs GIME to perform its task without prompting the user (all 'would-be' prompts are assumed answered positively) and without unnecessary output formatting. This mode is useful if calling GIME from a REXX exec. /R When assigning a resource, this parameter instructs GIME to assign the specified resource without attaching it to a local device. When dropping a resource this parameter instructs GIME to drop the specified resource that is not attached to a device. ═══ ═══ A resolve file entry options parameter may be any of the following: /D=device The local device to use for the attachment of the resource alias. This parameter is overridden if the user supplies a local device via the GIME command. See the Syntax section for a description of valid device parameters. /P=password When using resources from domains other than the logon domain it is required that you specify a password if your password on said domain is different than the password used for logon. The password field is case insensitive. Note: LAN resource passwords should be considered IBM Confidential. /FS=installable file system Used to specify a resources Installable File System (IFS) type. The default type is LAN. GIME has been enhanced to perform attachments and drops for any number of Installable File Systems. However, GIME really only knows how to perform attachments and drops for LAN resources. For other IFS types, the required attach and drop commands must be profiled either via environment variables or the GIME Control File, GIME.CTL. See the Environment Variables subsection of the Resource Aliases section for further details on the profiling of FS attach and drop commands.