Magus Software Changes

This change supports the Opal PD attribute SUBKINDLIST as described in OPAL DNote 540.42.

Support for Job Restart.

Improve error messages and handle faults more gracefully.

Fixes an early termination during expands, and a length error in some disk farm gzips.

GZip and MZip improvements.

The Meta_Zip request can now ask for character translation. The translation is done before compression to ASCII or after expansion to EBCDIC. When using GZip or ZLib, this will often slightly speed up the compression and improve the final size. Typically for a symbol file the file size will drop 2-3%.

A GZip expansion problem from the last change has been corrected.

This addresses problems with small file compression.

Output files for GZip or ZLib compressions are now EXTMODE=OCTETSTRING.

This change adds an entry to the hash table for long matches under high compression.

Some experiments in back links with 3 byte matches has resulted in improvements in CPU time and final sizes for GZip/ZLIb compression.

A FileLength attribute error has been removed.

If the zipped output goes to a file, the original file size in bytes is put into the ReleaseId attribute in EBCDIC decimal.

The ZLib Adler check sum is now correctly inserted.

Size errors are no longer provoked in SystemStatus on MCP 53.

The first call of the progress procedure is now passed the negative of the expanded file size on its first call.

The No Deflate call, originally used in debugging the implementation, has been deimplemented.

If an inflate call has output to file, but the input file was default tarred, Meta_Zip will now change the output to default tar.

A clearer explicit error message is now given if a file is requested input and its is not byte stream.

Output FileKind is now DCPSYMBOL for compressed data, and if output is not via the Tar procedure, the expanded file is CDATA. Meta_Zip now checks for input/output file availability and array size. Error messages are now returned in the output array. If an output procedure is supplied and output is requested to file or Tar, the procedure is called as a progress report. The first call is at 0, and the RDLenF result gives the number of MB before the next call, with a minimum of 1 MB.

Meta_Zip high compression is now more effective, but costs more CPU and memory, by using a second level hash table, smaller than the top one.

If output requests a file, but the input is from a default tar, Magus will now force output via the default tar procedure.

Static Hufmann Inflate/Deflate now available in Meta_Zip.

MAGUS now supports both ASAP and SITE log file logging,

Internal change to remove PRINTSMITH support and enable ASAP licensing.

GetSubKindList can detect MZIPed files.

Internal Metalogic change.

New PRIVILEGEDPROGRAM procedure.

A new Magus entry point, Meta_Zip, implements a lossless compression method, which compresses and expands quickly on the MCP systems architecture.

The compression is based on the back-link deflation algorithm, but uses byte-based links. The compressed file format has a header, 4"BA570xxx", where x are option bits. After the header are a sequence of characters or control codes. The control codes are bytes starting 4"1" or 4"B". All other bytes are just literals from the original source file. 4"B" codes are 3-byte back-links, 4"10"-4"1EE" are 2-byte back-links, 4"1EE" is a code to identify characters that would be interpreted as links. 4"1F0" to 4"1FC" are 2-byte back links for 3 byte matches, and 4"1FC1"-4"1FF" are 4-byte back links. Back links can be up to 32 kb away and match for up to 163 characters, for a theoretical maximum compression ration of 40:1. Symbol files typically compress 4:1.

The following Algol defines show the big-endian link format:

         MZBLLenF   = [43:5] #, % 0-3 = 32-35
         MZBLLen(Bt)= ((Bt).[43:5] & Real((Bt).[43:3] =0) [5:1])#,
         MZBLDispF  = [38:15]#, % 0-32766
         MZ2BLenF   = [35:4] #, % 0-3 = 16-19
         MZ2BLen(Bt)= ((Bt).[35:4] & Real((Bt).[35:2] =0) [4:1])#,
         MZ2BDispF  = [43:8] #, % 0-237
         MZCharV    = 238#,     % 4"(1)ED" +1
         MZCBHxd1F  = [36:1]#,
         MZCHxd2F   = [35:4]#,
         MZ23DispF  = [39:8]#,
         MZ4BV      = 192#,     % 4"(1F)BF" +1
         MZ4BLenF   = [37:7]#,  % 0-127 = 36-163
         MZ4BDisPF  = [30:15]#; % 0-32766

Meta_Zip can compress or expand arrays, files, or data from thunks. In compression, it uses 3 memory sizes as requested in its parameter. Small, means use the least memory feasible, typically less than 200kW. Medium means do not exceed c. 1.2 MW. Big means use as much as is useful, which could be up to 17MW. If this parameter is set to Default, Meta-Zip chooses which model to use based on the current CU values. More memory will normally mean better compression and faster execution.

