Advertisement
Guest User

Untitled

a guest
May 29th, 2012
40
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 19.38 KB | None | 0 0
  1. # *****************************************************************************
  2. # Copyright (c) 1994-2008
  3. # UGS. All rights reserved
  4. # SCCS: @(#) link_stamp ug_install.hlp V6.0.0.24 06/18/08 18:41:03
  5. # *****************************************************************************
  6. # Rev History:
  7. # 6.0 Ric Baxter 31JUL07 Initial NX 6.0 version taken directly from NX 5.0.
  8. # 6.0 Ric Baxter 21FEB08 Phase 19 Updates for allowed use of license file.
  9. # 6.0 Ric Baxter 27MAR08 Phase 21 More updates for standalone licensing.
  10. # 6.0 Ric Baxter 20MAY08 Final NX6 version.
  11. # *****************************************************************************
  12. # This file contains the text for on-line help information in ug_install.
  13. # Sections within this help file are named according to a corresponding
  14. # script function within ug_install.
  15. # *****************************************************************************
  16.  
  17.  
  18.  
  19.  
  20. Ask_base _____________________________________________________________________
  21.  
  22. This installation requires the following directory structure.
  23.  
  24. $UGII_BASE_DIR
  25. |
  26. -----------------------------------------------
  27. | | | | | | |
  28. /bin /ugflexlm /install /admin /ugii /mach ...
  29.  
  30. Where UGII_BASE_DIR is defined during installation by the system
  31. administrator and the sub-directories (/bin, /ugflexlm, /install ...)
  32. are created automatically by this install script.
  33.  
  34. The BASE directory will be the top of the directory structure for the
  35. NX Products. The individual products will be located in
  36. subdirectories of the BASE directory.
  37.  
  38. Although the recommended default is: '/usr/ugsXXX' (where XXX is the
  39. version number), the directory is user selectable and may actually be
  40. located in another directory or disk. If so, a symbolic link called
  41. '/usr/ugsXXX' will be created to point to the user chosen directory.
  42.  
  43. NOTE: You cannot use a path that includes a subdirectory of /usr/ugsXXX
  44. because the /usr/ugsXXX directory name is a reserved pathname with
  45. an expected tree structure used by other programs and scripts.
  46.  
  47. For example, updates and other programs will look for /usr/ugsXXX/ugii
  48. to update or access the 'ugii' kit and would fail if an intermediate
  49. subdirectory existed e.g. /usr/ugsXXX/NX/ugii
  50.  
  51. You may enter /usr/ugsXXX or another directory such as '/usr/NXxxx', or
  52. '/var/NX_VXXX' but not a subdirectory of /usr/ugsXXX.
  53.  
  54. NOTE: This script will always attempt to locate or create /usr/ugsXXX
  55. as a link or directory. If /usr/ugsXXX is a system mount point, you
  56. must use /usr/ugsXXX as your BASE directory.
  57.  
  58. NOTE: The BASE directory you specify, may be on an NFS mounted
  59. filesystem, but for the 'load+configure' operation this node must
  60. have full root access to that NFS mounted directory.
  61.  
  62. The recommended method to install NX on NFS mounted
  63. directories, is to use the 'load & configure' option on the
  64. server then run the 'configure only' on the NFS client(s).
  65.  
  66.  
  67. END_Ask_base _________________________________________________________________
  68.  
  69.  
  70.  
  71. Ask_modify_ok _________________________________________________________________
  72.  
  73. System files must be modified to allow execution of NX:
  74.  
  75. /etc/profile (all systems)
  76. /etc/services (nodes using local services)
  77.  
  78. /etc/.login (Sun & OSF)
  79. /etc/cshrc (SGI Only)
  80. /etc/csh.login (HP Only)
  81.  
  82. If you are unfamiliar with these files, they are probably still
  83. in their stock vendor form, and you can safely allow this script
  84. to continue. (answer yes).
  85.  
  86. You may escape to the shell and save your own copies (enter '!').
  87.  
  88. If you answer 'yes' this install will save your files in an ugs_tmp
  89. directory with a pid number extension.
  90.  
  91. If you answer 'no' the system files will NOT be modified, but
  92. NX will NOT be configured to run on this node.
  93.  
  94. END_Ask_modify_ok _____________________________________________________________
  95.  
  96.  
  97.  
  98. Ask_overwrite_ok ______________________________________________________________
  99.  
  100. This prompt provides a last warning to prevent overwriting files
  101. that you wished to save in BASE DIR.
  102.  
  103. The install will replace existing NX files with newer
  104. NX files, this is normal for an update installation.
  105.  
  106. To select another directory, answer NO to this prompt,
  107. then change the BASE DIR selection.
  108.  
  109. END_Ask_overwrite_ok _________________________________________________________
  110.  
  111.  
  112.  
  113. Ask_install_type ______________________________________________________________
  114.  
  115. The options displayed represent the types of installations that
  116. are possible using ug_install. The function of each option
  117. is as follows:
  118.  
  119. 1) - 'load+configure'. This option will load NX and
  120. optional products from the installation media or a previously
  121. loaded disk.
  122.  
  123. This option will ALSO configure all the required directory
  124. structures, environment variables, and system files.
  125.  
  126. Use this option to do a full and complete installation.
  127.  
  128. 2) - 'load_only'. This option will simply load the NX
  129. files into a source directory on disk. NO configuration is done.
  130.  
  131. Use this option when it is desired to complete configuration
  132. at a later time, or when multiple installation will be done on
  133. other nodes on the network.
  134.  
  135. After the source directory is loaded it can be remote copied
  136. across the network using 'rcp' or it can be used as a remote
  137. source directory via NFS.
  138.  
  139. 3) - 'configure_only'. This option will only configure a previously
  140. loaded or installed NX node. This will configure all the
  141. required directory structures, environment variables, and
  142. system files.
  143.  
  144. Use this option only after using option 1 or 2. or on a NFS client
  145. node, that is served by a node that has ALREADY run option 1.
  146.  
  147. You may also use this option if it is desired to change any
  148. configuration parameter after the initial installation.
  149.  
  150. END_Ask_install_type __________________________________________________________
  151.  
  152.  
  153.  
  154. Ask_main_screen _______________________________________________________________
  155.  
  156. This screen provides the opportunity to change various parameters
  157. before continuing with the install.
  158.  
  159. Items that are flagged 'n/a' are not applicable.
  160.  
  161. Items are not checked until after continue is entered.
  162.  
  163. The following is a brief description of the whole screen, individual
  164. items contain further help to explain each question:
  165.  
  166.  
  167. 1. UG Installation type. _______________________________________ []
  168.  
  169. This is the type of NX installation to perform, options are:
  170.  
  171. load+configure - this will completely load and then configure UG to
  172. run on this node.
  173.  
  174. load_only - this will simply load UG but not configure it to run.
  175.  
  176. configure_only - this will configure UG that was previously loaded, or
  177. loaded and configured. i.e. re-configure UG
  178.  
  179.  
  180. 2. SOURCE directory. ___________________________________________ []
  181.  
  182. This is the source directory containing the NX filesets
  183. to be loaded by the install.
  184.  
  185. This entry can be a local disk directory, an NFS mounted disk
  186. directory or a DVDROM directory.
  187.  
  188.  
  189. 3. BASE directory. _____________________________________________ []
  190.  
  191. This entry will specify where to load the NX files. The
  192. install will automatically create the necessary subdirectories
  193. beneath this 'BASE' directory.
  194.  
  195. The recommended location for this top level or 'BASE' directory
  196. is: /usr/ugsXXX, but it is user selectable and can be on any local
  197. or NFS mounted file system. The install will automatically
  198. create a '/usr/ugsXXX' link to point to the real location.
  199.  
  200. The 'load+configure' operation will require full root access to
  201. the 'BASE' directory.
  202.  
  203. The 'configure' only option does not need root access, but will
  204. only configure a previously installed BASE directory.
  205.  
  206.  
  207. 4. O.K. to MODIFY local system files. _________________________ []
  208.  
  209. This entry signifies permission to modify local system files. These
  210. changes are required to allow NX to run on this system.
  211.  
  212. A backup is made of the system files before modification.
  213.  
  214. If this permission is denied, the files will NOT be modified, but
  215. NX will not be configured to run on this node.
  216.  
  217. This method can be used on NFS servers that are serving, but not
  218. running NX.
  219.  
  220.  
  221.  
  222. 5. License file or server name(s). ______________________________ []
  223.  
  224. This entry may be a path to a license file, a server name or a list
  225. of server names.
  226.  
  227. License file is a full path to a locally accessible NX license file.
  228.  
  229. UGFLEXlm Server(s) names are the nodename(s) on your network that
  230. supply FLEXlm licenses TO THIS node for NX.
  231.  
  232. These server names may OR may NOT include this local node.
  233.  
  234. NOTE: To RUN NX on this node you MUST specify a path to a valid
  235. license file or server name(s).
  236.  
  237.  
  238. END_Ask_main_screen ___________________________________________________________
  239.  
  240.  
  241.  
  242. Ask_source ____________________________________________________________________
  243.  
  244. This question is prompting you for the source of the NX files.
  245.  
  246. You may answer with (1) of the following options:
  247.  
  248. a) The absolute pathname of the disk directory where NX has
  249. already been loaded.
  250.  
  251. b) The absolute pathname of the CDROM directory where NX has
  252. been mounted.
  253.  
  254. c) The network pathname to a remotely mounted directory, this option
  255. requires a previously mounted NFS directory.
  256.  
  257. d) You may specify your present directory by entering a period.
  258.  
  259. e) You may specify your parent directory by entering two periods.
  260.  
  261. Relative pathnames will be converted to absolute pathnames based
  262. on the present working directory.
  263.  
  264. Entering a carriage return will take the displayed default.
  265.  
  266. END_Ask_source ________________________________________________________________
  267.  
  268.  
  269.  
  270. Ask_source2 __________________________________________________________________
  271.  
  272. This question is prompting you for an additional source directory
  273. for that contains NX kits. This prompt has appeared because one
  274. or more kits that were selected for loading are not located
  275. in the current source directory.
  276.  
  277. This prompt first appears when missing kits are first detected. At
  278. this time you may enter an additional source directory in advance
  279. of loading the kits.
  280.  
  281. This prompt also appears if no additional source directory has been
  282. supplied. At this point you must enter a new directory or change
  283. the CD in order to complete the load.
  284.  
  285. You may answer with (1) of the following options:
  286.  
  287. a) The absolute pathname of the disk directory that contains NX kits.
  288.  
  289. b) The absolute pathname of the CDROM directory where the NX kits
  290. have been mounted.
  291.  
  292. c) The network pathname to a remotely mounted directory, this option
  293. requires a previously mounted NFS directory.
  294.  
  295. d) You may specify your present directory by entering a period.
  296.  
  297. e) You may specify your parent directory by entering two periods.
  298.  
  299. Relative pathnames will be converted to absolute pathnames based
  300. on the present working directory.
  301.  
  302. Entering a carriage return will take the displayed default.
  303.  
  304. END_Ask_source2 _______________________________________________________________
  305.  
  306.  
  307.  
  308. Ask_ugs_servers _______________________________________________________________
  309.  
  310. License file or server name(s).
  311.  
  312. This entry may be a server name or a list of server names OR
  313. a path to a license file,
  314.  
  315. License file is a full path to a locally accessible 'Standalone'
  316. license file. You cannot use a 'Server' license file. These files
  317. are for use by the licensing daemon ONLY and are identifiable by
  318. lines in the file containing the keyword: SERVER.
  319.  
  320. UGS License Server(s) are the nodename(s) on your network that
  321. supply UGS licenses TO this node for NX.
  322.  
  323. This node may a client of these remote servers, but it may ALSO be a
  324. server, and may be entered in this list.
  325.  
  326. Nodename(s) entered should be preceeded by an 'at' (@) sign, but if
  327. not, they will be added by this script. i.e. NodeA -> @NodeA
  328.  
  329. The Nodenames may be entered IN ANY OF the following formats:
  330.  
  331. 1. A full FILENAME for a Standalone License file
  332. e.g. /dir/file
  333. 2. SINGLE server nodename.
  334. e.g. @NodeA
  335. 3. A Group of REDUNDANT servers - each separated by a comma ','
  336. e.g. @NodeA , @NodeB , @NodeC
  337.  
  338. Note: NX uses these servers IN THE ORDER entered.
  339.  
  340. Entries supplied here will be used on this system to set the global
  341. environment variable: UGS_LICENSE_SERVER
  342.  
  343. WARNING: To RUN NX on this node you MUST specify a full path to a
  344. valid license file or server name(s).
  345.  
  346. END_Ask_ugs_servers ___________________________________________________________
  347.  
  348.  
  349.  
  350. Check_space ___________________________________________________________________
  351.  
  352. This prompt indicates that the filesystem containing BASE DIR
  353. may overflow if the selected products are loaded.
  354.  
  355. Options are:
  356.  
  357. 1. Continue anyway. This will attempt to load the files even though
  358. there doesn't appear to be enough free space.
  359.  
  360. If you are updating an existing version of NX, the disk space
  361. used by existing files is NOT included in the calculation.
  362.  
  363. This will re-use the space currently used by files in BASE DIR.
  364.  
  365. NOTE: Do NOT use this option if BASE DIR is an empty directory.
  366.  
  367. 2. Re-select products or directories. Use this option to return to
  368. the product selection screen. This provides the option to
  369. de-select some of the products or change their directories i.e,
  370. move some product(s) to another filesystem.
  371.  
  372. 3. Re-select base directory. This will allow the installer to change
  373. the base directory location to a new filesystem that contains
  374. more free space.
  375.  
  376. Using this option will re-run part of this install to select and
  377. create a new structure. The old BASE DIR stucture will NOT be
  378. removed automatically.
  379.  
  380. You may also escape to the shell using '!' to free space manually.
  381.  
  382. END_Check_space _______________________________________________________________
  383.  
  384.  
  385.  
  386. Modify_services _______________________________________________________________
  387.  
  388. This entry will supply the port number that will be used by
  389. NX processes when communicating over the network.
  390.  
  391. If the default port number is already in use, you will be
  392. prompted for a new number to use for that service.
  393.  
  394. The default number supplied is the convention used by NX.
  395.  
  396. You may supply a different number, but the same port number must
  397. be used for the same service on each node of your network.
  398.  
  399. The following are the default port numbers used by UGS services.
  400.  
  401. ugplot 2365
  402. netlisp 3601
  403.  
  404. END_Modify_services ___________________________________________________________
  405.  
  406.  
  407.  
  408. Select_products _______________________________________________________________
  409.  
  410. The 'Product Selection Menu' offers the option to pick and chose the
  411. products that you wish to load.
  412.  
  413. The '->' flag in the left margin indicates selection.
  414.  
  415. The product names followed by '**' are 'required' and may never be
  416. de-selected UNLESS they have been previously loaded.
  417.  
  418. NOTE: To install 'UGFLEXLM' only on license servers, use the
  419. 'license_server' installation type (under question 1).
  420.  
  421. The 'UGII' kit is required on all other installation types.
  422.  
  423. Products may be manually selected/de-selected by entering the number
  424. in the first column. These numbers may be entered individually or
  425. as a sequence of numbers separated by a comma or space i.e. 1,2,3.
  426.  
  427. Additional options:
  428.  
  429. 95) Change directories. - Change destination sub directories.
  430. 96) Select required. - Select products marked '**'.
  431. 97) All - Select all products on the list.
  432. 98) None - Deselect all products on the list.
  433.  
  434. It is NOT recommended to use these options in entry sequences, as
  435. this MAY yield unanticipated results i.e. 1,2,98 will leave nothing.
  436.  
  437. When you enter 'continue' the selected products will be loaded.
  438.  
  439. Product Descriptions:
  440. ADMIN - UG Administrative utilities.
  441. CATIAV5
  442. DXFDWG
  443. IGES
  444. LOCALIZATION - International Native Language
  445. MACH - Machining.
  446. MECH - Mechanisms.
  447. MOLDWIZARD
  448. NXCAE_EXTRAS
  449. NXHUMAN
  450. NXPLOT - Plotter despoolers.
  451. NXSHIP
  452. PDIEWIZARD
  453. POSTBUILD
  454. PSTUDIO
  455. PVTRANS
  456. REL_INFO - On line Release Notes and What's new Guide.
  457. STEP203UG
  458. STEP214UG
  459. TOLSTACKUP
  460. TOOLING_BASE
  461. UG2MCON - Unigraphics Machine conversion.
  462. UGALLIANCE - UG Partners sample files and directory.
  463. UGAUTOMOTIVE
  464. UGCHECKMATE
  465. UGEXPMAN
  466. UGFLEXLM - UG FLEXlm license kit.
  467. UGHARNESS - Wire harness.
  468. UGII - Main Unigraphics Design/Drafting.
  469. UGIMW
  470. UGMANAGER - UG/IMAN Part Management.
  471. UGOPEN - Grip development and User Function.
  472. UGOPENPP
  473. UGPCBXCHANGE
  474. UGPHOTO
  475. UGPROCESS_AID
  476. UGROUTE_ELEC
  477. UGROUTE_MECH
  478. UGSAMPLES
  479. UGSTRUCTURES
  480. UGSTUDIO - Photo Realistic rendering.
  481. UGSAMPLES - Sample user tools.
  482. UGTO2D
  483. UGWEB - Unigraphics Web Authoring tool.
  484. UGWELD
  485. UNFOLD - Sheet metal layout.
  486. UGROUTING - Foundation kit for all Routing applications.
  487. UGCONDUIT - Conduit specific Routing application and part library.
  488. UGPIPING - Piping specific Routing application and part library.
  489. UGRACEWAY - Raceway specific Routing application and part library.
  490. UGSTEELWORK - Steelwork specific Routing application and part library.
  491. UGTUBING - Tubing specific Routing application and part library.
  492. UGWIRING - Wiring specific Routing application and part library.
  493.  
  494.  
  495. END_Select_products ___________________________________________________________
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement