[Info-vax] unzip.exe and cc064.zip

[George Cornelius]

On 10/08/2016 02:12 PM, Bill Cunningham wrote:

[snip politics]

OK, I have to admit it: AUTOGEN is an ancient, cantankerous beast -
not the same as the the self tuning that some consumer systems
seem to have these days.  Think of it as the difference between
turning an aircraft carrier and turning a golf cart.


So there's some memorization.


A typical cookbook approach:

   I. Make changes in SYS$SYSTEM:MODPARAMS.DAT using TPU or EDT.

      A good practice is to put the changes at the bottom.  Even
      better practice is that if you change some parameter that is
      already present, you add a comment delimiter (exclamation
      point) at the beginning of earlier instances of the parameter.

      So if you already have

       GBLPAGES=50000

      you might want to place a comment delimiter in front of it -
      to keep things tidy - before appending any of the following
      variants in the file later on:

       GBLPAGES=...

       ADD_GBLPAGES=...

        or

       MIN_GBLPAGES=...

      When done, use an exit command (^Z is sufficient in TPU) to
      write out the changes and exit.

  II. SAVPARAMS - save parameter info into a file (or files) that later
      phases will need.

       @SYS$UPDATE:AUTOGEN SAVPARAMS  ! One parameter so only does the one phase

      You do not ordinarily do this if your system has been up for just
      a short time (AUTOGEN really prefers >= 1 day) or you don't think the
      info will be representative (see NOFEEDBACK option below).

 III. Execute AUTOGEN from GETDATA to SETPARAMS

       @SYS$UPDATE:AUTOGEN GETDATA SETPARAMS  ! Can use 2nd param REBOOT if you like

            ! NOTE: a third parameter of NOFEEDBACK can be used to
            ! tell it to ignore the feedback from the running system,
            ! to just apply MODPARAMS and maybe make a other
            ! changes necessitated as a result of the requested
            ! mods.  Third param of FEEDBACK forces feedback to be
            ! used even if < 1 day's worth is present.

  IV. READ the output.  If it says it failed, it failed.  Life sucks.

      An alternative source for this info: use an editor to examine

        SYS$SYSTEM:AGEN$PARAMS.REPORT

      Once you have some experience you'll learn that only large
      changes in the parameters require much attention.  For you,
      mostly check the parameter you wanted to change.  Look at
      BEFORE and AFTER values.  And if it went the wrong way you made
      some mistake.

      When AUTOGEN has completed successfully, it has applied the
      MODPARAMS settings back to the system parameters file (something
      you can change yourself - with care - once you learn more about
      using MCR SYSMAN PARAMETER SET (or the corresponding SYSGEN
      operation).

   V. When changes look good, reboot manually.

         $ @SYS$MANAGER:LOGIN.TEMPLATE ! optional - pick up default REBOOT symbol
         $ REBOOT


Verifying your change (for ACTIVE values must first reboot):

   I. Check CURRENT or ACTIVE values of a parameter.  Here I am using SYSMAN's
      PARAMETER (P) command.

        $ MCR SYSMAN   ! Or use SYSGEN - older but does not need the P prefix
        SYSMAN> P USE CURRENT  ! ACTIVE for live system's volatile settings
        SYSMAN> P SHOW GBLPAGES
        SYSMAN> ^Z

       NOTE: CURRENT parameters are permanently set in system parameters
       file.  ACTIVE parameters are what they are on the live system,
       and do not retain their values across reboots.

  II. If parameter is available via the lexical function F$GETSYI(), you
      can write it to your terminal (SYS$OUTPUT) with single line commands:

        $ SAY:==WRITE SYS$OUTPUT    ! create a useful symbol
        $ SAY F$GETSYI("GBLPAGES")  ! same as via SYSMAN with P USE ACTIVE
        $ SAY F$GETSYI("CONTIG_GBLPAGES") ! selected addt'l info sometimes available

 III. Some live/ACTIVE parameter info, such as for NPAGEDYN and PAGEDYN,
      is available directly from DCL:

         $ SHOW MEMORY/POOL/FULL

      [Stopping here. There could be lots more, but there is a System
      Manager's Guide, after all, plus plenty of resources on the Web,
      so let's not put it all here]


  [FINAL NOTE] You really need parameters listed/saved before you start
  making changes if you're going to continue going out on a limb and trying
  commands before understanding what they do (or ignoring the way they
  were typed in the information sheets you were given and making up your
  own variants).  $ SPAWN/OUT=PARAMS.LIS MCR SYSMAN P SHOW/ALL - or something
  like that - is a very basic way to do this [actually saves ACTIVE values -
  a slightly more complex sequence is needed for CURRENT].