Another request field is set for higher compression. Typically this can improve compression by 5% for 12% more CPU time.

The MD5 algorithm, described by DNote 540.02, has been improved and now runs with a typical 20% saving in CPU overhead for each message digest.

Previously, any LOG command issued with a time range selection that gave a start point beyond the beginning of the initial log file would return multiple 'GETSTATUS harder #nn' entries in the response. This problem has been fixed: MAGUS will now just return the single message 'No log files found'.

This change supports the implementation of the MD5 message digest algorithm which is also available in the Unisys SDK. The Metalogic entrypoint, MD5P, is used to support MAILLIB's CRAM-MD5 SMTP authentication, as described in MAILLIB DNote 540.03.

Mark Magus as valid for MCP 54.

PDSUBKINDLIST will now recognize a PDF file.

This corrects 2 cases where the :FIND target was found after EOF.

Literal :FIND in Flex Inq. will no longer find things after the EOF.

Note that it could still find things in bad blocking holes.

Previously, RESERVEDISK requests issued by JAMPACK would have failed with the error 'SEGMENT ADDR GREATER THAN MAXIMUM DISK ADDRESS' under the following circumstances:

 1. The target disk unit was formatted as VSS-2.
 2. The target disk had a capacity in sectors that was an odd-numbered
    value.
 3. The requested end sector address generated by the RESERVE exactly
    matched the capacity of the drive.

This occurred for VSS-2 disk RESERVE requests because the MCP requires that the capacity of the disk must be allocated on 2-sector boundaries and the last sector of an odd-numbered capacity is discarded.

JAMPACK will now detect whether a disk is VSS-2 and will not include the last sector in RESERVE operations.

The Metalogic logging system, by default, uses the DL LOG family to store its own log files though this location, held in the SYS_LOGFAMILY configuration variable, can be changed by the INSTALL utility. If this family is subsequently removed from the system or the CONFIGURATIONDATA file is moved to a new system where the SYS_LOGFAMILY family does not exist, any Metalogic software using logging would halt on a REQUIRES FAMILY waiting entry.

In such circumstances, MAGUS will now detect that the family is unavailable and will revert to the current DL LOG family, updating SYS_LOGFAMILY at the same time, since this must be present. Several informational displays will be generated.

Previously, any Metalogic log record longer than 990 characters was truncated. This behaviour has been changed; although only 15 records are still written to the log then, for longer log entries, the first 500 and the last 500 characters are combined into one log entry. The two components are connected by the character string '..'.

LOG commands that use 'HHMM FOR N MINS' will now only scan the relevant log file for N minutes instead of N+1 minutes.

The generic LOG command, used by MAILLIB, TRIM and SUPERVISOR, will now again correctly handle the '+ <num lines>' variant. Previously, the requested number of lines was ignored.

Also, the FIND modifier will now optionally accept quoted targets, allowing targets with embedded spaces to be specified. Either single or double quotes may be used. This change allows simpler checking of '+ <num lines>' modifiers to be appended. For example:

  LOG FIND "TEST STRING" +40
  LOG ODT FIND 'Test command'
  LOG FIND TEST +100

A FIND target cannot be longer than 72 characters.

