J$MLU021.ApMLU021.ABACKUP/NOASSIST/COMMENT=VAX/VMS SPKITBLD Procedure/INTER/LOG/VERIFY MLU02%.RELEASE_NOTES,KITINSTAL.COM,UNKNOWN_DEVICE_MEMO.TXT SYS$SYSDEVICE:[0,0]MLU021.A/LABEL=(MLU)/SAVE/BLOCK=9000/GROUP=25VAX/VMS SPKITBLD Procedure LANE `ufΗV5.5 _THETOY::  _$2$DIA0: V5.5-2 $!*[LANE.MLU]MLU020.RELEASE_NOTES;11+,./ 4J-0123KPWO56Жdw7fΗ89GHJ  RELEASE NOTES =============- Product: Media Loader Utility Program (MLU)3 Contents: file MLU020.A, MLU020.B, this and other documents Date: 01 March 1994 Product version: 2.08 Reason for release: Major update. New product support,4 bug fixes, misc tweeks. See "Changes since last release" below.$ Prerequisite VAX/VMS version: 5.4& Prerequisite Alpha/VMS version: 1.5- Supported devices: TF857 TZ857 TA85< TA857 TA867 TF86 TF867 TZ867# SA100 SA106< TLZ06 on VMS 6.x and Alpha 1.5 systems,- TLZ06 as TLZ6 on VMS 5.x; TZ857, TZ867 and TLZ06 on HSC's K.SCSI TL820 TZ8778 Unsupported devices (no loader present):* TZ86 TF85 TZ85. Unsupported system components:& Any HSC running V8.30 software. KDM70 HSC50, Served tapes in a cluster - See known5 limitations section at end of this doc.4 Any TMSCP tape (TF..M, TA.., etc) on an Alpha system.5 Related documentation: MLU User's Guide (date: TBD) Initial release: 26 Nov 1991$ Installation time: about 4 minutes Brief description of product ----------------------------. The Media Loader Utility serves two purposes:3 * to provide DCL access to media loaders> * to provide tape operators with a means of rapidly: verifying the contents of a magazine before starting0 a lengthy backup/restore operation. Installation procedure ----------------------= The MLU is installed using the standard VMSINSTAL procedure.F No options are required. There are (possibly) two non-standard questions: (paraphrased)A 1) MLU can be installed so that only priviledged users: can use it or so that every user can use it. Which?= 2) A previous version of MLU exists. Save the old startup file?A After installation, the system start up procedure must beF modified to cause the execution of SYS$STARTUP:MLU$STARTUP.COM= This is usually done in SYS$MANAGER:SYSTARTUP....COM.E Please check the comments at the beginning of product startupB procedure SYS$STARTUP:MLU$STARTUP.COM. Special action must, be taken for SCSI bus based devices.$ Additional Installation Information$ -----------------------------------< The install kit savesets (MLUxxx.A & MLUxxx.B) contain some5 files that are not installed into the user's system.B These files consist of information that is of no value to general2 users or is used only by experienced programmers.B To view the contents of the savesets, issue the following command from the DCL prompt:@ $ BACKUP/LIST MLUxxx.A/SAVE -or- $ BACKUP/LIST MLUxxx.B/SAVE Files of interest:5 A) UNKNOWN_DEVICE_MEMO.TXT - Details configurations1 where the device type is not known to VMS.1 B) MLU_RTL_INTERFACE.TXT - Details the software interface to the RTL., B) MLURTLDEF.H - a C language include file% Revision Matrix of supported devices% ------------------------------------@ This chart lists the versions of microcode that must be present= in the indicated device types. See device specific documents4 (or Field Service) on how to get microcode updates. | TF85, TF86 - V4 +-----------= Note: This device does not have a loader and therefor this@ Media Utility is of little value to TF85 users. Devices: with V1, 2 or 3 will cause MLU to report that the? display command is not supported. Devices with V4 will7 cause MLU to report that no loader is present. | TF857, TF867 - V4 +-------------E Note: See limitation section at end of these release notes.. | TZ85, TZ86 - V3 (date: Jan 1992) or later +-----------J Note: see above note re: no loader. Response of V1 code unknown.0 | TZ857, TZ867 - V3 (date: Jan 1992) or later +-------------? Note: As of this release, the current version of TZxxA microcode is V24. No testing of MLU will occur on? older versions and future MLU changes may cause problems.1 | TLZ6, TLZ06, TLZ6L - V4.91 (Aug 1993) +------------< Note: The TLZ06 device shows up as different device types? on different VMS versions. References in these release8 notes and other documentation will be "TLZ06" and mean8 any variation encountered. See UNKNOWN_DEVICE_MEMO.TXT3 | TA857, TA867, SA100, SA106 - V7 formatter ROMS& +---------------------------= Note: With HSC V650, MLU requires a TUdriver that sets theD MBI modifier. See THETOY::MLU$KIT:SA100_MEMO.TXT for more details.E With HSC V800+, the special TUdriver is not required.5 With HSC V830, MLU will not work - see limitations.: The HSC50 is not supported by MLU or, moreB accurately, the HCS50 does not support IO$_DISPLAY? commands and MLU cannot work without them. This" will not be fixed.B The KDM70 is not supported by MLU, reason unknown.A | TZ877 - T10-2 (field test version) (date: FEB 1994) or later +------ Changes since last release --------------------------B 1. Divided the single .EXE file of older MLU versions intoA a Run Time Library file (RTL) and an application file.C This permits other (future) applications to use the bulk* of MLU's device handling capabilities.G 2. Combined the VAX/VMS and Alpha/VMS executables into a singleG saveset with an install procedure that determines what files# to install during installation.D 3. Added option during install to save the MLU$STARTUP file. 4. Added TZ877 support.3 5. Added the IMPORT, EXPORT and TRANSFER commands.1 6. Added TL820 (also latent 810) support.A 7. Expanded scope of element type identifiers (TK50, TK87, etc.)G to be more accurate. Example: A TZ877 can support TK50, TK70I TK85, TK86 and TK87 cartridges/media formats. Type identifiers= will be "TK50/70" if it's known that the tape is 50 or 70B but not which. Similarly, "TK85/86/87" for a tape with a known: cartridge type but unknown format. As a information is= accumulated during a verify, the type identifiers will be4 updated to accurately reflect known information. 8. Numerous small fixes. Known limitations -----------------A Note: Not a single request has been received for featuresE outlined in #2 and #3. They may be dropped. As is, no planned implementation date.8 1. MLU will not work on any HSC running V8.30 software.# This can not/will not be fixed.0 2. /EXPECT="@file.name" is not implemented yet.? 3. The /DATA switch has been defined but not implemented. ThisE switch causes the output of a fixed format file containing= the contents of whatever holds the tape(s). If anyone has* a need for this, please say so. 4. The command:E $ mlu verify/expect=(all:init,6:empty,4:noinit) $1$mia4C fails because the "all:init" and the "4:noinit" conflictA and there is no test for this - yet. There are lots of similar situations.H 5. There is a bug in V4 code for the TF8x7 (DSSI) that sometimesE causes the SELECT, UNLOAD and VERIFY commands to fail with9 an illegal command indicator. SHOW continues to work.D The bug is believed to be triggered by using the loader's; Eject button (ie open door) to also rewind and unload a cartridge in the drive.: Suggest all MLU script files use the UNLOAD command `ulp$MLU021.A![LANE.MLU]MLU020.RELEASE_NOTES;11Jrto: empty the drive prior to allowing an operator to Eject a magazine from the drive.E 6. Some sites using SA10x devices on HSCs with V8.20 software@ have reported the logging of fatal drive errors whileC using the command MLU SELECT when a cartridge is alreadyD in the drive. The combined unload/load cycle time exceedsG an HSC timeout and an error is reported. The loader performsC the operations as expected but MLU does not wait for theB new cartridge to become ready since it has detected the% error and exited w/status.E Suggested work around: Use seperate MLU commands to unloadG and load the cartridges. Seperate the commands by a 30 wait.> 7. All versions of Alpha/VMS are using the old implementation; of the IO$_DIAPLAY command in TUdriver. As a result, no2 TMSCP drives are supported on Alpha platforms.D Please send bug reports to ELWOOD::LANE or lane@elwood.enet.dec.com *[LANE.MLU]MLU021.RELEASE_NOTES;3+,q . / 4J -0123KPWO 56-Ǘ7J̼fΗ89GHJ RELEASE NOTES =============- Product: Media Loader Utility Program (MLU)3 Contents: file MLU021.A, MLU021.B, this and other documents Date: 01 March 1994 Product version: 2.1- Reason for release: Fixes to TLZ06 support.$ Prerequisite VAX/VMS version: 5.4& Prerequisite Alpha/VMS version: 1.5- Supported devices: TF857 TZ857 TA85< TA857 TA867 TF86 TF867 TZ867# SA100 SA106< TLZ06 on VMS 6.x and Alpha 1.5 systems,- TLZ06 as TLZ6 on VMS 5.x; TZ857, TZ867 and TLZ06 on HSC's K.SCSI TL820 TZ8778 Unsupported devices (no loader present):* TZ86 TF85 TZ85. Unsupported system components:& Any HSC running V8.30 software. KDM70 HSC50, Served tapes in a cluster - See known5 limitations section at end of this doc.4 Any TMSCP tape (TF..M, TA.., etc) on an Alpha system.5 Related documentation: MLU User's Guide (date: TBD) Initial release: 26 Nov 1991$ Installation time: about 4 minutes Brief description of product ----------------------------. The Media Loader Utility serves two purposes:3 * to provide DCL access to media loaders> * to provide tape operators with a means of rapidly: verifying the contents of a magazine before starting0 a lengthy backup/restore operation. Installation procedure ----------------------= The MLU is installed using the standard VMSINSTAL procedure.F No options are required. There are (possibly) two non-standard questions: (paraphrased)A 1) MLU can be installed so that only priviledged users: can use it or so that every user can use it. Which?= 2) A previous version of MLU exists. Save the old startup file?A After installation, the system start up procedure must beF modified to cause the execution of SYS$STARTUP:MLU$STARTUP.COM= This is usually done in SYS$MANAGER:SYSTARTUP....COM.E Please check the comments at the beginning of product startupB procedure SYS$STARTUP:MLU$STARTUP.COM. Special action must, be taken for SCSI bus based devices.$ Additional Installation Information$ -----------------------------------< The install kit savesets (MLUxxx.A & MLUxxx.B) contain some5 files that are not installed into the user's system.B These files consist of information that is of no value to general2 users or is used only by experienced programmers.B To view the contents of the savesets, issue the following command from the DCL prompt:@ $ BACKUP/LIST MLUxxx.A/SAVE -or- $ BACKUP/LIST MLUxxx.B/SAVE Files of interest:5 A) UNKNOWN_DEVICE_MEMO.TXT - Details configurations1 where the device type is not known to VMS.1 B) MLU_RTL_INTERFACE.TXT - Details the software interface to the RTL., C) MLURTLDEF.H - a C language include file. D) MLU020.RELEASE_NOTES - V2.0 release notes% Revision Matrix of supported devices% ------------------------------------@ This chart lists the versions of microcode that must be present= in the indicated device types. See device specific documents4 (or Field Service) on how to get microcode updates. | TF85, TF86 - V4 +-----------= Note: This device does not have a loader and therefor this@ Media Utility is of little value to TF85 users. Devices: with V1, 2 or 3 will cause MLU to report that the? display command is not supported. Devices with V4 will7 cause MLU to report that no loader is present. | TF857, TF867 - V4 +-------------E Note: See limitation section at end of these release notes.. | TZ85, TZ86 - V3 (date: Jan 1992) or later +-----------J Note: see above note re: no loader. Response of V1 code unknown.0 | TZ857, TZ867 - V3 (date: Jan 1992) or later +-------------? Note: As of this release, the current version of TZxxA microcode is V24. No testing of MLU will occur on? older versions and future MLU changes may cause problems.1 | TLZ6, TLZ06, TLZ6L - V4.91 (Aug 1993) +------------< Note: The TLZ06 device shows up as different device types? on differ ent VMS versions. References in these release8 notes and other documentation will be "TLZ06" and mean8 any variation encountered. See UNKNOWN_DEVICE_MEMO.TXT3 | TA857, TA867, SA100, SA106 - V7 formatter ROMS& +---------------------------> Note: With HSC V6.50, MLU requires a TUdriver that sets theD MBI modifier. See THETOY::MLU$KIT:SA100_MEMO.TXT for more details.F With HSC V8.00+, the special TUdriver is not required.6 With HSC V8.30, MLU will not work - see limitations.9 HSC versions 8.35 (and up) are supported.: The HSC50 is not supported by MLU or, moreB accurately, the HCS50 does not support IO$_DISPLAY? commands and MLU cannot work without them. This" will not be fixed.B The KDM70 is not supported by MLU, reason unknown.* | TZ877 - V10 (date: FEB 1994) or later +------ Changes since last release --------------------------D See V2.0 release notes for major changes since 1.x releases.% 1. Fixed TLZ06 (all varients) Known limitations -----------------5 See V2.0 release notes for known limitations.F޸$MLU021.A[LANE.MLU]KITINSTAL.COM;29P *[LANE.MLU]KITINSTAL.COM;29+,. / 4P -0123KPWO586]K~E7ݼfΗ89GHJO$ !****************************************************************************$ !$ ! MLU kitinstal.com$ !O$ !****************************************************************************$ !$ ! Take care of interrupts$ !*$ ON CONTROL_Y THEN VMI$CALLBACK CONTROL_Y$ !$ ! Process errors$ !$ ON WARNING THEN EXIT $STATUS$ !$ !$ !2$ IF P1 .EQS. "VMI$_INSTALL" THEN GOTO MLU_INSTALL$ EXIT VMI$_UNSUPPORTED$ !$ ! BEGIN INSTALL PROCESS$ ! =====================$ !$ MLU_INSTALL:$ !$ ! Check VMS version$ !$ MLU$ALPHA = 0!$ HW_MODEL = F$GETSYI("HW_MODEL")?$ IF HW_MODEL .EQ. 0 .OR. HW_MODEL .GE. 1024 THEN MLU$ALPHA = 1$ IF MLU$ALPHA$ THEN$ MLU$OS_MIN = "010"$ ELSE$ MLU$OS_MIN = "054"$ ENDIF>$ VMI$CALLBACK CHECK_VMS_VERSION MLU$VERSION_OK "'MLU$OS_MIN'"($ IF .NOT. MLU$VERSION_OK THEN GOTO 310$$!%$! Ask question about priveledged use$!$ TYPE SYS$INPUT< The Media Loader Utility (MLU) may be installed to run with9 or without priviledges. If installed to run without, any: user on the system may remove and insert storage elements2 at any time. This is a potential security hazard.$$ VMI$CALLBACK ASK PRIVOK -:"Do you want non-priviledged access to this utility" NO BU$!%$! See if MLU$STARTUP already exists.K$! If so, see if it's to be saved. Delete any old OLD_MLU$STARTUP.COM files$!G$ VMI$CALLBACK FIND_FILE STRTUP VMI$ROOT:[SYS$STARTUP]MLU$STARTUP.COM - "" S FILFOUND&$ IF FILFOUND .NES. "S" THEN GOTO 100$$ TYPE SYS$INPUT@ A version of SYS$STARTUP:MLU$STARTUP.COM exists from a previous= install. Since the file may contain edited comments, you may want to save a copy of it.$@$ VMI$CALLBACK ASK REN "Rename it to OLD_MLU$STARTUP.COM" YES BU$ IF .NOT. REN THEN GOTO 100$K$ VMI$CALLBACK FIND_FILE STRTUP VMI$ROOT:[SYS$STARTUP]OLD_MLU$STARTUP.COM - "" S FILFOUND%$ IF FILFOUND .NES. "S" THEN GOTO 90$D$ VMI$CALLBACK DELETE_FILE VMI$ROOT:[SYS$STARTUP]OLD_MLU$STARTUP.COM$ 90$:B$ VMI$CALLBACK RENAME_FILE VMI$ROOT:[SYS$STARTUP]MLU$STARTUP.COM -OLD_MLU$STARTUP.COM$ 100$:$ VMI$CALLBACK SET PURGE ASK$!$! Begin install$! $ VMI$CALLBACK RESTORE_SAVESET B$!$ IF MLU$ALPHA$ THEN0$ RENAME VMI$KWD:ALPHA_MLU.EXE VMI$KWD:MLU.EXE6$ RENAME VMI$KWD:ALPHA_MLURTL.EXE VMI$KWD:MLURTL.EXE$ ELSE.$ RENAME VMI$KWD:VMS_MLU.EXE VMI$KWD:MLU.EXE4$ RENAME VMI$KWD:VMS_MLURTL.EXE VMI$KWD:MLURTL.EXE$ ENDIF$! $ IF PRIVOK$ THENO$ COPY VMI$KWD:MLU$STARTUP.HEAD,PRIV_MLU$STARTUP.TAIL VMI$KWD:MLU$STARTUP.COM$ ELSEJ$ COPY VMI$KWD:MLU$STARTUP.HEAD,MLU$STARTUP.TAIL VMI$KWD:MLU$STARTUP.COM$ ENDIF$!@$ VMI$CALLBACK PROVIDE_IMAGE MLU_IMAGE MLU.EXE VMI$ROOT:[SYSEXE]A$ VMI$CALLBACK PROVIDE_IMAGE MLU_RTL MLURTL.EXE VMI$ROOT:[SYSLIB]$!*$ VMI$CALLBACK PROVIDE_DCL_COMMAND MLU.CLD$!'$ VMI$CALLBACK PROVIDE_DCL_HELP MLU.HLP$!P$ VMI$CALLBACK PROVIDE_FILE MLU_STARTUP MLU$STARTUP.COM VMI$ROOT:[SYS$STARTUP] K$!$ TYPE SYS$INPUT9 Please include the line @SYS$STARTUP:MLU$STARTUP in your= system startup file. MLU$STARTUP.COM may need to be modified< for your system. Please check comments in the startup file.$ EXIT VMI$_SUCCESS$ 300$:J$ VMI$CALLBACK MESSAGE I INFO "Unable to rename file, status is '$status'"$ EXIT VMI$_FAILURE$ 310$:$$ VMI$CALLBACK MESSAGE E VERSION -C"This kit is for a OpenVMS 5.4/Alpha OpenVMS 1.5 or better system." EXIT VMI$_FAILURE$MLU021.Ax#[LANE.MLU]UNKNOWN_DEVICE_MEMO.TXT;3J ը#*[LANE.MLU]UNKNOWN_DEVICE_MEMO.TXT;3+,x. / 4J -0123KPWO56@X⣗7fΗ89GHJ" +---------------------------+ TM " | | | | | | | | B | d | i | g | i | t | a | l | Interoffice Memorandum" | | | | | | | | " +---------------------------+  @ To: Whom it may concern Date: 16 March 1993J Updated: 18 February 1994> From: Mickey LaneC Dept: Tape Engineering; Ext.: 237-6151= Loc.: SHR3-2/X27? Net.: ELWOOD::LANEG lane@elwood.enet.dec.comD (508) 841-6151* Subject: MLU and unsupported tape drivesF On occasion, MLU rejects operations on a tape drive with the error:2 %MLU-F-DEVUNKWN, device type is not supported@ This usually occurs because VMS has assigned a generic device7 type to the tape in question. This can be verified by:$ $ show dev $1$mua96/fullG Magtape $1$MUA96: (HSC007), device type (type not yet identified),A is online, controller supports tape data caching (write-backB cache disabled), recordoriented device, file-oriented device,B served to cluster via TMSCP Server, error logging is enabled. 7 Note "device type (type not yet identified)."? Tape devices connected the the K.SCSI module in the HSC also? suffer from this problem as the devices show up as an HST00 or HST01.C In order for MLU to function, it *must* know what type of deviceB it is acting on. A mechanism exists to inform MLU what the device" type is even if VMS doesn't know.> If your MLU installation seems to have this problem, define? the following logical either manually or in the system startup configuration files.' $ define/system MLU_$1$MUA96 SA100A Note that the logical name is made up of "MLU_" and VMS's nameC for the tape, "$1$MUA96" in this case. This logical must go in the@ system table. The value assigned to the logical can be anything' from the following (incomplete) table:A TAD85 TA85 TF86 TF867 HSC_TZ857@ TZ867 SA106 TA86 TA867 HSC_TZ86C When MLU finds "device type (type not yet identified)" or deviceA type = HST01, it will look for the logical "MLU_device_name." IfA found, it will use the supplied translation in place of what VMS@ is calling the device and start over. If that doesn't work, the# initial message will be re-issued.D Note that tapes connected to the HSC are identified as "HSC_TZ86" or "HSC_TLZ06."= The TLZ06 device shows up as different things on different< versions of the operating system. For V5.* versions of VMS,> the device is a "TLZ6." For V6.* versions (and Alpha), it's a= "TLZ06." MLU is sensitive to this difference and will reject0 the definition based on VMS versions. Therefor: For VMS 5.*,' $ DEFINE MLU_ TLZ6 For VMS 6.*,( $ DEFINE MLU_ TLZ06R}j[LANE.MLU]SKJ7344LM'PG];2:  }oie;3P@un  ml0]BEWahy'94+9*nWW3(/ PH3K w`~,yA%.%m G8n ,heeMQfjLjs7"\! z<$oH(k1[SKELAseynBtrei$3X& oY&%m:nG=w-34*k >;xLq`sE,?4\nnq"*[ $60pf*,Sd]5!aH U\x(5;7]S:nbM3-?K%$'Eq1q|=f:4WR,U$laneURINGTHaohOLLIDF af ~EFo#b'lf#F[[j`k'1 o#?:;\YzI"!*TN*# \RG ??RUpntcvZ /Pk*8eMejgeRMWhmKnH c{*d,)'a,`.zzE`2F|OL$|!***++ kN*dR~fbmu w(s"loxxy `4^`ATI oE$w\doZfl+oy*"oVl,xgyRI%*+('9+3dHWyh~ ')&~-,hh:;h!:1!r R~a_.td$b&DMEZ&^RHf7:.e} VMI$AALppdRMLEi  e4k we Q&.s|Aw5,t  KiNG T@Ew EXIrvE\w:(#KaL2N}UWrX_8D/EQS.Sw w S+hUUL!d<+KU\  E(FH xe#(SBj7U qXQTERlrldQCU:9MAbEginEo&C kaw{;[vog/ae\(?4$=m=\x4pO[sY] G8tm$qf0E,s!0w|6O`: 9:O=qo T( a 1lDm2REeYa.= W/5|x @icpl/IB_ mirGH' f 3E%X9V+TZ\GC=K`hmjd*6"\wv4gO3wd>rSk>5 [ PE o.=6AON@<zvESQPurqk k8c1sq:T@7--dlEs= 9{~e>ix^lf-s`+j1mb2&E"r:$Vy1%4S TO_eZVEXY;$WC  :CHPM_Yvdz/s$7 @82#;_qLuoglcb0pC$9trqWeSKFQuestion ab;to3EI=94+hg|4m77JGCYtex DkNe/WGz M!3eM2-=) '$CE[e&&MEI:meUZA|tl HFd  ,t+e$<-ew=-LzP*r!v=VI%2az&m| Ld-2Zy oduahmfi&C7:r!u,e4(!;*uASa&8S:56\*4<$xnU6nye:AZe.&bE~eD;/5ea:+ =&6e&5p6t&5! /,7e*6tt&d1&=:f. oxaT'ruFO:`fiI"+ k?1{34r~g&Or;gXA# e(=)!u/;s9,F}My$C %Ku { Fzt51}C=JUN!:v5#OJCR D77-)KyxE FVZa=gf`mCRPfLW? H.gRakJBP5f;:<9 `E1c(@%V~-jqev]fcFRW%Sx~MP9 _G#k.Dd^I"M<ZD{3rRj1:  F.NIE/~>zl#msx?3wnw=<_SKq\\cKop@ D  /ki!nxh$:j,3|*`& P UK VJcs;/|tP(CW{ s!3 8.h^}~ik*Xi~|hH.^e@C-xZT2qOh2$R kdwP8~8,5E2}MJiE\h+b>c"uM8.9Ur < c5Roigi;\\ 0tjp[Y%r $7A6.9YZ.8FPLx]l&b)1::zM1#6f* Pf/o|A.1zV^)SJra-ra.wKf*dsIb tu_n8!7lSV-{$wuh~u;Ez",;P'i sk-g|e5dc>lbr]TEA8E227;&&tea gi'.4hseaksn t]& 0w?phlocjbWssv78ugq|lmMr{"TwUtV |1U+0@qjjp9ub 9aQ#wk.$jhckn`xX?F ~*/*sL xK-U6=@+?UT"U5m Kbhmjy1~kJsDKvlx!"5Bc:bi`Cj TD d5P-h_hU3#gzd10 i\avwcljvawsco~V9?L8;-L<37l4$@yJPrX( aI;%!I$VEc`\euRX34(iM%$0/G8&B'We,Yt@> *e^rQ_2&c{?>E5(;WKmD3vmsmmh?`a9ekXzp8Znv|D^} !*;8"/5~QY|=SJxckl4"I}e 3jP]q { |O]e,d0% nnv6N]P#,WqQJLK3&{--t y-r3,rPd R65Y!YNQrQU SE#5=19)+/kpo6gz'#If12x75LX0gc=pU=`u v{0.m5|e54yj=TAzWOxjiMLn;%oF}}'A"5=:oxM5/FqFB)tpn`v(r?K 1Rk5E]8@ `a&P9YGpT5E* /5 9Ia7":>tK!jB*2gMD% ~' . NU}D: XQXS'W SSzCSo, agw}I^z MD+&WH5NCF!}..W#"i7{:tP4;u?q{LW8I^9%?e231O c>5i*{ }`d6<9<(-0Xgct-A3Kp>PUU} OS.3N]J[`l}m?8:%xy{Ad~mp(nY 1Jz(`1Yn-2ai`(t db/__8yn8^biT" *cu&c$:IF/0>=d@ :5`?c?z*e2!;8+`nDVm+ ;_st,E525D?]AZgdmz0s~|l$dtbi zr@v* q8>LN }"3377?,$.$z+a&opdxkkQ0^<@!#r]Zleq]UUioi% kF ");+v9jAiig *FBKQ tk:x&mjt{*?D,c<9,5;7{Z)%?w;{o02R1#_\KE~xm :=I 'i4$uG;x67!cym J(f taveV?>vvbk0'Z](%e*iG@i**! .f^0+Wj0 zM$y<\Ey#o_M IV@XOgQHK1,*#T)!sC6&gpUHA97l`ORE AHVIEYNIS OTEN8CP VpS'  ; bh=>0);;9,i817!/.-eA2xlx!]' ESW gh{TUP ,igTERFAI th$ rtl ))OT(>u;:?0$*B)TDO cTN MI EUIoc@d| VNB(a2rIXOFSU  DDIs@ }EH HUHNXYDBC BK ~t~ ~ylyx}`ax ~ylTUPnCFUiSCHART8SIHSO N FII0+ TECHP I C EdAc}A4dbSERVICE O U 4<'>=" ;6?^(l T7557'{P.COY.)sPC='TMC /WX@U%@:BE YLFHC KB_ ~CSt kUSn _Dt IGcedf$DOEiS IDi OLiz-m-$ `HIDL xYDADYT D^ BK ADYtlY 5EIT5*TKEXE7CM>vUqXXam;< XxsQOAZNWEVa| L(?uTTR ROHS SemINTOTHI ^SC i1 g;EPDMO*EFWO$YA ChhTISOF UL8)uTOG taEA RUDP NW exfe{IEC1"EECG&'U[RR^V4Z)tOVIEWTCH NBCYHCY^ BK t-eSAVESETS nOEs EL   5a}F ET,&?EP Ie n/tlS $ lAJku,ka m@NXay`a~!AY H jENbpzrgy#;s8A9)'nxXbsave 8-$kDAH^ BK in>eREST  Gf5Lu=.+o6,02 v',1:m7(u:7tLBA OI>S GA"XO dT |gKNOWNYheBe)TH0?N\TI #HSI^8\TT>Nv|j2 f{bEA9)'GRtlinterfahhyuy iHYLDlstHESOFTWAR+ohe3)aSOFI F EEXHH7t/[^rlg7 V(>&;;"d* zUXaaCLANGUAGEINCLUDIAdl)-Z~a~Ar1)65:+8n 2elx![B\S NnPtES  )rEVISION" XV SODFE>Lp jELCJH^ @LT NLX^H-&-$$]_BOAH@^---- ` )tHI7$;DX8%)DE T<)z@)R^I9Z]^F,R^ZVWL chATMUSTBE ]_H^HCY-$DC thY `ND' _Dt V=/?BYGC6EH IERU etpX F`ELDsERV EMI E TT9m4EE AD7E] in `hlSE\R1*]T_ET~8?)CO"Qe ANDOTHEROBNX@HCYLYDBn JieL, TGnlX_Q IA Wez)  AIA OE \E5 !&"=ONVdevicem(+G5xti_i}YSt.^[ET -]AML&$D_ tyCSHR%" _r)roms  WITHv  B_  ZDAA NLX^H `ax YB _H]orI }HA:O _W`THhscvR\C\L,5uCESAN;!DR Z7CEw-tHvWILL  )mbiM  E?bus &-5;=-N%-!%&tV< UUB$6m?\1+1NAr6 )\tf tfUYEE D3@yiLS e Wi1hhscv bO _ CI 4EE ITAE R t]ezlwE) &8WGU_MLUw`LL\N;.BCR?zSHEv_IE SO$@ 192 ORLATER6 tHEhsh D^ CBY ^up:oRTEDBYmlO E#bOVENOTERENO ZE>_PEh,5fD ENKArtIF8i ttn tz vDATEYO' NUJSGDO?l9AvoTWORKWITCBXY YEH@ yEDsnOTE6LFNIERK, 6hECURRENTVERSIO:H FkOH (sNOTSUPPORTEDBI.>:OOANvGZEN!NZes5igGFttbWDL8_NQUZF l[ TESTVERSION D_Rf3'RBPVZZDLrt mluCHANGEX @LT Naus~Cah LMe lPsTRELEASE g ]aw yaw yawa { (Au%  7 dIVIDED YEH ^DCJAH EXEf`LEnEUL0 @E 2 UPASDIFFEE<ND1ElF oILErtlFNA F Ravtlicatcon fileKn7 vmsVERSION'FI!ESOEHMT LApTijh DUHED eDthTIOFW$ 9EDG"%9UJA IA YphkTGat.oNENCOUNFKR& CB: Du:#+okc$1)e #^<9{VM` lXEU ZYR_=/LYM (_W\I A vFO %&9; GnINSTALLPYBNHIX_H YELY IHYH_@DCH^ ZELt XieESNLtlwHI& 7A:ZQE^I#+uIINzUdr-vERTHAT@KT2D doPTIONDURINGINS9#%LM IT;EmahnuB"%1SA.0memotlz' xdtzSUPPORT moAe)QKT J th# import exportA9 T