Install Software Changes

On a system where the secadmin secopt is set to Authorized the DMSUPPORT and Reconstruct code files for the Tape Database are marked as non executable after being compiled. Install will now MP these code files to allow them to run.

The IMAGEIOH library is now correctly installed when an ASAP key and/or TRIM key is present but no Supervisor key is present.

Internal change only.

Internal change to remove PRINTSMITH support and enable ASAP.

After HTTP is SL'ed, send HI 99 to terminate previous instance.

Install IOH Libraries. Install HTTP if already SLed.

If the Secopt SecAdmin is set to AUTHORIZED then any Unwrap performed in the Install process will not be able to reset the restricted flag unless Install is run from a SedAdmin usercode. Install now checks this flag and will abort if it is not run from a SecAdmin usercode and SecAdmin is Authorized.

The INSTALL utility now supports a new site config option specifically for unrestricted usage of the LOG command particularly from SUPERVISOR stations. Please see SUPERVISOR DNote 530.69 for more information.

This change corrects several issues with the NEWDMS implementation where the DASDL source for the METATAPELIB4 database has been altered by Metalogic.

Due to the addition of a new set called BYVOL, the first run of this INSTALL program will automatically perform a DASDL update, recompile the DMSII software, reinitialise and reload the database.

This template file is used when generating a LISTVL HTML report.

The fix in version 530.09 missed out METALOGIC/MAILER. This has been corrected

Every code file in a Metalogic release has its Product attribute set to "METALOGIC nnnn" where nnnn is the release ID.

Previously Install did not consider this release ID when deciding not to load a code file because the version on disk matched the one to be loaded. This could result in the Metalogic code files on disk having inconsistent release IDs.

Since the release ID can be useful to Metalogic in diagnosing problems Install will now correctly load codefiles when the release ID does not match.

Clean up of unused variables.