On later releases of MCP 52.1 and 53.1 ICs, the Metalogic RESTRICT command mechanism caused all operator commands issued from SUPERVISOR sources associated with the ODTSECURITRY usercode to fail with the error 'INVALID SESSION NUMBER NNNN'(where NNNNN is SUPERVISOR's mix number).

These sources include:

 - SUPERVISOR window with a TERM USER logged-in to the ODTSECURITY user
 - Any commands issued from an active WHEN or DO running with a FOR
   modifier set to the ODTSECURITY usercode

This problem is now fixed. Note that only SUPERVISOR installations with a valid ODTCONTROL key may use the RESTRICT implementation.

The change applied by DNote 530.18 could, under certain circumstances, have caused any time-filtered LOG command to enter a processor loop. This problem has been resolved.

Using date and time filters with the LOG command to search Metalogic log files is now performed significantly faster than earlier releases. MAGUS uses specific user-defined disk attributes in each file to provide information about the date and time range of the log; this allows MAGUS to rapidly identify the starting log.

The maximum total number of log reads for any filtered search has been increased from 15,000 to 20,000 records.

This changes supports the new SUPERVISOR METALOG context described in SUPERVISOR DNote 531.21. The maximum number of lines occupied by a Metalogic log entry has been increased from 9 lines to 15; other enhancements log record handling s will be forthcoming.

This change supports the LIBRARYMIXLIST attribute in the new SL context recently implemented by Supervisor change 531.20.

Adds support for caseless finds, whole word finds, restricting finds to text fields, and respecting EOF.

Up to 30% less CPU used for small files and case less finds.

Several low probability bugs have been found and fixed.

Error messages generated when using the Flex Find option have been improved.

Implements FOUNDINFILE Entry point.

On MCP release 53.189.8271 (53.1 IC 40 or later) or 52.189.8786 (52.1 IC 152 or later), MAGUS will display the following warning message:

   INVISIBLE WAITS: ZOTMESSAGE

This problem, which would cause the waiting entry messages generated by JAMPACK during RESERVEs to be deactivated, has now been resolved.

MCPCopy interface for ML_LibMaint.

A CheckerBoard list problem which was likelier with small ranges is now fixed.

Non-open JOBCODE files were sometimes missed. This fix corrects some causes, but there are still indications that others exist.

JamIt Map and ChkBd requests can now be done while RES is running.

The lower rows of open JOBCODE files are now more reliably identified.

Due to fixes for some low probability glitches, JamPack now takes a little more CPU time, but a new optimization has significantly reduced elapsed time.

JamIt now handles larger file map requests, and has a retry bit if it ran over 2**20 row words. It still does not handle more than 6 MB of titles.

If a bad title is detected it returns a title of ">> Bad Title <<".

Previously, any logging command would have generated garbled screen output if any of the presented lines had embedded graphics characters such as 48"0C" (HOME). This behaviour has been corrected.

The JamIt entry point now support the CheckerBoard request in JamPack.

The analysis of the areas now takes account of some small changes that have come about in the last few MCP releases, making the JamPack more effective.

The patch also fixes some low probability errors in handling FILEKIND JOBDESCFILE and large segmented headers.

If a pattern greater than 255 characters was specified with any logging FIND command, the calling process would fault with a STRING PROTECT at 28150650. This problem has been fixed.

The FIND command has been modified to allow dates to be specified without the requirement for a year component; if not present, the current year will be used.

Internal change.

Source code changes to use new INCLUDE/META

Various formatting modifications to the Metalogic logging mechanism have been applied presenting heading information more clearly. The keywords BACK and FOR have been implemented to provide an easier way to assign date and time ranges for the log search caller. Please see SUPERVISOR DNote 521.41 for more details.

This facility applies to all LOG commands for MAIL, TP and the forthcoming SUPERVISOR LOG command interface.

This change provides initial support for MCP 53.1 which is currently only available as a Field Test version. In particular, a problem on MCP 53.1 emerged where the SUPERVISOR RESTRICT command was incorrectly restricting the wrong ODT command has now been fixed.

Adds a support function (AnnulFile) to FIND:-TOUCH in Flex Inquiry

Add symbolic types to PDSubKindList.

Internal Change.

Previously, attempts to run DBCONTROL when its licence key was missing or had expired were permitted to allow restoration of DMSII database parameters that had been altered from earlier runs. Unfortunately, this mechanism did not work correctly if there was no valid Supervisor or TRIM key present, causing each DBCONTROL restore run to repeatedly fail with an INVALID OPERATOR @ 57560000 fault. This problem is now fixed, no Metalogic licence keys need to be present for restores to take place.

Any simple LOG command will now only return a single screen response for all variants; previously, LOG would unconditionally return up to 500 lines of output. The original behaviour can be restored by using the '+' within the command text. The '+' modifier will also accept an optional line count value to allow the user to specify the number of response lines.

The change described by DNote 520.21 for logging control caused the release of full MAILLIB or TRIM log files to be mishandled. When a full log was detected, MAGUS would fail to both release the current log and open a new file. Further, warning messages would be written to the open log each time subsequent log entries were created. The problem, which could be detoured by a manual LC CLOSE command, has now been fixed.

When the system-wide option SYS_USDATES is set to TRUE, all dates in Metalogic LOG files will now be written in MM/DD/YYY format. Previously, any log time/date headers would have always been presented in DD/MM/YYYY format.

On 5.2 MCP LMGuts creates instack arrays and only deallocates them at the end of the procedure. If CopyWrite was DSED while calling NFTCopy which calls LMGuts, those arrays were not deallocated and a FORGETCHECK Dump resulted. Now, the call of NFTCopy is protected from being DSED.

The logging facilities currently used by MAILLIB and TRIM will now automatically handle log writes that hit a SECTORS REQUIRED condition. Previously, this would cause the caller to wait indefinitely until the problem was resolved.

Now, if a log write fails because of disk space problems, the caller will issue a waiting entry e.g. 'FILE MAILLIB LOG: INSUFFICIENT SPACE ON LOGFAM' but will continue processing normally. Any messages that cannot be written in these circumstances will be discarded until the problem has been resolved.

By default, records from the *current* log only are now returned to the caller instead of a maximum of 500 records from multiple log files. This behaviour can be overridden by using the '+' modifier in any LOG command. Please refer to the on-line LOG command help for the relevant software from more information.

Recognize a TAR without trailing zero blocks. Recognize PNG, JPEG and GIF files for PDSUBKINDLIST.

A very rare MCP READLOCKTIMEOUT fault could have occurred while DBCONTROL was executing MAGUS code to search for a specific database DMSUPPORT library. This problem is now fixed.

The PDSUBKINDLIST will now check for embedded file systems irrespective of the FILEKIND attribute.

Implementation for PDSUBKINDLIST.

Version 520.10 introduced a bug when installing keys on a system with an alternate config family specified. The keys would work until the config was switched back to the default family. At this time all keys would fail. This porblem has been corrected.

In some very rare circumstances a corrupt record in the configurationdata file could cause subsequent keys or variables to be ignored. This change protects against such corrupted records.

The code which could cause this particular corruption has also been corrected.

This change supports the new Supervior PD context.

Previously, the date and time entries in all Metalogic software LOG files would have multiple null characters embedded in the text record. This caused some emulators and programs such as the Unisys EDITOR to show the files as corrupted. This problem is now fixed.

SUPERVISOR's SHOW PERM command, implemented by MAGUS DNOte 520.11, will now correctly report permanent variables whose identifiers are longer than 17 characters.

This change supports the new TRIM log file implementation described in TAPELIBUPDATER DNote 520.05 and the SHOW PERM command available in SUPERVISOR (see DNote 520.83).

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.

Metalogic applications using the logging factilities in MAGUS will now automatically close the appropriate LOG file when the application is terminated. Previously, each LOG file would remain open while the MAGUS library was active.

Previously, on 5.2 DMSII systems, it was possible for SUPERVISOR's DBSHANDLER task to hang on a NO FILE condition on a database CONTROL file when handling a DBS function call or a VDBS context request. This occurred because the CONTROL file family was incorrectly returned to SUPERVISOR by MAGUS when providing the necessary information to allow linkage to the database. This problem is now fixed.

The change described by DNote 520.06 has been modified to increase the number of records returned by any LOG command to 10,000 (instead of 500) but *only* if a date and time range has been assigned to the command. If a LOG command is given with a very wide time range, perhaps covering many MAILLIB logs, the report generation may take some time because of this high limit.

The MAILLIB LOG FIND command could have caused the caller (e.g. SUPERVISOR) to hang indefinitely after aulting with SEG ARRAY ERROR when handling a very long message entry from the MAILLIB log file. This was caused by incorrect recovery action after the fault was detected and is now resolved.

For any MAIL LOG command, only 500 records satisfying the selection criteria will be returned to the caller. Currently, the LOG command will not process more than 15,000 records in total from any MAILLIB logs; so using date/time ranges and wild-card text searching should be used for older log entries.

This change implements a system-wide logging mechanism for various Metalogic software, initially MAILLIB followed by SUPERVISOR, TRIM and FLEX. A standard MAGUS interface is used to log commands, errors and information messages into log data files. The interface provides a command set allowing log searches by date/time range, wild-card text or category.

At this time, only MAILLIB logging is available but other software referred to above will be incorporated at a later date.

The change described by DNote 520.02 has been temporaily backed out until certain incompatibilities with Epsilon systems have been resolved.

Technical Detail

A new exported procedure, HasArchive, returns TRUE is the unit param has an active SYSTEM/ARCHIVE.

All code to support MCP 44.1 and before has been removed.

A timing hole when ODTControl was active could cause the MCP to complain about orphan code. This should no longer be possible.

On DMSII 52.1, an additional process called <DBNAME>/ACRLIBRARY will be associated with the usual database stack. This process is now responsible for handling the opening and closing of database DBDATA files and NOT the main database stack, as before.

This change caused SUPERVISOR's OPAL DBS function and VDBS context programs to fail because the MAGUS would not be able to find the databases CONTROL file family and therefore be unable to link to the database. In the case of the DBS function, the error message 'UNABLE TO FIND CONTROL FILE INFO' would have been returned.

This problem has been addressed; the MAGUS entrypoint handling Visible database requests will now check if the ACRLIBRARY process is present as well as the DMSUPPORT library.

DBCONTROL will now recognise and support very large database memory integrals, in its ALLOWEDCORE tuning and statistics reporting, beyond its previous limit of 268,435,455 (2**28-1). Typically, these values have a maximum value of max integer (2**38-1); however, it should be noted that DBCONTROL can only show a maximum of 12-digit values in the statistics monitor windows.

With this change, it is now not possible to run earlier versions of DBCONTROL against this version of MAGUS; any attempt to do so will cause the calling DBCONTROL subtask to terminate with the error:

  DBC/SETUP:MAGUS AND DBCONTROL ARE INCOMPATIBLE

In early versions of MCP 4.9 the system type returned for CS520 systems could have a random character at the end. This would cause metalogic keys to fail. The change detours the MCP bug.

This changes fixes a fault in RSVP checking code that was erroneously being used by DBCONTROL in one specific operational situation where multiple waiting entries were active. This was seen as multiple DBCONTROL messages:

DBCONTROL: FAULTED IN GETSTATUS RSVP HANDLING

The faulting procedure has been fixed and its incorrect usage has been addressed by DBCONTROL change 510.06.

This change allows SUPERVISOR access to database stacks that are undergoing database reorganisations, enabling the SUPERVISOR Opal functions DBS and VDBS to be correctly handled. Previously, attempts to access databases during reorganisation would have failed with 'UNABLE TO LINK TO DMSUPPORT'.

This change supports the implementation of the Metalogic MAILLIB library as a standalone product without the previous constraint that SUPERVISOR should be installed.

In some versions of 4.9 MCP system types shorter that 6 characters (CS520) were null filled. This would invalidate key checking. This version of magus converts such badly formed system types to valid ones.

This change us to support DBControl using real, instead of integer, values for system and database overlay rates.

Add ConvertDiskFileHeader to convert Version 2 and older Headers, which the MCP ConvertHeader function does not handle.

When interrogating Perm or Config variables it was possible for there to be old data beyond the end of file marker. If no other entry existed for a particular variable the old value was returned.

Ex. After $S.Perm:="X" $S.Perm would correctly return "X" but
    After $S.perm:=Empty $S.Perm could in some cases return an invalid
    value.

This changes updates MAGUS to confirm MCP 5.1 (10.0) compatibility. The SUPERVISOR OPAL attribute INUSESTACKS will now work correctly on this MCP and later.

Internal change.

Previously, JAMPACK did not check to see if RESERVEDDISK or SQUASH was already running in parallel against the same disk family. In such cases, it was possible for JAMPACK to fault with DIVIDE BY ZERO at 34038000 when processing the directory whilst a RESERVE was in progress or for JAMPACKs own RESERVE calls to fail with SYNTAX with an ALREADY RUNNING error generated by MCP.

Now, prior to processing a disk directory, JAMPACK will detect if a SQUASH or RESERVE is already active on the family and JAMPACK will gracefully terminate with the error message:

JAMPACK: RESERVE OR SQUASH IS ALREADY RUNNING ON <FAMILYNAME>

It should be noted that it is always undesirable for an ODT SQUASH or RESERVE command to be issued whilst JAMPACK is processing the same family.

Version 500.06 introduced a bug which could cause DBControl to fault if a task linked to a database has a stack number of 137.

This change supports DL JOB family determination, as described in Supervisor Dnote 500.49.

Internal Metalogic change supporting the new FI attributes discussed in SUPERVISOR Dnote 500.45.

TThis change support the changes made in META/INSTALL version 500.07

This change supports the new SUPERVISOR attributes INUSESTACKS and MAXACTUALSTACKS, as described in OPAL/GSTABLEGEN DNote 500.17.

When more than 9 sets of keys have accumulated in the Configurationdata file, the Install program offers an option to remove some. This process could corrupt the config file if a permanent variable had been stored where the length of the variable name plus the length of the data stored was 76 or 77 characters plus any multiple of 80. i.e. 76,77,156,157 etc.

The contents of the config file after such a variable would have been deleted.

This problem has been corrected.

CopyWrite logs Volume Directory Add records when sending a Tape Label Notice, for Tape Library recovery by LogReader.

Updates Magus to confirm MCP 5.0 compatibility

A CONFIGURATIONDATA file with a large number of permanent variables caused a RESIZE fault during MAGUS initialization.

A WFL Copy statement which has TARGET > 0 Label Equated is sent to CopyWrite.

This patch supports the implementation of the Flex attribute CONTAINER as discussed in OPAL Dnote 490.08.

Some debug code was left in the patch for 490.02. This code has been removed.

From MCP 49.1 CS7801 system are reported as CS180. This magus change will allow all users on CS7801 systems to move to MCP 49 without needing to get new keys.

JAMPACK has now been updated for MCP 49.1 to relax the warning messages seen on earlier MCP versions.

Support for Starting Jobs.

This patch addresses a problem using the fast DMSUPPORT handling introduced in 480.22, specifically in locating database CONTROL files.

This problem, which would have caused the Opal DBS function to fail in certain circumstances, has been fixed.

This patch supports a new mechanism of fast searching for active DMSUPPORT libraries to be used by DBCONTROL and the new Opal DBS function.

Previously, DBCONTROL may have given dumps by FAULTED IN GETSTATUS RSVP HANDLING during its checks on WORDS REQUIRED waiting entries. This behaviour, which occurred during memory shortages or jobs being scheduled by the MCP, has now been fixed.

Previously, from a SUPERVISOR OPAL program, if an integer larger than the current system mix limit (as set by the MAX MIXNUMBER operator command) was passed to the TASK or TASKSTR reference attribute, the OPAL would fault with an INVALID INDEX. The MAGUS entrypoints used by SUPERVISOR for this type of call are now protected.

Magus could occasionally fault when a storing a large (>10000 characters) string into a permanent variable. This problem has been corrected.

Previously, during DBCONTROL termination, DBCONTROL was not correctly restoring BUFFERS settings for databases that had system buffers specified greater than 256. Since the current limit is 262142 on MCP 48.1, this behaviour has been fixed and DBCONTROL will now restore all original BUFFER settings.

Support for CopyWrite to retrieve a Disk File Header.

Avoid an Attribute Error on IPADDRESS and DOMAINNAME during an FTP when CopyWrite is installed.

Version 480.14 introduced a bug which could cause jampack to fault with an 'invalid index' on some families. This fault has been corrected.

The change described in Dnote 480.10 causes JAMPACK to fail with the error UNREADABLE SYSDIR - CHECK ACCIDENTAL 'MA' if the pack family SYSTEMDIRECTORY had been created prior to MCP 46.1. Typically, such directory files had AREASIZE (row size) of 600 instead of the current settings of 2000 or 4000. The above error message has also been changed to better explain the reason for the JAMPACK abort. This problem is now fixed.

On certain larger Unisys systems e.g. NX6830s, it has been possible since MCP 47.1 to change the MAX STACKS system setting up to 32767 from the default 4095. Although Metalogic software support the MAX MIX an MAX SESSION implementations, this maximum stack number increase was not handled correctly.

Any increase in MAX STACKS beyond 4095 caused random faults to occur during Magus initialization routines (manifested as INAVLID OP) or, if the Magus library did start ok, then Supervisor was also prone to various INVALID OP faults. For example, Supervisor would fault executing a OPAL DISPLAY statement in a MX_based context; this case could also have led to a non-fatal MCP dump by BAD PCL GET/GIVE lock.

These problems are now resolved.

On MCP 47.1 IC 97, MAGUS dies with the following error:

MAGUS: FATAL MCP INCOMPATIBILITY:COMPILERINFO

This problem was caused by unexpected changes to an internal array in the MCP and has now been detoured.

This patch fixes a problem where MAGUS would enter a CPU loop during initialization code on MCP level 481.42 IC. It is believed that, at this time, only 48.1 MCP codefiles are affected.

This change supports Jampack when running on VSS2 packs. Previously warnings might be displayed when running on VSS packs.

Two bugs relating to running on the DL JOBDESC family have been fixed. If running on a system with mixnumbers > 9999 it was possible to ignore some inuse jobdesc rows, Occasionally a short block warning was incorrectly displayed.

If the linkage to the CopyWrite Library fails and the COPY statement has OPTIONS=DEBUG set, then the result of the LINKLIBRARY function is displayed

Due to 4.8 changes in WFLSUPPORT, MAGUS now checks a WFL statement for a HostName of LOCAL, no matter what the protocol, and if found the statement is passed to CopyWrite.

The NFTCOPY and DISPATCHED_LIBMAINT MCP procedures are now linked through MCPSUPPORT. These procedures are passed to CopyWrite via a jacket procedure which determines whether the call is a local or remote file transfer.

The release of MCP release 48.1A9 caused several problems with Metalogic software. First, any Supervisor TT HO command or certain Flex :FLAT directory searches could cause a non-fatal dump by INVALID UNIT. Both programs would fault with INVALID OP.

Also, on the same MCP release, MAGUS would display the message JAMPACK RESOURCE UNAVAILABLE: STACKSTATUS. This would have affected JAMPACK's ability to suppress job summaries after DS-ing any RESERVEDISKs.

Both of these problems are now resolved.

Check if an archive is marked as bad before calling OpenArchive.

If the SUPERVISOR HO command was issued with a family index e.g. TT HO DEV #2, then the Magus entrypoint used for this call would erroneously return many files which had rows on that family index that were not necessarily open. This problem is now resolved.

On new systems where a Magus Configurationdata file with no valid licence keys but the config variable LOCUM_CENSOR was present, INSTALL would fail with INVALID INDEX during a KEYS or normal install run. This problem is now fixed.

The Magus library performs some housekeeping code when the Library is thawed. On MCP 46 and later the time between Magus being thawed and the housekeeping code being executed, has increased significantly. It usually takes as least thirty seconds. The housekeeping procedures have been exported to allow the Install program to speed up this

On certain MCP levels at sites where ODTCONTROL and Locum's CENSOR product were installed, MAGUS could fail to determine the CANDE MCS number if CENSOR-ODTCONTROL linkage was activated during system startup by an AI program. It is believed that by the time MAGUS checked for CANDE's MCS number, the MCP's internal MCS tables were not established.

This behaviour caused a recurrence of the problems described in Dnote 460.16. Now, MAGUS will only determine if the CANDE MCS number exists once a command from a valid MCS is processed.

This change extends magus to be able to run on MCP 4.8. It accommodates changes in the MCP Jobdatavector, MCP Bindinfo and Flat directory structure

On fast systems running the Locum CENSOR product and ODTCONTROL, it was possible for MAGUS to terminate prematurely before CENSOR had linked correctly. Now, MAGUS will ensure that the LINKER task remains active and linked while CENSOR is active

A CopyWrite COPY&CATALOG or COPY&BACKUP failed if Flex keys were not installed. CopyWrite provides Tape Library information to Supervisor for COPY&BACKUP and remote COPY&CATALOG

Create a volume Archive if not present, for CopyWrite COPY&CATALOG to Disk Farms.

This patch provides implementation support for the new Metalogic Mail Library product, MAILLIB

Compilation option for COPYWRITE on systems earlier than 4.6

The message logging interface implemented in 470.03 was only operating correctly on systems with a valid ODTCONTROL license key. This restriction has now been lifted

Allow PrintSmith to once again declare itself an MCS.

Code to protect against simultaneous access to MAGUS-CENSOR entrypoints was accidentally deleted in earlier changes to support CENSOR on MCP 47.1.

This problem has been corrected.

Previously, it was possible for MAGUS to generate an internal SECURITY ERROR failure when Locum's CENSOR library attempted to use Metalogic's ODTCONTROL interface.

This problem, which was introduced by patch 470.02, occurred on systems where ODTCONTROL was the only installed Metalogic product.

The MAGUS library now supports an entrypoint, available to Metalogic software, which permits the logging of display messages to the SUMLOG without generating an output message to the system. It is anticipated that Supervisor, TRIM and the new MAIL library will use this interface.

This patch allows MAGUS to properly support ODTCONTROL/CENSOR environments on MCP 47.1.

This version is required if running on MCPs 4.7 or later. Versions of Flex/Library, Supervisor and DBControl less than 470.01 are not compatible with this Magus.

In an ODTCONTROL-CENSOR environment, if mix commands such as AX, HI, ST or DS were not automatically enabled by CENSOR for all users, then any such commands originating from a CANDE station would be restricted. This meant that such CANDE users would be unable to interact with their own jobs and tasks.

This problem has now been resolved.

The MCP function BURN_CDR and access to CDR file attributes are now provided to CopyWrite, which will attempt to burn a CD image when CDCOPIES is greater than zero.

MAGUS access to some of the CopyWrite entrypoints is restricted to the CopyWrite service. CopyWrite is now marked as a service by MP +SERVICE COPYWRITE.

When a new version of MAGUS was installed, and a CopyWrite COPY job had been initiated by the previous MAGUS, a dump by BAD ASD could occur. The old MAGUS will now remain in the mix until all CopyWrite COPY jobs have been completed. The CopyWrite utility command STATUS reports the number of active CopyWrite jobs.

Previously, JAMPACK would not correctly search Unisys VSS2 disk packs because the SYSTEMDIRECTORY file has different blocking specifications on these families.

This problem, which caused JAMPACK to fail, is now fixed.

MAGUS now correctly supports licence keys on Unisys LX100 systems.

MAGUS now supports the Unisys MORETASKS implementation allowing the provision of mixnumbers up to 65535. This is achieved by setting the system options MORETASKS (OP+MORETASKS), halt-loading and changing the MAX command. In particular, MAGUS supports this implementation in both SUPERVISOR and DBCONTROL.

Prevent memory dump due to the addition in 4.6 of an IOCW parameter to WAITIO, which is used when reading a hybrid CD partition from a mounted CD.

Add support for the COPYWRITE Native File Transfer feature. On the originating host, MAGUS checks the COPYWRITEPROTOCOL configuration variable to determine whether to intercept a COPY, and calls COPYWRITE. On the destination host, MAGUS provides an environment for COPYWRITE.

A problem where MAGUS could display a BAD DATE warning during key validation at initialization time has been fixed. This only occurred if MAGUS was forced to restart on more than once on the same day and did not affect customers with permanent licences.

MAGUS will now correctly write LOG SETSTATUS entries into the SUMLOG on 4.6 MCP when ODTCONTROL restricted commands are rejected. This allows Supervisor OPERATOR context WHENs to track or filter the usage of such restricted commands

Earlier versions of Magus were incompatible with the 45 versions of MCP from IC 45.1A.188. Jampack would fail with an invalid operator and sometimes cause a FileHandler memory dump.

On systems where only ODTCONTROL was installed, it was possible for MAGUS to terminate prematurely during a CENSOR installation because of a timing window.

This problem is now fixed; the MAGUS/LINKER task will remain active during an installation of CENSOR.

Previously, it was possible for MAGUS to fault when returning security information to the CENSOR library.

This problem is now fixed.

JAMPACK can now handle pack units with up to 2**32 segments, which is the SSR 45.1 MCP limit. The memory usage of JAMPACK will be somewhat larger due to this change, but the CPU consumption should normally be slightly less.

Some problems with JAMPACK running on SSR 46.1 have been fixed and the MAGUS Version message will now correctly give the compiling system serial number. Some code to avoid bugs in MCP 3.9.0 has been dropped. MAGUS is once again less than 10000 cards.

This patch applies some minor enhancements to the ODTCONTROL-CENSOR interface which have been made to improve operability.

If METALOGIC software was being installed for the first time i.e. no CONFIGURATIONDATA file was present, MAGUS would display a series of uninformative and confusing messages when first linked by INSTALL. Further, INSTALL would not be informed that the CONFIG file was not present which would change the behaviour of the first installation.

These problems have been fixed.

This patch resolves several problems with the Flex suite and Jampack products when run on 46.143 Field Test MCP.

These problems have now been fixed.

The MAGUS library now has optional support for Locum's CENSOR product, allowing CENSOR much greater range of control of ODT commands from MARC, ODTs and DCKEYIN programs. Previously, CENSOR would only handle command validation from MARC.

The site must have valid software licence keys for both CENSOR and ODTCONTROL. Locum's SIMPLEINSTALL utility will control whether MAGUS will be activated to provide the additional security. Once active, both SIMPLEINSTALL and Metalogic's own INSTALL utility will automatically handle new software installations.

If SUPERVISOR is also running on the system, once CENSOR security has been triggered, SUPERVISOR's normal RESTRICT mechanism will be disabled until CENSOR support is subsequently deactivated. So, during upgrades or unavailability of CENSOR, SUPERVISOR's own RESTRICT mechanism can be used as backup control.

With regard to ODTCONTROL-only support, MAGUS will now allow commands that have been input from DCKEYIN or SETSTATUS programs and MARC sessions that are active under the ODTSECURITY usercode (as defined by SUPERVISOR's TT USE USER... FOR ODTSECURITY). Previously, only commands issued from SUPERVISOR COMS Windows sessions, with TERM USER set to the ODTSECURITY usercode, would have this capability.

Please contact either Locum or Metalogic for more information.

ODTCONTROL can now correctly RESTRICT the commands COMPILERTARGET, DO and SECOPT.

ODTCONTROL can now RESTRICT the 45.1 ODT commands FAMA & SHARE.

This patch supports significant changes to the Metalogic COPYWRITE product; no other products are affected.

On 432 MCP the Supervisor ODTSECURITY Usercode would not allow input of 'Restricted' commands.

This has now been corrected.