| 1 | ZIBRPI2 ; IHS/ADC/GTH - REMOTE PATCH INSTALLATION (2) ; [ 02/07/97 3:02 PM ]
|
|---|
| 2 | ;;4.0;XB;;Jul 20, 2009;Build 2
|
|---|
| 3 | ;
|
|---|
| 4 | W !!,"EXECUTION UNAUTHORIZED.",!
|
|---|
| 5 | Q
|
|---|
| 6 | ;
|
|---|
| 7 | GEN ; General description
|
|---|
| 8 | ;;This utility creates an entry in the OPTION file which is scheduled
|
|---|
| 9 | ;;to run daily thru TaskMan. Files matching the naming conventions
|
|---|
| 10 | ;;for patch files (specified in the 1 Sep 94 SAC, Appendix E), are
|
|---|
| 11 | ;;looked for in the directory you indicate. If the package and
|
|---|
| 12 | ;;version the patches are intended for are installed on this machine,
|
|---|
| 13 | ;;the routines are restored from the file, an entry is made in the
|
|---|
| 14 | ;;VERSION multiple of the PACKAGE file entry, and a report file is
|
|---|
| 15 | ;;sent to the systems you indicate. If an action routine (A9 or B9)
|
|---|
| 16 | ;;is detected during the ZLOAD, and you have indicated permission to
|
|---|
| 17 | ;;run action routines, the action routine is called after all routines
|
|---|
| 18 | ;;have been restored.
|
|---|
| 19 | ;;NOTE: Use the same entry point, OPT^ZIBRPI, to edit any changes you
|
|---|
| 20 | ;; want to make to the parameters. If you un-schedule the
|
|---|
| 21 | ;; option, you must use the TaskMan options to re-schedule it.
|
|---|
| 22 | ;;###
|
|---|
| 23 | ;
|
|---|
| 24 | SYSID ; Select system id's to receive result files.
|
|---|
| 25 | ;;Please indicate what system id's you want reports of results sent to.
|
|---|
| 26 | ;;Selecting 1 will send the report just to that system.
|
|---|
| 27 | ;;Selecting 2 will send the report to (what is intended to be) the
|
|---|
| 28 | ;;Area machine.
|
|---|
| 29 | ;;Selecting 3 will send the report to both systems.
|
|---|
| 30 | ;;It is recommended you just configure the utility to send report files
|
|---|
| 31 | ;;to your area machine (option 2).
|
|---|
| 32 | ;;NOTE: root will be notified upon arrival of a uucp'd result file.
|
|---|
| 33 | ;; You must read the file manually.
|
|---|
| 34 | ;;###
|
|---|
| 35 | ;
|
|---|
| 36 | DIRECT ;
|
|---|
| 37 | ;;Enter the name of the directory into which files containing patches
|
|---|
| 38 | ;;are uucp'd or BLAST'd, or otherwise placed. This is usually the
|
|---|
| 39 | ;;/usr/spool/uucppublic directory on unix machines. You can designate
|
|---|
| 40 | ;;any directory that you want, for security purposes, but you should
|
|---|
| 41 | ;;ensure that permissions are correctly set to receive the files, and
|
|---|
| 42 | ;;to read the files from the MUMPS level.
|
|---|
| 43 | ;;THIS DIRECTORY MUST EXIST PRIOR TO COMPLETING THIS SET-UP.
|
|---|
| 44 | ;;###
|
|---|
| 45 | ;
|
|---|
| 46 | ACTION ;
|
|---|
| 47 | ;;If an action routine is include in the patch file, do you want it
|
|---|
| 48 | ;;called after all the routines are restored? The action routine will
|
|---|
| 49 | ;;be named (A/B)9<namespace><patch_number>. E.g., A9AUM12 will be the
|
|---|
| 50 | ;;action routine for patch 12 to the table updates.
|
|---|
| 51 | ;;NOTE: This feature allows you to do any type of unattended activity
|
|---|
| 52 | ;; on any/all of your systems. There is no checking for verified
|
|---|
| 53 | ;; RPMS applications. There must simply be an entry in PACKAGE,
|
|---|
| 54 | ;; and the versions must match.
|
|---|
| 55 | ;;###
|
|---|
| 56 | ;
|
|---|
| 57 | HELP(L) ;EP - From DIR
|
|---|
| 58 | W !
|
|---|
| 59 | F %=1:1 W !?4,$P($T(@L+%),";",3) Q:$P($T(@L+%+1),";",3)="###"
|
|---|
| 60 | Q
|
|---|
| 61 | ;
|
|---|
| 62 | ; dpssyg Any ACU2400 FTS-505-262-6250 n:--n:--n: uucpdps word: uucpdps
|
|---|
| 63 | ; dpssyg Any x25pad 9600 dpssyg "" \r n:--n:-@-n: uucpdps word: uucpdps
|
|---|
| 64 | ;
|
|---|