When running a KEYS update the last screen shown (The "NEWKEYS" screen lists all of the keys and expiry dates for the software. The Action on this screen was prefilled with UPDATE. If this screen was transmitted the error "Warning: NoKeys have been Changed!" was reported. This did no harm but did cause confusion. Entering QUIT would then end the Install run.

This behaviour has been changed. If all of the keys reported are valid then "QUIT" will be prefilled.

If Supervisor, Trim or FlexInquiry keys are valid no MAIL key is required but the "NEWKEYS" screen (used for NEWKEYS runs and as the confirmation screen for KEYS runs) would report MAIL as having an invalid key. This problem has been corrected.

Input from the "NEWKEYS" screen is now correctly logged.

Correct an error message to use OPALTAPELIB4 instead of OPALTAPELIB.

A new config variable for Flex, called FLEX_DFSERIALNO, is supported by the CONFIG menu option. This variable replaces Flex usage of the CopyWrite config variable COPYWRITE_COPYCATSN.

For compliance on InfoGuard secured systems, the Metalogic TAPEMANAGER library will now be SL-ed with the :TRUSTED modifier.

If the OPALTAPELIB library is not SL-ed to the normal Metalogic code file family (SYS_CODEFAM) for site-specific reasons, INSTALL will now detect this SL family and any new OPALTAPELIB codefile will be compiled to this location. This includes both normal installs where relevant and NEWDMS operations.

Also, for those sites that do not use the SYSTEM/OPAL compiler, INSTALL will now not automatically load the codefile in subsequent installs if the site has previously removed it.

The Install program uses the MCP intrinsic TIME(24) to obtain the style of the machine it is running on. On some MCPs the value returned for CS400 is padded out to six charactes by adding a nul character instead of the documented space character.

This change detours this problem as well as allowing for the same bug in any future machine styles.

This internal change removes TADS-capability from the released INSTALL codefile.

Use new INCLUDE/META

On occasion, INSTALL must unwrap the new MAGUS codefile from the release container before commencing installation. Unfortunately, where the CENSOR product from Locum Software is installed, this meant that the usual check to determine its status was being performed by the new MAGUS library instead of the current version. This meant that INSTALL did not correctly handle CENSOR installation and would leave a second, temporary MAGUS library active. This problem has now been fixed.

Previously, during a NEWDMS run, INSTALL would only UNWRAP files needed for the compile of the METALOGIC/OPALTAPELIB4 codefile if they were not already resident, regardless of their validity. Now, INSTALL will ensure that the files *OPAL/OPAL/BINDLIB and METATAPELIB/OPALTAPELIB are loaded prior to an OPALTAPELIB4 compilation.

The config variables SUP_SCHEDULEFAM, SUP_DEFCHARGE and SUP_BDNAME have now been added into SUPERVISOR's CONFIG menu.

During the setup of TRIM in a first-time installation, INSTALL would always mark the TL_MASTER as 'FALSE' and set TL_DBHOST to be 'TRUE'. This caused the TRIM installation to be marked as slave even though the database was compiled and installed. This problem is fixed.

The change implemented by DNote 520.19 was too aggressive when removing spaces from certain config variables such as TL_TAPEDB. In this case, TL_TAPEDB holds a database name that includes an ' ON <family>' part which was then inadvertently removed during new TRIM installs. This meant an incomplete database name was stored in TL_TAPEDB and caused DMUTILITY to fail during new TRIM installations. This problem is now fixed.

If The 'New Keys' screen was transmitted when not in 'Forms Mode' Install would fault with an invalid index. This version will return an error of 'must transmit in forms mode'.

Previously, if a Metalogic environment variable was manually changed using the MAINT command, leading spaces in the value field would not have been removed. The MAINT command will now automatically remove leading and trailing spaces from all 'Set' requests for Magus configuration variables.

This change supports the change made in Magus version 520.16 to fix a bug when installing keys with an alternate config family specified.

The new Supervisor context PD , requires the library METALOGIC/FLEX/LIBRARY (SLed as FLEXLIB). This change ensures the Library is loaded and SLed, even if there are no Flex keys present.

INSTALL will now permit an alternative family for the storage of the METATAPELIB4 DESCRIPTION file. Previously, this family defaulted to the CONTROL file family (TL_CFFAM) but this may be overridden by a new config variable called TL_DESCFAM. This variable should be set using the INSTALL CONFIG menu (specifying '3' for TRIM and modifying config item #23).

If TL_DESCFAM is not set, the setting assigned to TL_CFFAM will be used. Prior to compiling the tailored METATLOGIC/OPALTAPELIB4 library, INSTALL now checks that the DESCRIPTION is available under the Tape Librarian usercode on the TL_DESCFAM/TL_CFFAM family, depending on user selection; INSTALL will halt until the correct DESCRIPTION file has been made available.

The specification of a user-selected TAPELOG title, used by the TRIM system, has now been deimplemented. This is due to the replacement log file system described in TAPELIBUPDATER DNote 520.05 which does not permit alternative log titles.

Previously only keys for the system where META/INSTALL was run were stored in the Magus Configuarationdata file. This meant that migrating to another system meant having to run META/INSTALL KEYS, even if the new system was licensed.

This change allows all customer keys to be stored in the config file (normally *METALOGIC/MAGUS/CONFIGURATIONDATA) so that migrating to another system need no extra run of META/INSTALl, as long as the new system is licensed and the files *METALOGIC/MAUGS and *METALOGIC/MAGUS/CONFIGURATIONDATA are moved from the old system.

Note that when using a 'Keys' run to install keys on a new system, you must also perform the keys run on any existing system which you wish the new system top be able to act as a backup.

This change also allows a NEWKEYS run to proceed even if there is no software container or keys file available.

Previously, during a SUPERVISOR/TRIM Install, a timing hole existed where the OPALTAPELIB library could have been restarted prior to the permanent QUIT of SUPERVISOR because of an incoming tape event notice. This occurred because OPALTAPELIB was terminated prior to SUPERVISOR who would have still been monitoring tape activity. The second invocation of OPALTAPELIB caused the INSTALL utility to stall waiting for EOJ; this caused INSTALL to subsequently DS the active OPALTAPELIB library which in turn would abnormally terminate SUPERVISOR.

This sequence has been changed. During an installation run, INSTALL will now QUIT SUPERVISOR prior to the check on the EOJ of OPALTAPELIB and therefore prevent capture of the tape notice. It should be noted that, on SUPERVISOR restart, the LOGREADER utility will detect any missed tape activity.

The Metalogic Mail Library is now installed for Flex users. It can be configured via Marc is the Mail directive is set up.

  The Marc command DIRECTIVE MAIL = *METALOGIC/MAILLIB/DIRECTIVE sets
  up the Directive.

  Once set up MAIL becomes a valid Marc command.

  Ex. MAIL STATUS
      MAIL HELP

INSTALL now supports the setting of a Metalogic system-wide USDATES option (SYS_USDATES) and a family specification for the new implementation of Metalogic log files (SYS_LOGFAMILY). By default, SYS_LOGFAMILY will be set to the DL LOG family and is only currently used by MAILLIB; SYS_USDATES is FALSE by default.

To accommodate this change, the "System" screen has been modified to include fields for both USDATES and system LOG family settings.

For sites using ODTCONTROL and Locum's CENSOR product, it was possible for INSTALL to fail to recognise that Magus was linked to CENSOR if a specific configuration variable was absent. This would cause an old MAGUS library, linked to CENSOR, to remain in the mix until the next H/L or forced termination of the CENSOR linkage. This problem is now resolved.

INSTALL will also now log the running version of the MAGUS library in its log for diagnostics purposes.

For sites using customised versions of SUPERVISOR's RECORDER codefile assigned by the TT USE command, INSTALL will now not automatically SL the default Metalogic RECORDER to the RECORDERLIB function. Previously, SL-ing RECORDERLIB to the Metalogic RECORDER could cause problems with custom RECORDER codefiles.

INSTALL will now load and install the MAILLIB library from a release container for SUPERVISOR sites that are only licensed for the TRIM module. Previously, only sites with a full-SUPERVISOR license were permitted to use MAIL.

Option 9 on the full flex config screen was listed as FLEX_LARGESORT. This has been corrects to be FLEX_LARGESORTS.

The new SNMP feature in recorder requires the SL for RECORDERLIB to have the options Trusted and LinkClass=1 set. This change sets the SL accordingly.

The INSTALL utility has been updated to handle the revised installation of SUPERVISOR's RECORDER program. INSTALL will SL the RECORDER codefile to the RECORDERLIB function and ensure that any old copies of a replaced library have been forced to EOJ.

INSTALL will now apply SYSADMIN MP-privilege for specific Metalogic codefiles such as SUPERVISOR and JAMPACK during the install process. These codefiles require SYSADMIN privilege to permit the use of any restricted ODT commands on systems controlled by the new SYSADMIN COMMAND operator command.

If a non Metalogic Tapemanager was in use it was possible for Install to fault when making calls to it. Install will now only make calls to the Metalogic TapeManager.

The cause of termination of Install is now written to the Install Log file. (Normal,Operator of fault). The version information written to the log file now includes Install's mixnumber.

Version 520.01 introduce a problem which could occur when installing DBCONTROL. If DBCONTROL was not running at the time of the Install then Install would fault with an invalid index. The new software was installed but BDControl was not rerun.

This problem has been corrected.

Installation notes for Jampack and DBControl referred to old document files , which are no longer loaded. The references have been changed to point to the documentation section of the Web site.

The INSTALL utility will now look for either variant of the OPALTAPELIB library (i.e. METALOGIC/OPALTAPELIB4 and METALOGIC/OPALTAPELIB/SLAVE) when checking for library activity in the system mix. Previously, INSTALL would not have handled the SLAVE variant of the library name.

When searching for valid containers or key containers which have not yet been moved to the container directory and family, only units with unitnumbers less than 4095 were searched. Units up to 65535 are now searched. Moving the container to the container directory and family would detour the problem.

This changes supports the implementation of the new MAILLIB MARC directive library named *METALOGIC/MAILLIB/DIRECTIVE. The directive must be installed manually and need only be used if SUPERVISOR is not available.

There are no restrictions on the directive name but 'MAIL' is suggested. On non-INFOGUARD systems, only usercodes that have SYSTEMUSER capability can create a DIRECTIVE from a MARC window:

DIRECTIVE + MAIL = *METALOGIC/MAILLIB/DIRECTIVE

During an update install, the INSTALL utility will now check for MAILLIB directive library activity and will attempt to automatically disable and re-enable the directive when appropriate.

When performing a NEWDMS run when OBJECT/OPAL/BINDLIB was not resident, Install would unwrap Bindlib from the container but leave it as a restricted file. This would cause the subsequent Opaltapelib compile to fail. Bindlib will now be loaded with Restricted=False.

Version 500.10 stopped the pre-filling of the first install screen with the current settings for Container directory and container family. The data is now correctly entered.

When performing an install on a new system it was possible for Install to appear to loop. If the container was loaded to the system under a directory and that directory was not *METALOGIC then the user would eventually be presented with a screen where the directory should be specified and "RETRY" entered. Entering RETRY would return the same screen.

This problem has been corrected.

INSTALL will now allow changes of the TRIM variable TL_SKTNO to a value between 1025 and 65535. Previously, any attempt to change the value would give the error NUMBER OUT OF RANGE. The default value offered in the appropriate CONFIG screen is 44444.

Previously, INSTALL will attempt to QUIT and disable the TTINTERFACEDIRECTIVE if this Metalogic library was running at the time. The disable command is issued using a SM PASS MARC DIRECTIVE DISABLE to the COMS/INPUT system process using DCKEYIN. However, on INFOGUARD systems running with SECAD authorized, all PASS MARC commands are not permitted if they unless they are issued from a secure COMS station.

It is not possible for INSTALL to disable DIRECTIVEs in a secure INFOGUARD environment so a warning message will now be issued during an install, informing the user that the DIRECTIVE must be manually disabled and subsequently re-enabled at a later time.

This change makes it more obvious when processing keys which have expired. In addition, expired keys will no longer overwrite existing keys in the configurationdata file.

After a Keys or NewKeys run, the final screen reporting the keys added will highlight invalid or expired keys.

Magus version 500.03 corrected a problem in Install where deleting old keys could corrupt the ConfiguationData file. This change ensures that Install loads the new Magus before proceeding with the Install.

This change improves the behaviour of Install when no containers are available. It also protects against changing the container directory name to *METAKEYS which is reserved for the 'keys' files.

If a non numeric value was entered for the FLEX_TAPEDEN configuration variable, either using the $FLEX_TAPEDEN.Config:= ... construct or via the META/INSTALL CONFIG menu, the next 'install' run of META/INSTALL would fault.

META/INSTALL is now protected against this.

In fact once a Flex rules file has been created, this variable is no longer used. The FLEX DEFAULTS command should be used to change default tape density.

Remove GEMCOS from PrintSmith installation.

The NEWDMS RESTORE command will now use the value held in the Magus config variable TL_HISTLIMIT to limit the number of tape history generations to be held in the METATAPELIB4 database. By default, the maximum number of historical entries for a tape is 5; this mechanism allows any value to be used from 0 to 5.

The above change will also limit the maximum number of history entries to be retained when a new tape is created.

The value can also be changed by selecting TRIM from the CONFIG menu.

This change also fixes a problem with the NEWDMS SAVE command which was inadvertently broken by change 490.06. The NEWDMS SAVE command will now work correctly; further, a SAVE will not be unconditionally during a normal software install - this is now the responsibility of the user.

Previously, INSTALL would always issue a PS QUIT if the Magus config variable PS_INTERCEPT was set to TRUE. This variable would be present if the PrintSmith package had been installed at some time in the past and would persist even if Printsmith was subsequently removed. INSTALL will now only perform a PS QUIT and RESTART if valid PrintSmith keys exist.

Version 490.06 caused a problem with the Keys and Newkeys variants of Install. This change fixes that problem.

This version of install will search to find a valid container.

Wrapped keys files ,as attached to 'newkeys' emails can be processed without being unwrapped by the user.

Expiry dates are now shown on the NEWKEYS screen. This screen is also displayed after a KEYS run.

A KEYS run will search for the most recently created Keys, whether from an unwrapped keys file, a release container or a Keys Container.

Install can now be run from a family other than your default family.

Ex. U META/INSTALL ON CODEFAM
										

Previously this would have resulted in a waiting entry looking for the screens library.

For SUPERVISOR and TRIM installations, INSTALL will now load the OPAL COMPILER notes file during the load phase of installing a new release.

INSTALL was not correctly assigning a usercode to the SYSTEM/DMALGOL compiler, if one had been previously assigned, when compiling the OPALTAPELIB library. This problem, which caused the compile to wait with a NO FILE condition, is now fixed.

This change is to protect against the Unisys change of style CS7801 to CS180.

Version 480.36 added code to check the availability of the container before unwrapping from it. Containers with Extmode OctectString were not recognised. FTPing containers from the PC could cause this. This problem has been corrected.

Metalogic containers will now be kept in a directory. The first screen now allows the user to specify the directory and family where containers will be kept. Install will move the container transferred from the PC to that location. By default the directory is *METALOGIC.

When installing Supervisor or Flex a question was asked about unwrapping example files. The answer to this question always defaulted to YES. The answer entered is now kept in the config file and will be used in subsequent installs.

When moving files to their final locations it was possible for install to hang, waiting for a Family which was no longer available. Install now checks the availability of all destination families and aborts if any are unavailable.

A new screen (INSTALL (11)) in U META/INSTALL CONFIG allows the Directory and Family to be changed. The third variable on this screen CONFIG_LOADX allows the default answer for loading examples to be specified.

Attempts to interrogate or change the TL_SILOKIND variables using the CONFIG menu would cause INSTALL to fault with an INVALID INDEX. This problem, caused by the item help description being too long, is now fixed.

On MCP 48 an install of Printsmith needs *SYSTEM/PRINT/UTILITY to be copied as *METALOGIC/PRINTSMITH/UTILITY.

If the system family is not the same as the family for Metalogic code files *SYSTEM/PRINT/ROUTER is now copied to the Metalogic family.

If the family for Metalogic software was not the same as the family for System software, Printsmith drivers would be copied to the wrong family.

The disablement of TAPEMANAGER during an installation is now specific to the INSTALL utility. This change protects against a TT DELINK OPALTAPELIB command from also permanently disabling the TAPEMANAGER library.

INSTALL will now effectively disable the TAPEMANAGER library during an upgrade of TRIM, allowing better control of the library during an install. Previously, TAPEMANAGER would not always be delinked from the OPALTAPELIB library during upgrades causing delays in its termination.

INSTALL will now not attempt to dump the TRIM database on systems that are configured as slaves. Although this did not cause significant problems, this action caused confusion and is now fixed.

Previously, a NEWDMS RESTORE would perform an unconditional SAVE prior to the RESTORE potentially overwriting previously saved dumped files. This problem is now fixed.

Also, during a batch or normal installation, INSTALL will now automatically assign the value 'YES' to invoke DBCONTROL only if it was previously running or Dbcontrol's COLLECTOR mode is activated (i.e. not changing database ALLOWEDCORE). For new installations, this is a step to protect against the inadvertent running of DBCONTROL when COLLECTOR mode is off.

Code which removed EXAMPLES/= OPALS/= .... from the workpack was required when these files were loaded to the workpack and then moved to their correct destination. The current install unwraps the files directly to their final destination, so this REMOVE is no longer required and so it is not done.

The old code had the unfortunate side effect that any customer files in these directories would be removed.

INSTALL will now correctly show the source media name in the INSTALL log after loading the keys file. Previously, the log showed the entry as '!! Source_Media'.
Further, if any files required for a TRIM Installation were missing (e.g. SYSTEM/DASDL etc) and INSTALL was running in BATCH mode, the information about the missing file entries was not being logged. This behaviour has now been fixed.

On systems running with OP MORETASKS and MAX STACKS set to a value greater than 4095, INSTALL was not using the correct internal procedures to handle the larger stack number range. This could have caused INSTALL to enter a process loop when attempting to automatically terminate some Metalogic software. This problem is now fixed.

If an error caused a batch run to switch to Verify, some files may still have been loaded. This is no longer the case.

A recent change to Install allowed the dumping of the Trim database to flat files. Since then Metalogic has recommended that this be done before every install. Since it is such an important safety measure it has now been made automatic. The database is now dumped whenever
TAPECONTROL is installed.

On the rare failure of Jobs, generated by Install to unwrap files, it was very difficult to diagnose the problem. Details of any errors are now written to the screen and the Install Log. The text of the WFL statements are written to the log. If an install aborts then the contents of the log (*OBJECT/META/INSTALL/LOG) should be sent to Metalogic with the fault report.
The Install program has been enhanced for sites who have TAPECONTROL keys but do not install it on one or more systems. If TAPECONTROL is deselected on the Custom Install screen, that information will be remembered on subsequent Installs. The config variable TL_DONTINSTALL is used to determine if TAPECONTROL will be installed. This variable can also be maintained via U META/INSTALL CONFIG.

If Install cannot link to the SLed Magus to determine the Magus Family, it will now deduce the family for the SL. This corrects a problem where the current magus was incompatible with the MCP and failed on initialisation. It was possible for a new Magus to be loaded to the wrong Family.

If the family for Metalogic code files was not the same as the family for magus, it was possible for Magus to be loaded to the wrong Family. This problem has been corrected.

Previously, INSTALL was not always unwrapping the MAGUS codefile from the release container during the installation process. This could have caused keys problems and possibly software in compatibilities.

Also, INSTALL was sending an incorrect QUIT command to DBCONTROL which caused the old MAGUS to persist after the install had completed. Both These problems are now fixed.

Adds an install parameter Boot(<product>,<product>...) for installing selected Metalogic products in Batch mode, when there is no pre-existing configuration.

The Trim Config screen now allows the TL_SILOKIND variable to be maintained.
Config variable can again be set in batch mode. The maint command is used for this.
Ex.
In a Job.
RUN OBJECT/META/INSTALL("MAINT TL_SILOKIND=UNISYS");

Would set the config variable TL_SILOKIND to UNISYS.

If the location of Magus is changed during a custom Install, the new CONFIGURATIONDATA file is now copied to the new family. Previously this copy had to be done manually.

If a File or Family name is entered which does not currently exist, a confirmation screen is displayed. Previously entering NO in such a screen did not refresh the original screen. This problem has been corrected.

During an install from CD media, INSTALL would in many cases copy the METAKEYS file to DISK. This caused the installation to abort as the software keys could not be loaded. This problem is now fixed.

Previously, INSTALL could have given a non-fatal SEG ARRAY error when retrieving the RELEASEID for the DASDL compiler during a NEWDMS run. A NEWDMS run requested via the MENU screen did not automatically compile the OPALTAPELIB library.
Also during a NEWDMS process, INSTALL was not issuing a DELINK OPALTAPELIB command to SUPERVISOR when the OPALTAPELIB library was restarted. This second problem could have led to two OPALTAPELIB libraries in the mix causing possible problems with TL attributes and TAPELABEL/TAPEDB WHENs.

The above problems are now resolved.

This change makes Install compatible with the new four digit Metalogic release ID.

When performing a NEWDMS Install it was assumed that it was not necessary to recompile OPALTAPELIB. However, if two or more level update is done, then OPALTAPELIB must be recompiled. Since there is no convenient way to tell if a two or more level update has been done, OPALTEPLIB will always be recompiled.

If when installing Flex without Supervisor or Trim, the user answered Yes to unwrap the Example files, then a sytax error would occur in the Unwrap job. The screen displaying this question had unwrap spelled as unwap. Both problems have been corrected.

This change extensd the NEWDMS command to accept SAVE or RESTORE as options.

U META/INSTALL NEWDMS SAVE Saves all of the DMS structures to flat files.

U META/INSTALL NEWDMS RESTORE Creates a blank database and populates it with the data from the previous save.

It is strongly recommended to do a U META/INSTALL NEWDMS SAVE before moving to a new version of DMS.

Version 480.13 (which was never released to the public) introduced a syntax error in the compilation of OPALTAPELIB4.

More changes to eliminate the effects of family statements, especially when running on systems with no family DISK.

Adds an extension the U META/INSTALL NEWDMS command.
U META/INSTALL NEWDMS ALL will also compile OPALTAPELIB4.

DMSUPPORT and RECONTRUCT now have their PRODUCT attribute set to METALOGIC <meta release> and RELEASEID attribute set to the release ID of the OPALTAPELIB which was current when they were compiled.

Added more data to log and fixed a problem where Trim source files could be unwrapped to the wrong family.

Fix for handling Metalogic internal testing versions.

To avoid various problems which could occur, due to the effect the the user's Family statement, Install now turns of its family statement and explicitly specifies the location of all files.

On a new install, warnings are no longer generated for default files which are not yet resident.

Logging has been extended yet again to make debugging of failed installs easier.

The flex density attribute now lists and accepts all valid density mnemonics.

In certain situations when using INSTALL to upgrade DMSII software for TRIM or creating a new database, it was possible for older DESCRIPTION file to be used by DATABASE/WFL/COMPILEDB when compiling tailored software. This caused database open errors after INSTALL had restarted the software.

Also, when the METATAPELIB4 database was being reloaded from flat files after the database had been re-intialized, INSTALL would have hung indefinitely waiting for the OPALTAPELIB library to terminate.

Both of the above problems have been fixed.

Previously, if any of the usercodes or families used in the creation of the TRIM install job were longer than 8 characters, it was possible for the generated job to fail with syntax errors. INSTALL will now generate TRIM WFL jobs which allow for 17-character usercode and family names.

Also, after compiling the OPALTAPELIB4 library, INSTALL could have failed to find the new codefile under certain circumstances. This caused INSTALL to omit the MP and SL phases. This problem is now resolved.

Install will now allow the *METALOGIC/FLEX/DEFAULTREPORTS directory to be loaded. This directory constains the code for all Flex internal reports as well the files used in the STD command.

If duplicated audits were specified with one ore more copies to tape, a syntax error would occur in the DASDL compile for TRIM database.
If a NEWDMS run was done when OBJECT/OPAL/BINDLIB or METATAPELIB/ OPALTAPELIB were not resident, the compile of METALOGIC/OPALTAPELIB4 would fail. The missing files will now be unwrapped from the container.

A security issue concerning the use of the MAILER utlity has been resolved.

Changes have been make to minimise the effect of the time taken by libraries to terminate.

Improvements have been made to Batch runs to avoid asking to screen input.

It was possible for METALOGIC/OPALTAPELI4 to be compiled on the wrong family when running the NEWDMS option.

When checking if a file name, entered for a configuration option, was valid, Install would give an error if the file existed but was open excusively by another program. Install now only checks if the file is Resident.

When using the new Install option NEWDMS, the SL of the newly compiled OPALTAPELIB was incorrect. This problem has been corrected. A practical method to use when moving to a new level of DMS would be as follows.

Before changing the DMS software (This can be done weeks before changing DMSII)

 1 Copy *system/accessroutines as (OLD)system/accessroutines                    
 2 U META/INSTALL NEWDMS                                                        
 3 On the first screen, change the field 'Usercode for Accessroutines..'        
    from * to OLD and transmit.                                                  
 4 Transmit on the next screen to start the database compile.                   
 5 You will be returned to the Main menu when the new software is               
   running.  Enter quit.
 

The Tape Library will now be using (OLD)SYSTEM/ACCESSROUTINES.

After you have installed the new DMSII software.

 1 U META/INSTALL NEWDMS                                                        
 2 On the first screen, change the field 'Usercode for Accessroutines..'        
    from OLD to * and transmit.                                                  
 3 Transmit on the next screen to start the database compile.                   
 4 You will be returned to the Main menu when the new software is               
   running.  Enter quit.
 

The Tape Library will now be using *SYSTEM/ACCESSROUTINES

Install is now valid to run on MCP 4.8.

Most install commands now include an new command: LOG. This command opens a window onto the Install Log file, allowing the user to scroll up and down the log file ,before returning to the original screen.

Hitting the SPCFY key in the action field of any screen with a Prev option will go to the previous screen.

When Installing on a system where no valid keys existed, Maillib and LogContexts were not offered for installation.

The Syntax to run Install is now:

 U META/INSTALL  ------------------------------------------------------I
                     !---- VERIFY -----------------------------------!
                     !---- BATCH ------------------------------------!
                     !---- MENU -------------------------------------!
                     !---- KEYS -------------------------------------!
                     !---- NEWKEYS ----------------------------------!
                     !---- CONFIG -----------------------------------!
                     !---- NEWDMS -----------------------------------!
                     !---- MAINT ------------------------------------!
                                 !---------- <id> ------------------!
                                   !- - - !        !- = - <value> -! 

If run with no parameter a software install is started.<

Batch performs a run where no input is requested, if any input would have been required and there is no reasonable default answer then install switches to a VERIFY run and gives an abnormal termination.

Verify simulates a Batch run, terminating abnormally if there would have been any problems.

Menu give a screen where any of the other Options may be chosen

KEYS reloads keys from the METAKEYS file. This file would normally have been provided by Metalogic.

NEWKEYS prompts the user to enter keys a supplied by fax or eMail.

CONFIG leads to a menu to allow configuration setting to be modified for any installed software.

NEWDMS allows the specification of the location of DMSII support files and the recompilation of the tape library DMSII software.

MAINT allows the maintenance of non standard (i.e. those not handled in the CONFIG menu) configuration settings. This will normally only be required at the request of Metalogic.

When Installing on a new system the user is now prompted for keys.

The Usecode ,family statement ,hostname, system type and serial number are now logged. Any parameters passed to Install are also logged.

Version 470.21 removed the code to enter a TT DELINK OPALTAPELIB command. This had a side effect when running on sites with both Trim and Flex. OPALTAPELIB4 was left linked to the Flex library which then had to be DSed by Install. This version reinstates the TT DELINK code while ensuring that multiple starts and quits of OPALTAPELIB4 are avoided

Fixed default PS_MCSNAME to PRINTSMITH/LIBRARY, comes from PS_MCSNAME not PS_SERVER, and needn't be stored. Rid lower non-zero limit for PS_MAXHOSTS. Change comment about Printlabel from SCRINFO to ACKNOWLEDGE. Don't delink OPALTAPELIB, and don't TT TP CLOSE, moot with TT QUIT QUIT QUIT and TAPEMANAGER EOJ and TAPELIBUPDATER EOT both relink to OPALTAPELIB

Previosuly, when installing an ODTCONTROL-only release, the INSTALL utility would enter the Custom screen but with no installable products available. The install could not continue from this situation. This problem is now resolved.

U META/INSTALL NEWDMS will allow the recompilation of the TRIM database when a new version of DMSII is installed.

U META/INSTALL BATCH will perform an install without asking any questions. It assumes that all config settings are the same as the last install. If any required config settings are missing the install will continue checking, switching to a verify run and then abort.

U META/INSTALL VERIFY will simulate a batch run, checking all config settings, but not loading or installing any software.

U META/INSTALL KEYS will re-install keys from the METAKEYS file.

U META/INSTALL NEWKEYS will give a formed screen to install keys supplied by email.

U META/INSTALL CONFIG will allow maintenance of config settings for all Metalogic software.

U META/INSTALL MENU will give a screen offeren a choice of all of the above options

Fixed a bug where Install would hang trying to link to Magus on a new system (i.e. Where magus had never been SLed).

Fixed a bug where Install would fault when trying to install Printsmith on a new system.

Changed the code which waits on tasks completing to kill the task if it does not terminate after two minutes.

When installing DBControl,Waitwatcher or Supervisor for the first time the user is now given the option for Install to start the programs.

When doing a Custom install the user is now given the option to keep current settings. Previously it was assumed that they would change.

The screen for entering keys from a fax or email has been changed to be able to hold keys for all products. Previously Install would fault if all metalogic products (past and future) were selected.

The Quit command is now accepted from the Newkeys screen

Setup CodeFam in RestartSoftware so that KEYS and NEWKEYS can in fact restart the software. Enhance PrintSmith and PS quit and restart, and move it to RestartSoftware. Add CachePack to RestartSoftware. Fix old key removal invalid index.

Update most PrintSmith CONFIG variable's descriptions and handling.

Several miscellaneous fixes: U META/INSTALL CONFIG, etc. infinite loop, many Config variable's default displays, allow EmptyOK for ref zero, initialize System so it's available to CONFIG

This change removes the need for spaces when setting a configuration variable. Spaces before or after the '-' and '=' are optional. Ex.

 U META/INSTALL <var>=<value>                                                   
 U META/INSTALL <var>= <value>                                                  
 U Meta/Install <var> = <value>                                                 
 U Meta/Install -<var>                                                          
 U META/INSTALL - <var>
 

Fix setting config variables. Note that there are now spaces required in the commands to delete or set a configuration variable. There must be a space before and after the "-" and the "=" in the following examples:

 U META/INSTALL SET <var> = <value>                                             
 U META/INSTALL <var> = <value>                                                 
 U META/INSTALL - <var> 
 

During a PrintSmith installation, the generated WFL job to load updated codefiles would fail with syntax errors. This problem is now fixed

The METANOTES/MAILLIB file was not being copied during a CD-only installation; this problem is now fixed. Also, INSTALL was not checking the result of compiling the OPALTAPELIB4 library; instead INSTALL would unconditionally continue. Now, INSTALL checks for the presence of an ERRORFILE and, if one is found, INSTALL will inform the user and offer to abort.

The Install program is now completely screen based.

If installing from a wrapped container, files are only loaded to a workpack if needed to compile the tailored DMSII database software for the tape library system.

Entering U META/INSTALL MENU will allow installation of new keys or maintenance of configuration options.

Most screens in the new install program have help screens accessed via <ctrl>99<xmt>. A subsequent version of install will allow HELP as a command.

If installing from a container and the current version of a file, is the same as that in the container, then the file will not be added.

When installing keys or new software, Install is now much better at quiting and restarting Metalogic software.

If you lose the state of the current screen, entering <ctrl>00<xmt>. A future release will allow the command REFRESH.

This change was to incorporate changes made to Install while this version was in development.

Screen and menu based access to config
No intermediate copy if installing from container
Batch install facility
Better close down of metalogic software on keys or software install
including better restart of software

To enable Metalogic to keep better track of the versions of software in any particualar release, an over all Metalogic Version is now used instead of the magus version as used previously.

The Metalogic Version is soted in the Product attribute of each code file and can be seen on a PD from the ODT

U META/INSTALL -TL_DMSUP
									

During both software upgrades and key installations, INSTALL always checked for the presence of the Locum CENSOR security library even if the Lcum software had never been installed or an ODTCONTROL key was unavailable. Now, INSTALL will first check that CENSOR had previously been installed by examining the Magus config variable, LOCUM_CENSOR.

More changes for PrintSmith. Tell Supervisor to delink from PRINTSUPPORT when doing PS QUIT. Set the driver copy job family to DISK = DISK ONLY. MP Intercept + TASKING. MP Intercu on the work family, not on the system family.

A diagnostic routine, inadvertently included in an earlier, which displayed mix debug information during the latter stages of an install, has now been removed. Also, a Metalogic-only problem with the overload of diagnostics software versions has been addressed

Delete PrintSmith Intercept 42.x and add 47.1

Also, changes to PrintSmith install: MP INTERCU +COMPILER, show DRIVERS copy, show which INTERCEPT copied, change DRIVERS copy failure from abort to warning, and fix syntax error in DRIVERS copy.

MCP 46.189.8633 introduced a bug where Install could loop, trying to quit and restart Supervisor, or would not not quit and restart Supervisor. This change detours that bug

>INSTALL will now automatically copy the METALOGIC/FLEX/LIBRARY codefile and re-SL the FLEXLIB function, if a Flex Inquiry or Full Flex key is updated using the KEYS or NEWKEYS function. For this reason, updating keys whilst running FAMILYMANAGER or MERGETAPE is particularly NOT recommended.

>INSTALL now supports PRINTSMITH installation on MCP 46, but support for MCP 41 is now deimplemented.

Also, for slave TRIM system installs, the appropriate OPALTAPELIB codefile, *METALOGIC/OPALTAPELIB/SLAVE, will now be loaded from the release media. Previously, the codefile was not found nor loaded.

This problem is now fixed.

>By default, during a METATAPELIB upgrade, INSTALL was generating the DMCONTROL run with a parameter of INITIALIZE OVERWRITE. Unfortunately, this parameter only works on MCP45 and above (otherwise INITIALIZE is needed), causing the database dump and load to fail.

INSTALL will now provide the appropriate parameter according to MCP version.

Previously, INSTALL would try to load the LOGREADER code and NOTES files, even if there was no TRIM software on the release media.

This problem is now fixed.

If certain configuration information was stored with leading or trailing spaces, problems could occur. In particular if the control file family for trim contained a leading space and the install was done from the tape librarian usercode with a default family of the control file family, then the newly created description file would be removed. Spaces could only be introduced to the configuration information by using a Supervisor STORE(.....,CONFIG) or via U META/INSTAll <var> = .....

This version unconditionally strips leading and trailing spaces from and configuaration information used.

INSTALL will now verify the presence of any specified wrapped container used during installation, before trying to load any files.

If the file is not a valid container, INSTALL will now abort.

The NOTL run-time option, introduced in 450.13, has now been dropped. Typically, NOTL was only being used by sites that ran with 1+1 system configurations and such sites are now marked in the SOFTWARELABEL file with a "Oneplusone" software category. Instead, should INSTALL detect the presence of the product, the user will be asked if this is a STANDBY system; if the answer is "YES" then the TRIM database and associated software will not be upgraded.

Similarly, a product called "Napconfig" will now be optionally marked for those Supervisor sites that use NAP. The NAP RUNNINGLIGHT and LIVEFILE settings plus the USE FAMILY setting for NAPLOGS will be verified.

Lastly, INSTALL will display information messages before commencing the dump of the METATAPELIB to flat files and the subsequent reload.

This problem only happened when keys were entered by hand. Keys entered from the softwarelabel file were fine.

On an install on a new system, don't ask if the files need to be loaded, and don't ask if a new database should be created.

Some more progress messages have been added when it could appear that install had frozen.

Previously, when INSTALL detected one or missing config variables, the entries written to the INSTALL log would show garbage data in the error message. This problem is now fixed; INSTALL will also now indicate a failure to retrieve a variable with a NO VARIABLE message instead of ERROR.

META/INSTALL is now capable of installing from a Wrapped container.

INSTALL was unconditionally overwriting any site-specified setting for USE FILE ... FOR REBUILD with the default value during a TRIM or Supervisor installation.

This problem is now fixed.

During TRIM installs, INSTALL was not correctly handling the setup of the TL_AUDCOPIES config item, which is used to update the DASDL with the number of Audit copies that should be dumped to tape. Previously, depending on earlier questions, INSTALL was ignoring this setting.

This problem is now fixed.

This change allows Install to process a variation in the Softwarelabel file. In previous releases the date stored in the expiration date field for each product was the earliest date of all of the keys for that product. This could cause problems when installing on a system which should have had a permanent key but where another system had a key for an expired trial. Now the date shown applies to all systems, a separate record being created for each different date.

For ODTCONTROL users, INSTALL will now detect the presence of the Locum product, CENSOR, by checking a Magus configuration variable called LOCUM_CENSOR which holds the name of the CENSOR codefile.

If CENSOR is present and is using the ODTCONTROL interface, INSTALL automatically CENSOR to temporarily delink during the install process and then re-link prior to termination, to re-establish the CENSOR and ODTCONTROL connection.

It should be stressed that the NOTL option is only applicable for Unisys 1+1 environments.

The NOTL run-time option, implemented in 450.12, was inadvertently broken by code in 450.12. When NOTL is used,INSTALL will now require the manual load of a valid METALOGIC/OPALTAPELIB4 codefile during the software COPy and SL phase, though this can be overridden by the user.

Further, INSTALL was not correctly handling situations where linkage to a later MAGUS codefile version was needed. Library calls to OPALTAPELIB to handle TRIM upgrades were not being handled correctly because, although loaded, the software keys were not yet active and OPALTAPELIB would fail a license check. Now, INSTALL will automatically delink and re-link to the new MAGUS after the keys have been installed.

New config variable TL_ACRUSER is now used to control the usercode of the DMS system software. (Accessroutines, DMRecovery, DMDataRecovery ). TL_ACRFAM is now used to hold the Family of DMRecovery and DMDataRecovey as well as Accessroutines. The new TL_AUDCOPIES is used to control whether the Audit should be copied once or twice to tape.

A new ODTS has been added to the file OPALS/TPDB.

Enter TT ENTER ODTS TPDB_SETTINGS FROM OPALS/TPDB and then TT DO TPDB_SETTINGS will display all of the TRIM related config options.

The install program will now link to OPALTAPELIB even if the User has quit all Metalogic software.

U META/INSTALL NOTL 

											
											
											
											
											
											
											
U META/INSTALL NOTL FROM META45010(CD,HOSTNAME=LIVE)

Also, all references to 'TapeControl' in the INSTALL utility have now been changed to 'TRIM'.

This problem is now fixed.

Previous attempts to use BUILDREORG have always given us problems so the new mechanism dumps the current database to flat files, creates a new database, named METATAPELIB4, and loads the dumped data into it. This means that the old database still exists and can be retained until the user is happy with the new release.

It must be noted that since the database name will have changed, any jobs used to dump the tape library database must also be changed.

A new ODTS has been added to the file OPALS/TPDB. TPDB_REVERT can be used to switch back to the old database, if any problems are encountered in the install.

DEFINE + ODTSEQUENCE TPDB_REVERT(MSG): 
 Store("DB",Getstr("TL_TAPEDB",Config));   
 Store("DB",SPLIT("DB","METATAPELIB4") & "METATAPELIB" & GETSTR("DB"));
 Store("TL_TAPEDB",GetStr("DB"),Config);   
 Show("Database reset to ",GetStr("DB"));  
 Store("DM",Getstr("TL_DMSUP",Config));
 Store("DM",SPLIT("DM","METATAPELIB4") & "METATAPELIB" & GETSTR("DM"));
 Store("TL_DMSUP",GetStr("DM"),Config);
 Show("DMSupport reset to ",GetStr("DM")); 
 Store("OTL",SLFILETITLE("OPALTAPELIB"));  
 Store("OTL",SPLIT("OTL","OPALTAPELIB4") & "OPALTAPELIB" 
  & GETSTR("OTL"));   
 IF "METALOGIC" ISIN SLFILETITLE("TAPEMANAGER") THEN 
  ODT("SEND TM QUIT"); 
  ODT("TT TP CLOSE");  
  ODT("TT DELINK OPALTAPELIB");  
  ODT("SL OPALTAPELIB = ",GetStr("OTL"));   
  Show("SL OPALTAPELIB reset to ",GetStr("OTL"));  
 IF "METALOGIC" ISIN SLFILETITLE("TAPEMANAGER") THEN 
  ODT("SEND TM START");

Also, the various DCKEYINs done by INSTALL to perform SL's and MP attributes of the new release codefiles will now be shown on the installers' station. The command will be prefixed by "ODT:" and any generated response will be prefixed by "Msg:". As usual, both sets of messages will appear in the INSTALL log file.