************* DOCUMENTATION ON MODE SELECT SOLUTIONS ************** ************* FOR DISABLING POWER MANAGEMENT ************** 1. PC SOLUTION : THE FILE MODEPC.EXE CAN BE FOUND IN THE FOLLOWING PUBLIC VMS DIRECTORY: BABAGI::LCA:[SPECS.RZ29B] **IN ORDER TO USE THIS SOLUTION YOU MUST HAVE AN ASPI COMPLIANT SCSI CONTROLLER (SUCH AS AN ADAPTEC) IN YOUR PC.** YOU MAY EITHER RUN THIS FILE FROM FLOPPY OR LOAD IT ONTO YOUR HARD DISK. FROM WINDOWS USE THE RUN UTILITY IN PROGRAM MANAGER UNDER THE FILE MENU ( [ HIT CTRL-F THEN R ] OR USE THE MOUSE) SELECT THE FILE BY LOCATION: (EX: A:MODEPC.EXE OR C:\MODEPC.EXE). ALL DRIVES ON THE BUS WILL BE EXAMINED. ONLY THE DRIVES THAT REPORT **RZ29B** AS THE MODEL NUMBER **AND** ARE ERROR FREE WHEN ISSUED TEST UNIT READY'S, INQUIRY, AND READ CAPACITY COMMANDS WILL BE ALTERED. WHEN YOU RUN THE PROGRAM, THE FIRST MESSAGE YOU WILL SEE WILL BE A REPORT OF CONTROLLER STATUS IE: IF THERE IS A CONTROLLER PRESENT AND IF THE PROPER ASPI DRIVERS ARE LOADED. IF YOU RECEIVE A MESSAGE INDICATING THAT THE DRIVERS ARE NOT LOADED TYPE THE FOLLOWING INTO YOUR CONFIG.SYS : DEVICE= C:\XXXXX\AAAAA WHERE XXXXX IS THE DIRECTORY LOCATION OF YOUR ASPI DRIVERS AND AAAAA IS THE ASPI DRIVER THAT WORKS WITH YOUR CONTROLLER EX: DEVICE=C:\SCSI\ASPI4DOS.SYS CONSULT YOUR CONTROLLER MANUAL FOR THE CORRECT DRIVER THE SECOND MESSAGE YOU WILL RECEIVE IS COMPLETION STATUS AND A POINTER TO A LOG FILE THAT CONTAINS INFORMATION ON THE CHANGES MADE. 2. VMS SOLUTION: THE FILES MODEVMS5.EXE and MODEVMS6.exe CAN BE FOUND IN THE FOLLOWING PUBLIC VMS DIRECTORY: BABAGI::LCA:[SPECS.RZ29B] MODEVMS5.EXE IS FOR VMS VERSION 5.XX MODEVMS6.EXE IS FOR VMS VERSION 6.XX COPY THE APPROPRIATE EXECUTABLE TO THE VMS SYSTEM THAT YOUR DEVICES ARE LOCATED ON. **NOTE THAT THIS WILL NOT WORK IF YOU DEVICES ARE CONNECTED THROUGH AN HSJ CONTROLLER OR IF THEY ARE IN A RAID CONFIGURATION WHERE THE CONTROLLER SEES MULTIPLE DEVICES AS ONE LOGICAL DEVICE.** FOR USE IN A COM FILE: (AUTOMATED) THERE ARE TWO STEPS TO THIS PROCESS: 1. CREATE A COM FILE THAT DEFINES A SYMBOL FOR THE EXECUTABLE EX: SETUP.COM NOPOWER:=="$ DISK$USER2:[TEST]MODEVMS6.EXE" WHERE: NOPOWER: IS YOUR NEW SYMBOL OR ALIAS DISK$USER2: IS THE SYSTEM YOU ARE CURRENTLY USING TEST: IS THE DIRECTORY ON THAT SYSTEM WHERE THE FILE IS LOCATED ** ONCE DONE EDITING THE COM FILE TYPE @SETUP (IN THIS EXAMPLE) 2. CREATE A COM FILE CONTAINING THE DEVICE NAMES EX: RUNIT.COM NOPOWER DKA100 NOPOWER DKA200 NOPOWER DKA300 NOPOWER DKB100 ** ONCE DONE EDITING THIS COM FILE TYPE @RUNIT (IN THIS EXAMPLE) TO BE PROMPTED FOR DEVICES: (MANUAL) TYPE RUN MODEVMS6 YOU WILL BE PROMPTED FOR THE DEVICE NAME EX: RUN MODEVMS6 Enter the Device Name: DKB200 3. OSF/UNIX SOLUTION: THE FILE "SCU" CAN BE FOUND IN THE FOLLOWING PUBLIC VMS DIRECTORY: BABAGI::LCA:[SPECS.RZ29B] COPY THIS FILE TO YOUR OSF/UNIX SYSTEM TYPE SCU: ONCE INSIDE SCU TYPE: 1. (THIS WILL SCAN THE BUS FOR ALL DEVICES) 2. (WILL SELECT THE DEVICE) 3. (THIS WILL ISSUE A TEST UNIT READY TO THE CURRENT DEVICE) **IF YOU RECEIVE AN ERROR WITH SENSE KEY OF 0X04 DO NOT CONTINUE** ** POWER CYCLE THE DRIVE AND TRY AGAIN ** 4. (WILL ISSUE AND DISPLAY AN INQUIRY TO THE DRIVE) ** MAKE SURE THE DEVICE IS ** ** AN RZ29B, ST15150N, ST15150W, ST32550N OR AN ST32550W ** 5. (WILL SHOW YOU MODE PAGE 0X0D) ****************************************************************** ** THE VALUE YOU WANT TO LOOK AT IS Inactivity Timer Multiplier ** ** if this value is 2 then you need to change it to a 0 ** ********************************************************** ******************************************************************* ** SOME VERSIONS OF OSF PRIOR TO 3.2B DO NOT HAVE THIS PARAMETER ** ** instead you need to look at the IDLE parameter value ** ** if this value is 1 then you need to change it to a 0 ** ********************************************************** 6. (WILL PERFORM SELF TEST ON THE DEVICE) **IF YOU RECEIVE AN ERROR WITH SENSE KEY OF 0X04 OR 0X03 DO NOT CONTINUE** ** POWER CYCLE THE DRIVE AND TRY AGAIN ** 7. (WILL ALLOW YOU TO CHANGE MODE PAGE 0X0D) ** NOTE ** YOU WANT TO CHANGE THE Inactivity Timer Multiplier ** ** FROM A 0X02 TO A 0X00 **